[Touch-packages] [Bug 1995173] Re: Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue

2022-10-29 Thread Yosua Liu
** Description changed:

  The device is Lenovo Legion 7. This laptop has a mux switch to switch
  between dynamic/hybrid or discrete graphics mode. This laptop has a high
  resolution with high pixel density than the other displays out there,
  but I don't know the exact number. Additionally, this laptop can adjust
  the display refresh rate between 60 and 165 Hz.
  
  ---
  
  There were 1 problem I encountered in dynamic/hybrid graphics mode:
  
  - The widgets shown were too small.
  
  Details:
  
  The resolution was correct, at 2560x1600, but all widgets shown were too
  small. I suspected this was due to the laptop screen high pixel density
  and the widget size calculation didn't make use of physical dimension,
  but in terms of pixel.
  
  I thought installing NVIDIA driver would fix this, but no; this worked
  in OpenSUSE Leap with KDE Plasma and I think it was because of the
  inclusion of NVIDIA OpenGL driver.
  
  The current workaround was to scale by 200% in "Display Settings",
  although the login screen isn't affected by the scaling at all.
  
  ---
  
  There were 3 problems I encountered in discrete graphics mode:
  
  - The widgets were are too small, like the hybrid graphics mode issue.
  - The DE seemed to use wrong screen refresh rate.
  
  The refresh rate was fixed at 93 Hz in the "Display Settings".
  
  Changing the refresh rate between 60 Hz and 165 Hz by Fn keys didn't
  update the 93 Hz in the "Display Settings".
  
  This didn't happen in the hybrid graphics mode.
  
  OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I
  think it may be either GNOME DE or xorg misconfigurations.
- 
- Details:
- 
- The above 2 problems were the same issue as encountered in the hybrid
- graphics mode.
  
  - Screen brightness was fixed at 100%.
  
  Details:
  
  Screen brightness could be adjusted by the keyboard Fn keys, but the
  brightness was fixed at 100%.
  
  This didn't happen in the hybrid graphics mode.
  
  This is the most annoying problem and have forced me to use the hybrid
  graphics mode which I don't like.
  
  My first thought was either a specific NVIDIA issue or xorg
  misconfigurations.
  
  So I tried adding "acpi_backlight=vendor" and
  "nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but
  didn't work at all.
  
  ---
  
  In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed
  below:
  
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, 
During name lookup/catalog (20210730/psobject-220)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading 
X.509 certificate -65
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  
  In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above
  except that there was no:
  
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  520.56.06  Release 
Build  (dvs-builder@U16-T12-10-2)  Thu Oct  6 21:33:54 UTC 2022
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 29 18:50:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/520.56.06, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev 
a1) (prog-if 00 [VGA controller])

[Touch-packages] [Bug 1995173] Re: Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue

2022-10-29 Thread Yosua Liu
** Description changed:

  The device is Lenovo Legion 7. This laptop has a mux switch to switch
  between dynamic/hybrid or discrete graphics mode. This laptop has a high
  resolution with high pixel density than the other displays out there,
  but I don't know the exact number. Additionally, this laptop can adjust
  the display refresh rate between 60 and 165 Hz.
  
  ---
  
- There were 2 problems I encountered in dynamic/hybrid graphics mode:
+ There were 1 problem I encountered in dynamic/hybrid graphics mode:
  
  - The widgets shown were too small.
  
  Details:
  
  The resolution was correct, at 2560x1600, but all widgets shown were too
  small. I suspected this was due to the laptop screen high pixel density
  and the widget size calculation didn't make use of physical dimension,
  but in terms of pixel.
  
  I thought installing NVIDIA driver would fix this, but no; this worked
  in OpenSUSE Leap with KDE Plasma and I think it was because of the
  inclusion of NVIDIA OpenGL driver.
  
  The current workaround was to scale by 200% in "Display Settings",
