[Touch-packages] [Bug 1730606] Re: systemd idleaction=suspend not working in multiseat while a screen is showing login prompt

[amk]

After upgrade to Ubuntu version 20.4 the issue with the idle status
reporting by lightdm-greeter remains. This continues to have idle
setting of logind.conf ignored:

https://www.freedesktop.org/software/systemd/man/logind.conf.html
> Note that this requires that user sessions correctly report the idle status 
> to the system. The system will execute the action after *all sessions* report 
> that they are idle, no idle inhibitor lock is active, and subsequently, the 
> time configured with IdleActionSec= (see below) has expired.

At the other hand, installing lightdm and unity-greeter causes suspend
to happen every 20 minutes while one screen shows greeter, regardless of
all other screens. Reported also at
https://askubuntu.com/questions/1337649/how-to-disable-suspend-in-20
-minutes-from-the-lightdm-login-screen and as
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1928305

There is a workaround available there (set both org.gnome.settings-
daemon.plugins.power and com.canonical.unity.settings-
daemon.plugins.power sleep-inactive-ac-type to 'nothing'), preventing
the unexpected suspend by greeter. Issue of this bug remains since the
greeter still does not report idle to logind.

The script to check idle status of all session and force suspend overriding 
login screen needs update, systemd-inhibit --list does not have parseable 
output, like it was the case in systemd version 229. Needed to be replaced by 
command
gdbus call --system --dest org.freedesktop.login1 --object-path 
/org/freedesktop/login1 --method org.freedesktop.login1.Manager.ListInhibitors


There are several other reports of this problem, for example also at 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896083 or 
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/22 but I am not 
sure about be the best upstream place to track this. It looks like gdm/lightdm 
greeter is not designed to work under logind but attempts to control the system 
sleep status on its own.

** Bug watch added: Debian Bug tracker #896083
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896083

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #22
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/22

** Attachment added: "Workaround, checking idle/inhibit status of all sessions, 
ignoring greeter"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606/+attachment/5501243/+files/idlecheck.pl

-- 
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/1730606

Title:
  systemd idleaction=suspend not working in multiseat while a screen is
  showing login prompt

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.3 LTS, multiseat setup.
  systemd:  Installed: 229-4ubuntu21
  lightdm:  Installed: 1.18.3-0ubuntu1.1

  logind.conf:IdleAction=suspend
  logind.conf:IdleActionSec=300

  Using multiseat, it is not possible to have gnome settings controlling
  idle suspend, as it would ignore the other seat. IdleAction=suspend in
  /etc/systemd/logind.conf works well, provided both seats are logged in
  or locked.

  After boot, or after logout the seat remains showing login screen and
  the system never suspends.

  loginctl show-session provides IdleHint=yes that allows to determine
  whether the user is active. For some reason Active property is yes all
  the time.

  But for the login screen the show-session does not provide the hint
  about seat idling:

  $ loginctl show-session c9
  Id=c9
  User=108
  Name=lightdm
  Timestamp=Sun 2017-11-05 22:35:37 CET
  TimestampMonotonic=13418600852
  VTNr=7
  Seat=seat0
  Display=:1
  Remote=no
  Service=lightdm-greeter
  Scope=session-c9.scope
  Leader=12431
  Audit=0
  Type=x11
  Class=greeter
  Active=yes
  State=active
  IdleHint=no
  IdleSinceHint=0
  IdleSinceHintMonotonic=0

  Working on a script to check for IdleHint=Yes and Service=lightdm-
  greeter and suspend based on this.

  I am marking this as a bug in lightdm because I think it is not
  correctly reporting the idle status to the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606/+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 1881432] Re: System hangs after pulseaudio error: "snd_pcm_avail() returned a value that is exceptionally large: 125388 bytes (710 ms)"

[Hui Wang]

Thanks Jeronimo, I saw you reported a upstream bug, let me add the link
here:

https://github.com/alsa-project/alsa-lib/issues/141
https://github.com/alsa-project/alsa-lib/issues/68
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1078


** Bug watch added: github.com/alsa-project/alsa-lib/issues #141
   https://github.com/alsa-project/alsa-lib/issues/141

** Bug watch added: github.com/alsa-project/alsa-lib/issues #68
   https://github.com/alsa-project/alsa-lib/issues/68

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1078
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1078

-- 
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/1881432

