[Desktop-packages] [Bug 2061856]

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. Your bug report is more likely to get attention if it is made in
English, since this is the language understood by the majority of Ubuntu
developers.  Additionally, please only mark a bug as "security" if it
shows evidence of allowing attackers to cross privilege boundaries or to
directly cause loss of data/privacy. Please feel free to report any
other bugs you may find.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061856

Title:
  gnome terminal

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ola Bomdia Eu estou com um problema no terminal shell do ubuntu ele
  esta fechando assim que clico para abrir elefecha automaticamente ja
  tentetei usar outro terminal e tambem faz a mesma coisa eu tenho  o
  fish instalado tambem mas esta fazendo a mesma coisa fechando
  automaticamente, o unico que funciona e o terminal do vscode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18
  Uname: Linux 4.15.0-213-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.29
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 16 12:04:00 2024
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Core Processor Integrated Graphics 
Controller [1019:1324]
  InstallationDate: Installed on 2023-07-23 (267 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  Lsusb:
   Bus 002 Device 006: ID 04f3:0210 Elan Microelectronics Corp. Optical Mouse
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEGAWARE H55H-CM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic 
root=UUID=3cfdb2f5-e8ec-4728-844a-29c984321037 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MW-H55H-CM
  dmi.board.vendor: MEGAWARE
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: M0418501001
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEGAWARE
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/18/2010:svnMEGAWARE:pnH55H-CM:pvrMEGAWARE:rvnMEGAWARE:rnMW-H55H-CM:rvr1.0:cvnMEGAWARE:ct3:cvr1.0:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: H55H-CM
  dmi.product.version: MEGAWARE
  dmi.sys.vendor: MEGAWARE
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.15
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Apr  4 13:22:01 2024
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPS/2+USB Mouse   MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.15

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


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

[Desktop-packages] [Bug 2061856] Re: gnome terminal

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061856

Title:
  gnome terminal

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ola Bomdia Eu estou com um problema no terminal shell do ubuntu ele
  esta fechando assim que clico para abrir elefecha automaticamente ja
  tentetei usar outro terminal e tambem faz a mesma coisa eu tenho  o
  fish instalado tambem mas esta fazendo a mesma coisa fechando
  automaticamente, o unico que funciona e o terminal do vscode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18
  Uname: Linux 4.15.0-213-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.29
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 16 12:04:00 2024
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Core Processor Integrated Graphics 
Controller [1019:1324]
  InstallationDate: Installed on 2023-07-23 (267 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  Lsusb:
   Bus 002 Device 006: ID 04f3:0210 Elan Microelectronics Corp. Optical Mouse
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEGAWARE H55H-CM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic 
root=UUID=3cfdb2f5-e8ec-4728-844a-29c984321037 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MW-H55H-CM
  dmi.board.vendor: MEGAWARE
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: M0418501001
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEGAWARE
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/18/2010:svnMEGAWARE:pnH55H-CM:pvrMEGAWARE:rvnMEGAWARE:rnMW-H55H-CM:rvr1.0:cvnMEGAWARE:ct3:cvr1.0:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: H55H-CM
  dmi.product.version: MEGAWARE
  dmi.sys.vendor: MEGAWARE
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.15
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Apr  4 13:22:01 2024
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPS/2+USB Mouse   MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.15

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


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

[Desktop-packages] [Bug 2060575] [NEW] gnome-keyring fails to automatically unlock login keyring after recent updates in noble

[Alex Murray]

Public bug reported:

After installing recent updates in 24.04, upon logging in the gnome-
shell based UI pops up saying that the login keyring was not unlocked
and asking for the users password to be input to unlock it.

Similarly a second, non-gnome-shell based UI is also present asking the
same thing. Will try and get a screenshot to attach.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libpam-gnome-keyring 46.1-2build1
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  9 06:16:46 2024
InstallationDate: Installed on 2021-08-03 (980 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


** Tags: amd64 apport-bug noble wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2060575

Title:
  gnome-keyring fails to automatically unlock login keyring after recent
  updates in noble

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  After installing recent updates in 24.04, upon logging in the gnome-
  shell based UI pops up saying that the login keyring was not unlocked
  and asking for the users password to be input to unlock it.

  Similarly a second, non-gnome-shell based UI is also present asking
  the same thing. Will try and get a screenshot to attach.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libpam-gnome-keyring 46.1-2build1
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 06:16:46 2024
  InstallationDate: Installed on 2021-08-03 (980 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago)

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


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

[Desktop-packages] [Bug 2056458] Re: upgrade to thunderbird snap, missing snapd depdency

[Alex Murray]

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056458

Title:
  upgrade to thunderbird snap, missing snapd depdency

Status in thunderbird package in Ubuntu:
  New

Bug description:
  latest upgrade on noble replaces thunderbird with snap version.
  This package does not provide snapd dependency.
  Simple dist-upgrade on installations (lxqt minimal or server installations) 
not having snapd installed at all breaking thunderbird because of missing snapd.
  There is another problem with the missing snapd depdency: the package could 
not be blocked via pin priority on snapd (when i want use package with the same 
name from anothe ppa).
  In general the snapd thunderbird is big crap (cursor theme not working, much 
slower, x11 ssh forwarding issues etc).

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


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

[Desktop-packages] [Bug 2054924] Re: color emoji are broken with fontconfig 2.15

[Alex Murray]

As per
https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/409#note_2298588
this can also be fixed by adding an additional rule to
/etc/fonts/conf.d/70-no-bitmaps.conf of the form:

false

** Bug watch added: gitlab.freedesktop.org/fontconfig/fontconfig/-/issues #409
   https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/409

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/2054924

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Confirmed

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

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


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

[Desktop-packages] [Bug 2039577] Re: gnome-control-center incorrectly claims remote login is off

[Alex Murray]

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2039577

Title:
  gnome-control-center incorrectly claims remote login is off

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  GNOME control center offers a way to disable or enable remote shell
  (ssh) connections. This functionality is outsourced to
  /usr/libexec/cc-remote-login-helper which starts and stops the systemd
  service ssh.service using the code:

if (!cc_disable_service (SSHD_SERVICE, G_BUS_TYPE_SYSTEM, ))
...

if (!cc_enable_service (SSHD_SERVICE, G_BUS_TYPE_SYSTEM,
  ))

  
  The irony is that ssh.service is socket activated:

  zyga@x240:~$ systemctl status ssh.service
  ● ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   └─00-socket.conf
   Active: active (running) since Tue 2023-10-17 16:40:04 CEST; 21s ago
  TriggeredBy: ● ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 7055 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
 Main PID: 7056 (sshd)
Tasks: 1 (limit: 9305)
   Memory: 1.4M
  CPU: 21ms
   CGroup: /system.slice/ssh.service
   └─7056 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

  paź 17 16:40:04 x240 systemd[1]: Starting ssh.service - OpenBSD Secure Shell 
server...
  paź 17 16:40:04 x240 sshd[7056]: Server listening on :: port 22.
  paź 17 16:40:04 x240 systemd[1]: Started ssh.service - OpenBSD Secure Shell 
server.

  
  In effect, it will always activate again whenever someone attempts to connect.

  This bug is a security vulnerability, as users may be prone to attacks
  while thinking remote shell is disabled.

  I would suggest to *mask* the service, so that it cannot be socket
  activated.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 16:36:23 2023
  InstallationDate: Installed on 2023-10-17 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu

[Alex Murray]

Subscribing ~ubuntu-archive to look at this request.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-pptp in Ubuntu.
https://bugs.launchpad.net/bugs/2041751

Title:
  RM: Remove dangerously insecure MPPE PPTP from Ubuntu

Status in linux package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in pptp-linux package in Ubuntu:
  New
Status in pptpd package in Ubuntu:
  New

Bug description:
  Remove dangerously insecure MPPE PPTP from Ubuntu

  https://pptpclient.sourceforge.net/protocol-security.phtml

  It has been dead for over 20 years now.

  IPSec OpenVPN Strongswan are much better alternatives.

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


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

[Desktop-packages] [Bug 2044588] Re: Gnome crash after suspend mode , all openapps auto closed

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2044588

Title:
  Gnome crash after suspend mode , all openapps auto closed

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  ubuntu-bug gnome-shell - all open apps crashed after suspend mode

  chrome, 
  fir fox, 
  terminal etc..

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.9-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-37.38~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 25 08:54:29 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2023-11-23 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  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/2044588/+subscriptions


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

[Desktop-packages] [Bug 2044625] Re: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to install/upgrade: зацикливание триггеров, отмена работы

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/2044625

Title:
  package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to
  install/upgrade: зацикливание триггеров, отмена работы

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  ubuntu update to lunar lobster version

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.15.0-89.99-generic 5.15.126
  Uname: Linux 5.15.0-89-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Nov 26 02:02:30 2023
  ErrorMessage: зацикливание триггеров, отмена работы
  InstallationDate: Installed on 2023-11-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf-2.0-0:amd64 2.42.10+dfsg-1build1 failed to 
install/upgrade: зацикливание триггеров, отмена работы
  UpgradeStatus: Upgraded to lunar on 2023-11-25 (0 days ago)

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


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

[Desktop-packages] [Bug 2044707] Re: package thunderbird 1:115.4.1+build1-0ubuntu0.23.10.1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2044707

Title:
  package thunderbird 1:115.4.1+build1-0ubuntu0.23.10.1 failed to
  install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error
  exit status 2

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Will not update my mail account

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: thunderbird 1:115.4.1+build1-0ubuntu0.23.10.1
  Uname: Linux 6.4.6-060406-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.27.0-0ubuntu5
  AptOrdering:
   thunderbird-locale-en:amd64: Install
   thunderbird:amd64: Install
   thunderbird-gnome-support:amd64: Install
   thunderbird-locale-en-us:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  graham263595 F wireplumber
   /dev/snd/seq:graham263579 F pipewire
  BuildID: 20231024181440
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Mon Nov 27 18:21:10 2023
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  ForcedLayersAccel: False
  InstallationDate: Installed on 2023-07-13 (137 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IpRoute:
   default via 192.168.1.1 dev enp3s0 proto dhcp src 192.168.1.112 metric 100 
   169.254.0.0/16 dev enp3s0 scope link metric 1000 
   192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.112 metric 
100
  NoProfiles: True
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird 1:115.4.1+build1-0ubuntu0.23.10.1 failed to 
install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2010
  dmi.bios.release: 15.35
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3069
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 21.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 33.20
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.23:bd12/21/2010:br15.35:efr33.20:svnHewlett-Packard:pnCompaqPresarioCQ61NotebookPC:pvrRev1:rvnHewlett-Packard:rn3069:rvr21.14:cvnHewlett-Packard:ct10:cvrN/A:skuNW982PA#ABG:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario CQ61 Notebook PC
  dmi.product.sku: NW982PA#ABG
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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


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

[Desktop-packages] [Bug 1884759] Re: [snap] U2f yubikey not recognized until unplugged and plugged back in

[Alex Murray]

Thanks @nteodosio - I can confirm that refreshing chromium to the edge
channel and then manually connection hardware-observe allows u2f keys to
work OOTB as expected. Now we just need to organise auto-connect :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1884759

Title:
  [snap] U2f yubikey not recognized until unplugged and plugged back in

Status in chromium-browser package in Ubuntu:
  Fix Committed

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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


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

[Desktop-packages] [Bug 1884759] Re: [snap] U2f yubikey not recognized until unplugged and plugged back in

[Alex Murray]

As per https://forum.snapcraft.io/t/request-for-auto-connection-of-
hardware-observe-for-brave/37604 it sounds like if the chromium snap
plugged hardware-observe and had this auto-connected, this should be
sufficient to fix this bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1884759

Title:
  [snap] U2f yubikey not recognized until unplugged and plugged back in

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I was previously using u2f from yubikey in chromium snap, but now it doesn't 
work.
  No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
  U2f still works in firefox installed as deb.

  # snap connections chromium | grep u2f
  u2f-devices   chromium:u2f-devices   :u2f-devices 
   manual

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


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

[Desktop-packages] [Bug 2041478] Re: /usr/bin/gnome-calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event

[Alex Murray]

Ah I see this is already in 45.1-1 in noble

** Also affects: gnome-calendar (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Also affects: gnome-calendar (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: gnome-calendar (Ubuntu Noble)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/2041478

Title:
  /usr/bin/gnome-
  
calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event

Status in gnome-calendar package in Ubuntu:
  Fix Committed
Status in gnome-calendar source package in Mantic:
  New
Status in gnome-calendar source package in Noble:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
45.0-1, the problem page at 
https://errors.ubuntu.com/problem/556afecb4d0b594b8bfdac2aa521cb12fa243a76 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 2041478] Re: /usr/bin/gnome-calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event

[Alex Murray]

I can reliably reproduce this by just launching gnome-calendar on
mantic.

This looks to be the same issue as the upstream
https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1106 which has an
associated fix in https://gitlab.gnome.org/GNOME/gnome-
calendar/-/merge_requests/366

** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #1106
   https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1106

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/2041478

Title:
  /usr/bin/gnome-
  
calendar:6:g_assertion_message:g_assertion_message_expr:recalculate_layout_blocks:gcal_month_view_row_add_event:gcal_month_view_add_event

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-calendar.  This problem was most recently seen with package version 
45.0-1, the problem page at 
https://errors.ubuntu.com/problem/556afecb4d0b594b8bfdac2aa521cb12fa243a76 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 2039607] Re: ClamTK not working properly

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

** Package changed: gnome-terminal (Ubuntu) => clamtk (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/2039607

Title:
  ClamTK not working properly

Status in clamtk package in Ubuntu:
  New

Bug description:
  Clam scans and detects viruses, but there is no way to see what it has
  detected, quarantine it and remove it.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-terminal 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 23:18:59 2023
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   LANG=pl_PL.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2039589] Re: Nwidia driver Ubuntu bug

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2039589

Title:
  Nwidia driver Ubuntu bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Nvidia driver error 470: UFW main window not displayed properly and
  Help not displayed. The issue affects Ubuntu 22.04.3 LTS, Ubuntu 23.10
  and Linux Mint.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-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  470.199.02  Thu May 11 
11:46:56 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 18:13:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology GK107 [GeForce GTX 650] [10b0:0fc6]
  InstallationDate: Installed on 2023-10-16 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic 
root=UUID=7faab2db-29fa-4024-ae67-d6f019c15904 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-S1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr10b:bd02/25/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.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: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 2037655] Re: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs

[Alex Murray]

Proposed fix for snapd in https://github.com/snapcore/snapd/pull/13304

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2037655

Title:
  dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor"
  spamming logs

Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  On the latest 23.10 Mantic beta using firefox 118.0 spams the log with
  message:

  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gnome/Mutter/IdleMonitor/Core"
  interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime"
  mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox"
  peer_pid=3234 peer_label="unconfined"

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


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

[Desktop-packages] [Bug 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

[Alex Murray]

This is planned to be fixed in the apparmor package itself in mantic by
proving a suitable profile for chrome - something like the following in
/etc/apparmor.d/opt.google.chrome.chrome


abi ,

include 

/opt/google/chrome/chrome flags=(unconfined) {
  userns,

  # Site-specific additions and overrides. See local/README for details.
  include if exists 
}

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2017980

Title:
  FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)

Status in OEM Priority Project:
  New
Status in linux-meta-nvidia-5.19 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I 
experience that google-chrome crashes.
  It shows

  ```shell
  [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap (core dumped)".
  ```

  To be honest I don't think it has anything to do with google-chrome at all.
  When google-chrome starts it (normally) request the system key-manager 
(KWallet in my case) for access to the users keys before it actually shows 
anything from chrome. Not even that part (the KWallet password box) shows up.

  I can only reproduce this problem with this specific kernel. It should
  be possible to take google-chrome out of the equation by using another
  application that starts by request the desktop key manager for access.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-nvidia-5.19 (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92
  Uname: Linux 5.15.0-1023-nvidia x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Apr 28 11:23:23 2023
  InstallationDate: Installed on 2016-01-08 (2666 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: linux-meta-nvidia-5.19
  UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2017980/+subscriptions


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

[Desktop-packages] [Bug 2031406] Re: [MIR] libei

[Alex Murray]

I reviewed libei 1.0.0-0ubuntu2 as checked into mantic.  This shouldn't be
considered a full audit but rather a quick gauge of maintainability.

libei is a library to emulate input, particularly for the Wayland graphics 
stack. It provides 3 components
  - libei - the library to emulate inputs on the client side
  - libeis - a library to process these inputs on the server side
  - oeffis - a library for communicating with the XDG RemoteDesktop Portal

- CVE History
  - None
- Build-Depends
  - No interesting / security relevant dependencies
- No pre/post inst/rm scripts
- No init scripts
- No systemd units
- No dbus system/session services
- No setuid binaries
- No binaries in PATH
- No sudo fragments
- No polkit files
- No udev rules
- unit tests / autopkgtests
  - No autopkgtests but since this package is just a library with minimal 
external depencies, I don't think this should be a blocker.
  - unit tests look quite comprehensive:

1/9 libei / unit-tests-utils  OK  0.02s
2/9 libei / unit-tests-ei OK  0.02s
3/9 libei / unit-tests-eisOK  0.02s
4/9 libei / unit-tests-oeffis OK  0.01s
5/9 libei / eierpeckenOK  0.08s
6/9 libei:python / python-black   OK  0.49s
7/9 libei:python / scanner-pytest OK  0.52s
8/9 libei:python / oeffis-pytest  OK  2.58s
9/9 libei:python / protocol-test  OK  6.61s

Ok: 9
Expected Fail:  0
Fail:   0
Unexpected Pass:0
Skipped:0
Timeout:0

- No cron jobs
- Build logs contain a couple warnings - the second of which should ideally be 
fixed:
../tools/ei-demo-client.c:102:9: warning: ignoring return value of read 
declared with attribute warn_unused_result [-Wunused-result]
../src/util-sources.c:311:9: warning: ignoring return value of read declared 
with attribute warn_unused_result [-Wunused-result]


- No processes spawned
- Memory management
  - Given this is written in C there is suprisingly little dynamic memory 
management - when malloc() etc are used, the code has a tendency to use 
assert() to die immediately if memory fails to be allocated. Whilst not very 
graceful, this is pretty standard in higher order libraries like glib etc so is 
not really concerning to see it here. In general the code appears quite 
defensive too.
- File IO
  - Only really used for creating a lock file and reading its own cmdline - 
again this is quite safe.
- Logging
  - Appears quite careful, no apparent uses of directives that might be 
vulnerable to string-format attacks etc
- Environment variable usage
  - Only uses XDG_RUNTIME_DIR and its own LIBEI_SOCKET environment variables
- No apparent use of privileged functions
- Uses rand() to assign a non-overlapping token for requests to 
xdg-desktop-portal - this is fine, they are not expected to be 
cryptographically secure etc, they just need to be unique within a session
- No use of temp files
- Uses AF_UNIX sockets for local communication
- No use of WebKit
- No use of PolicyKit

- No significant cppcheck results
- One significant Coverity result
  - I reported this upstream 
https://gitlab.freedesktop.org/libinput/libei/-/issues/43 who fixed it within 
24 hours - along with a related issue they noticed
- No significant shellcheck results
- No significant bandit results
  - all issues identified are in the test suite and most can be ignored (ie. 
use of assert etc.)
- No significant govulncheck results
- No significant Semgrep results

In general libei looks to be quite a well-written and maintained code-
base. The upstream is responsive to issues and easy to work with as
well.

Security team ACK for promoting libei to main.


** Bug watch added: gitlab.freedesktop.org/libinput/libei/-/issues #43
   https://gitlab.freedesktop.org/libinput/libei/-/issues/43

** Changed in: libei (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2031406

Title:
  [MIR] libei

Status in libei package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  [Availability]
  - The package libei is already in Ubuntu universe.
  - The package libei builds for the architectures it is designed to work on.
  - Link to package https://launchpad.net/ubuntu/+source/libei

  [Rationale]
  - The package libei is required in Ubuntu main as a new required dependency 
for Mutter 45
  - The package libei will generally be useful for a large part of our user base
  - The package libei is a new runtime dependency of package mutter that we 
already support
  - There is no other/better way to solve this that is already in main or 
should go universe->main instead of this.

  The package libei is required in Ubuntu main no later than August 17
  due to Ubuntu 23.10 Feature Freeze. 

[Desktop-packages] [Bug 1969141] Re: [snap] seccomp denials for syscall=312, 314, 330 on amd64

[Alex Murray]

Limited use for sys_kcmp (aka the kcmp() system call) was added to the
base template in https://github.com/snapcore/snapd/pull/12673 - this
should be available in snapd >= 2.60 if you want to try testing that
snapd version with chromium

The sched_setattr() is a known limitation of the current snapd seccomp
sandbox where a snap can set the scheduling policy for a given thread
*by that same thread* only - so if some coordinator thread wants to set
the policy for a child thread that will be denied unfortunately. But
this is usually just noise and does not impact the application in
general.

Currently no snapd interface nor the base template itself provides
access to the pkey system calls so this is a missing feature of snapd.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1969141

Title:
  [snap] seccomp denials for syscall=312,314,330 on amd64

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  New

Bug description:
  # Steps to reproduce

  1) Install Chromium's snap
  snap install chromium
  2) Monitor logs
  journalctl -o cat -f --grep chromium
  3) Start Chromium

  journalctl will be filled with errors due to some syscalls not
  permitted by the seccomp policy, like those:

  Apr 14 11:18:14 sdeziel-lemur audit[1734639]: SECCOMP auid=1000 uid=1000 
gid=1000 ses=3 subj=snap.chromium.chromium pid=1734639 comm="chrome" 
exe="/snap/chromium/1961/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=314 compat=0 ip=0x77ccfac2276d code=0x5
  Apr 14 11:18:14 sdeziel-lemur audit[1734751]: SECCOMP auid=1000 uid=1000 
gid=1000 ses=3 subj=snap.chromium.chromium pid=1734751 comm="chrome" 
exe="/snap/chromium/1961/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=312 compat=0 ip=0x7a9d5be7f76d code=0x5
  Apr 14 11:18:14 sdeziel-lemur audit[1734790]: SECCOMP auid=1000 uid=1000 
gid=1000 ses=3 subj=snap.chromium.chromium pid=1734790 comm="chrome" 
exe="/snap/chromium/1961/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=330 compat=0 ip=0x735f8ecd303b code=0x5

  # Additional information
  $ uname -a
  Linux sdeziel-lemur 5.13.0-39-generic #44~20.04.1-Ubuntu SMP Thu Mar 24 
16:43:35 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  $ snap list chromium
  Name  VersionRev   Tracking   Publisher   Notes
  chromium  100.0.4896.88  1961  latest/stable  canonical✓  -

  $ snap connections chromium
  Interface PlugSlot
 Notes
  audio-playbackchromium:audio-playback 
:audio-playback  -
  audio-record  chromium:audio-record   
:audio-record-
  bluez chromium:bluez  :bluez  
 -
  browser-support   chromium:browser-sandbox
:browser-support -
  camerachromium:camera :camera 
 manual
  content[gnome-3-38-2004]  chromium:gnome-3-38-2004
gnome-3-38-2004:gnome-3-38-2004  -
  content[gtk-3-themes] chromium:gtk-3-themes   
gtk-common-themes:gtk-3-themes   -
  content[icon-themes]  chromium:icon-themes
gtk-common-themes:icon-themes-
  content[sound-themes] chromium:sound-themes   
gtk-common-themes:sound-themes   -
  cups-control  chromium:cups-control   
:cups-control-
  desktop   chromium:desktop:desktop
 -
  desktop-legacychromium:desktop-legacy 
:desktop-legacy  -
  gsettings chromium:gsettings  :gsettings  
 -
  home  chromium:home   :home   
 -
  joystick  chromium:joystick   :joystick   
 -
  mount-observe chromium:mount-observe  -   
 -
  mpris -   
chromium:mpris   -
  network   chromium:network:network
 -
  network-bind  chromium:network-bind   
:network-bind-
  network-manager   chromium:network-manager-   
 -
  openglchromium:opengl :opengl 
 -
  password-manager-service  chromium:password-manager-service   -   
   

[Desktop-packages] [Bug 2015873] Re: Firefox does not open when clicked -- first time

[Alex Murray]

This sounds very similar to
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2011806

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2015873

Title:
  Firefox does not open when clicked -- first time

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When clicking Firefox starter in the side bar, the browser does not
  load. The cursor changes into a running action but nothing happens.
  Close with the drop down menu and click the starter again does open
  the Firefox browser. First attempt to open the browser is failing.

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


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

[Desktop-packages] [Bug 2008428] [NEW] xdg-desktop-portal-gnome fails to startup after upgrading to 44~beta-1

[Alex Murray]

Public bug reported:

Since upgrading xdg-desktop-portal-gnome to 44~beta-1, it fails to
startup (along with xdg-desktop-portal as well) - downgrading to 43.1-2
fixes the issue. As a result of this launching any GTK application seems
to take ~25 seconds - I assume that GTK or some such is trying to
contact the portal backend over dbus and then eventually timing out.

Relevant excerpts from journalctl:


[amurray:~] 3 $ systemctl status --user xdg-desktop-portal-gnome.service
× xdg-desktop-portal-gnome.service - Portal service (GNOME implementation)
 Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-gnome.service; 
static)
 Active: failed (Result: timeout) since Fri 2023-02-24 09:39:03 ACDT; 57s 
ago
Process: 52457 ExecStart=/usr/libexec/xdg-desktop-portal-gnome 
(code=killed, signal=TERM)
   Main PID: 52457 (code=killed, signal=TERM)
CPU: 11ms

Feb 24 09:37:33 graphene systemd[7592]: Starting Portal service (GNOME 
implementation)...
Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal-gnome.service: start 
operation timed out. Terminating.
Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal-gnome.service: 
Failed with result 'timeout'.
Feb 24 09:39:03 graphene systemd[7592]: Failed to start Portal service (GNOME 
implementation).


[amurray:~] 1 $ systemctl status --user xdg-desktop-portal.service
× xdg-desktop-portal.service - Portal service
 Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static)
 Active: failed (Result: timeout) since Fri 2023-02-24 09:39:03 ACDT; 53s 
ago
Process: 52453 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, 
signal=TERM)
   Main PID: 52453 (code=killed, signal=TERM)
CPU: 15ms

Feb 24 09:37:33 graphene systemd[7592]: Starting Portal service...
Feb 24 09:38:23 graphene xdg-desktop-por[52453]: Failed to create settings 
proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was reached
Feb 24 09:38:48 graphene xdg-desktop-por[52453]: Failed to create file chooser 
proxy: Error calling StartServiceByName for 
org.freedesktop.impl.portal.desktop.gnome: Timeout was reached
Feb 24 09:38:48 graphene xdg-desktop-por[52453]: No skeleton to export
Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal.service: start 
operation timed out. Terminating.
Feb 24 09:39:03 graphene systemd[7592]: xdg-desktop-portal.service: Failed with 
result 'timeout'.
Feb 24 09:39:03 graphene systemd[7592]: Failed to start Portal service.


[amurray:~] $ systemctl status --user xdg-desktop-portal-gtk.service
○ xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)
 Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-gtk.service; 
static)
 Active: inactive (dead)