- although this make some widgets pixelated or blurred and the login
- screen isn't affected by the scaling at all.
- 
- - The DE seemed to use wrong screen refresh rate.
- 
- The refresh rate I usually used is 165 Hz, but the "Display Settings"
- showed 93 Hz.
- 
- Changing the refresh rate between 60 Hz and 165 Hz didn't update the 93
- Hz in the "Display Settings".
- 
- OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I
- think it may be either GNOME DE or xorg misconfigurations.
+ although the login screen isn't affected by the scaling at all.
  
  ---
  
  There were 3 problems I encountered in discrete graphics mode:
  
- - The widgets were are too small.
+ - The widgets were are too small, like the hybrid graphics mode issue.
  - The DE seemed to use wrong screen refresh rate.
+ 
+ The refresh rate was fixed at 93 Hz in the "Display Settings".
+ 
+ Changing the refresh rate between 60 Hz and 165 Hz by Fn keys didn't
+ update the 93 Hz in the "Display Settings".
+ 
+ This didn't happen in the hybrid graphics mode.
+ 
+ OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I
+ think it may be either GNOME DE or xorg misconfigurations.
  
  Details:
  
  The above 2 problems were the same issue as encountered in the hybrid
  graphics mode.
  
  - Screen brightness was fixed at 100%.
  
  Details:
  
- Screen brightness could be adjusted by the keyboard fn keys, but the
+ Screen brightness could be adjusted by the keyboard Fn keys, but the
  brightness was fixed at 100%.
+ 
+ This didn't happen in the hybrid graphics mode.
  
  This is the most annoying problem and have forced me to use the hybrid
  graphics mode which I don't like.
  
- My first thought was a specific NVIDIA issue.
+ My first thought was either a specific NVIDIA issue or xorg
+ misconfigurations.
  
  So I tried adding "acpi_backlight=vendor" and
  "nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but
  didn't work at all.
  
  ---
  
  In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed
  below:
  
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, 
During name lookup/catalog (20210730/psobject-220)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading 
X.509 certificate -65
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  
  In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above
  except that there was no:
  
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): 
Could not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
  Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  520.56.06  

[Touch-packages] [Bug 1992206] Re: bash: non existent locale crashes bash

2022-10-29 Thread Bug Watch Updater
** Changed in: bash (Debian)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1992206

Title:
  bash: non existent locale crashes bash

Status in bash package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bash package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1021109:

  Package: libc6
  Version: 2.35-1
  Severity: grave
  Justification: renders package unusable
  X-Debbugs-Cc: kos...@debian.org

  Dear maintainer,

  After upgrading to libc6 2.35-1 (or 2.36-1 in experimental), nonexistent 
locale setting
  starts to crash the system.

  This is dangerous because a remote system might not always have the same 
locale installed.
  An auto update will soft-brick the system unless the sysadmin knows to set 
their LC_ALL=POSIX
  before attempting to ssh.

  Steps to reproduce:

  From a clean installed Debian sid, upgrade to libc6 2.35-1.
  Only install C locale and en_US.UTF-8.

  $ LC_ALL=ja_JP.UTF-8 bash
  bash: warning: setlocale: LC_ALL: cannot change locale (ja_JP.UTF-8)
  Segmentation fault (core dumped)

  $ LC_ALL=ja_JP.UTF-8 gdb bash

  Fatal signal: Segmentation fault
  - Backtrace -
  0x55ed3e1e8dcf ???
  0x55ed3e2df312 ???
  0x55ed3e2df488 ???
  0x7f0b4a39ba9f ???
  0x7f0b4b412204 _rl_init_locale
  0x7f0b4b4122f1 _rl_init_eightbit
  0x7f0b4b3f10f2 rl_initialize
  ... snip ...

  Downgrade to 2.34-8 seems also don't fix the issue, probably some locale
  state was invalidated when upgrading.

  Thanks,
  Kan-Ru

  
  -- System Information:
  Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: amd64 (x86_64)

  Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
  Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
  Shell: /bin/sh linked to /usr/bin/dash
  Init: systemd (via /run/systemd/system)
  LSM: AppArmor: enabled

  Versions of packages libc6 depends on:
  ii  libgcc-s1  12.2.0-3

  Versions of packages libc6 recommends:
  ii  libidn2-0  2.3.3-1+b1

  Versions of packages libc6 suggests:
  ii  debconf [debconf-2.0]  1.5.79
  pn  glibc-doc  
  ii  libc-l10n  2.35-1
  pn  libnss-nis 
  pn  libnss-nisplus 
  ii  locales2.35-1

  -- debconf information:
glibc/kernel-too-old:
glibc/restart-failed:
glibc/disable-screensaver:
glibc/upgrade: true
  * libraries/restart-without-asking: false
  * glibc/restart-services: cron
glibc/kernel-not-supported:

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1921920] Re: Xubuntu 20.04.2.1 cannot log out, shut down or restart from a temporary guest session.

2022-10-29 Thread Sean Davis
** Package changed: xubuntu-meta (Ubuntu) => xfce4-session (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1921920

Title:
  Xubuntu 20.04.2.1 cannot log out, shut down or restart from a
  temporary guest session.

Status in lightdm package in Ubuntu:
  New
Status in xfce4-session package in Ubuntu:
  New

Bug description:
  I cannot log out, shut down or restart from an activated temporary guest 
session. Only via tty or REISUB. Clicking anything in the 
logout/restart/shutdown GUI dialog window will only result in the message "An 
error occurred while logging out"
  GDBus.Error:org.freedesktop.Dbus.Error.InvalidArgs: Type ofmessage, "(yb)", 
does not match expected type "(b)"

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1434986] Re: Not working network connection after boot

2022-10-29 Thread Alex
I can confirm that this is still happening in Kubuntu 18.04. Rudolfs
Caunes's solution actually works.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1434986

Title:
  Not working network connection after boot

Status in NetworkManager:
  Expired
Status in network-manager package in Ubuntu:
  Triaged

Bug description:

  Directly after boot the network connections are not working. I am
  connected and have an IP address, but I cannot establish a connection
  with any Internet server.

  I have the impression it is related to thee DNS lookup, which waits
  forever for a result.

  Cycling the connection (disconnect->reconnect) seems to fix the
  problem for some time.

  I am reporting this against network-manager, but I am not sure if it is 
directly in network manager or if it is systemd related.
  With 14.10 everything worked perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 22 12:38:26 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-30 (50 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  IpRoute:
   default via 192.168.1.1 dev eth0 proto static metric 1024
   169.254.0.0/16 dev wlan0 scope link metric 1000
   192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26
   192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-16T00:14:50.662693
  nmcli-dev:
   DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
   eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 
Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb 
/org/freedesktop/NetworkManager/ActiveConnection/4
   wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 
4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 
/org/freedesktop/NetworkManager/ActiveConnection/3
   lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1434986/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1995173] [NEW] Lenovo Legion 7 Display Issues : Cannot Control Display Brightness, High Pixel Density Issue, and Resolution Issue

2022-10-29 Thread Yosua Liu
Public bug reported:

The device is Lenovo Legion 7. This laptop has a mux switch to switch
between dynamic/hybrid or discrete graphics mode. This laptop has a high
resolution with high pixel density than the other displays out there,
but I don't know the exact number. Additionally, this laptop can adjust
the display refresh rate between 60 and 165 Hz.

---

There were 2 problems I encountered in dynamic/hybrid graphics mode:

- The widgets shown were too small.

Details:

The resolution was correct, at 2560x1600, but all widgets shown were too
small. I suspected this was due to the laptop screen high pixel density
and the widget size calculation didn't make use of physical dimension,
but in terms of pixel.

I thought installing NVIDIA driver would fix this, but no; this worked
in OpenSUSE Leap with KDE Plasma and I think it was because of the
inclusion of NVIDIA OpenGL driver.

The current workaround was to scale by 200% in "Display Settings",
although this make some widgets pixelated or blurred and the login
screen isn't affected by the scaling at all.

- The DE seemed to use wrong screen refresh rate.

The refresh rate I usually used is 165 Hz, but the "Display Settings"
showed 93 Hz.

Changing the refresh rate between 60 Hz and 165 Hz didn't update the 93
Hz in the "Display Settings".

OpenSUSE Leap with KDE Plasma properly detected 60 and 165 Hz, so I
think it may be either GNOME DE or xorg misconfigurations.

---

There were 3 problems I encountered in discrete graphics mode:

- The widgets were are too small.
- The DE seemed to use wrong screen refresh rate.