Title:
  System hangs after pulseaudio error: "snd_pcm_avail() returned a value
  that is exceptionally large: 125388 bytes (710 ms)"

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This is a bug on Ubuntu 20.04 (Focal Fossa) for pulseaudio version:
  1:13.99.1-1ubuntu3.2.

  Description:

  At random intervals, pulseaudio gives the following error message:
  "snd_pcm_avail() returned a value that is exceptionally large: 125388
  bytes (710 ms)," after which the system slows down to a crawl. It has
  occurred in two instances: while playing a video game, and while
  working in two different workspaces with a zoom client and Spotify
  open (though not actively playing any audio). The system is
  recoverable with the SysRq key. I have not been able to duplicate it
  on command, but it is recurrent.

  Possible duplicates:

  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1750947. The
  patch committed to fix this bug was reverted to fix a subsequent bug,
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767784.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-01 (59 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  NonfreeKernelModules: wl
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Tags:  focal
  Uname: Linux 5.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.70
  dmi.board.name: B450M-HDV R4.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.70:bd11/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881432/+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 1930178] Re: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  saw the following

  mkinitramfs failure cpio 141 lz4 -9 -l 24

  searched for it and found

  apt-get install --reinstall cpio gzip initramfs-tools initramfs-tools-
  core

  install completed.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.5
  ProcVersionSignature: Ubuntu 4.15.0-143.147-generic 4.15.18
  Uname: Linux 4.15.0-143-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 30 19:05:55 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-05-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1930178/+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 1930178] [NEW] package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Neal Kazmi]

Public bug reported:

saw the following

mkinitramfs failure cpio 141 lz4 -9 -l 24

searched for it and found

apt-get install --reinstall cpio gzip initramfs-tools initramfs-tools-
core

install completed.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.5
ProcVersionSignature: Ubuntu 4.15.0-143.147-generic 4.15.18
Uname: Linux 4.15.0-143-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun May 30 19:05:55 2021
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2021-05-31 (0 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  saw the following

  mkinitramfs failure cpio 141 lz4 -9 -l 24

  searched for it and found

  apt-get install --reinstall cpio gzip initramfs-tools initramfs-tools-
  core

  install completed.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.5
  ProcVersionSignature: Ubuntu 4.15.0-143.147-generic 4.15.18
  Uname: Linux 4.15.0-143-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun May 30 19:05:55 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.5 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2021-05-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1930178/+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 1930128] Re: Xorg freeze

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Tags added: nvidia

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

-- 
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/1930128

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  I just started Foxit Reader to config it. While I browse through the
  title menues to find the preferences the whole GDM or x.org sessione
  freezes. The only way to restart was to some restart commands over the
  Off-Shell (Ctrl + Alt + F3).

  Wont fixed the issue:

  - busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s 
'Meta.restart("Restarting...")'
  - sudo killall -HUP gnome-shell
  - sudo systemctl restart gdm (kicked me back to login after every login)

  Fixed the issue:
  - sudo systemctl restart systemd-logind

  The last command fixed it after a short time. I tried to jump back
  every time with Ctrl + Alt + F1 and anytime it worked.

  I have no idea if this is a Foxit Reader bug or a issue by GDM/xorg.

  I additionally attached you my latest protocols. In this time the
  freeze occured.

  Best regards,
  Johannes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .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 x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 29 12:28:07 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A] 
[1043:875c]
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.40
  dmi.board.name: Z390 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  

[Touch-packages] [Bug 1930138] Re: When i use super+left arrow key, my desktop items flash.

[Daniel van Vugt]

Thanks for the bug report. Please also report it to the developer at:

  https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues

and then tell us the new issue ID.