Feb 24 09:36:22 graphene systemd[7592]: Starting Portal service (GTK/GNOME 
implementation)...
Feb 24 09:36:22 graphene systemd[7592]: Started Portal service (GTK/GNOME 
implementation).

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xdg-desktop-portal-gnome 44~beta-1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.24.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 24 09:36:16 2023
InstallationDate: Installed on 2021-08-03 (569 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
SourcePackage: xdg-desktop-portal-gnome
UpgradeStatus: Upgraded to lunar on 2023-01-27 (27 days ago)

** Affects: xdg-desktop-portal-gnome (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/2008428

Title:
  xdg-desktop-portal-gnome fails to startup after upgrading to 44~beta-1

Status in xdg-desktop-portal-gnome package in Ubuntu:
  New

Bug description:
  Since upgrading xdg-desktop-portal-gnome to 44~beta-1, it fails to
  startup (along with xdg-desktop-portal as well) - downgrading to
  43.1-2 fixes the issue. As a result of this launching any GTK
  application seems to take ~25 seconds - I assume that GTK or some such
  is trying to contact the portal backend over dbus and then eventually
  timing out.

  Relevant excerpts from journalctl:

  
  [amurray:~] 3 $ systemctl status --user xdg-desktop-portal-gnome.service
  × xdg-desktop-portal-gnome.service - Portal service (GNOME implementation)
   Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-gnome.service; 
static)
   Active: failed (Result: timeout) since Fri 2023-02-24 09:39:03 ACDT; 57s 
ago
  Process: 52457 ExecStart=/usr/libexec/xdg-desktop-portal-gnome 
(code=killed, signal=TERM)
 Main PID: 52457 (code=killed, signal=TERM)
  CPU: 11ms

  Feb 24 09:37:33 graphene systemd[7592]: 

[Desktop-packages] [Bug 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental

[Alex Murray]

> I do not intend to take further action to modify those packages. If it is a 
> blocker for Ubuntu 
> that they are fixed, then someone from Ubuntu will need to do that work.

Given the relationship between the packages has now changed - ie.
polkitd-pkla is not mutually exclusive from the javascript backend and
then allows both legacy pkla policies as well as the "new" javascript
policies to be handled - then this is not a blocker anymore from my
point of view. I suspect Marc may also agree (especially given the
relatively small number of packages in this category).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1972654

Title:
  [security review] Sync policykit-1 0.120-6 (main) from Debian
  experimental

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 0.120-6 (main) from Debian experimental

  Changelog entries since current kinetic version 0.105-33:
  https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

  It appears the Debian maintainer is considering switching Debian to the
  updated version in time for the next Debian Stable release (so uploading
  to unstable later this year).

  My requested deadline is August 25, Ubuntu 22.10 Feature Freeze.

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


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

[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

[Alex Murray]

>> I don't think it's appropriate to display that in the settings app.

> I suppose that not knowing is more secure?

Yes if you consider the risk of users DoS'ing themselves by having to
potentially hack around in the CLI / BIOS settings to try and find the
right incantations to get a green check mark to appear. The status quo
is a lack of awareness - so we need to trade of the risks of showing
something which is unactionable and potentially alarming vs. keeping
things as they are. Once there is support to rectify these issues from
the GUI then I am not at all opposed to showing this information and
would welcome it. However even then, we will want to ensure this is a
robust process since we don't want to say make it easy to enable Secure
Boot and then prevent machines from booting since the user doesn't
actually run a signed kernel, or say end up having hardware devices
silently disabled on a subsequent reboot since they were previously
using unsigned modules etc. There is a lot of complexity and corner
cases here so it is prudent to be conservative in our approach IMO.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1987162

Title:
  43: New Device Security feature is confusing and unhelpful currently

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  GNOME 43 added a new Device Security feature in the Settings app.

  You can access it in gnome-control-center 1:43~beta-1ubuntu1
  1. Open the Settings app
  2. Click Privacy then Device Security

  The Security Events aren't clickable.

  A default Ubuntu install only gets us "Security Level 1". The highest
  level is "Security Level 3".

  There isn't anything an Ubuntu user can do to get to a higher security
  level from the Device Security screen.

  If a user attempts to get their system to a higher security level, I
  think they could break their system since this isn't something we
  currently support.

  Therefore, I think we ought to hide/disable the screen for Ubuntu
  22.10. We can work towards better integrating this screen for Ubuntu
  in future releases.

  I'm attaching several screenshots although it's worth trying out the
  feature for yourself too.

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


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

[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently

[Alex Murray]

Indeed - I don't think it is useful to have such information displayed
prominently when there is nothing that user's can do to affect this (in
general) and so this will only cause alarm. Like Marc said, it is then
not useful to display this without offering actionable tasks that a user
an perform to increase their security, since then as jbicha suggested,
some users will likely try and manually workaround these findings to
'increase' their security and potentially break their systems.

Whilst it is commendable that GNOME is trying to perhaps raise security
awareness for users, doing this in a way where users don't really have
any control over the results is likely to cause more harm than good.

So I agree, this should not be part of the standard gnome-control-center
at this stage for Ubuntu.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1987162

Title:
  43: New Device Security feature is confusing and unhelpful currently

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

Bug description:
  GNOME 43 added a new Device Security feature in the Settings app.

  You can access it in gnome-control-center 1:43~beta-1ubuntu1
  1. Open the Settings app
  2. Click Privacy then Device Security

  The Security Events aren't clickable.

  A default Ubuntu install only gets us "Security Level 1". The highest
  level is "Security Level 3".

  There isn't anything an Ubuntu user can do to get to a higher security
  level from the Device Security screen.

  If a user attempts to get their system to a higher security level, I
  think they could break their system since this isn't something we
  currently support.

  Therefore, I think we ought to hide/disable the screen for Ubuntu
  22.10. We can work towards better integrating this screen for Ubuntu
  in future releases.

  I'm attaching several screenshots although it's worth trying out the
  feature for yourself too.

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


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

[Desktop-packages] [Bug 283115] Re: Gimp: toolbox windows can't be minimized

[Alex Murray]

** Changed in: gimp (Ubuntu)
   Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/283115

Title:
  Gimp: toolbox windows can't be minimized

Status in The Gimp:
  Fix Released
Status in GTK+:
  Unknown
Status in gimp package in Ubuntu:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  gimp 2.6 in intrepid:
  it is impossible to minimize toolbar windows; they have only a x-Button to 
close

  ideally, these windows should be minimized automatically when the
  (last) Gimp image window is minimized

  Update
  While waiting, I designed some sort of workaround :
  Gnome>System>Preferences>Windows>Double-click titlebar>Roll up

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


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

[Desktop-packages] [Bug 1982493] Re: gnome-remote-desktop: Couldn't retrieve RDP username: Credentials not set - and more

[Alex Murray]

The security issue you refer to looks to have been assigned
CVE-2022-24882 which was fixed via
https://ubuntu.com/security/notices/USN-5461-1 more than a month ago. If
there is still a subsequent bug in gnome-remote-desktop / freerdp then
you should file a specific bug about that *and* mark it as public so the
appropriate Ubuntu developers can see it.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24882

** Changed in: gnome-remote-desktop (Ubuntu)
   Status: New => Fix Released

** Package changed: gnome-remote-desktop (Ubuntu) => freerdp2 (Ubuntu)

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1982493

Title:
  gnome-remote-desktop: Couldn't retrieve RDP username: Credentials not
  set - and more

Status in freerdp2 package in Ubuntu:
  Fix Released

Bug description:
  An immediate upgrade to 2.7.0 appears to be critical both for
  functionality (cannot work without it and having the backported NTLM
  fixes) and security:

  Please see the following for details:
  
https://askubuntu.com/questions/1419705/gnome-remote-desktop-couldnt-retrieve-rdp-username-credentials-not-set-and

  The FreeRDP developers believe that Ubuntu has not backported the NTLM
  fixes from 2.7.0 to 2.6.1 and subsequently the reason for the failures
  users are experiencing.

  The easier / more clean path appears to be to upgrade to FreeRDP
  2.7.0.

  It seems to be related to this vulnerability bounty:
  https://vuldb.com/?id.198528

  See: 
  * https://www.freerdp.com/2022/04/25/2_7_0-release
  * https://github.com/FreeRDP/FreeRDP/blob/2.7.0/ChangeLog

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


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

[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched

[Alex Murray]

** Also affects: evince (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: apparmor (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: evince (Ubuntu Kinetic)
   Importance: High
   Status: In Progress

** Also affects: apparmor (Ubuntu Kinetic)
   Importance: High
   Status: Confirmed

** Changed in: apparmor (Ubuntu Kinetic)
   Status: Confirmed => In Progress

** Changed in: apparmor (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: apparmor (Ubuntu Kinetic)
 Assignee: (unassigned) => Alex Murray (alexmurray)

** Changed in: apparmor (Ubuntu Jammy)
 Assignee: (unassigned) => Alex Murray (alexmurray)

** Changed in: apparmor (Ubuntu Jammy)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1969896

Title:
  Evince Document Viewer(42.0) does not remember last page in 22.04 and
  opens in a tiny window when launched

Status in apparmor package in Ubuntu:
  In Progress
Status in evince package in Ubuntu:
  In Progress
Status in apparmor source package in Jammy:
  In Progress
Status in evince source package in Jammy:
  New
Status in apparmor source package in Kinetic:
  In Progress
Status in evince source package in Kinetic:
  In Progress

Bug description:
  Just switched from Ubuntu 20.04 to 22.04 and realized that Document
  Viewer no longer open on the last viewed page and doesn't remember the
  side pane preference even after using the "Save Current Settings as
  Default" option. Kindly advise

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.1-3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:58:50 2022
  InstallationDate: Installed on 2022-03-19 (34 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

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


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

[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched

[Alex Murray]

FYI I have sent a MR to the upstream AppArmor project to remove this
dbus deny rule from the exo-open abstraction:
https://gitlab.com/apparmor/apparmor/-/merge_requests/884

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1969896

Title:
  Evince Document Viewer(42.0) does not remember last page in 22.04 and
  opens in a tiny window when launched

Status in apparmor package in Ubuntu:
  New
Status in evince package in Ubuntu:
  In Progress

Bug description:
  Just switched from Ubuntu 20.04 to 22.04 and realized that Document
  Viewer no longer open on the last viewed page and doesn't remember the
  side pane preference even after using the "Save Current Settings as
  Default" option. Kindly advise

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.1-3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:58:50 2022
  InstallationDate: Installed on 2022-03-19 (34 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

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


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

[Desktop-packages] [Bug 1975407] Re: pulseaudio is getting crashed

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1975407

Title:
  pulseaudio is getting crashed

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Operating System: Ubuntu 22.04
  Life cycle: LTS
  Architecture: AMD64
  Kernel version (uname -a): 5.15.0-30-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnm  3822 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 12:08:58 2022
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2019
  dmi.bios.release: 15.104
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.68
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 88.33
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1008C11:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuB7A48EA#ABV:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 4540s
  dmi.product.sku: B7A48EA#ABV
  dmi.product.version: A1008C11
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 
2022-01-28T22:42:20.933634

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


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

[Desktop-packages] [Bug 1975408] Re: Performance is much worse than expected (Normal friendly behaviors)

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1975408

Title:
  Performance is much worse than expected (Normal friendly behaviors)

Status in xorg package in Ubuntu:
  New

Bug description:
  Operating System: Ubuntu 22.04
  Life cycle: LTS
  Architecture: AMD64
  Kernel version (uname -a): 5.15.0-30-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 22 12:10:30 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: sysdig/0.27.1, 5.15.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics 
Controller [103c:17f4]
  MachineType: Hewlett-Packard HP ProBook 4540s
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic 
root=UUID=cf164159-2e29-4cee-aef2-f8d16c319f1a ro snapd_recovery_mode snap_core 
quiet splash crashkernel=512M-:192M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2019
  dmi.bios.release: 15.104
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IRR Ver. F.68
  dmi.board.name: 17F6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 58.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 88.33
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IRRVer.F.68:bd04/11/2019:br15.104:efr88.33:svnHewlett-Packard:pnHPProBook4540s:pvrA1008C11:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.21:cvnHewlett-Packard:ct10:cvr:skuB7A48EA#ABV:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 4540s
  dmi.product.sku: B7A48EA#ABV
  dmi.product.version: A1008C11
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.14.1+22.04.20211217-0ubuntu2
  version.libdrm2: libdrm2 2.4.110+git2205140500.3f266e~oibaf~j
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2~git2205160600.3c0f34~oibaf~j
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2~git2205170600.fffafa~oibaf~j
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1974181] Re: package libreoffice-common 1:7.3.3-0ubuntu0.22.04.1 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned er

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1974181

Title:
  package libreoffice-common 1:7.3.3-0ubuntu0.22.04.1 failed to
  install/upgrade: installed libreoffice-common package post-
  installation script subprocess returned error exit status 128

Status in libreoffice package in Ubuntu:
  New

Bug description:
  check

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-common 1:7.3.3-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon May 16 11:34:57 2022
  DuplicateSignature:
   package:libreoffice-common:1:7.3.3-0ubuntu0.22.04.1
   Setting up libreoffice-common (1:7.3.3-0ubuntu0.22.04.1) ...
   Replacing config file /etc/libreoffice/registry/main.xcd with new version
   dpkg: error processing package libreoffice-common (--configure):
installed libreoffice-common package post-installation script subprocess 
returned error exit status 128
  ErrorMessage: installed libreoffice-common package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2022-05-04 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:7.3.3-0ubuntu0.22.04.1 failed to 
install/upgrade: installed libreoffice-common package post-installation script 
subprocess returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1974074] Bug is not a security issue

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1974074

Title:
  missing symlink in /root/.config/libreoffice/4/user/config/

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  missing symlink in /root/.config/libreoffice/4/user/config/

  javasettings_Linux_*.xml

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


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

[Desktop-packages] [Bug 1973644] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-470 470.10

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1973644

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package
  nvidia-utils-470 470.103.01-0ubuntu0.20.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  I am having video problems ever since I tried to fix the problem with
  the dimmer controls

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon May 16 16:41:03 2022
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.108-0ubuntu5.20.04.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.108-0ubuntu5.20.04.2_amd64.deb 
(--unpack):
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in 
package nvidia-utils-470 470.103.01-0ubuntu0.20.04.1
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-utils-470 470.103.01-0ubuntu0.20.04.1
  InstallationDate: Installed on 2022-01-14 (122 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-470 470.103.01-0ubuntu0.20.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1973644/+subscriptions


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

[Desktop-packages] [Bug 1973028] Re: gnome-remote-desktop user service is always running

[Alex Murray]

I am not sure I agree with the statement that this is "harmless" for the
user service to be running if remote desktop sharing is not enabled - on
my jammy system I can see the RDP port open thanks to gnome-remote-
desktop:

$ ss -tlp | grep gnome-remote
LISTEN 0  10*:ms-wbt-server*:*
users:(("gnome-remote-de",pid=5851,fd=13))

And I have not manually enabled this - so I feel like this is
potentially a security issue and should be prioritised as such for
jammy.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1973028

Title:
  gnome-remote-desktop user service is always running

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in gnome-remote-desktop source package in Jammy:
  Triaged

Bug description:
  Impact
  --
  The gnome-remote-desktop systemd user service is always running.

  This was a contributing factor for LP: #1971415

  Although it's "harmless" for the user service to be running if remote
  desktop sharing is not enabled, it's a waste of resources to run a
  service if it's not needed.

  Test Case
  -
  Install all Ubuntu updates and the gnome-remote-desktop update.
  From a clean install (or new user), run this command:
  systemctl --user status gnome-remote-desktop.service

  It should show the service as "Active: inactive"

  Open the Settings app to the Sharing page. Turn on Sharing and turn on
  Remote Desktop. Use the systemctl command to verify that the service
  is "Active: active (running). Log out and log back in and reverify.

  Now turn off Remote Desktop Sharing and verify that the service is
  inactive. Log out and log back in and reverify.

  More details
  ---
  This fix uses a dpkg maintscript to remove 
/etc/systemd/user/gnome-session.target.wants/gnome-remote-desktop.service . 
(That file is a symlink to the actual service).

  It also modifies debian/rules so that that file is no longer
  automatically added.

  Instead of /etc/systemd/user/ , the user service is intended to be
  enabled with the symlink ~/.config/systemd/user/gnome-
  session.target.wants/gnome-remote-desktop.service . That is
  appropriate since the GNOME implementation is per-user, not system-
  wide and it is also disabled by default.

  Fixing this bug has been strongly urged by the GNOME Remote Desktop
  maintainers, and this brings us in line with how non-Debian distros
  have been packaging gnome-remote-desktop.

  What could go wrong
  ---
  The RDP and VNC sharing services in GNOME could start when they shouldn't or 
not start when they should.

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


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

[Desktop-packages] [Bug 1973472] Re: Vea la página de manual apt-secure(8) para los detalles sobre la creación de repositorios y la configuración de usuarios. W: El objetivo Sources (main/source/Sour

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. Your bug report is more likely to get attention if it is made in
English, since this is the language understood by the majority of Ubuntu
developers.  Additionally, please only mark a bug as "security" if it
shows evidence of allowing attackers to cross privilege boundaries or to
directly cause loss of data/privacy. Please feel free to report any
other bugs you may find.

** Information type changed from Private Security to Public

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1973472

Title:
   Vea la página de manual apt-secure(8) para los detalles sobre la
  creación de repositorios y la configuración de usuarios. W: El
  objetivo Sources (main/source/Sources) está configurado varias veces
  en /etc/apt/sources.list:2 y /etc/apt/sources.list:7 W: El objetivo
  Sources (main/source/Sources) está configurado varias veces en
  /etc/apt/sources.list:2 y /etc/apt/sources.list:7

Status in duplicity package in Ubuntu:
  Incomplete

Bug description:
Error de GPG: https://packages.microsoft.com/repos/edge stable InRelease: 
Las firmas siguientes no se pudieron verificar porque su clave pública no está 
disponible: NO_PUBKEY EB3E94ADBE1229CF
  E: El repositorio «https://packages.microsoft.com/repos/edge stable 
InRelease» no está firmado.

  
  Vea la página de manual apt-secure(8) para los detalles sobre la creación de 
repositorios y la configuración de usuarios.
  W: El objetivo Sources (main/source/Sources) está configurado varias veces en 
/etc/apt/sources.list:2 y /etc/apt/sources.list:7
  W: El objetivo Sources (main/source/Sources) está configurado varias veces en 
/etc/apt/sources.list:2 y /etc/apt/sources.list:7

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


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

[Desktop-packages] [Bug 1968397]

[Alex Murray]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1968397

Title:
  bootloader

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  root@a-ThinkPad-X220:~# apt install telnetd
  E: 无法获得锁 /var/lib/dpkg/lock-frontend - open (11: 资源暂时不可用)
  E: 无法获取 dpkg 前端锁 (/var/lib/dpkg/lock-frontend)，是否有其他进程正占用它？
  root@a-ThinkPad-X220:~# apt install telnetd
  E: 无法获得锁 /var/lib/dpkg/lock-frontend - open (11: 资源暂时不可用)
  E: 无法获取 dpkg 前端锁 (/var/lib/dpkg/lock-frontend)，是否有其他进程正占用它？
  root@a-ThinkPad-X220:~# killall

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Apr  9 13:01:34 2022
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2022-04-07 (1 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  MachineType: LENOVO 4286AC9
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=cf25f7a7-bda4-4979-9a0f-eb1cb472be49 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286AC9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn4286AC9:pvrThinkPadX220:rvnLENOVO:rn4286AC9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 4286AC9
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Apr  9 20:55:35 2022
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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


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

[Desktop-packages] [Bug 1968397] Re: bootloader

[Alex Murray]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1.
the specific steps or actions you took that caused you to encounter the
problem, 2. the behavior you expected, and 3. the behavior you actually
encountered (in as much detail as possible). Thanks!

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

** Information type changed from Private Security to Public

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1968397

Title:
  bootloader

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  root@a-ThinkPad-X220:~# apt install telnetd
  E: 无法获得锁 /var/lib/dpkg/lock-frontend - open (11: 资源暂时不可用)
  E: 无法获取 dpkg 前端锁 (/var/lib/dpkg/lock-frontend)，是否有其他进程正占用它？
  root@a-ThinkPad-X220:~# apt install telnetd
  E: 无法获得锁 /var/lib/dpkg/lock-frontend - open (11: 资源暂时不可用)
  E: 无法获取 dpkg 前端锁 (/var/lib/dpkg/lock-frontend)，是否有其他进程正占用它？
  root@a-ThinkPad-X220:~# killall

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-112-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Apr  9 13:01:34 2022
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2022-04-07 (1 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  MachineType: LENOVO 4286AC9
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic 
root=UUID=cf25f7a7-bda4-4979-9a0f-eb1cb472be49 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4286AC9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn4286AC9:pvrThinkPadX220:rvnLENOVO:rn4286AC9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 4286AC9
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Apr  9 20:55:35 2022
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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


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

[Desktop-packages] [Bug 1968402] Re: Ubuntu 20.04.3 boots to black screen, no TTY available

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1968402

Title:
  Ubuntu 20.04.3 boots to black screen, no TTY available

Status in gdm:
  New
Status in gnome-session:
  New
Status in grub:
  New
Status in os-prober-efi/trunk:
  New
Status in shim:
  New
Status in subiquity:
  New
Status in tty:
  New
Status in grub2 package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  A fresh attempted install failed utterly, just as 20.04.1 failed two
  years ago.  Has anyone been paying attention?

  Ubuntu 20.04.3 burned just now to a USB stick and attempted to be
  installed.

  The first fail was that the stick booted to a couple of impenetrable
  boot-time messages and hung.  Really.  I'm not making this up.  It
  didn't just open the installer, as it should.

  The second fail was having just to guess that rebooting and trying
  another GRUB menu option might work and give that a try.  Really.  I'm
  not making this up, either.  The installer was entirely incapable of
  providing any direction

  The third failure was that the installer was incapable of detecting
  the video configuration and proceeding accordingly.  This is 20.04.3,
  the third attempt at getting this right, and it still fails.

  The fourth fail was an error message insisting on a designation of
  where root should be, even after the destination partition already had
  been specified.

  The fifth failure was that no obvious means existed to satisfy the
  installer about the root specification, which of course already had
  been made by specifying the destination partition.  All one could do
  was to see whether a context menu existed for any object on the screen
  that might possibly drill down through a few layers to something
  approximating what the content of the error message suggested.

  The sixth failure was that no GRUB menu appeared during boot,
  notwithstanding that the EFI system partition had clearly been
  identified in the installer.

  The seventh failure was that the machine booted only to a black screen
  with a non-blinking _ midway toward the upper left.  No login
  screen/display manager.  No GUI at all.  Just this little _.

  The eighth failure was that Ctrl-alt-f2, ctrl-alt-f5-f12 have no
  effect.  No TTY is available.  There is no way whatsoever to interact
  with the system.

  Expected behavior:  The software would install and the computer would
  work.

  Actual behavior:  The installer bricked my workstation.

  Obviously, no debug information is available BECAUSE THE SOFTWARE
  FAILED.  This post is being made from a borrowed Windows laptop.

  Any thoughts about how to get a working system would be appreciated.
  I am not optimistic about the prospects for 22.04.

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


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

[Desktop-packages] [Bug 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected

[Alex Murray]

Yep with this patch applied I can no longer reproduce the crash and the
valgrind output is clean - have just uploaded this as 2.9.4-1ubuntu1 to
jammy-proposed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1964532

Title:
  /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin
  chunk detected

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
udisks2.  This problem was most recently seen with package version 2.9.4-1, the 
problem page at 
https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected

[Alex Murray]

Ok so this looks to be the same as https://github.com/storaged-
project/udisks/pull/926 which was fixed upstream - and according to the
comment there causes exactly the type of issue we are seeing:

"leading to memory corruption causing random failures of further atexit
handlers such as cryptsetup and openssl destructors."

I'll try rebuilding udisks2 with this patch and see if it helps.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1964532

Title:
  /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin
  chunk detected

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
udisks2.  This problem was most recently seen with package version 2.9.4-1, the 
problem page at 
https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected

[Alex Murray]

Sadly running it under valgrind doesn't detect this memory corruption -
we see an invalid memory read on shutdown but that is all:

$ sudo valgrind /usr/libexec/udisks2/udisksd
==567833== Memcheck, a memory error detector
==567833== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==567833== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==567833== Command: /usr/libexec/udisks2/udisksd
==567833== 
udisks-Message: 15:23:12.496: udisks daemon version 2.9.4 starting

** (udisksd:567833): WARNING **: 15:23:12.985: failed to load module
mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file
or directory

(udisksd:567833): udisks-WARNING **: 15:23:13.018: Failed to load the 'mdraid' 
libblockdev plugin
udisks-Message: 15:23:17.443: udisks daemon version 2.9.4 exiting
==567833== Invalid read of size 4
==567833==at 0x4B5BB14: g_resource_unref (gresource.c:527)
==567833==by 0x4B5D8C0: g_static_resource_fini (gresource.c:1449)
==567833==by 0x400624D: _dl_fini (dl-fini.c:142)
==567833==by 0x4E85494: __run_exit_handlers (exit.c:113)
==567833==by 0x4E8560F: exit (exit.c:143)
==567833==by 0x4E69D96: (below main) (libc_start_call_main.h:74)
==567833==  Address 0x9246130 is 0 bytes inside a block of size 16 free'd
==567833==at 0x484B27F: free (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==567833==by 0x4B5D8B8: g_static_resource_fini (gresource.c:1448)
==567833==by 0x400624D: _dl_fini (dl-fini.c:142)
==567833==by 0x4E85494: __run_exit_handlers (exit.c:113)
==567833==by 0x4E8560F: exit (exit.c:143)
==567833==by 0x4E69D96: (below main) (libc_start_call_main.h:74)
==567833==  Block was alloc'd at
==567833==at 0x4848899: malloc (in 
/usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==567833==by 0x4D64718: g_malloc (gmem.c:125)
==567833==by 0x4B5D137: UnknownInlinedFun (gresource.c:545)
==567833==by 0x4B5D137: g_resource_new_from_data (gresource.c:613)
==567833==by 0x4B5D1F8: register_lazy_static_resources_unlocked 
(gresource.c:1374)
==567833==by 0x4B5D8FC: UnknownInlinedFun (gresource.c:1393)
==567833==by 0x4B5D8FC: UnknownInlinedFun (gresource.c:1387)
==567833==by 0x4B5D8FC: g_static_resource_get_resource (gresource.c:1472)
==567833==by 0x14E463: udisks_linux_mount_options_get_builtin (in 
/usr/libexec/udisks2/udisksd)
==567833==by 0x12BA6E: ??? (in /usr/libexec/udisks2/udisksd)
==567833==by 0x4CCB03E: g_object_new_internal (gobject.c:2053)
==567833==by 0x4CCC757: g_object_new_valist (gobject.c:2355)
==567833==by 0x48C: g_object_new (gobject.c:1824)
==567833==by 0x1288BF: udisks_daemon_new (in /usr/libexec/udisks2/udisksd)
==567833==by 0x128935: ??? (in /usr/libexec/udisks2/udisksd)


I also tried rebuilding udisks2, cryptsetup and openssl with ASan enabled but 
that also didn't appear to detect it... I am out of ideas of where to look / 
what to try to dig further into this.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1964532

Title:
  /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin
  chunk detected

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
udisks2.  This problem was most recently seen with package version 2.9.4-1, the 
problem page at 
https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected

[Alex Murray]

I can reproduce this by just running `sudo systemctl restart
udisks2.service` - will see if I can perhaps run it under valgrind and
see where the memory corruption is happening.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1964532

Title:
  /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin
  chunk detected

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
udisks2.  This problem was most recently seen with package version 2.9.4-1, the 
problem page at 
https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal

[Alex Murray]

Upstream bug filed https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/5242

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5242
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5242

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964442

Title:
  [jammy][regression] gnome-shell PolicyKit password prompt sends
   keys to the terminal

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This is a regression not seen until this week (not seen until March 4
  at least).  Calling debsign from a terminal pops up the window to
  enter the key, but the terminal is sent continuous  keys and
  the terminal scrolls down with empty input lines. You can still sign
  the file, however you end up with an empty scroll buffer if the
  signing takes too long time.

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


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

[Desktop-packages] [Bug 1964442] Re: [jammy][regression] gnome-shell PolicyKit password prompt sends keys to the terminal

[Alex Murray]

I personally don't think this should be low priority - this affects any
application which ends up causing the gnome shell prompt dialog to
appear - so in my case when reading my email and opening a GPG encrypted
email I get prompted for my GPG passphrase - whilst this is happening my
email client is repeatedly getting  sent to it, causing it to
advance forward to the next email and mark the current one as read - so
this has a real usability impact IMO. This is not just relevant to
terminal applications  etc.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1964442

Title:
  [jammy][regression] gnome-shell PolicyKit password prompt sends
   keys to the terminal

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This is a regression not seen until this week (not seen until March 4
  at least).  Calling debsign from a terminal pops up the window to
  enter the key, but the terminal is sent continuous  keys and
  the terminal scrolls down with empty input lines. You can still sign
  the file, however you end up with an empty scroll buffer if the
  signing takes too long time.

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


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

[Desktop-packages] [Bug 1965837] Re: Erroneous / extra input generated in requesting application when prompting to unlock keys

[Alex Murray]

If it is not clear from the video - watch the terminal window in the
background when the prompt for the passphrase appears - it keeps
scrolling as though getting input by newlines all the time - and this
then persists even after the prompt is dismissed until I manually
provide some input myself.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1965837

Title:
  Erroneous / extra input generated in requesting application when
  prompting to unlock keys

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Recently I have noticed that when I am being prompted for the
  passphrase for to unlock a GPG/SSH key via the gnome-shell prompter,
  whilst the prompt is visible the requesting window seems to get
  spammed by input - this can be reproduced via running the following
  (but replace the gpg recipient with the one of your own user's private
  key):

  $ echo RELOADAGENT | gpg-connect-agent; echo foo | gpg --encrypt
  --recipient alex.mur...@canonical.com | gpg --decrypt

  See attached for a short video demonstrating the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 11:43:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-03 (230 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-01-14 (66 days ago)

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


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

[Desktop-packages] [Bug 1965837] [NEW] Erroneous / extra input generated in requesting application when prompting to unlock keys

[Alex Murray]

Public bug reported:

Recently I have noticed that when I am being prompted for the passphrase
for to unlock a GPG/SSH key via the gnome-shell prompter, whilst the
prompt is visible the requesting window seems to get spammed by input -
this can be reproduced via running the following (but replace the gpg
recipient with the one of your own user's private key):

$ echo RELOADAGENT | gpg-connect-agent; echo foo | gpg --encrypt
--recipient alex.mur...@canonical.com | gpg --decrypt

See attached for a short video demonstrating the issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 22 11:43:36 2022
DisplayManager: gdm3
InstallationDate: Installed on 2021-08-03 (230 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-01-14 (66 days ago)

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


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "Screencast from 22-03-22 11:45:41.webm"
   
https://bugs.launchpad.net/bugs/1965837/+attachment/5571537/+files/Screencast%20from%2022-03-22%2011%3A45%3A41.webm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1965837

Title:
  Erroneous / extra input generated in requesting application when
  prompting to unlock keys

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Recently I have noticed that when I am being prompted for the
  passphrase for to unlock a GPG/SSH key via the gnome-shell prompter,
  whilst the prompt is visible the requesting window seems to get
  spammed by input - this can be reproduced via running the following
  (but replace the gpg recipient with the one of your own user's private
  key):

  $ echo RELOADAGENT | gpg-connect-agent; echo foo | gpg --encrypt
  --recipient alex.mur...@canonical.com | gpg --decrypt

  See attached for a short video demonstrating the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42~beta-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 22 11:43:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-08-03 (230 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-01-14 (66 days ago)

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


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

[Desktop-packages] [Bug 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected

[Alex Murray]

This looks to be the same as LP: #1955758

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1964532

Title:
  /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin
  chunk detected

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
udisks2.  This problem was most recently seen with package version 2.9.4-1, the 
problem page at 
https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1964532] Re: /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin chunk detected

[Alex Murray]

See attached - it looks like the crash happens during shutdown - see
line 11443

** Attachment added: "journalctl-udisks-crash.log.gz"
   
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1964532/+attachment/5571201/+files/journalctl-udisks-crash.log.gz

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1964532

Title:
  /usr/libexec/udisks2/udisksd:malloc_consolidate(): unaligned fastbin
  chunk detected

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
udisks2.  This problem was most recently seen with package version 2.9.4-1, the 
problem page at 
https://errors.ubuntu.com/problem/ee70e42ef96a41e0ae118869c75b7cc675ae974c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1897454] Re: [snap] Chromium has Wayland support disabled

[Alex Murray]

The priority of this bug is Low but since Wayland is now the default
session this means chromium runs via XWayland and then when doing
window/screen sharing on say Google Meet I can only share windows which
are also using XWayland, not native ones - which is the majority of the
rest of the desktop. Any chance this can get given higher priority so we
don't regress too much for Jammy?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1897454

Title:
  [snap] Chromium has Wayland support disabled

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Since v87 Chromium ships with support for Ozone/Wayland:
  https://www.phoronix.com/scan.php?page=news_item=Chrome-87-Ozone-Try-Again.

  This build flag is not disabled in dev (edge) channel build, so it should be 
possible to run Chromium with flags
--enable-features=UseOzonePlatform --ozone-platform=wayland.

  This does not work due to environment variable DISABLE_WAYLAND set to 1 here:
  
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18.

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


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

[Desktop-packages] [Bug 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed

[Alex Murray]

See this related debian bug https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1006368

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1962276

Title:
  [jammy] Laptop monitor does not turn off/disconnect when the lid is
  closed

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  After today's updates I can no longer run my Laptop in clam shell mode. 
  I don't use a dock. I connect the second monitor via HDMI cable and and 
external keyboard/mouse via a USB hub. 

  Usually I can just plugin the monitor and close the lid and the
  primary display will switch to the external monitor. Now it will
  default to Monitor 2 as part of the joint display.

  I also tested booting the machine and closing the lid but this still
  defaulted to the external monitor as the 2nd display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 25 16:44:37 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2226]
  InstallationDate: Installed on 2022-02-23 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  MachineType: LENOVO 20CLS3JN0F
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2015
  dmi.bios.release: 1.7
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET30W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CLS3JN0F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250:
  dmi.product.family: ThinkPad X250
  dmi.product.name: 20CLS3JN0F
  dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-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-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Desktop-packages] [Bug 1962276] Re: [jammy] Laptop monitor does not turn off/disconnect when the lid is closed

[Alex Murray]

This appears to be caused (for me at least) by upower 0.99.16-1 - after
upgrading today to 0.99.16-2 things are working again as expected.

** Also affects: upower (Ubuntu)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1962276

Title:
  [jammy] Laptop monitor does not turn off/disconnect when the lid is
  closed

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  After today's updates I can no longer run my Laptop in clam shell mode. 
  I don't use a dock. I connect the second monitor via HDMI cable and and 
external keyboard/mouse via a USB hub. 

  Usually I can just plugin the monitor and close the lid and the
  primary display will switch to the external monitor. Now it will
  default to Monitor 2 as part of the joint display.

  I also tested booting the machine and closing the lid but this still
  defaulted to the external monitor as the 2nd display.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 25 16:44:37 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2226]
  InstallationDate: Installed on 2022-02-23 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  MachineType: LENOVO 20CLS3JN0F
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2015
  dmi.bios.release: 1.7
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET30W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CLS3JN0F
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET30W(1.07):bd03/05/2015:br1.7:efr1.9:svnLENOVO:pn20CLS3JN0F:pvrThinkPadX250:rvnLENOVO:rn20CLS3JN0F:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20CL_BU_Think_FM_ThinkPadX250:
  dmi.product.family: ThinkPad X250
  dmi.product.name: 20CLS3JN0F
  dmi.product.sku: LENOVO_MT_20CL_BU_Think_FM_ThinkPad X250
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.109-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-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-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Desktop-packages] [Bug 1962351] [NEW] login screen shown on inactive monitor

[Alex Murray]

Public bug reported:

My laptop is docked with the lid closed and connected to 2 external
monitors. After upgrading a bunch of packages from jammy in the last 24
hours I notice that when logging in, both of my external monitors just
show the purple background whilst the login dialog was actually
displayed on the closed lid of my laptop.

Wasn't sure if this should be filed against some other package as it
doesn't look like gnome-shell or gdm3 have changed lately (I only see
gnome-shell-extension-appindicator and gnome-shell-extension-ubuntu-dock
in my apt history that could be related...)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 41.3-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 26 09:52:39 2022
InstallationDate: Installed on 2021-08-03 (206 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
SourcePackage: gdm3
UpgradeStatus: Upgraded to jammy on 2022-01-14 (42 days ago)

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


** Tags: amd64 apport-bug jammy wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1962351

Title:
  login screen shown on inactive monitor

Status in gdm3 package in Ubuntu:
  New

Bug description:
  My laptop is docked with the lid closed and connected to 2 external
  monitors. After upgrading a bunch of packages from jammy in the last
  24 hours I notice that when logging in, both of my external monitors
  just show the purple background whilst the login dialog was actually
  displayed on the closed lid of my laptop.

  Wasn't sure if this should be filed against some other package as it
  doesn't look like gnome-shell or gdm3 have changed lately (I only see
  gnome-shell-extension-appindicator and gnome-shell-extension-ubuntu-
  dock in my apt history that could be related...)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 41.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 26 09:52:39 2022
  InstallationDate: Installed on 2021-08-03 (206 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-01-14 (42 days ago)

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


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

[Desktop-packages] [Bug 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug

[Alex Murray]

See https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962127
for an ubuntu-bug of the gnome-shell crash file when this occurred for
me yesterday.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1961910

Title:
  Ubuntu 22 crash when updating, broken network manager and cannot
  report bug

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  A new day, a new struggle with Ubuntu 22.04.

  So, I decided to get my daily updates and in the middle of the process the 
system just crashed, leaving me at the login page. When I got back, the wifi 
was no longer there and the network configuration was reporting an error about 
the network manager having problems.
  I shut down and restarted, the wifi came back.

  Went to the var/crash folder to report the bug with

  $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash

  and it started complaining about older packages that need to be
  upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried
  `apt install dbus` and another even uglier crash that left me with a
  black screen from which I could only come back with a forced shutdown
  and restart.

  Now, how do I get out of this mess and report the bug?

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


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

[Desktop-packages] [Bug 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable

[Alex Murray]

@leosilva - as you did the original update for exiv2 could you please
sponsor the attached debdiff? Thanks.

** Changed in: exiv2 (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Fix Released
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1946578] Re: Placeholder for CVE-2021-41133

[Alex Murray]

** Also affects: flatpak (Ubuntu Impish)
   Importance: Undecided
 Assignee: Andrew Hayzen (ahayzen)
   Status: New

** Also affects: flatpak (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: flatpak (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: flatpak (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flatpak in Ubuntu.
https://bugs.launchpad.net/bugs/1946578

Title:
  Placeholder for CVE-2021-41133

Status in flatpak package in Ubuntu:
  New
Status in flatpak source package in Bionic:
  New
Status in flatpak source package in Focal:
  New
Status in flatpak source package in Hirsute:
  New
Status in flatpak source package in Impish:
  New

Bug description:
  *** Placeholder until regressions are fixed upstream ***

  [Links]
  https://github.com/flatpak/flatpak/security/advisories/GHSA-67h7-w3jq-vh4q
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995935
  https://security-tracker.debian.org/tracker/CVE-2021-41133

  
  [Impact]
  Versions in Ubuntu right now:
  Impish: 1.10.2-3
  Hirsute: 1.10.2-1ubuntu1
  Focal: 1.6.5-0ubuntu0.3
  Bionic: 1.0.9-0ubuntu0.3

  Affected versions:
  1.11.x, 1.10.x <= 1.10.3, all <= 1.8.2

  Patched versions:
  1.10.5, 1.12.1, also expected in 1.8.2

  
  [Test Case]
  Unknown

  
  [Regression Potential]
  Flatpak has a test suite, which is run on build across all relevant 
architectures and passes.

  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .

  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .

  Regression potential is low, and upstream is very responsive to any
  issues raised.

  
  [Patches]
  There were 8 initial patches, then some regressions have been found, one has 
been patched, but a second has a pending pull request (see the github advisory 
for links). As noted in the debian bug as well there might be further changes 
to bubblewrap, so guess it makes sense to wait until this has settled.

  
  [Other Information]
  An anonymous reporter discovered that Flatpak apps with direct access to 
AF_UNIX sockets such as those used by Wayland, Pipewire or pipewire-pulse can 
trick portals and other host-OS services into treating the Flatpak app as 
though it was an ordinary, non-sandboxed host-OS process, by manipulating the 
VFS using recent mount-related syscalls that are not blocked by Flatpak's 
denylist seccomp filter, in order to substitute a crafted /.flatpak-info or 
make that file disappear entirely.
  Impact

  Flatpak apps that act as clients for AF_UNIX sockets such as those
  used by Wayland, Pipewire or pipewire-pulse can escalate the
  privileges that the corresponding services will believe the Flatpak
  app has.

  Mitigation: Note that protocols that operate entirely over the D-Bus
  session bus (user bus), system bus or accessibility bus are not
  affected by this. This is due to the use of a proxy process xdg-dbus-
  proxy, whose VFS cannot be manipulated by the Flatpak app, when
  interacting with these buses.

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


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

[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

[Alex Murray]

Is there any option to do this via portals - ie can evince use
https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-
org.freedesktop.portal.OpenURI to open the URI? Would then this allow to
avoid going via xdg-open?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1794064

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged

Bug description:
  This is related to bug #1792648. After fixing that one (see discussion
  at https://salsa.debian.org/gnome-team/evince/merge_requests/1),
  clicking a hyperlink in a PDF opens it correctly if the default
  browser is a well-known application (such as /usr/bin/firefox), but it
  fails to do so if the default browser is a snap (e.g. the chromium
  snap).

  This is not a recent regression, it's not working on bionic either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: evince 3.30.0-2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 24 12:28:06 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (813 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago)
  modified.conffile..etc.apparmor.d.abstractions.evince: [modified]
  mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158

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


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

[Desktop-packages] [Bug 1919078] Re: Ubuntu SSO login - not working (Throws "Error connecting to server"

[Alex Murray]

** Package changed: ubuntu => gnome-online-accounts (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1919078

Title:
  Ubuntu SSO login - not working (Throws "Error connecting to server"

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Hi,

  I'm looking for possible ways to add an Ubuntu SSO account with my
  Ubuntu system for the past few weeks.

  But I'm getting the error as "Error connecting to Ubuntu SSO server.
  Something went wrong. Please try again later".

  I tried to login via the web, it works fine.

  
  I'm on the latest build.
  Check my system version at https://ibb.co/7bc1JgP

  Screenshot (of error):
  https://ibb.co/v1JvKZ6

  
  Kindly help me with this error.

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

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

[Desktop-packages] [Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp

[Alex Murray]

** Also affects: flatpak (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: flatpak (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: flatpak (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flatpak in Ubuntu.
https://bugs.launchpad.net/bugs/1918482

Title:
  Update for GHSA-xgh4-387p-hqpp

Status in flatpak package in Ubuntu:
  In Progress
Status in flatpak source package in Bionic:
  New
Status in flatpak source package in Focal:
  New
Status in flatpak source package in Groovy:
  New

Bug description:
  [Links]
  https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp
  https://github.com/flatpak/flatpak/pull/4156
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859

  [Impact]
  Versions in Ubuntu right now:
  Hirsute: 1.10.1-4
  Groovy: 1.8.2-1ubuntu0.1
  Focal: 1.6.5-0ubuntu0.2
  Bionic: 1.0.9-0ubuntu0.2

  Affected versions:
  >= 0.9.4

  Patched versions:
  >= 1.10.2

  [Test Case]

  No test case has been mentioned yet, but in the patches there are
  changes/additions to the unit tests.

  [Regression Potential]

  Flatpak has a test suite, which is run on build across all relevant
  architectures and passes.

  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .

  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .

  Regression potential is low, and upstream is very responsive to any
  issues raised.

  [Other information]

  Sandbox escape via special tokens in .desktop file (flatpak#4146)

  Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature 
which can be used by an attacker to gain access to files that would not 
ordinarily be allowed by the app's permissions.
  Impact

  By putting the special tokens @@ and/or @@u in the Exec field of a
  Flatpak app's .desktop file, a malicious app publisher can trick
  flatpak into behaving as though the user had chosen to open a target
  file with their Flatpak app, which automatically makes that file
  available to the Flatpak app.

  A minimal solution is the first commit "Disallow @@ and @@U usage in desktop 
files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: 
Refuse to export .desktop files with suspicious uses of @@ tokens" are 
recommended, but not strictly required.
  Workarounds

  Avoid installing Flatpak apps from untrusted sources, or check the contents 
of the exported .desktop files in exports/share/applications/*.desktop 
(typically ~/.local/share/flatpak/exports/share/applications/*.desktop and 
/var/lib/flatpak/exports/share/applications/*.desktop) to make sure that 
literal filenames do not follow @@ or @@u.
  References

  Acknowledgements

  Thanks to @AntonLydike for reporting this issue, and @refi64 for
  providing the initial solution.

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

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

[Desktop-packages] [Bug 1909334] Re: bug

[Alex Murray]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

** Changed in: xorg (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1909334

Title:
  bug

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  bug

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Dec 25 18:45:40 2020
  DistUpgraded: 2020-12-22 12:02:59,073 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:30a3]
  InstallationDate: Installed on 2020-12-21 (4 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 10AAS39X00
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic 
root=UUID=956b6a42-972b-4ae3-813d-38976087b2bf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2020-12-22 (3 days ago)
  dmi.bios.date: 10/22/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTA1AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  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:bvnLENOVO:bvrFBKTA1AUS:bd10/22/2014:svnLENOVO:pn10AAS39X00:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvr0B98401WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10AAS39X00
  dmi.product.version: ThinkCentre M93p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Dec 24 01:04:29 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   10293 
   vendor HWP
  xserver.version: 2:1.15.1-0ubuntu2.11

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

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

[Desktop-packages] [Bug 1913493] Re: pc

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1913493

Title:
  pc

Status in xorg package in Ubuntu:
  New

Bug description:
  pc

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-45-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jan 28 00:27:54 2021
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Device [1234:] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Red Hat, Inc. Device [1af4:1100]
  InstallationDate: Installed on 2019-05-05 (633 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  Lsusb:
   Bus 001 Device 004: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 003: ID 0409:55aa NEC Corp. Hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=218dfaed-f9ed-4bbe-af1a-aeb8953f26c8 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.0
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.0
  dmi.sys.vendor: QEMU
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jan 28 00:23:55 2021
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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

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

[Desktop-packages] [Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2

[Alex Murray]

** Also affects: flatpak (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: flatpak (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: flatpak (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: flatpak (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Andrew Hayzen (ahayzen)
   Status: In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flatpak in Ubuntu.
https://bugs.launchpad.net/bugs/1911473

Title:
  Update for ghsa-4ppf-fxf6-vxg2

Status in flatpak package in Ubuntu:
  In Progress
Status in flatpak source package in Bionic:
  New
Status in flatpak source package in Focal:
  New
Status in flatpak source package in Groovy:
  New
Status in flatpak source package in Hirsute:
  In Progress

Bug description:
  [Links]

  Upstream Advisory: 
https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-fxf6-vxg2
  Debian: https://security-tracker.debian.org/tracker/CVE-2021-21261
  DSA: https://security-tracker.debian.org/tracker/DSA-4830-1

  [Impact]

  Versions in Ubuntu right now:
  Hirsute: 1.8.4-2
  Groovy: 1.8.2-1
  Focal: 1.6.5-0ubuntu0.1
  Bionic: 1.0.9-0ubuntu0.1

  Affected versions:
  >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5

  Patched versions:
  Expected to be >= 1.9.4, 1.8.x >= 1.8.5

  There are also branches with patches for 1.6.x (Ubuntu 20.04), but
  nothing available yet for 1.0.x (Ubuntu 18.04).

  [Test Case]

  No test case has been mentioned yet, but in the patches there are
  changes/additions to the unit tests.

  [Regression Potential]

  Flatpak has a test suite, which is run on build across all
  architectures and passes.

  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak .

  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak .

  Regression potential is low, and upstream is very responsive to any
  issues raised.

  [Other information]

  Simon McVittie discovered a bug in the flatpak-portal service that can
  allow sandboxed applications to execute arbitrary code on the host
  system (a sandbox escape).

  The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus 
service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox 
to launch their own subprocesses in a new sandbox instance, either with the 
same security settings as the caller or with
  more restrictive security settings. For example, this is used in 
Flatpak-packaged web browsers such as Chromium to launch subprocesses
  that will process untrusted web content, and give those subprocesses a more 
restrictive sandbox than the browser itself.

  In vulnerable versions, the Flatpak portal service passes caller-
  specified environment variables to non-sandboxed processes on the host
  system, and in particular to the flatpak run command that is used to
  launch the new sandbox instance. A malicious or compromised Flatpak
  app could set environment variables that are trusted by the flatpak
  run command, and use them to execute arbitrary code that is not in a
  sandbox.

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

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

[Desktop-packages] [Bug 1903677] Re: Mozilla Firefox / Firefox ESR Arbitrary Code Execution Vulnerability

[Alex Murray]

firefox 82.0.3 was released for xenial, bionic, focal, groovy and
hirsute yesterday.

** Changed in: firefox (Ubuntu)
   Status: New => Fix Released

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1903677

Title:
  Mozilla Firefox / Firefox ESR Arbitrary Code Execution Vulnerability

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  A use-after-free error related to the MCallGetProperty opcode can be
  exploited to execute arbitrary code.

  The vulnerability is reported in Mozilla Firefox versions prior to
  82.0.3 and in Mozilla Firefox ESR versions prior to 78.4.1.

  Affected Software

  The following software is affected by the described vulnerability.
  Please check the vendor links below to see if exactly your version is
  affected.

  Mozilla Firefox 78.x
  Mozilla Firefox 82.x

  Update to a fixed version.

  Mozilla Firefox:
  Update to version 82.0.3.

  Mozilla Firefox ESR:
  Update to version 78.4.1.

  References

  1. https://www.mozilla.org/en-US/security/advisories/mfsa2020-49
  

  Please provide a patch as soon as possible.

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

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

[Desktop-packages] [Bug 1898083] Re: emacs snap has many errors on startup

[Alex Murray]

Marking this as invalid against emacs in Ubuntu since that corresponds
to the emacs deb not the snap. Please follow up via the existing (or a
new) github issue for snap specific issues.

** Changed in: emacs (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs in Ubuntu.
https://bugs.launchpad.net/bugs/1898083

Title:
  emacs snap has many errors on startup

Status in emacs package in Ubuntu:
  Invalid

Bug description:
  I just upgraded to Ubuntu 20.04 and my first shell command was
  'emacs'. The response was:

  Command 'emacs' not found, but can be installed with:

  sudo snap install emacs# version 27.1, or
  sudo apt  install e3   # version 1:2.71-2
  sudo apt  install emacs-gtk# version 1:26.3+1-1ubuntu2
  sudo apt  install emacs-lucid  # version 1:26.3+1-1ubuntu2
  sudo apt  install emacs-nox# version 1:26.3+1-1ubuntu2
  sudo apt  install jove # version 4.17.2.7-1

  See 'snap info emacs' for additional versions.

  
  So I tried the first command 'sudo snap install emacs'. So I tried it:

  $ sudo snap install emacs
  [sudo] password for eggert: 
  error: This revision of snap "emacs" was published using classic confinement
 and thus may perform arbitrary system changes outside of the security
 sandbox that snaps are usually confined to, which may put your system 
at
 risk.

 If you understand and want to proceed repeat the command including
 --classic.

  
  That didn't look promising, but I was stubborn, and continued as follows:

  $ sudo snap install --classic emacs
  emacs 27.1 from Alex Murray (alexmurray) installed

  
  Great! Now I can run Emacs. But the experience was not good at all:

  $ emacs notes

  (emacs:5050): Gtk-WARNING **: 09:40:34.782: Theme parsing error:
  gtk.css:1521:23: 'font-feature-settings' is not a valid property name

  (emacs:5050): Gtk-WARNING **: 09:40:34.786: Theme parsing error:
  gtk.css:3460:25: 'font-feature-settings' is not a valid property name

  (emacs:5050): Gtk-WARNING **: 09:40:34.787: Theme parsing error: 
gtk.css:3922:23: 'font-feature-settings' is not a valid property name
  Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 4: 
unknown element "its:rules"
  Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: 
unknown element "its:translateRule"
  Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid 
attribute 'translate'
  Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid 
attribute 'selector'
  Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid 
attribute 'xmlns:its'
  Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid 
attribute 'version'
  Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 8: 
unknown element "description"
  Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 4: 
unknown element "its:rules"
  Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: 
unknown element "its:translateRule"
  Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: 
invalid attribute 'translate'
  Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: 
invalid attribute 'selector'
  Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: 
invalid attribute 'xmlns:its'
  Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: 
invalid attribute 'version'
  Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 8: 
unknown element "description"
  Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 4: 
unknown element "its:rules"
  Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 5: 
unknown element "its:translateRule"
  Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 5: 
invalid attribute 'translate'
  Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 5: 
invalid attribute 'selector'
  Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 6: 
invalid attribute 'xmlns:its'
  Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 6: 
invalid attribute 'version'
  Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 8: 
unknown element "description"
  Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 4: 
unknown element "its:rules"
  Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf&quo

[Desktop-packages] [Bug 1895839] Re: CVE-2020-24977

[Alex Murray]

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1895839

Title:
  CVE-2020-24977

Status in libxml2 package in Ubuntu:
  New

Bug description:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977

  Upstream patch:
  
https://gitlab.gnome.org/GNOME/libxml2/-/commit/8e7c20a1af8776677d7890f30b7a180567701a49

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

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

[Desktop-packages] [Bug 1890047] Re: Sessions crash, all X11 remote users disconnected

[Alex Murray]

** Changed in: glib-networking (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib-networking in Ubuntu.
https://bugs.launchpad.net/bugs/1890047

Title:
  Sessions crash, all X11 remote users disconnected

Status in glib-networking package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have a Ubuntu 16.04.6 LTS (Xenial Xerus) used by many X11 remote
  user.

  When upgrading to glib-networking, glib-networking-common and lib-
  networking-services to 2.48.2-1~ubuntu16.04.2; all sessions crash
  randomly at the same time many times a day.

  When it happens, all users are disconnected and it looks like lightdm
  is restarted.

  Downgrading to 2.48.2-1~ubuntu16.04.1 resolve the problem.

  X11 terminals were not upgraded.

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

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

[Desktop-packages] [Bug 1890047] Re: Sessions crash, all X11 remote users disconnected

[Alex Murray]

How are your users connecting to the X server? From the description you
mention lightdm - can you explain the setup and I will see if I can
reproduce it?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib-networking in Ubuntu.
https://bugs.launchpad.net/bugs/1890047

Title:
  Sessions crash, all X11 remote users disconnected

Status in glib-networking package in Ubuntu:
  New

Bug description:
  Hello,

  I have a Ubuntu 16.04.6 LTS (Xenial Xerus) used by many X11 remote
  user.

  When upgrading to glib-networking, glib-networking-common and lib-
  networking-services to 2.48.2-1~ubuntu16.04.2; all sessions crash
  randomly at the same time many times a day.

  When it happens, all users are disconnected and it looks like lightdm
  is restarted.

  Downgrading to 2.48.2-1~ubuntu16.04.1 resolve the problem.

  X11 terminals were not upgraded.

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

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

[Desktop-packages] [Bug 1879159] Re: Boot Problem

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1879159

Title:
  Boot Problem

Status in xorg package in Ubuntu:
  New

Bug description:
  It shows graphics problem during booting and unable to operate mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219
  Uname: Linux 4.4.0-179-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun May 17 13:19:12 2020
  DistUpgraded: 2020-03-29 23:06:17,899 DEBUG /openCache(), new cache size 56855
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0555]
  InstallationDate: Installed on 2020-03-24 (54 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Dell Inc. Inspiron 3520
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-179-generic 
root=UUID=2e048bbe-fc79-442e-ae8d-aac97ebb2938 ro quiet splash vt.handoff=7 
init=/sbin/upstart
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2020-03-29 (48 days ago)
  dmi.bios.date: 05/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3520
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 17 13:15:51 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   21569 
   vendor SEC
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Desktop-packages] [Bug 1879211] Re: Charging my cellphone through usb breaks internet connection.

[Alex Murray]

One more thing - I expect your phone has USB Tethering enabled - and so
presents itself as an rndis USB/ethernet device - and then network
manager uses this as a preferred interface to route traffic through
rather than the wireless interface.

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

Title:
  Charging my cellphone through usb breaks internet connection.

Status in network-manager package in Ubuntu:
  New

Bug description:
  I don't know what package is responsible for this. I entered iptables
  because the ip command was not recognized as a package.

  I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
  #ip route
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  Here it is after I plug my cellphone
  #ip route
  default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  So my computer is trying to access all ips using my cellphone as a
  router, which of course fails.

  the command "sudo ip route del default" followed by "sudo ip route add
  default via 192.168.0.1 dev wlp2s0" restores my connection.

  Thank you for your attention. I'm available to answer any questions
  and fix this bug. Reporting this bug was already effort diverted from
  my other tasks, so let's make this count no matter how deep it cuts.

  P.S: I went ahead and marked this bug as a security vulnerability
  because I can think of ways this can be exploited, especially if the
  cellphone can trigger the bug and route traffic so that the user
  doesn't suspect it. If you feel the security impact is small and that
  there are other more important security issues, feel free to unmark it
  and we can deal with it's usability impact, which is probably more
  impactful.

  Regards,
  Tomás.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iptables 1.6.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 22:59:02 2020
  InstallationDate: Installed on 2019-02-08 (464 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879211] Re: Charging my cellphone through usb breaks internet connection.

[Alex Murray]

This doesn't seem like a security issue to me - I believe this is the
default behaviour when using network manager for tethering - it will
route traffic via the tethered device. I am reassigning this against
network-manager which is likely doing the route setup.

** Information type changed from Private Security to Public

** Package changed: iptables (Ubuntu) => network-manager (Ubuntu)

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

Title:
  Charging my cellphone through usb breaks internet connection.

Status in network-manager package in Ubuntu:
  New

Bug description:
  I don't know what package is responsible for this. I entered iptables
  because the ip command was not recognized as a package.

  I use the ip route to debug internet problems. Here it is before plugging my 
cellphone through usb:
  #ip route
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  Here it is after I plug my cellphone
  #ip route
  default via 192.168.42.129 dev enp0s20f0u1 proto dhcp metric 100 
  default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
  25.0.0.0/8 dev ham0 proto kernel scope link src 25.69.248.65 
  169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 
  192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.51 metric 600 
  192.168.42.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.42.114 
metric 100 
  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown 

  So my computer is trying to access all ips using my cellphone as a
  router, which of course fails.

  the command "sudo ip route del default" followed by "sudo ip route add
  default via 192.168.0.1 dev wlp2s0" restores my connection.

  Thank you for your attention. I'm available to answer any questions
  and fix this bug. Reporting this bug was already effort diverted from
  my other tasks, so let's make this count no matter how deep it cuts.

  P.S: I went ahead and marked this bug as a security vulnerability
  because I can think of ways this can be exploited, especially if the
  cellphone can trigger the bug and route traffic so that the user
  doesn't suspect it. If you feel the security impact is small and that
  there are other more important security issues, feel free to unmark it
  and we can deal with it's usability impact, which is probably more
  impactful.

  Regards,
  Tomás.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iptables 1.6.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 17 22:59:02 2020
  InstallationDate: Installed on 2019-02-08 (464 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: iptables
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879234] Re: Xorg freeze

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1879234

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  when i was my computer on and start blinking middle of screen please
  solve it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 10:24:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1867735] Re: Can't login after computer locks on idle

[Alex Murray]

gnome-shell is responsible for the lock screen so reassigning to that

** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1867735

Title:
  Can't login after computer locks on idle

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After a leave my computer on idle and try to put my password to login the 
screen starts to blink whenever I click on the screen. The workaround I found 
is to click on the switch user button to log back in but some windows are 
closed on this process.
  Also when the screen is locked I'm able to see the windows running on the 
user profile without unlocking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: login 1:4.8.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 17 09:49:09 2020
  InstallationDate: Installed on 2019-12-24 (83 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: Upgraded to focal on 2020-03-15 (1 days ago)

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

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

[Desktop-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

[Alex Murray]

** Information type changed from Private Security to Public Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1706770

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in Ubuntu MATE:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mate-session-manager package in Ubuntu:
  Confirmed

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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

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

[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1866256

Title:
  Disabled animations breaks lock screen and other dialogs, reveals
  information from the screen without unlocking

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Dear Ubuntu Team,
  I'm using the latest Ubuntu 20 focal, update it every day.
  After some of the upgrades something happened and screenlock and other 
dialogs became broken (i'll describe below).
  It was very hard to find what caused this (i reset all keys in dconf one by 
one and restarted) and finally i found it:   
/org/gnome/desktop/interface/enable-animations  My animations were disabled 
(they are slow even on supertop hardware). 

  So the problem is: it seems that new GNOME 3.36 lock screen and other
  dialogs like "Ask for a root password" rely on animations and without
  it they do not work or work incorrectly/insecure.

  1. Screenlock can lock a screen without any problem. When i try to
  unlock it and click by mouse/key, i except a dialog with password
  prompt to appear.  However, instead of the dialog Screenlock just
  shows my screen and running applications with all my data, for some
  time.  Then it again locks the screen.  I can repeat this as many
  times as i want and steal all the information.  See the attached
  video, you will see the dconf-editor running. Sorry for the video
  quality.

  The only way to unlock the screen is to click an icon at the bottom-
  right "Change user". Then i get  a list of users, can choose myself
  and type a password.

  2. Other dialogs like asking for a root password (when it's required
  to run an application under root), just do not appear.  Screen blinks
  and that's all.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
  Uname: Linux 5.4.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 23:32:51 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-12-11 (85 days ago)
  InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1866042] [NEW] AppIndicator labels are not centered vertically

[Alex Murray]

Public bug reported:

After a recent gnome-shell + yaru-theme update, AppIndicator labels are
now shown aligned with the top of the top bar instead of aligned
vertically centered as previously https://imgur.com/a/jKVP5w9

(This is the indicator-sensors snap, which creates an AppIndicator with
a label as per https://github.com/alexmurray/indicator-
sensors/blob/master/indicator-sensors/is-indicator.c#L211)

Whilst this only became evident after the most recent gnome-shell
upgrade it is not clear to me which package this should be filed
against, and so am filing it against the appindicator extension
initially as directed by Laney in #ubuntu-desktop :)

Let me know if there is anything I can do to help debug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-appindicator 32-1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  4 21:26:31 2020
InstallationDate: Installed on 2019-11-18 (106 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-appindicator
UpgradeStatus: Upgraded to focal on 2020-01-22 (42 days ago)

** Affects: gnome-shell-extension-appindicator (Ubuntu)
 Importance: Undecided
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1866042

Title:
  AppIndicator labels are not centered vertically

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  After a recent gnome-shell + yaru-theme update, AppIndicator labels
  are now shown aligned with the top of the top bar instead of aligned
  vertically centered as previously https://imgur.com/a/jKVP5w9

  (This is the indicator-sensors snap, which creates an AppIndicator
  with a label as per https://github.com/alexmurray/indicator-
  sensors/blob/master/indicator-sensors/is-indicator.c#L211)

  Whilst this only became evident after the most recent gnome-shell
  upgrade it is not clear to me which package this should be filed
  against, and so am filing it against the appindicator extension
  initially as directed by Laney in #ubuntu-desktop :)

  Let me know if there is anything I can do to help debug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-appindicator 32-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 21:26:31 2020
  InstallationDate: Installed on 2019-11-18 (106 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to focal on 2020-01-22 (42 days ago)

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

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

[Desktop-packages] [Bug 1866042] Re: AppIndicator labels are not vertically centered

[Alex Murray]

Image demonstrating the issue

** Attachment added: "Screenshot from 2020-03-04 21-21-01.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1866042/+attachment/5333430/+files/Screenshot%20from%202020-03-04%2021-21-01.png

** Summary changed:

- AppIndicator labels are not vertically centered
+ AppIndicator labels are not centered vertically

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1866042

Title:
  AppIndicator labels are not centered vertically

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  After a recent gnome-shell + yaru-theme update, AppIndicator labels
  are now shown aligned with the top of the top bar instead of aligned
  vertically centered as previously https://imgur.com/a/jKVP5w9

  (This is the indicator-sensors snap, which creates an AppIndicator
  with a label as per https://github.com/alexmurray/indicator-
  sensors/blob/master/indicator-sensors/is-indicator.c#L211)

  Whilst this only became evident after the most recent gnome-shell
  upgrade it is not clear to me which package this should be filed
  against, and so am filing it against the appindicator extension
  initially as directed by Laney in #ubuntu-desktop :)

  Let me know if there is anything I can do to help debug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-appindicator 32-1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  4 21:26:31 2020
  InstallationDate: Installed on 2019-11-18 (106 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to focal on 2020-01-22 (42 days ago)

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

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

[Desktop-packages] [Bug 1857539] Re: nautilus crashed with SIGSEGV

[Alex Murray]

@seb128  - I just noticed this - Apport popped up just after login
saying Files (aka nautilus) had crashed - and pointed at this bug
report. This was the first time I have seen it so not sure if it is
reproducible and I didn't take any particular steps to make it occur.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1857539

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  after turn on pc

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 25 01:52:06 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-12-22 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax
   PC (0x7f3fb437f962) ok
   source "0x380(%rax)" (0x0380) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:
   
  usr_lib_nautilus:

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

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

[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages

[Alex Murray]

Thanks for the patch - I've rebuilt gnome-software with it here
https://launchpad.net/~alexmurray/+archive/ubuntu/lp1862158 and will let
you know how that behaves.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1862158

Title:
  gnome-software tries to install snap updates in the background,
  causing unprompted polkit authentication for authorisation to install
  packages

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Every morning about ~30mins after powering on my focal machine I get
  (unprompted) a gnome-shell policykit authorisation popup saying
  'authentication is required to install software' - I haven't yet
  actually authorised it since I wasn't sure what was causing it,
  however I notice that if I cancel the authorisation then I see a bunch
  of notifications from gnome-software about updates having been
  successfully installed (even though I presume it hasn't been since I
  never authorised it).

  Is gnome-software fighting snapd to refresh snaps?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 21:37:29 2020
  InstallationDate: Installed on 2019-11-18 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago)

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

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

[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages

[Alex Murray]

Happened again this morning - see attached for some screenshots which
demonstrate the various elements.

** Attachment added: "polkit dialog trigged automatically with no user 
interaction"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+attachment/5326025/+files/Screenshot%20from%202020-02-07%2008-18-07.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1862158

Title:
  gnome-software tries to install snap updates in the background,
  causing unprompted polkit authentication for authorisation to install
  packages

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Every morning about ~30mins after powering on my focal machine I get
  (unprompted) a gnome-shell policykit authorisation popup saying
  'authentication is required to install software' - I haven't yet
  actually authorised it since I wasn't sure what was causing it,
  however I notice that if I cancel the authorisation then I see a bunch
  of notifications from gnome-software about updates having been
  successfully installed (even though I presume it hasn't been since I
  never authorised it).

  Is gnome-software fighting snapd to refresh snaps?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 21:37:29 2020
  InstallationDate: Installed on 2019-11-18 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago)

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

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

[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages

[Alex Murray]

Also note after choosing 'Cancel' for the authentication, it notifies to
say updates were successfully installed which is very odd :/

** Attachment added: "Notification of updated snaps even though operation was 
not authorised"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+attachment/5326026/+files/Screenshot%20from%202020-02-07%2008-18-20.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1862158

Title:
  gnome-software tries to install snap updates in the background,
  causing unprompted polkit authentication for authorisation to install
  packages

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Every morning about ~30mins after powering on my focal machine I get
  (unprompted) a gnome-shell policykit authorisation popup saying
  'authentication is required to install software' - I haven't yet
  actually authorised it since I wasn't sure what was causing it,
  however I notice that if I cancel the authorisation then I see a bunch
  of notifications from gnome-software about updates having been
  successfully installed (even though I presume it hasn't been since I
  never authorised it).

  Is gnome-software fighting snapd to refresh snaps?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 21:37:29 2020
  InstallationDate: Installed on 2019-11-18 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago)

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

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

[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages

[Alex Murray]

Happened again this morning - see attached for some screenshots which
demonstrate the various elements.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1862158

Title:
  gnome-software tries to install snap updates in the background,
  causing unprompted polkit authentication for authorisation to install
  packages

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Every morning about ~30mins after powering on my focal machine I get
  (unprompted) a gnome-shell policykit authorisation popup saying
  'authentication is required to install software' - I haven't yet
  actually authorised it since I wasn't sure what was causing it,
  however I notice that if I cancel the authorisation then I see a bunch
  of notifications from gnome-software about updates having been
  successfully installed (even though I presume it hasn't been since I
  never authorised it).

  Is gnome-software fighting snapd to refresh snaps?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 21:37:29 2020
  InstallationDate: Installed on 2019-11-18 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago)

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

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

[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages

[Alex Murray]

** Attachment added: "journalctl --grep gnome-software --since 'Thu 2020-02-06 
05:40:25 ACDT'"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+attachment/5325864/+files/journalctl--grep-gnome-software-for-today.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1862158

Title:
  gnome-software tries to install snap updates in the background,
  causing unprompted polkit authentication for authorisation to install
  packages

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Every morning about ~30mins after powering on my focal machine I get
  (unprompted) a gnome-shell policykit authorisation popup saying
  'authentication is required to install software' - I haven't yet
  actually authorised it since I wasn't sure what was causing it,
  however I notice that if I cancel the authorisation then I see a bunch
  of notifications from gnome-software about updates having been
  successfully installed (even though I presume it hasn't been since I
  never authorised it).

  Is gnome-software fighting snapd to refresh snaps?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 21:37:29 2020
  InstallationDate: Installed on 2019-11-18 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago)

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

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

[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages

[Alex Murray]

Attached log output for gnome-software (if there is a better way to
obtain this or more complete logs for gnome-software please let me
know).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1862158

Title:
  gnome-software tries to install snap updates in the background,
  causing unprompted polkit authentication for authorisation to install
  packages

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Every morning about ~30mins after powering on my focal machine I get
  (unprompted) a gnome-shell policykit authorisation popup saying
  'authentication is required to install software' - I haven't yet
  actually authorised it since I wasn't sure what was causing it,
  however I notice that if I cancel the authorisation then I see a bunch
  of notifications from gnome-software about updates having been
  successfully installed (even though I presume it hasn't been since I
  never authorised it).

  Is gnome-software fighting snapd to refresh snaps?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 21:37:29 2020
  InstallationDate: Installed on 2019-11-18 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago)

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

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

[Desktop-packages] [Bug 1862158] [NEW] gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages

[Alex Murray]

Public bug reported:

Every morning about ~30mins after powering on my focal machine I get
(unprompted) a gnome-shell policykit authorisation popup saying
'authentication is required to install software' - I haven't yet
actually authorised it since I wasn't sure what was causing it, however
I notice that if I cancel the authorisation then I see a bunch of
notifications from gnome-software about updates having been successfully
installed (even though I presume it hasn't been since I never authorised
it).

Is gnome-software fighting snapd to refresh snaps?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software 3.35.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  6 21:37:29 2020
InstallationDate: Installed on 2019-11-18 (79 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.35.2-0ubuntu1
SourcePackage: gnome-software
UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago)

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


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1862158

Title:
  gnome-software tries to install snap updates in the background,
  causing unprompted polkit authentication for authorisation to install
  packages

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Every morning about ~30mins after powering on my focal machine I get
  (unprompted) a gnome-shell policykit authorisation popup saying
  'authentication is required to install software' - I haven't yet
  actually authorised it since I wasn't sure what was causing it,
  however I notice that if I cancel the authorisation then I see a bunch
  of notifications from gnome-software about updates having been
  successfully installed (even though I presume it hasn't been since I
  never authorised it).

  Is gnome-software fighting snapd to refresh snaps?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.35.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 21:37:29 2020
  InstallationDate: Installed on 2019-11-18 (79 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.35.2-0ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago)

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

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

[Desktop-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

[Alex Murray]

** Attachment added: "Brother_HL_L2375DW_series.ppd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309146/+files/Brother_HL_L2375DW_series.ppd

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1853879

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

[Alex Murray]

** Attachment added: "brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309145/+files/Brother_HL_L2375DW_series%40BRW0C96E67E441E.local.ppd

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1853879

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

[Alex Murray]

** Attachment added: "error_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309038/+files/error_log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1853879

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

[Alex Murray]

** Attachment added: "attrs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+attachment/5309039/+files/attrs.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1853879

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

[Alex Murray]

Let me know which of these PPDs to attach:

$ ls -la /etc/cups/ppd/Brother_HL_L2375DW_series*
-rw-r--r-- 1 root root 8499 Dec  1 17:14 
/etc/cups/ppd/brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd
-rw-r- 1 root lp   8424 Dec  1 17:13 
/etc/cups/ppd/brother_hl_l2375dw_ser...@brw0c96e67e441e.local.ppd.O
-rw-r- 1 root lp   8615 Dec  1 17:13 
/etc/cups/ppd/Brother_HL_L2375DW_series.ppd
-rw-r--r-- 1 root root 8487 Dec  1 16:32 
/etc/cups/ppd/Brother_HL_L2375DW_series.ppd.O


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1853879

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge

[Alex Murray]

I have the same problem with a Brother HL L2375-DW printer on Ubuntu
19.10.

This was auto-detected and added to the GNOME Printers as
'Brother_HL_L2375DW_series' - if I print double sided (long-edge) using
the then it prints the second page upside down (as though I had selected
short-edge) - but selecting short-edge also prints as short-edge.

However, I then went into 'Printer Details' via the gear menu for the
printer, and selected 'Select from Database...' and chose the  'Brother
HL-L2375DW series, driverless, cups-filters 1.25' driver. At this stage
a second instance of the printer appeared in GNOME Printers
('Brother_HL_L2375DW_series@BRW0C96E67E441E.local') - and printing to
this second instance seems to work correctly.

I am unsure how to know which PPD was used for the first auto-detected +
added instance but if you can help me to find out I will happily attach
the PPD here. See below for error_log, attrs.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1853879

Title:
  Dell E310dw: Default driver doesn't work, driverless fails on sides
  =two-sided-long-edge

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Dell E310dw printer which worked well on 19.04 has problems in 19.10:

  First, I went through the CUPS web interface to add the printer. The
  interface gave me a choice of two entries with the same name plus one
  with "driverless" added. I chose the first entry (not driverless) and
  completed adding the printer. On the Printers page, the Dell was now
  listed. When I tried "Print Test Page", I got many pages each
  containing a single line of symbols.

  I deleted the printer in the web interface, intending to start again and 
choose the second option. But after I did Delete Printer, CUPS took me back to 
the Printers page which now listed:
  Dell_Printer_E310dw@DELL316BAA.local  Dell Printer E310dw, 
driverless, cups-filters 1.25.11

  So I clicked on that printer and tried Print Test Page, which worked.
  So then I tried a duplex print (which is really what I need this
  morning):

   lp -o sides=two-sided-long-edge -o collate=true -d
  Dell_Printer_E310dw@DELL316BAA.local filename.pdf

  It printed the PDF 2-sided, but with the sides flipped around the
  short edge, as if it was a landscape print. I tried the same command
  with sides=two-sided-short-edge and it flipped the same way. So sides
  is handling duplex but ignoring which edge is supposed to be used, and
  defaulting to landscape which I'd guess is less commonly what people
  want.

  This is all using what's built into Ubuntu. I haven't yet downloaded
  any extra drivers from Dell's site since Ubuntu claims to have a
  driver for the printer, and I'm pretty sure it was working in 19.04 (I
  may still have a working 19.04 to check that, if it would help).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Mon Nov 25 09:58:21 2019
  InstallationDate: Installed on 2019-10-10 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat:
   device for Brother_HL-3170CDW_series: 
dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee
   device for Dell_Printer_E310dw@DELL316BAA.local: 
implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/
  MachineType: LENOVO 20QDCTO1WW
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', 
'/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied
   grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET30W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage 

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

[Alex Murray]

@gunnarhj - updated packages for ibus are now available in the ubuntu-
security-proposed PPA at https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa

Also I note the bug descriptions lists ibus in Focal as Fix Released -
but the latest version in focal (1.5.21-1~exp2ubuntu2) is the one with
the patch reverted - would you like me to upload an updated focal
version as well to the above PPA?

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  In Progress
Status in glib2.0 source package in Bionic:
  In Progress
Status in glib2.0 source package in Disco:
  In Progress
Status in glib2.0 source package in Eoan:
  In Progress
Status in glib2.0 source package in Focal:
  Fix Committed
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849920] Re: ubuntu display problem

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1849920

Title:
  ubuntu display problem

Status in xorg package in Ubuntu:
  New

Bug description:
  wrong resolution
  login takes time
  does not detect intel graphics

  i am using ubuntu 18.04.03

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 02:35:27 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13d1]
  InstallationDate: Installed on 2019-10-09 (16 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 13d3:5a11 IMC Networks 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash 
i915.alpha_support=1 vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier "Card0"
   Driver "intel"
   Option "AccelMethod" "sna"
   EndSection
  dmi.bios.date: 06/11/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441UAR.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441UAR.308:bd06/11/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook14_ASUSLaptopX441UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook 14_ASUS Laptop X441UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100+git1910190630.fc9336~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1910200730.7ceafa~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1910200730.7ceafa~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

[Alex Murray]

>From a security point of view, it is best if this issue is fixed not
just in Ubuntu but other distributions - and the best way to ensure that
is to get a CVE assigned for it. Has a CVE been applied for for this
issue? If not, could you please submit one to MITRE and when one is
assigned please report it back here https://cveform.mitre.org/ - if one
has already been assigned please post the CVE number here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833479

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in jackd2 package in Ubuntu:
  New
Status in jackd2 package in Debian:
  New

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

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

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

[Desktop-packages] [Bug 1834815] Re: usb mouse is not being detect

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1834815

Title:
  usb mouse is not being detect

Status in xorg package in Ubuntu:
  New

Bug description:
  plug in usb mouse but not being detected and is not working

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 11:30:48 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 430.26, 5.0.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
   NVIDIA Corporation GF108M [GeForce GT 620M/630M/635M/640M LE] [10de:0de9] 
(rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo GeForce GT 640M LE [17aa:3977]
  InstallationDate: Installed on 2019-06-28 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO Lenovo IdeaPad Y480
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN40WW(V2.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Mainboard version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y480
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN40WW(V2.07):bd10/10/2012:svnLENOVO:pnLenovoIdeaPadY480:pvrLenovoIdeaPadY480:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoIdeaPadY480:
  dmi.product.family: IDEAPAD
  dmi.product.name: Lenovo IdeaPad Y480
  dmi.product.sku: Type1Sku0
  dmi.product.version: Lenovo IdeaPad Y480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/xorg/+bug/1834815/+subscriptions

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

[Desktop-packages] [Bug 1835166] [NEW] Update bolt to latest 0.8 release for eoan

[Alex Murray]

Public bug reported:

bolt 0.8 adds support for IOMMU handling which should help mitigate some
of the risks identified in the thunderclap research
https://thunderclap.io/

https://gitlab.freedesktop.org/bolt/bolt/-/tags/0.8

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

** Affects: bolt (Ubuntu Eoan)
 Importance: Undecided
 Status: New

** Also affects: bolt (Ubuntu Eoan)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bolt in Ubuntu.
https://bugs.launchpad.net/bugs/1835166

Title:
  Update bolt to latest 0.8 release for eoan

Status in bolt package in Ubuntu:
  New
Status in bolt source package in Eoan:
  New

Bug description:
  bolt 0.8 adds support for IOMMU handling which should help mitigate
  some of the risks identified in the thunderclap research
  https://thunderclap.io/

  https://gitlab.freedesktop.org/bolt/bolt/-/tags/0.8

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

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

[Desktop-packages] [Bug 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor

[Alex Murray]

>From a security PoV this is basic security by obscurity and effectively
pointless - they are simply XORing each byte with a fixed value and then
base64 encoding it - since the source code is public anyone can easily
find this out and hence easily decode it - the only way to do this
securely would be to have the DBus peers negotiate a session key and
encrypt it properly using this - so I don't think there is any point
adding this faux-encryption in this case.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1828124

Title:
  org.gnome.evolution.dataserver.Source completely unveils account
  credentials in plain text while using dbus-monitor

Status in evolution-data-server:
  New
Status in evolution-data-server package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Install Evolution
  3. Set-up Google account with default settings (this will end with e-mail and 
calendar)
  4. Reboot
  5. Open evolution Calendar and/or indicator-datetime
  6. Launch `dbus-monitor`

  Expected results:
  * Evolution does not show account credentials in plain text in `dbus-monitor` 
output

  Actual results:
  * Evolution shows account credentials in plain text in `dbus-monitor` output:

  
  method call time=1557268474.383095 sender=:1.74 -> destination=:1.40 
serial=939 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=InvokeAuthenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]
  method return time=1557268474.383686 sender=:1.40 -> destination=:1.74 
serial=366 reply_serial=939
  signal time=1557268474.389206 sender=:1.40 -> destination=(null destination) 
serial=367 path=/org/gnome/evolution/dataserver/SourceManager/Source_17; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
 ]

  signal time=1557268520.956861 sender=:1.40 -> destination=(null destination) 
serial=408 path=/org/gnome/evolution/dataserver/SourceManager/Source_19; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.960443 sender=:1.40 -> destination=(null destination) 
serial=409 path=/org/gnome/evolution/dataserver/SourceManager/Source_18; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]
  signal time=1557268520.964374 sender=:1.40 -> destination=(null destination) 
serial=410 path=/org/gnome/evolution/dataserver/SourceManager/Source_20; 
interface=org.gnome.evolution.dataserver.Source; member=Authenticate
 array [
string "password:myrealpassword"
string "ssl-trust:"
string "username:real@email"
 ]

  -
  This is huge security flaw. The malicious script can parse `dbus-monitor` 
output...
  Not sure about more recent Ubuntu and Evolution versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution-data-server-common 3.18.5-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170
  Uname: Linux 4.4.0-143-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  8 01:40:27 2019
  InstallationDate: Installed on 2018-01-04 (488 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: evolution-data-server
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+subscriptions

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

[Desktop-packages] [Bug 1828218] Re: boeug

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1828218

Title:
  boeug

Status in xorg package in Ubuntu:
  New

Bug description:
  l'ecran seiltiller et sauter aucune action possible

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-1030.35-oem 4.15.18
  Uname: Linux 4.15.0-1030-oem x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May  8 14:07:10 2019
  DistUpgraded: 2018-12-01 19:20:26,688 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « 
./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8))
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0870]
  InstallationDate: Installed on 2018-11-14 (174 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  MachineType: Dell Inc. G3 3779
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1030-oem 
root=UUID=4a3ac732-314e-4b02-a764-e7333473d040 ro acpi_osi=Linux-Dell-Video 
acpi_osi=Linux-Dell-Video acpi_osi=Linux-Dell-Video acpi_osi=Linux-Dell-Video 
quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-12-01 (157 days ago)
  dmi.bios.date: 07/18/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0NY03M
  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:bd07/18/2018:svnDellInc.:pnG33779:pvr:rvnDellInc.:rn0NY03M:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: GSeries
  dmi.product.name: G3 3779
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1827959]

[Alex Murray]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1827727, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1827727
   All plugins disabled due to expired cert

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1827959

Title:
  All extensions disabled due to expiration of intermediate signing cert

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to the expiration of a signing certificate, a collection of addon
  (some related to privacy) are disabled. There are a variety of
  workarounds, but these all reduce browser users safety (including the
  approach proposed by Mozilla).

  Mozilla has released a version that repairs the cert chain 66.0.4 (see
  https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-
  in-firefox/), but this has not been packaged for any ubuntu version
  except Eoan Ermine.

  Please release an update for other supported ubuntu versions.

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

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

[Desktop-packages] [Bug 1827959] Re: All extensions disabled due to expiration of intermediate signing cert

[Alex Murray]

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

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1827959

Title:
  All extensions disabled due to expiration of intermediate signing cert

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973

  Due to the expiration of a signing certificate, a collection of addon
  (some related to privacy) are disabled. There are a variety of
  workarounds, but these all reduce browser users safety (including the
  approach proposed by Mozilla).

  Mozilla has released a version that repairs the cert chain 66.0.4 (see
  https://blog.mozilla.org/addons/2019/05/04/update-regarding-add-ons-
  in-firefox/), but this has not been packaged for any ubuntu version
  except Eoan Ermine.

  Please release an update for other supported ubuntu versions.

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

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

[Desktop-packages] [Bug 1827282] Re: package sgml-base 1.29 failed to install/upgrade: triggers looping, abandoned

[Alex Murray]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sgml-base in Ubuntu.
https://bugs.launchpad.net/bugs/1827282

Title:
  package sgml-base 1.29 failed to install/upgrade: triggers looping,
  abandoned

Status in sgml-base package in Ubuntu:
  New

Bug description:
  No se

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: sgml-base 1.29
  ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:45:03 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-04-16 (1110 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1
   apt  1.8.0
  SourcePackage: sgml-base
  Title: package sgml-base 1.29 failed to install/upgrade: triggers looping, 
abandoned
  UpgradeStatus: Upgraded to disco on 2019-05-01 (0 days ago)

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

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