Details:

The above 2 problems were the same issue as encountered in the hybrid
graphics mode.

- Screen brightness was fixed at 100%.

Details:

Screen brightness could be adjusted by the keyboard fn keys, but the
brightness was fixed at 100%.

This is the most annoying problem and have forced me to use the hybrid
graphics mode which I don't like.

My first thought was a specific NVIDIA issue.

So I tried adding "acpi_backlight=vendor" and
"nvdia.NVreg_RegistryDwords=EnableBrightnessControl=1" to GRUB, but
didn't work at all.

---

In discrete graphics mode, a quick "sudo journalctl -p3 -b0" showed
below:

Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20210730/dswload2-162)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: AE_NOT_FOUND, 
During name lookup/catalog (20210730/psobject-220)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: integrity: Problem loading 
X.509 certificate -65
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)

In hybrid graphics mode, "sudo journalctl -p3 -b0" output like above
except that there was no:

Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI BIOS Error (bug): Could 
not resolve symbol [\_SB.PCI0.GP17.VGA.LCD._BCM.AFN7], AE_NOT_FOUND 
(20210730/psargs-330)
Okt 29 18:48:04 jiazhang-Legion-7-16ACHg6 kernel: ACPI Error: Aborting method 
\_SB.PCI0.GP17.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) 
(20210730/psparse-529)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX Open Kernel Module for x86_64  520.56.06  Release 
Build  (dvs-builder@U16-T12-10-2)  Thu Oct  6 21:33:54 UTC 2022
 GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 29 18:50:17 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: nvidia/520.56.06, 5.15.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3aa6]
InstallationDate: Installed on 2022-10-29 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 82N6
ProcKernelCmdLine: 

[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

2022-10-29 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/124440

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  New
Status in GTK+:
  New
Status in Mir:
  Fix Released
Status in Mutter:
  New
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

2022-10-29 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1766503

Title:
  ibus-* randomly use high CPU

Status in GNOME Shell:
  Fix Released
Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Opinion
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1970144] Re: [vmwgfx] Qt Creator windows don't render correctly, VMware 16, Ubuntu 22.04

2022-10-29 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1970144

Title:
  [vmwgfx] Qt Creator windows don't render correctly, VMware 16, Ubuntu
  22.04

Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  xdpyinfo 
  name of display::0
  version number:11.0
  vendor string:The X.Org Foundation
  vendor release number:12201001
  X.Org version: 1.22.1.1
  maximum request size:  16777212 bytes
  motion buffer size:  256
  bitmap unit, bit order, padding:32, LSBFirst, 32
  image byte order:LSBFirst
  number of supported pixmap formats:7
  supported pixmap formats:
  depth 1, bits_per_pixel 1, scanline_pad 32
  depth 4, bits_per_pixel 8, scanline_pad 32
  depth 8, bits_per_pixel 8, scanline_pad 32
  depth 15, bits_per_pixel 16, scanline_pad 32
  depth 16, bits_per_pixel 16, scanline_pad 32
  depth 24, bits_per_pixel 32, scanline_pad 32
  depth 32, bits_per_pixel 32, scanline_pad 32
  keycode range:minimum 8, maximum 255
  focus:  None
  number of extensions:23
  BIG-REQUESTS
  Composite
  DAMAGE
  DOUBLE-BUFFER
  DRI3
  GLX
  Generic Event Extension
  MIT-SHM
  Present
  RANDR
  RECORD
  RENDER
  SHAPE
  SYNC
  X-Resource
  XC-MISC
  XFIXES
  XFree86-VidModeExtension
  XINERAMA
  XInputExtension
  XKEYBOARD
  XTEST
  XVideo
  default screen number:0
  number of screens:1

  screen #0:
dimensions:3838x1781 pixels (1015x471 millimeters)
resolution:96x96 dots per inch
depths (7):24, 1, 4, 8, 15, 16, 32
root window id:0x2bb
depth of root window:24 planes
number of colormaps:minimum 1, maximum 1
default colormap:0x43
default number of colormap cells:256
preallocated pixels:black 0, white 16777215
options:backing-store WHEN MAPPED, save-unders NO
largest cursor:3838x1781
current input event mask:0xda0030
  EnterWindowMask  LeaveWindowMask  StructureNotifyMask 
 
  SubstructureNotifyMask   SubstructureRedirectMask PropertyChangeMask  
 
  ColormapChangeMask

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 09:25:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=e6bcbb51-635a-42a1-ab99-75af8c14475f ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-10-29 Thread Ludovic Rousseau
I wrote a blog article about this issue
https://ludovicrousseau.blogspot.com/2022/10/ubuntu-2204-and-pcscd-auto-start-failure.html

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1969709] Re: libreoffice font selection unusably slow

2022-10-29 Thread perkoug
After hint there is no problem with:
Tools > Options > LibreOffice > View > checked out το Show preview of fonts

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1969709

Title:
  libreoffice font selection unusably slow

Status in LibreOffice:
  Won't Fix
Status in fontconfig package in Ubuntu:
  Incomplete
Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Trying to scroll through the font list in the menu bar, I experience
  an unacceptable degree of lagging. Just popping up the dropdown list
  takes 7-10 seconds and the system takes the same amount of time to
  respond to perform individidual scrolling gestures. The CPU jumps to
  100% and the whole system becomes unresponsive.

  I have tried deb, snap and even the packages offered on the site of
  the LibreOffice project. They all manifest the same behaviour. The
  only thing that works is disabling font previews. I have downgraded to
  7.2 for now, which appears to be unaffected.

  I have contacted the LibreOffice team and they tell me that this
  should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is
  shipping 2.13...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-core 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 05:01:24 2022
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2022-03-27 (24 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1969709/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1922047] Re: Touchpad scrolling is too fast

2022-10-29 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1922047

Title:
  Touchpad scrolling is too fast

Status in Mozilla Firefox:
  Confirmed
Status in GTK+:
  Fix Released
Status in Mutter:
  New
Status in firefox package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This is an issue which has troubled me for a while. Anecdotally,
  scrolling feels way too fast in GNOME on Wayland compared to on X11. I
  finally tested it semi-scientifically, and it seems like GNOME on
  Wayland scrolls almost exactly 1.5x faster than GNOME on X11.

  I tested this by testing how many lines are scrolled from a full two-
  finger touchpad swipe from the bottom of my touchpad to the top of my
  touchpad, and logged a few attempts in both X and Wayland. I kept
  track of the results in this spreadsheet:
  
https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing

  I scrolled in one of my own GTK applications
  (https://github.com/mortie/lograt) because it lets me easily see how
  many lines I scrolled. Attach is a video of one full scroll on X11 and
  one full scroll on Wayland.

  This testing was performed on a Dell XPS 13 9343, but I've also used
  Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way
  too fast. I don't have other hardware to test on.

  This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 31 11:44:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-11-21 (495 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1924689] Re: When changing screen scale in GNOME Xorg, gnome-initial-setup's window shadow should not be glitched

2022-10-29 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1924689

Title:
  When changing screen scale in GNOME Xorg, gnome-initial-setup's window
  shadow should not be glitched

Status in Mutter:
  New
Status in OEM Priority Project:
  New
Status in gnome-initial-setup package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Ubuntu release:
  Ubuntu 20.04.2 LTS

  Issue description:
  When the gnome-initial-setup launched, if user changes the scale 200 -> 400 
or 100 -> 200.
  There is some garbage on the edge of the window.

  The issue is not seen if we login in wayland session.

  A video is attached.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

2022-10-29 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1738676

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1838838] Re: username is not saved in openconnect connection dialog

2022-10-29 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1838838

Title:
  username is not saved in openconnect connection dialog

Status in GNOME Shell:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Same issue as https://bugs.launchpad.net/ubuntu/+source/network-
  manager-openconnect/+bug/1609700

  This was marked resolved. The report of its reappearance in Ubuntu
  19.04 and 19.10 has not been acknowledged.

  This was working for me in 18.10, but a fresh install of 19.04 and
  19.10 show that it is back. The password is saved when the option to
  save passwords is selected, but the username must be entered manually
  upon connection.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