** Package changed: xorg (Ubuntu) => gnome-shell-extension-desktop-icons
(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/1930138

Title:
  When i use super+left arrow key, my desktop items flash.

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  I can have like 10 windows open, each one being fullscreen, but when i use 
super+left, the trash bin (and other items on my desktop) flashes through all 
the layers and appears on the top layer.
  Please see attached video, it demonstrates the glitch.

  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 29 09:50:00 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.8.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. 2nd Generation Core Processor Family Integrated 
Graphics Controller [106b:00eb]
  InstallationDate: Installed on 2021-05-16 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Apple Inc. MacBookAir4,2
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic 
root=UUID=750cf8ea-6f55-46ba-8cb9-e0888e6f4335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 135.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-742912EFDBEE19B3
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir4,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-742912EFDBEE19B3
  dmi.modalias: 
dmi:bvnAppleInc.:bvr135.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir4,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  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.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-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/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1930138/+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 1930112] Re: Error When Shutting Down via GUI- Xubuntu 21.04

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xfce4 (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/1930112

Title:
  Error When Shutting Down via GUI- Xubuntu 21.04

Status in xfce4 package in Ubuntu:
  New

Bug description:
  I get an error when I try to shutdown via the GUI, screenshot
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri May 28 19:59:00 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:3e92] (prog-if 00 
[VGA controller])
 Subsystem: Dell UHD Graphics 630 (Desktop) [1028:085a]
  InstallationDate: Installed on 2021-05-27 (1 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. OptiPlex 7060
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic 
root=UUID=c7908293-5a44-4112-b804-867efc7801ac ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2021
  dmi.bios.release: 1.12
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0NC2VH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd05/05/2021:br1.12:svnDellInc.:pnOptiPlex7060:pvr:rvnDellInc.:rn0NC2VH:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7060
  dmi.product.sku: 085A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.104-1build1
  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
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfce4/+bug/1930112/+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 1912911] Re: When printing with my Brother hl-2170w printer I keep getting an invalid page range error on a blank page, after the desired pages are printed

[sokolov]

However, it is not 100% reproducable.

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

Title:
  When printing with my Brother hl-2170w printer I keep getting an
  invalid page range error on a blank page, after the desired pages are
  printed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I run uname -a, this is basically what I get:
  "5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux"

  apt-cache policy cups gives me the following:

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
===

  4 and 5 are being answered together...

  Before the upgrade, I was able to print one or more pages, and not see the 
extra error page.
  This is the desired behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 23 13:15:24 2021
  InstallationDate: Installed on 2020-12-21 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for SCRIBE: 
dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/
  MachineType: Dell Inc. Inspiron 7773
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/SCRIBE.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/SCRIBE.ppd: Permission denied
  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.8.0-38-generic 
root=UUID=9899e123-f378-4328-a399-78cd6361f58e ro quiet splash 
resume=UUID=46e80ad1-16de-4fdf-b1f7-96f4f58b1c57
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0R58C3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd09/14/2017:br1.2:svnDellInc.:pnInspiron7773:pvr:rvnDellInc.:rn0R58C3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7773
  dmi.product.sku: 0809
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1912911/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)

[Daniel van Vugt]

Also after reproducing the problem again, please run:

  journalctl -b0 > newjournal.txt

and attach the resulting text file here.

-- 
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/1872802

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second (in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)

[Daniel van Vugt]

Thanks Roman. Is that still on an Intel i5-7200U ?

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Released => Incomplete

** Changed in: mesa (Ubuntu)
   Status: Fix Released => Incomplete

** Changed in: mutter (Ubuntu)
   Status: Fix Released => Incomplete

-- 
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/1872802

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second (in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1912911] Re: When printing with my Brother hl-2170w printer I keep getting an invalid page range error on a blank page, after the desired pages are printed

[sokolov]

I also get additional pages printed with an error message. It reads

"Invalid page range: none printer-location= marker-levels=36"

uname -a gives me:

Linux 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:39:42 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux

apt-cache policy cups gives me the following:

 Installed: 2.3.1-9ubuntu1.1
  Candidate: 2.3.1-9ubuntu1.1
  Version table:
 *** 2.3.1-9ubuntu1.1 500

My computer has an Intel Xeon CPU.

My printer is a Dell E514dw, which is a rebadged Brother MFC-L5750DW
(except for the printer cartridges).

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

Title:
  When printing with my Brother hl-2170w printer I keep getting an
  invalid page range error on a blank page, after the desired pages are
  printed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I run uname -a, this is basically what I get:
  "5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux"

  apt-cache policy cups gives me the following:

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
===

  4 and 5 are being answered together...

  Before the upgrade, I was able to print one or more pages, and not see the 
extra error page.
  This is the desired behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 23 13:15:24 2021
  InstallationDate: Installed on 2020-12-21 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for SCRIBE: 
dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/
  MachineType: Dell Inc. Inspiron 7773
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/SCRIBE.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/SCRIBE.ppd: Permission denied
  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.8.0-38-generic 
root=UUID=9899e123-f378-4328-a399-78cd6361f58e ro quiet splash 
resume=UUID=46e80ad1-16de-4fdf-b1f7-96f4f58b1c57
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0R58C3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd09/14/2017:br1.2:svnDellInc.:pnInspiron7773:pvr:rvnDellInc.:rn0R58C3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7773
  dmi.product.sku: 0809
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1912911/+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 1912911] Re: When printing with my Brother hl-2170w printer I keep getting an invalid page range error on a blank page, after the desired pages are printed

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cups (Ubuntu)
   Status: New => Confirmed

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