2022-10-29 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1865300

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  gnome-shell-hotplug-sniffer crashes when attaching some device that
  may have files with unknown content type

  [ Test case ]

  - Plug a media, but it's not yet known which kind of files cause this issue,
so we should just monitor the e.u.c crash:
https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  [ Regression potential ]

  - No valid application for opening a media is shown by gnome-shell

  ---

  This is for 3.34:

  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec

  ---

  Happened during normal use of the desktop.

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards

2022-10-29 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1895486

Title:
  [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
  Lock" keyboards

Status in GNOME Shell:
  New
Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  I use Ubuntu 20.04.1.

  After some use, I noticed a delay when using keyboard media controls
  (for example: increase volume audio).

  The first time I push these key Gnome hangs for a short time before
  display the action on the screen.

  (This problem is still happening in Ubuntu 18.04 too. Even worse some
  times, the system crashes when using media keys.)

  For some reason, my Gnome freezes when using Fn keys, or when I try to
  use two keyboards. A friend of mine pointed to me that it occurs when
  switching to a keyboard layout that has Scroll Lock enabled, so I
  disabled it in the X11 keyboard layout file for my language, and it
  solved the problem.

  
  A workaround to solve the problem is:

  1) Opened the keyboard layout file for my language, in my case:

  sudo nano /usr/share/X11/xkb/symbols/br

  2) Commented the line:

  modifier_map Mod3 { Scroll_Lock };

  3) Logged out and logged in again or run command setxkbmap.

  These steps are specific for the Brazilian Portuguese ABNT2 Layout and
  may not work for other layouts, but it can help you find a similar
  solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-xkb-utils 7.7+5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 21:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
  InstallationDate: Installed on 2020-08-15 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
  SourcePackage: x11-xkb-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.15
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.15
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1896171] Re: Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

2022-10-29 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1896171

Title:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver)

Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Wayland GL apps appear corrupt on Raspberry Pi 4B (v3d driver).

  Seen in glmark2-wayland, glmark2-es2-wayland, weston-simple-egl.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

2022-10-29 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/124440

Title:
  [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed

Status in gnome-control-center:
  New
Status in GTK+:
  New
Status in Mir:
  Fix Released
Status in Mutter:
  Unknown
Status in Unity:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  Won't Fix

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1876267] Re: Changing sound left/right balance impacts on front/back

2022-10-29 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1876267

Title:
  Changing sound left/right balance impacts on front/back

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  What happens:

  If an Asus STXII 7.1 sound card is installed and another output device
  is present, there is a strange behavior in the Gnome audio settings.

  After the first start of Ubuntu the Asus soundcard is not the default
  device. This can be selected in the Gnome settings. If a different
  speaker configuration is selected now. E.g. stereo instead of 5.1 or
  vice versa, the selection jumps from the Asus output device back to
  the original output device. The Asus sound card can then be selected
  again and the corresponding speaker configuration will fit now.

  If 5.1 is selected as the mode, there is a second problem.
  Moving the balance slider (left / right) moves the slider (front / back) 
slightly as well.
  The slider for lfe is grayed out, even when I enable the lfe remixing in 
/etc/pulse/daemon.conf
  In the speaker test, all 5.1 channels work fine, including the lfe.

  For better illustration I made a screen video. (see attachment)

  This is probably a general bug in Gnome - it has been occurring since
  Ubuntu 18.x and affects all distros that use Gnome since then.
  Unfortunately I was not able to make a report in Gnome, because the
  registration on the Gnome site does not work anymore... Maybe you have
  a good contact to the Gnome team?

  Ubuntu 20.04 LTS (Release 20.04)
  Package: gnome-control-center (1:3.36.1-1ubuntu5)

  Expected behavior:
  It should be possible to select the sound card and the setting should be 
retained even if the speaker configuration is changed. Furthermore, the balance 
sliders should not influence each other.
  Lfe slider should work. (And in a perfect world this would also activate lfe 
remixing and gives the user a cross over frequency option, but this is just an 
idea :)

  BR,
  Mathias
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-23 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=de_AT:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1911456] Re: Can't receive files over bluetooth unless settings dialog is open

2022-10-29 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1911456