Title:
  When printing with my Brother hl-2170w printer I keep getting an
  invalid page range error on a blank page, after the desired pages are
  printed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I run uname -a, this is basically what I get:
  "5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux"

  apt-cache policy cups gives me the following:

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
===

  4 and 5 are being answered together...

  Before the upgrade, I was able to print one or more pages, and not see the 
extra error page.
  This is the desired behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 23 13:15:24 2021
  InstallationDate: Installed on 2020-12-21 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for SCRIBE: 
dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/
  MachineType: Dell Inc. Inspiron 7773
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/SCRIBE.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/SCRIBE.ppd: Permission denied
  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.8.0-38-generic 
root=UUID=9899e123-f378-4328-a399-78cd6361f58e ro quiet splash 
resume=UUID=46e80ad1-16de-4fdf-b1f7-96f4f58b1c57
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0R58C3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd09/14/2017:br1.2:svnDellInc.:pnInspiron7773:pvr:rvnDellInc.:rn0R58C3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7773
  dmi.product.sku: 0809
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1912911/+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 1928305] Re: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter

[amk]

Lightdm shall never suspend the system itself. Instead it should
properly report idle status to systemd where a decision can be taken by
checking all relevant services, sessions and inhibitors.

In the past I have reported that idle suspend does not work while showing login 
screen:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606

After upgrade to 20.4 the system keeps suspending when one seat is
showing login screen despite of a user is typing on another seat.

The workaround here seems to help with the unwanted suspend, and still
needs the cron job to override the missing idle hint and to suspend when
applicable.

Another similar reports mentioning multiseat setup as a victim of the
gdm not playing in the team with systemd: https://gitlab.gnome.org/GNOME
/gnome-control-center/-/issues/22


** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #22
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/22

-- 
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/1928305

Title:
  Lightdm ignores power saving settings; suspends system in 20 minutes
  regardless of sleep-inactive-ac-timeout parameter

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Dear colleagues,

  We have discovered an abnormal operation of the lightdm
  (1.30.0-0ubuntu4~20.04.1) program.

  1. When no user is logged in (the initial user selection screen is
  displayed) the idle system goes into suspend (sleep) mode. The timeout
  for this event is 20 minutes.

  2. I tried to cancel the entering into sleep mode. To do this, I
  altered the sleep-inactive-ac-timeout and sleep-inactive-battery-
  timeout parameters to 0.

  The command sudo -H -u lightdm dbus-launch --exit-with-session
  gsettings list-recursively org.gnome.settings-daemon.plugins.power
  gives the output:

  root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch 
--exit-with-session gsettings list-recursively 
org.gnome.settings-daemon.plugins.power
  No protocol specified
  org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend'
  org.gnome.settings-daemon.plugins.power time-critical 300
  org.gnome.settings-daemon.plugins.power power-button-action 'suspend'
  org.gnome.settings-daemon.plugins.power 
lid-close-suspend-with-external-monitor false
  org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate'
  org.gnome.settings-daemon.plugins.power idle-dim true
  org.gnome.settings-daemon.plugins.power button-power 'suspend'
  org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend'
  org.gnome.settings-daemon.plugins.power priority 0
  org.gnome.settings-daemon.plugins.power idle-brightness 30
  org.gnome.settings-daemon.plugins.power active true
  org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate'
  org.gnome.settings-daemon.plugins.power button-suspend 'suspend'
  org.gnome.settings-daemon.plugins.power button-sleep 'hibernate'
  org.gnome.settings-daemon.plugins.power percentage-critical 3
  org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
  org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend'
  org.gnome.settings-daemon.plugins.power ambient-enabled true
  org.gnome.settings-daemon.plugins.power notify-perhaps-recall true
  org.gnome.settings-daemon.plugins.power percentage-low 10
  org.gnome.settings-daemon.plugins.power percentage-action 2
  org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'
  org.gnome.settings-daemon.plugins.power time-low 1200
  org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
  org.gnome.settings-daemon.plugins.power time-action 120
  org.gnome.settings-daemon.plugins.power use-time-for-policy true

  
  3. I checked the result, the system still suspends (goes into sleep mode) in 
20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, 
because it may affect the suspend mode. It is set to ignore.

  #  This file is part of systemd.
  #
  #  systemd is free software; you can redistribute it and/or modify it
  #  under the terms of the GNU Lesser General Public License as published by
  #  the Free Software Foundation; either version 2.1 of the License, or
  #  (at your option) any later version.
  #
  # Entries in this file show the compile time defaults.
  # You can change settings by editing this file.
  # Defaults can be restored by simply deleting this file.
  #
  # See logind.conf(5) for details.

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  #HandleLidSwitch=suspend
  #HandleLidSwitchExternalPower=suspend
  #HandleLidSwitchDocked=ignore
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIg

[Touch-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.15.2+dfsg-6

---
qtbase-opensource-src (5.15.2+dfsg-6) unstable; urgency=medium

  * Backport upstream patch to adjust QMimeDatabase behavior (LP: #1857824).
  * Make qtbase5-dev break qt5-default (see #976389, LP: #1920130).

 -- Dmitry Shachnev   Sat, 29 May 2021 12:04:21
+0300

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: In Progress => Fix Released

-- 
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/1857824

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
  http://www.w3.org/1999/xhtml";>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1920130] Re: System icons missing in kubuntu 21.04

[Launchpad Bug Tracker]

This bug was fixed in the package qtbase-opensource-src - 5.15.2+dfsg-6

---
qtbase-opensource-src (5.15.2+dfsg-6) unstable; urgency=medium

  * Backport upstream patch to adjust QMimeDatabase behavior (LP: #1857824).
  * Make qtbase5-dev break qt5-default (see #976389, LP: #1920130).

 -- Dmitry Shachnev   Sat, 29 May 2021 12:04:21
+0300

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Fix Released

-- 
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/1920130

Title:
  System icons missing in kubuntu 21.04

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src-gles package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Hirsute:
  New
Status in qtbase-opensource-src-gles source package in Hirsute:
  New
Status in qtbase-opensource-src-gles package in Debian:
  Fix Released

Bug description:
  [Impact]

  This affects Groovy → Hirsute upgrades for users who had qt5-default
  package installed.

  For these users, apt could replace libqt5gui5 with libqt5gui5-gles,
  which is not suitable for most desktop systems and can result in all
  kinds of broken UI (such as missing icons).

  [Test Plan]

  1. Get a groovy amd64 system (e.g. a chroot).
  2. Install qt5-default package.
  3. Replace groovy with hirsute in /etc/apt/sources.list.
  4. Run "apt update".
  5. Run "apt dist-upgade".

  Incorrect behavior:

  The following packages will be REMOVED:
libqt5gui5 qt5-default qtbase5-dev
  The following NEW packages will be installed:
... libqt5gui5-gles ...

  Correct behavior: only qt5-default is removed, libqt5gui5 is not
  removed and libqt5gui5-gles is not installed.

  [Where problems could occur]

  The fix is adding "Breaks: qt5-default" in three packages:
  - qtbase5-dev (built from qtbase-opensource-src source).
  - qtbase5-gles-dev (built from qtbase-opensource-src-gles source).
  - libqt5gui5-gles (built from qtbase-opensource-src-gles source).

  It can affect apt's dependency resolver. Example of a problem may be
  the resolver keeping the old behavior in some cases.

  [Other Info]

  See this post for details on what the -gles packages are:
  https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html

  See my discussion with one of the developers of apt on this issue:
  https://lists.debian.org/debian-devel/2021/05/msg00076.html
  https://lists.debian.org/debian-devel/2021/05/msg00150.html
  https://lists.debian.org/debian-devel/2021/05/msg00162.html

  Also see this comment where I collected some links to stories of users who 
were affected by this bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389#10

  [Original Description]

  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade
  initially was fine, but I then install kdenlive and krita which has
  messed up the system icons and window decorations (corners of windows
  are showing black squares).

  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.

  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04

  Looking at the following may shed some light on the problem...

  Thanks, Paul.

  more .xsession-errors
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
   RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
   of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.

[Touch-packages] [Bug 1928305] Re: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lightdm (Ubuntu)
   Status: New => Confirmed

-- 
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/1928305

Title:
  Lightdm ignores power saving settings; suspends system in 20 minutes
  regardless of sleep-inactive-ac-timeout parameter

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Dear colleagues,

  We have discovered an abnormal operation of the lightdm
  (1.30.0-0ubuntu4~20.04.1) program.

  1. When no user is logged in (the initial user selection screen is
  displayed) the idle system goes into suspend (sleep) mode. The timeout
  for this event is 20 minutes.

  2. I tried to cancel the entering into sleep mode. To do this, I
  altered the sleep-inactive-ac-timeout and sleep-inactive-battery-
  timeout parameters to 0.

  The command sudo -H -u lightdm dbus-launch --exit-with-session
  gsettings list-recursively org.gnome.settings-daemon.plugins.power
  gives the output:

  root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch 
--exit-with-session gsettings list-recursively 
org.gnome.settings-daemon.plugins.power
  No protocol specified
  org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend'
  org.gnome.settings-daemon.plugins.power time-critical 300
  org.gnome.settings-daemon.plugins.power power-button-action 'suspend'
  org.gnome.settings-daemon.plugins.power 
lid-close-suspend-with-external-monitor false
  org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate'
  org.gnome.settings-daemon.plugins.power idle-dim true
  org.gnome.settings-daemon.plugins.power button-power 'suspend'
  org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend'
  org.gnome.settings-daemon.plugins.power priority 0
  org.gnome.settings-daemon.plugins.power idle-brightness 30
  org.gnome.settings-daemon.plugins.power active true
  org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate'
  org.gnome.settings-daemon.plugins.power button-suspend 'suspend'
  org.gnome.settings-daemon.plugins.power button-sleep 'hibernate'
  org.gnome.settings-daemon.plugins.power percentage-critical 3
  org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
  org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend'
  org.gnome.settings-daemon.plugins.power ambient-enabled true
  org.gnome.settings-daemon.plugins.power notify-perhaps-recall true
  org.gnome.settings-daemon.plugins.power percentage-low 10
  org.gnome.settings-daemon.plugins.power percentage-action 2
  org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend'
  org.gnome.settings-daemon.plugins.power time-low 1200
  org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
  org.gnome.settings-daemon.plugins.power time-action 120
  org.gnome.settings-daemon.plugins.power use-time-for-policy true

  
  3. I checked the result, the system still suspends (goes into sleep mode) in 
20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, 
because it may affect the suspend mode. It is set to ignore.

  #  This file is part of systemd.
  #
  #  systemd is free software; you can redistribute it and/or modify it
  #  under the terms of the GNU Lesser General Public License as published by
  #  the Free Software Foundation; either version 2.1 of the License, or
  #  (at your option) any later version.
  #
  # Entries in this file show the compile time defaults.
  # You can change settings by editing this file.
  # Defaults can be restored by simply deleting this file.
  #
  # See logind.conf(5) for details.

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  #HandleLidSwitch=suspend
  #HandleLidSwitchExternalPower=suspend
  #HandleLidSwitchDocked=ignore
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  IdleAction=ignore
  IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192

  I came to conclusion that lightdm ignores correctly given setting for
  not suspending the system (org.gnome.settings-daemon.plugins.power
  sleep-inactive-ac-timeout 0).

  Commentaries on this finding are welcome.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  PackageArchitecture: amd64
  Tags: focal third-party-packages
  Uname: Linux 5.4.96-050496-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago)
  UserGroups: andro

[Touch-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

[I And]

@Hui Wang
Eventually, i have applied your patch to the kernel.
I have DAC1 and DAC2 now and somehow sound is better now than before, but rear 
speakers are not working.
If i change the level of DAC1 - the sound volume changes, but the changing of 
DAC2 level does nothing.

Update:
The alsa-info is here
http://alsa-project.org/db/?f=08f7b48d840592556650cb156e51831780127958

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed

[Sean Davis]

Last updated in 2016. Is this still an issue with these greeters?

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

** Changed in: lightdm-gtk-greeter (Ubuntu)
   Status: Confirmed => Incomplete

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

-- 
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/1322275

Title:
  lightdm sessions started by dm-tool lock (or a session locker) never
  get closed

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Incomplete
Status in lightdm-gtk-greeter package in Ubuntu:
  Incomplete
Status in upstart package in Ubuntu:
  Incomplete

Bug description:
  dm-tool lock starts a new lightdm greeter (for unlocking) and a new
  logind session. After unlocking the greeter disappears, but the logind
  session never closes. loginctl session status c24 reports something
  like:

  c24 - lightdm (103)
 Since: Thu 2014-05-22 18:38:27 CEST; 30min ago
Leader: 7872
  Seat: seat0; vc8
   Display: :1
   Service: lightdm-greeter; type x11; class greeter
 State: closing
CGroup: systemd:/user/103.user/c24.session
└─7907 init --user --startup-event indicator-services-start

  This results in an accumulation of stale lightdm sessions after using
  e.g. a session locker for a while.

  I get this issue on a freshly installed and fully updated Xubuntu
  14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1322275/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Steve Langasek]

** Changed in: ubuntu-cdimage
 Assignee: GEO (geo218) => (unassigned)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[GEO]

** Changed in: ubuntu-cdimage
 Assignee: (unassigned) => GEO (geo218)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l

[Touch-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

[Dmitry Shachnev]

The fix should land in Impish (21.10) very soon:
https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.15.2+dfsg-6.

Do you also want a fix for Hirsute (21.04)? If yes, you can help me by
filling the SRU template in the description (see
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template).

-- 
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/1857824

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
  http://www.w3.org/1999/xhtml";>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1857824/+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 1920130] Re: System icons missing in kubuntu 21.04

[Dmitry Shachnev]

** Description changed:

+ [Impact]
+ 
+ This affects Groovy → Hirsute upgrades for users who had qt5-default
+ package installed.
+ 
+ For these users, apt could replace libqt5gui5 with libqt5gui5-gles,
+ which is not suitable for most desktop systems and can result in all
+ kinds of broken UI (such as missing icons).
+ 
+ [Test Plan]
+ 
+ 1. Get a groovy amd64 system (e.g. a chroot).
+ 2. Install qt5-default package.
+ 3. Replace groovy with hirsute in /etc/apt/sources.list.
+ 4. Run "apt update".
+ 5. Run "apt dist-upgade".
+ 
+ Incorrect behavior:
+ 
+ The following packages will be REMOVED:
+   libqt5gui5 qt5-default qtbase5-dev
+ The following NEW packages will be installed:
+   ... libqt5gui5-gles ...
+ 
+ Correct behavior: only qt5-default is removed, libqt5gui5 is not removed
+ and libqt5gui5-gles is not installed.
+ 
+ [Where problems could occur]
+ 
+ The fix is adding "Breaks: qt5-default" in three packages:
+ - qtbase5-dev (built from qtbase-opensource-src source).
+ - qtbase5-gles-dev (built from qtbase-opensource-src-gles source).
+ - libqt5gui5-gles (built from qtbase-opensource-src-gles source).
+ 
+ It can affect apt's dependency resolver. Example of a problem may be the
+ resolver keeping the old behavior in some cases.
+ 
+ [Other Info]
+ 
+ See this post for details on what the -gles packages are:
+ https://mitya57.me/weblog/2020/01/qt-opengl-es-packages-available.html
+ 
+ See my discussion with one of the developers of apt on this issue:
+ https://lists.debian.org/debian-devel/2021/05/msg00076.html
+ https://lists.debian.org/debian-devel/2021/05/msg00150.html
+ https://lists.debian.org/debian-devel/2021/05/msg00162.html
+ 
+ Also see this comment where I collected some links to stories of users who 
were affected by this bug:
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976389#10
+ 
+ [Original Description]
+ 
  Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially
  was fine, but I then install kdenlive and krita which has messed up the
  system icons and window decorations (corners of windows are showing
  black squares).
  
  I have been through all the normal checks and even created a new user,
  but the bug still persists. The system Icons are broken in the system
  and nothing to do with the user account.
  
  lsb_release -rd
  Description:Ubuntu Hirsute Hippo (development branch)
  Release:21.04
  
  Looking at the following may shed some light on the problem...
  
  Thanks, Paul.
  
- more .xsession-errors 
+ more .xsession-errors
  property "maximumWidth"
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
- 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
+  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
+ 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
+  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not 
permitted on grayscale PNG
  QSGTextureAtlas: texture atlas allocation failed, code=501
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94:
 TypeError: Cannot read pro
  perty 'position' of null
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93:
 TypeError: Cannot read pro
  perty 'background' of null
  file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: 
TypeError: Cannot read property 'useLabel'
-  of null
+  of null
  file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: 
QML ColumnLayout: Cannot anchor to an ite
  m that isn't a parent or sibling.
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, 
resource id: 69206064, major code: 18 (ChangePr
  operty), minor code: 0
  qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, 
resource id: 69206065, major code: 18 (ChangePr
  operty), minor code: 0
  QQmlEngine::setContextForObject(): Object already has a QQmlContext
  
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop 
detected for property "maximumWidth"
- 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9:
 QML
-  RowLayout (parent or ances

[Touch-packages] [Bug 1930145] Re: IBus Panel Show Icon on system tray doesn't persist

[Gunnar Hjalmarsson]

Thanks for your report! Yes, it doesn't seem to honor the "Show icon on
system tray" setting at login. Can't tell ATM if ibus or KDE is
responsible for that.

With that said, and considering that you prefer it to not be shown, I
can't help suspecting that ibus is running unnecessarily on your system.

Up to 20.04 ibus was installed for everyone on Kubuntu but only started
by default if the language was Chinese, Japanese, Korean or Vietnamese.
>From 20.10 ibus is not installed for everyone, but if you install it
it's started automatically. The idea is that if ibus is installed it's
assumed that you want to use it. (This can be controlled via the "Input
Method Configuration" GUI.) So unless you use some IBus input method,
the natural solution to fix it for you may be to simply uninstall ibus.

Please clarify your actual use case.

** Changed in: ibus (Ubuntu)
   Status: New => Incomplete

-- 
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/1930145

Title:
  IBus Panel Show Icon on system tray doesn't persist

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  After a reboot in Kubuntu 21.04 (and 20.10) the IBus Panel icon
  appears in the system tray despite "Show icon on system tray" NOT
  being checked.  Right clicking on the IBus Panel icon, checking "Show
  icon on system tray" and then unchecking again it causes the icon to
  be correctly hidden.  But the problem reappears after the next reboot.

  Another user reporting what is almost certainly the same behavior:
  https://www.reddit.com/r/kde/comments/j91t8f/ibus_panel_icon_in_system_tray/

  And this is an _identical_ bug report from 2012, so maybe it's a regression 
of some sort?
  https://bugzilla.redhat.com/show_bug.cgi?id=877135

  Based om the trouble shooting requested at that time I get:

  $ gconftool-2 --get /desktop/ibus/panel/show_icon_on_systray
  No value set for `/desktop/ibus/panel/show_icon_on_systray'

  Note that I am running KDE, in case that's the important detail.

  The primary problem is that if you click on it accidentally and close
  the panel, you lose all keyboard input.

  $ lsb_release -rd
  Description:Ubuntu 21.04
  Release:21.04
  $ apt-cache policy ibus
  ibus:
Installed: 1.5.24-1
Candidate: 1.5.24-1
Version table:
   *** 1.5.24-1 500
  500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1930145/+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 1930153] [NEW] Unattended upgrades does not report some updates that can't be installed automatically

[Simon Arlott]

Public bug reported:

When there are packages that fail a "sanity check" they are not reported
[by email] as expected. This results in updates being ignored
indefinitely.

More details: https://github.com/mvo5/unattended-upgrades/issues/223

This is fixed in version 1.18 but bionic is using version 1.1:
https://github.com/mvo5/unattended-upgrades/pull/255

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.14
Uname: Linux 5.4.108+ x86_64
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 30 10:14:02 2021
InstallationDate: Installed on 2014-05-10 (2576 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: Upgraded to bionic on 2018-11-24 (917 days ago)
modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-03-22T09:10:38.530578
mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2021-05-14T10:28:25.361164

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Unattended upgrades does not report some updates that can't be
  installed automatically

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  When there are packages that fail a "sanity check" they are not
  reported [by email] as expected. This results in updates being ignored
  indefinitely.

  More details: https://github.com/mvo5/unattended-upgrades/issues/223

  This is fixed in version 1.18 but bionic is using version 1.1:
  https://github.com/mvo5/unattended-upgrades/pull/255

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.14
  Uname: Linux 5.4.108+ x86_64
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 30 10:14:02 2021
  InstallationDate: Installed on 2014-05-10 (2576 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to bionic on 2018-11-24 (917 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  modified.conffile..etc.apt.apt.conf.d.50unattended-upgrades: [modified]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-03-22T09:10:38.530578
  mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 
2021-05-14T10:28:25.361164

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1930153/+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 1926697] Re: gdebi does not start w msg 'Download failed'

[corrado venturini]

Note: gdebi works fine if i click on a .deb and select 'open with gdebi'

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

Title:
  gdebi does not start w msg 'Download failed'

Status in gdebi package in Ubuntu:
  New

Bug description:
  Just click on gdebi icon on dash.
  problem occurs in both xorg and wayland sessions

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gdebi 0.9.5.7+nmu4
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 30 08:15:15 2021
  ExecutablePath: /usr/share/gdebi/gdebi-gtk
  InstallationDate: Installed on 2021-04-23 (6 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  InterpreterPath: /usr/bin/python3.9
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1926697/+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