Title:
  Can't receive files over bluetooth unless settings dialog is open

Status in gnome-control-center:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  On 18.04 I could send files from my phone to my laptop at any time.
  On 20.04 I can't get files to be accepted by the laptop over bluetooth. After 
much frustration and experimenting, I figured out that it will work, but only 
if the bluetooth settings dialog is open. If the settings dialog is not open, 
the incoming file is rejected.  If the dialog is closed after the file transfer 
begins, the transfer continues but the file is discarded when the transfer is 
complete.  This is very frustrating.
  I need to be able to send files (mostly photos and videos) from my phone to 
my laptop without having to open the settings dialog on the laptop, just like I 
could before upgrading.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1915358] Re: sound hdmi 5.1 subwoofer always disabled

2022-10-29 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1915358

Title:
  sound hdmi 5.1 subwoofer always disabled

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  In System Sound Settings, I chose HDMI 5.1 audio, but there is no
  sound from my subwoofer in any audio application.

  The System Sound Settings for HDMI 5.1 always shows a disabled
  subwoofer slider. When I open the test window and hit the subwoofer
  icon button, no sound is produced.

  
  But if I open Pulse Audio Volume Control -> Output Devices -> (unlock icon), 
all show mid-volume on the slider except for subwoffer.  But the subwoofer 
slider is enabled.  So I slide it to mid-volume, and go back to System Sound 
Settings -> test window and hit the subwoofer icon button, I hear my subwoofer 
is working fine.

  I also then hear the subwoofer in all audio applications.

  If I were to touch the System Sound Slider for the subwoofer, it
  immediately stops working again.

  I can fix it again in Pulse Audio Volumne Control again.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 10 19:47:38 2021
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2021-01-25 (16 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools

2022-10-29 Thread Aaron Renny Varghese
I agree with Jeremy Bicha here. Canonical needs to make money and those
ads aren't spammy at all. However I do want to see an option to turn
Ubuntu Advantage/Pro and promotional content off, for those who don't
want it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1930914

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1995160] [NEW] Some problem with graphic card driver

2022-10-29 Thread Nguyen Pham Thai Son
Public bug reported:

One day, I suddenly got the trouble with the graphics card driver. I
tried to switch almost the Nvidia driver but it's still not working. I
got the error message nvidia-gpu ic2 timeout error then only one screen
worked. Hence I have to use Xorg the default driver then it works. But
when I share screen, it display black screen, I can't share, and
performance when I use the default graphic driver is not good as well.
Please take a look my trouble

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15
Uname: Linux 5.17.0-1020-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 29 12:44:53 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: nvidia/470.141.03: added
GraphicsCard:
 NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU116 [GeForce GTX 1660 Ti] [1043:8840]
InstallationDate: Installed on 2022-06-30 (120 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: To Be Filled By O.E.M. B660M Pro RS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1020-oem 
root=UUID=53a88101-e9f6-4e5f-ac27-9c925fc462c0 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/28/2022
dmi.bios.release: 5.24
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 5.04
dmi.board.name: B660M Pro RS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr5.04:bd03/28/2022:br5.24:svnToBeFilledByO.E.M.:pnB660MProRS:pvrToBeFilledByO.E.M.:rvnASRock:rnB660MProRS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: B660M Pro RS
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1995160

Title:
  Some problem with graphic card driver

Status in xorg package in Ubuntu:
  New

Bug description:
  One day, I suddenly got the trouble with the graphics card driver. I
  tried to switch almost the Nvidia driver but it's still not working. I
  got the error message nvidia-gpu ic2 timeout error then only one
  screen worked. Hence I have to use Xorg the default driver then it
  works. But when I share screen, it display black screen, I can't
  share, and performance when I use the default graphic driver is not
  good as well. Please take a look my trouble

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.17.0-1020.21-oem 5.17.15
  Uname: Linux 5.17.0-1020-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 29 12:44:53 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/470.141.03: added
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU116 [GeForce GTX 1660 Ti] [1043:8840]
  InstallationDate: Installed on 2022-06-30 (120 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. B660M Pro RS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1020-oem 
root=UUID=53a88101-e9f6-4e5f-ac27-9c925fc462c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: