[Desktop-packages] [Bug 2064093] Re: if-up.d files do not have effect on ubuntu 24.04 LTS

[Nicolas]

It also looks like on 24.04, the if-up.d scripts aren't run at all when
resuming from sleep.

Before 24.04:
- Boot
- My if-up.d script that triggers for "IFACE=wlp0s20f3" gets properly triggered 
(it adds an IP alias to this interface using "ip addr add").
- Put ubuntu to sleep
- Resume ubuntu
- My if-up.d script that triggers for "IFACE=wlp0s20f3" gets properly triggered.

After 24.04:
- Boot
- My if-up.d script that triggers for "IFACE=wlp0s20f3" gets properly triggered 
(it adds an IP alias to this interface using "ip addr add"). Apparently I could 
fix this by triggering this script with "IFACE=-all". For now I manually run 
the "ip addr add" command.
- Put ubuntu to sleep
- Resume ubuntu
- My if-up.d script that triggers for "IFACE=wlp0s20f3" is not called (not even 
with "IFACE=-all"). The IP alias disappeared, so the interface did go down and 
get back up, but the script wasn't called at all. For this I don't think I have 
a fix?

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

Title:
  if-up.d files do not have effect on ubuntu 24.04 LTS

Status in ifupdown package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Some time ago I wrote a detailed answer to fix an error for lowering
  MTU size for a cisco-compatible VPN
  (here:https://unix.stackexchange.com/questions/768757/unable-to-ssh-
  into-remote-machine-but-able-to-ping-vpnc/768758#768758)

  After upgrading to Ubuntu 24.04 LTS, I'm unable with the same steps to
  lower the MTU size.

  In particular, if I run the following command from the terminal

  sudo ifconfig your_tunnel_name mtu 1370 up

  it seems to lower the MTU size.

  However, the script under /etc/network/if-up.d is not automatically
  triggered.

  Does something change with the newer Ubuntu version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2064093/+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 2063484] [NEW] Other Software now displays the Suites instead of the Comments

[nicolas]

Public bug reported:

Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk
shows the wrong field in the UI for Other Software.

Where it should show the Comment field, it shows the Suites field. It
only does it if there is a value in Comment though.

For instance, imagine I have Inkscape PPA as a software source, with the
Suites “hirsute” and the Comment “Inkscape”. In the UI, it will show
“hirsute” instead of “Inkscape” as a title like it used to do. If I
empty the Comment field, it does remove the title and “hirsute” is not
displayed.

One more thing from the upgrade: all the Comment fields’ content got
lost in the process. So I have no some sources that I can’t remember why
I had installed, even though I have software coming from them, which I
had indicated in Comment.

This has been working well for the past 10-15 years, so it’s definitely
a mistake that has been introduced with the new version. The field edit
dialogue has changed a little bit, so I’m guessing that change
introduced the bug.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Other Software now displays the Suites instead of the Comments

Status in software-properties package in Ubuntu:
  New

Bug description:
  Since updating from Ubuntu 24.04 (from 23.10), software-properties-gtk
  shows the wrong field in the UI for Other Software.

  Where it should show the Comment field, it shows the Suites field. It
  only does it if there is a value in Comment though.

  For instance, imagine I have Inkscape PPA as a software source, with
  the Suites “hirsute” and the Comment “Inkscape”. In the UI, it will
  show “hirsute” instead of “Inkscape” as a title like it used to do. If
  I empty the Comment field, it does remove the title and “hirsute” is
  not displayed.

  One more thing from the upgrade: all the Comment fields’ content got
  lost in the process. So I have no some sources that I can’t remember
  why I had installed, even though I have software coming from them,
  which I had indicated in Comment.

  This has been working well for the past 10-15 years, so it’s
  definitely a mistake that has been introduced with the new version.
  The field edit dialogue has changed a little bit, so I’m guessing that
  change introduced the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2063484/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)

[Nicolas Dechesne]

Thanks for the ping.. I have had no feedback from NVIDIA (DGX,
Bluefield, Tegra), and I have informed them that from now on, we
consider that 'no feedback' meant they are ok with the change.

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 2048105] [NEW] Connecting second bluetooth device fails

[Nicolas Krzywinski]

Public bug reported:

System:
Ubuntu 22.04
bluez version 5.64

Devices:
2x Playstation 5 DualSense Controllers

Problem description:
Connecting either of the controllers individually works without a problem. But 
when trying to connect both of them, the second fails.

Following sequence is typical and shows that there is no problem with the 
controllers itself:
1) connect controller #1 > succeeds
2) connect controller #2 > fails
3) disconnect controller #1
4) connect controller #2 > succeeds
5) connect controller #1 > fails

SOMETIMES it works though and I didn't found out what was different.
Connecting both of the controllers immediately after boot+logon works most of 
the times!

When connecting a controller fails, there is _nothing_ in syslog.
Both controllers have been paired successfully and marked as trusted devices.
The failing connect attempt of the second controller first shows the system 
notification "connected", followed by a "disconnected" approximately 10-20 
seconds later.

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


** Tags: jammy

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

Title:
  Connecting second bluetooth device fails

Status in bluez package in Ubuntu:
  New

Bug description:
  System:
  Ubuntu 22.04
  bluez version 5.64

  Devices:
  2x Playstation 5 DualSense Controllers

  Problem description:
  Connecting either of the controllers individually works without a problem. 
But when trying to connect both of them, the second fails.

  Following sequence is typical and shows that there is no problem with the 
controllers itself:
  1) connect controller #1 > succeeds
  2) connect controller #2 > fails
  3) disconnect controller #1
  4) connect controller #2 > succeeds
  5) connect controller #1 > fails

  SOMETIMES it works though and I didn't found out what was different.
  Connecting both of the controllers immediately after boot+logon works most of 
the times!

  When connecting a controller fails, there is _nothing_ in syslog.
  Both controllers have been paired successfully and marked as trusted devices.
  The failing connect attempt of the second controller first shows the system 
notification "connected", followed by a "disconnected" approximately 10-20 
seconds later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2048105/+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 2028864] Re: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64)

[Nicolas Dechesne]

hey Sandeep, there has been no (direct) progress so far on this issue.
However we now have Ubuntu 22.04 images/support for Jetson Orin. For now
without graphics/desktop support, but we are planning to enable
desktop/graphics in our current development cycle (before end of April).
We will look further into this issue during this timeframe.

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

Title:
  [snap] chromium browser does not work with accelerated graphics on
  Tegra (arm64)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Tegra Orin platforms come in various flavor / dev kit. They all ship
  with a 'slightly' customized Ubuntu image. One of the customization is
  the addition of the Nvidia GPU drivers for Tegra.

  When running chromium browser debian package (either when running
  18.04, or when running 22.04 with the package fetched from this PPA:
  https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages)
  then chromium works with hardware acceleration, as reported in
  chrome://gpu:

  Graphics Feature Status
  Canvas: Hardware accelerated
  Canvas out-of-process rasterization: Disabled
  Direct Rendering Display Compositor: Disabled
  Compositing: Hardware accelerated
  Multiple Raster Threads: Enabled
  OpenGL: Enabled
  Rasterization: Hardware accelerated
  Raw Draw: Disabled
  Video Decode: Hardware accelerated
  Video Encode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Hardware accelerated
  WebGL2: Hardware accelerated
  WebGPU: Disabled

  When using the snap version of chromium browser (on either 20.04 or
  22.04), hardware acceleration is disabled, as shown in chrome://gpu:

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Canvas out-of-process rasterization: Disabled
  Direct Rendering Display Compositor: Disabled
  Compositing: Software only. Hardware acceleration disabled
  Multiple Raster Threads: Enabled
  OpenGL: Disabled
  Rasterization: Software only. Hardware acceleration disabled
  Raw Draw: Disabled
  Skia Graphite: Disabled
  Video Decode: Software only. Hardware acceleration disabled
  Video Encode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Software only, hardware acceleration unavailable
  WebGL2: Software only, hardware acceleration unavailable
  WebGPU: Disabled
  Problems Detected
  WebGPU has been disabled via blocklist or the command line.
  Disabled Features: webgpu
  Accelerated video encode has been disabled, either via blocklist, about:flags 
or the command line.
  Disabled Features: video_encode
  Gpu compositing has been disabled, either via blocklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  These tests are done with X11.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028864/+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 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s

[Nicolas Dechesne]

thanks! I got feedback from xnox on my SRU, so it was still on my list
to improve it but got swamped with the sprints prep (it's only my 2nd
SRU..). Just to be clear I understand, do I need to open a new bug for
mantic, or can i reuse this one?

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

Title:
   [SRU] Fix fcc-unlock script for Lenovo X13s

Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Mantic:
  New
Status in modemmanager source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon
  8cx, come with an integrated 4G/5G modem. The modem on the X13s is
  manufactured by foxconn, and is based on the Qualcomm Snapdragon X55
  PCIe modem.

  Here is the output of mmcli -m 0 on an X13s

Hardware  |manufacturer: foxconn
  |   model: Qualcomm Snapdragon X55 5G
  |   firmware revision: T99W175.F0.6.0.0.6.OG.005
  |  045  1  [Feb 03 2023 10:00:00]
   
  All Linux kernel drivers are upstream to support this data modem, and 
included in the Ubuntu kernel for mantic. The support for this modem is also 
merged in modemmanager, including the fcc-unlock script for this modem model 
(https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22).
 

  We are however missing the symlink for the specific PCIe ID link
  reported on the X13s for this modem, which is shown by lspci as:

  0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc.
  T99W175 5G Modem [Snapdragon X55] [105b:e0c3]

  This is already fixed upstream with
  https://gitlab.freedesktop.org/mobile-
  broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838.

  With the backport of this patch the modem on the X13S can be enabled
  by laptop users using the fcc-unlock generic guidelines. And mobile
  broadband is working out of the box. Without it, the modem won't work.

  
  [ Test Plan ]

  Without the ability to FCC unlock this modem model, any attempt to
  enable/start the modem will fail / stall, as detailed on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/.

  With this backport/fix, the Ubuntu Mobile network settings/UI can be
  used to enabled the modem, unlock the SIM card and connect to the
  4G/5G network (assuming the user has a SIM card with an appropriate
  data plan).

  
  [ Where problems could occur ]

  The patch is fairly isolated change. The purpose of this change is to
  create an additional symlink in /usr/share/ModemManager/fcc-
  unlock.available.d/ whose name is the PCIe ID of this specific device.
  PCIe IDs are documented here: https://cateee.net/lkddb/web-
  lkddb/MHI_BUS.html.

  Also links in this folder have no effect on the system, unless the
  user manually enable the appropriate fcc unlock script, typically by
  adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate
  modem model script.

  [ Other Info ]
   
  I am working on a debdiff, and will upload shortly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+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 2039611] Re: [SRU] Fix fcc-unlock script for Lenovo X13s

[Nicolas Dechesne]

** Patch added: "modemmanager-1.20.6-1ubuntu2.patch"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+attachment/5710761/+files/modemmanager-1.20.6-1ubuntu2.patch

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

Title:
   [SRU] Fix fcc-unlock script for Lenovo X13s

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon
  8cx, come with an integrated 4G/5G modem. The modem on the X13s is
  manufactured by foxconn, and is based on the Qualcomm Snapdragon X55
  PCIe modem.

  Here is the output of mmcli -m 0 on an X13s

Hardware  |manufacturer: foxconn
  |   model: Qualcomm Snapdragon X55 5G
  |   firmware revision: T99W175.F0.6.0.0.6.OG.005
  |  045  1  [Feb 03 2023 10:00:00]
   
  All Linux kernel drivers are upstream to support this data modem, and 
included in the Ubuntu kernel for mantic. The support for this modem is also 
merged in modemmanager, including the fcc-unlock script for this modem model 
(https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22).
 

  We are however missing the symlink for the specific PCIe ID link
  reported on the X13s for this modem, which is shown by lspci as:

  0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc.
  T99W175 5G Modem [Snapdragon X55] [105b:e0c3]

  This is already fixed upstream with
  https://gitlab.freedesktop.org/mobile-
  broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838.

  With the backport of this patch the modem on the X13S can be enabled
  by laptop users using the fcc-unlock generic guidelines. And mobile
  broadband is working out of the box. Without it, the modem won't work.

  
  [ Test Plan ]

  Without the ability to FCC unlock this modem model, any attempt to
  enable/start the modem will fail / stall, as detailed on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/.

  With this backport/fix, the Ubuntu Mobile network settings/UI can be
  used to enabled the modem, unlock the SIM card and connect to the
  4G/5G network (assuming the user has a SIM card with an appropriate
  data plan).

  
  [ Where problems could occur ]

  The patch is fairly isolated change. The purpose of this change is to
  create an additional symlink in /usr/share/ModemManager/fcc-
  unlock.available.d/ whose name is the PCIe ID of this specific device.
  PCIe IDs are documented here: https://cateee.net/lkddb/web-
  lkddb/MHI_BUS.html.

  Also links in this folder have no effect on the system, unless the
  user manually enable the appropriate fcc unlock script, typically by
  adding a link in /etc/ModemManager/fcc-unlock.d/ to the appropriate
  modem model script.

  [ Other Info ]
   
  I am working on a debdiff, and will upload shortly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/2039611/+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 2039611] [NEW] [SRU] Fix fcc-unlock script for Lenovo X13s

[Nicolas Dechesne]

Public bug reported:

[ Impact ]

Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon
8cx, come with an integrated 4G/5G modem. The modem on the X13s is
manufactured by foxconn, and is based on the Qualcomm Snapdragon X55
PCIe modem.

Here is the output of mmcli -m 0 on an X13s

  Hardware  |manufacturer: foxconn
|   model: Qualcomm Snapdragon X55 5G
|   firmware revision: T99W175.F0.6.0.0.6.OG.005
|  045  1  [Feb 03 2023 10:00:00]
 
All Linux kernel drivers are upstream to support this data modem, and included 
in the Ubuntu kernel for mantic. The support for this modem is also merged in 
modemmanager, including the fcc-unlock script for this modem model 
(https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22).
 

We are however missing the symlink for the specific PCIe ID link
reported on the X13s for this modem, which is shown by lspci as:

0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc.
T99W175 5G Modem [Snapdragon X55] [105b:e0c3]

This is already fixed upstream with
https://gitlab.freedesktop.org/mobile-
broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838.

With the backport of this patch the modem on the X13S can be enabled by
laptop users using the fcc-unlock generic guidelines. And mobile
broadband is working out of the box. Without it, the modem won't work.


[ Test Plan ]

Without the ability to FCC unlock this modem model, any attempt to
enable/start the modem will fail / stall, as detailed on
https://modemmanager.org/docs/modemmanager/fcc-unlock/.

With this backport/fix, the Ubuntu Mobile network settings/UI can be
used to enabled the modem, unlock the SIM card and connect to the 4G/5G
network (assuming the user has a SIM card with an appropriate data
plan).


[ Where problems could occur ]

The patch is fairly isolated change. The purpose of this change is to
create an additional symlink in /usr/share/ModemManager/fcc-
unlock.available.d/ whose name is the PCIe ID of this specific device.
PCIe IDs are documented here: https://cateee.net/lkddb/web-
lkddb/MHI_BUS.html.

Also links in this folder have no effect on the system, unless the user
manually enable the appropriate fcc unlock script, typically by adding a
link in /etc/ModemManager/fcc-unlock.d/ to the appropriate modem model
script.

[ Other Info ]
 
I am working on a debdiff, and will upload shortly

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

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

Title:
   [SRU] Fix fcc-unlock script for Lenovo X13s

Status in modemmanager package in Ubuntu:
  New

Bug description:
  [ Impact ]

  Some of the Lenovo X13s laptop SKUs, based on the Qualcomm Snapdragon
  8cx, come with an integrated 4G/5G modem. The modem on the X13s is
  manufactured by foxconn, and is based on the Qualcomm Snapdragon X55
  PCIe modem.

  Here is the output of mmcli -m 0 on an X13s

Hardware  |manufacturer: foxconn
  |   model: Qualcomm Snapdragon X55 5G
  |   firmware revision: T99W175.F0.6.0.0.6.OG.005
  |  045  1  [Feb 03 2023 10:00:00]
   
  All Linux kernel drivers are upstream to support this data modem, and 
included in the Ubuntu kernel for mantic. The support for this modem is also 
merged in modemmanager, including the fcc-unlock script for this modem model 
(https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/ac06052b97cc02e60ae1ed7a551727b3c14d6a22).
 

  We are however missing the symlink for the specific PCIe ID link
  reported on the X13s for this modem, which is shown by lspci as:

  0004:01:00.0 Wireless controller [0d40]: Foxconn International, Inc.
  T99W175 5G Modem [Snapdragon X55] [105b:e0c3]

  This is already fixed upstream with
  https://gitlab.freedesktop.org/mobile-
  broadband/ModemManager/-/commit/8061bcd9c03c26946b6fa3356313e069203f8838.

  With the backport of this patch the modem on the X13S can be enabled
  by laptop users using the fcc-unlock generic guidelines. And mobile
  broadband is working out of the box. Without it, the modem won't work.

  
  [ Test Plan ]

  Without the ability to FCC unlock this modem model, any attempt to
  enable/start the modem will fail / stall, as detailed on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/.

  With this backport/fix, the Ubuntu Mobile network settings/UI can be
  used to enabled the modem, unlock the SIM card and connect to the
  4G/5G network (assuming the user has a SIM card with an appropriate
  data plan).

  
  [ Where problems could occur ]

  The patch is fairly isolated change. The purpose of this change is to
  create an additional symlink in 

[Desktop-packages] [Bug 2038391] [NEW] package firefox 118.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Franck NICOLAS]

Public bug reported:

while upgrading from Ubuntu 20.04 t0 22.04

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 118.0.1+build1-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
Uname: Linux 5.15.0-84-generic x86_64
NonfreeKernelModules: wl
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1187 F pulseaudio
BuildID: 20230927232528
CasperMD5CheckResult: unknown
Channel: Unavailable
Date: Wed Oct  4 00:05:31 2023
ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
ForcedLayersAccel: False
InstallationDate: Installed on 2022-02-27 (583 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
IpRoute:
 default via 10.0.0.138 dev wlx0013ef70255d proto dhcp src 10.0.0.90 metric 600 
 10.0.0.0/24 dev wlx0013ef70255d proto kernel scope link src 10.0.0.90 metric 
600 
 10.0.0.138 dev wlx0013ef70255d proto dhcp scope link src 10.0.0.90 metric 600 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.10
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 118.0.1+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
UpgradeStatus: Upgraded to jammy on 2023-10-03 (0 days ago)
dmi.bios.date: 07/17/09
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM31.88Z.00AD.B00.0907171535
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-F22C86C8
dmi.board.vendor: Apple Inc.
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 16
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22C86C8
dmi.modalias: 
dmi:bvnAppleInc.:bvrMM31.88Z.00AD.B00.0907171535:bd07/17/09:br0.1:svnAppleInc.:pnMacmini3,1:pvr1.0:rvnAppleInc.:rnMac-F22C86C8:rvr:cvnAppleInc.:ct16:cvrMac-F22C86C8:skuSystemSKU#:
dmi.product.family: Macmini
dmi.product.name: Macmini3,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-package jammy need-duplicate-check

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

Title:
  package firefox 118.0.1+build1-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  New

Bug description:
  while upgrading from Ubuntu 20.04 t0 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 118.0.1+build1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116
  Uname: Linux 5.15.0-84-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1187 F pulseaudio
  BuildID: 20230927232528
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Wed Oct  4 00:05:31 2023
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-02-27 (583 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IpRoute:
   default via 10.0.0.138 dev wlx0013ef70255d proto dhcp src 10.0.0.90 metric 
600 
   10.0.0.0/24 dev wlx0013ef70255d proto kernel scope link src 10.0.0.90 metric 
600 
   10.0.0.138 dev wlx0013ef70255d proto dhcp scope link src 10.0.0.90 metric 
600 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 118.0.1+build1-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2023-10-03 (0 days ago)
  dmi.bios.date: 07/17/09
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM31.88Z.00AD.B00.0907171535
  dmi.board.asset.tag: Base Board Asset Tag#
  

[Desktop-packages] [Bug 2028864] Re: [snap] chromium browser does not work with accelerated graphics on Tegra (arm64)

[Nicolas Dechesne]

** Attachment added: "terminal_logs_deb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028864/+attachment/5688860/+files/terminal_logs_deb.txt

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

Title:
  [snap] chromium browser does not work with accelerated graphics on
  Tegra (arm64)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Tegra Orin platforms come in various flavor / dev kit. They all ship
  with a 'slightly' customized Ubuntu image. One of the customization is
  the addition of the Nvidia GPU drivers for Tegra.

  When running chromium browser debian package (either when running
  18.04, or when running 22.04 with the package fetched from this PPA:
  https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages)
  then chromium works with hardware acceleration, as reported in
  chrome://gpu:

  Graphics Feature Status
  Canvas: Hardware accelerated
  Canvas out-of-process rasterization: Disabled
  Direct Rendering Display Compositor: Disabled
  Compositing: Hardware accelerated
  Multiple Raster Threads: Enabled
  OpenGL: Enabled
  Rasterization: Hardware accelerated
  Raw Draw: Disabled
  Video Decode: Hardware accelerated
  Video Encode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Hardware accelerated
  WebGL2: Hardware accelerated
  WebGPU: Disabled

  When using the snap version of chromium browser (on either 20.04 or
  22.04), hardware acceleration is disabled, as shown in chrome://gpu:

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Canvas out-of-process rasterization: Disabled
  Direct Rendering Display Compositor: Disabled
  Compositing: Software only. Hardware acceleration disabled
  Multiple Raster Threads: Enabled
  OpenGL: Disabled
  Rasterization: Software only. Hardware acceleration disabled
  Raw Draw: Disabled
  Skia Graphite: Disabled
  Video Decode: Software only. Hardware acceleration disabled
  Video Encode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Software only, hardware acceleration unavailable
  WebGL2: Software only, hardware acceleration unavailable
  WebGPU: Disabled
  Problems Detected
  WebGPU has been disabled via blocklist or the command line.
  Disabled Features: webgpu
  Accelerated video encode has been disabled, either via blocklist, about:flags 
or the command line.
  Disabled Features: video_encode
  Gpu compositing has been disabled, either via blocklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
  Disabled Features: gpu_compositing

  These tests are done with X11.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028864/+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 2028864] [NEW] [snap] chromium browser does not work with accelerated graphics on Tegra (arm64)

[Nicolas Dechesne]

Public bug reported:

Tegra Orin platforms come in various flavor / dev kit. They all ship
with a 'slightly' customized Ubuntu image. One of the customization is
the addition of the Nvidia GPU drivers for Tegra.

When running chromium browser debian package (either when running 18.04,
or when running 22.04 with the package fetched from this PPA:
https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages)
then chromium works with hardware acceleration, as reported in
chrome://gpu:

Graphics Feature Status
Canvas: Hardware accelerated
Canvas out-of-process rasterization: Disabled
Direct Rendering Display Compositor: Disabled
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
OpenGL: Enabled
Rasterization: Hardware accelerated
Raw Draw: Disabled
Video Decode: Hardware accelerated
Video Encode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated
WebGPU: Disabled

When using the snap version of chromium browser (on either 20.04 or
22.04), hardware acceleration is disabled, as shown in chrome://gpu:

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Canvas out-of-process rasterization: Disabled
Direct Rendering Display Compositor: Disabled
Compositing: Software only. Hardware acceleration disabled
Multiple Raster Threads: Enabled
OpenGL: Disabled
Rasterization: Software only. Hardware acceleration disabled
Raw Draw: Disabled
Skia Graphite: Disabled
Video Decode: Software only. Hardware acceleration disabled
Video Encode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Software only, hardware acceleration unavailable
WebGL2: Software only, hardware acceleration unavailable
WebGPU: Disabled
Problems Detected
WebGPU has been disabled via blocklist or the command line.
Disabled Features: webgpu
Accelerated video encode has been disabled, either via blocklist, about:flags 
or the command line.
Disabled Features: video_encode
Gpu compositing has been disabled, either via blocklist, about:flags or the 
command line. The browser will fall back to software compositing and hardware 
acceleration will be unavailable.
Disabled Features: gpu_compositing

These tests are done with X11.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "terminal_logs_snap.txt"
   
https://bugs.launchpad.net/bugs/2028864/+attachment/5688859/+files/terminal_logs_snap.txt

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

Title:
  [snap] chromium browser does not work with accelerated graphics on
  Tegra (arm64)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Tegra Orin platforms come in various flavor / dev kit. They all ship
  with a 'slightly' customized Ubuntu image. One of the customization is
  the addition of the Nvidia GPU drivers for Tegra.

  When running chromium browser debian package (either when running
  18.04, or when running 22.04 with the package fetched from this PPA:
  https://launchpad.net/~nteodosio/+archive/ubuntu/chromium/+packages)
  then chromium works with hardware acceleration, as reported in
  chrome://gpu:

  Graphics Feature Status
  Canvas: Hardware accelerated
  Canvas out-of-process rasterization: Disabled
  Direct Rendering Display Compositor: Disabled
  Compositing: Hardware accelerated
  Multiple Raster Threads: Enabled
  OpenGL: Enabled
  Rasterization: Hardware accelerated
  Raw Draw: Disabled
  Video Decode: Hardware accelerated
  Video Encode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Hardware accelerated
  WebGL2: Hardware accelerated
  WebGPU: Disabled

  When using the snap version of chromium browser (on either 20.04 or
  22.04), hardware acceleration is disabled, as shown in chrome://gpu:

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Canvas out-of-process rasterization: Disabled
  Direct Rendering Display Compositor: Disabled
  Compositing: Software only. Hardware acceleration disabled
  Multiple Raster Threads: Enabled
  OpenGL: Disabled
  Rasterization: Software only. Hardware acceleration disabled
  Raw Draw: Disabled
  Skia Graphite: Disabled
  Video Decode: Software only. Hardware acceleration disabled
  Video Encode: Software only. Hardware acceleration disabled
  Vulkan: Disabled
  WebGL: Software only, hardware acceleration unavailable
  WebGL2: Software only, hardware acceleration unavailable
  WebGPU: Disabled
  Problems Detected
  WebGPU has been disabled via blocklist or the command line.
  Disabled Features: webgpu
  Accelerated video encode has been disabled, either via blocklist, about:flags 
or the command line.
  Disabled Features: video_encode
  Gpu compositing has been disabled, either via blocklist, about:flags or the 
command line. The browser will fall 

[Desktop-packages] [Bug 1978757] Re: Can't playback preview on Intel IPU6 camera platform

[Nicolas DERIVE]

Hello @fourdollars @andch,


Any news on this topic? We just replaced our laptops at work and we now have a 
batch of some Dell XPS 13 experiencing this bug under 22.04LTS.

Webcams are working properly in Chromium, not in Firefox and Cheese. Is
there any workaround or fix available that could be deployed without
messing another thing on the machines?

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

Title:
  Can't playback preview on Intel IPU6 camera platform

Status in OEM Priority Project:
  Confirmed
Status in cheese package in Ubuntu:
  Confirmed
Status in pipewire package in Ubuntu:
  Confirmed
Status in v4l2loopback package in Ubuntu:
  Confirmed

Bug description:
  Cheese can't playback preview on Intel IPU6 camera platform.

  (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed

  On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on 
jammy.
  I tried command $ gst-launch-1.0 v4l2src ! glimagesink
  It can have camera image in the opened window.
  And https://webcamtests.com/ can work successfully.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-14 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220425-25
  MachineType: Dell Inc. XPS 9320
  Package: cheese 41.1-1build1 [origin: unknown]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  Tags: jammy third-party-packages wayland-session gstreamer-error
  Uname: Linux 5.15.0-36-generic x86_64
  UnreportableReason: This does not seem to be an official Ubuntu package. 
Please retry after updating the indexes of available packages, if that does not 
work then remove related third party packages and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/06/2022
  dmi.bios.release: 89.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 89.4.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3:
  dmi.product.family: XPS
  dmi.product.name: XPS 9320
  dmi.product.sku: 0AF3
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1978757/+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 606365]

[Nicolas-fella]

In Plasma 5.27 we changed the VPN  import to match what nmcli is doing,
so this should be fixed

See https://invent.kde.org/plasma/plasma-
nm/-/commit/9b22aa548f02ef43f7275ab2f9ffa48bde8a1ba8

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

Title:
  unable to import config with inlined ca, cert, key or tls-auth

Status in NetworkManager-OpenVPN:
  Fix Released
Status in plasma-nm:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in plasma-nm package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: network-manager-openvpn-gnome

  So a client of mine runs an OpenVPN setup. It exported a client.ovpn
  file but it fails to completely import this file using the network-
  manager (gnome) on Ubuntu 10.04.

  When I import the file, it gives me the name ("client") and gateway
  ("vpn.example.org") on the initial screen. No other fields are
  populated even though the client.ovpn file also includes a user
  certificate, server certifikate and a private key.

  When I go to advanced, some (most) of the settings obviously seem to
  import correct, others not at all. E.g. none of the TLS settings (key
  and key direction) are imported.

  From what I understand I should be able to use this without any
  additional settings.

  The following software is installed through aptitude:

   * openvpn (2.1.0)
   * openvpn-blacklist
   * network-manager-openvpn
   * network-manager-openvpn-gnome

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/606365/+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 1682133] Re: Dual screen is broken

[Nicolas]

Hi Paul, since my post, I migrated to Ubuntu 22.04. 
You can close this report.

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

Title:
  Dual screen is broken

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  After an update of Ubuntu 14.04 and a reboot, my second screen was not 
recognized by the laptop.
  This is the second time I get this. Last time I had to re-install all my 
stuffs...

  Laptop: Samsung NP900X3G
  System: Ubuntu 14.04.5 LTS
  Graphic card: Intel (00:02.0 VGA compatible controller: Intel Corporation 
Haswell-ULT Integrated Graphics Controller (rev 09))

  Need more informations, tell me thx.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.23
  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
  CurrentDesktop: Unity
  Date: Wed Apr 12 09:24:07 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Device [144d:c109]
  InstallationDate: Installed on 2016-04-18 (358 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5e26e584-5e80-41c8-9b69-9a0e61826dff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADU.025.140523.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SAMSUNG_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADU.025.140523.PS:bd05/23/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3G:pvrP05ADU:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSAMSUNG_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 900X3G
  dmi.product.version: P05ADU
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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: Wed Apr 12 09:23:02 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1495 
   vendor BOE
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1682133/+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 1987193] [NEW] restarted of system several times

[Nicolas]

Public bug reported:

1.worked to applications of my desktop
2.restarted of system  several times
3.tab in the computer for several program and system crash and restarted

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-screensaver 3.6.1-13ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun Aug 21 01:08:23 2022
GnomeSessionIdleInhibited: Unknown
GnomeSessionInhibitors: Failed to acquire
GsettingsGnomeSession:
 org.gnome.desktop.session idle-delay uint32 300
 org.gnome.desktop.session session-name 'ubuntu'
InstallationDate: Installed on 2020-08-24 (726 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=es_CO:es
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: Upgraded to jammy on 2022-08-19 (1 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2020-10-21T01:00:59.147631

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


** Tags: amd64 apport-bug jammy

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

Title:
  restarted of system  several times

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  1.worked to applications of my desktop
  2.restarted of system  several times
  3.tab in the computer for several program and system crash and restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver 3.6.1-13ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Aug 21 01:08:23 2022
  GnomeSessionIdleInhibited: Unknown
  GnomeSessionInhibitors: Failed to acquire
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2020-08-24 (726 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=es_CO:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (1 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2020-10-21T01:00:59.147631

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1987193/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid

[Nicolas Hasbun A.]

Deleting the certificate also worked for me.

To do this user needs admin privileges. I guess this breaks basic
printing functionality for regular users.

This is my printer: HP_Smart_Tank_530_series_21D133

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

Title:
  Printing does not work on Ubuntu 22.04 - cups-pki-invalid

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 22.04 printing did not work. There is cups-pki-
  invalid error and printer goes to paused state.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  Uname: Linux 5.17.7-051707-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 15:34:47 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-10-12 (214 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
  Lpstat: device for HP_Color_LaserJet_M552_5F80BF: 
implicitclass://HP_Color_LaserJet_M552_5F80BF/
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic 
root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago)
  dmi.bios.date: 03/29/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: G513QY.318
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G513QY
  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.ec.firmware.release: 0.81
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G513QY_G513QY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Nicolas-fella]

*** Bug 447585 has been marked as a duplicate of this bug. ***

-- 
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 1941752]

[Nicolas-fella]

*** Bug 444851 has been marked as a duplicate of this bug. ***

-- 
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 1941752]

[Nicolas-fella]

*** Bug 445763 has been marked as a duplicate of this bug. ***

-- 
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 1941752]

[Nicolas-fella]

*** Bug 447039 has been marked as a duplicate of this bug. ***

-- 
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 1942432] Re: third-party applications freeze gnome-shell reproducibly

[Nicolas Herzog]

Thank you for the quick response.
I'm sorry for the work I generated. After reporting the bug, I tried another 
display / window manager, respectively, and managed my system into a 
non-working GUI.
I then did a backup and reinstalled Linux, now cinnamon is working well.
So you can close the bug in my view.

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

Title:
  third-party applications freeze gnome-shell reproducibly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  On my Ubuntu 20.04.3 LTS, I have reproducible freezes of gdm3 
(3.36.3-0ubuntu0.20.04.4) caused by third-party applications. The only thing I 
found describing my problem was https://unix.stackexchange.com/a/39855 (passage 
*GUI Glitches Causing Unresponsive WM or X11/Wayland*). This is exactly my 
experience ("**an application stops responding and prevents you from entering 
input with the keyboard or mouse to other application windows**"). Specifically:
  - clicking on a hyperlink in (an open mail in) thunderbird freezes gdm3 at 
90%.
  - opening files via nemo (file manager) freezes gdm3 sometimes, regardless 
which file type.
  - libreoffice freezes gdm3 a lot when switching windows via alt-tab, but not 
when I switch windows via super key.

  Whenever a freeze occurs, the clock in my taskbar stops, the mouse and
  keyboard still work, but no window responds. Switching to tty works.
  Killing the last used application (e.g. thunderbird, nemo,
  soffice.bin) via tty brings gdm3 to life again. The funny thing is
  that when e.g. I open a link via thunderbird and gdm3 freezes, then I
  kill thunderbird via tty and switch back to X, then thunderbird is
  gone but firefox has opened the link.

  I activated gdm3 debug output but could not find anything (I'm not an 
ubuntu/X/gdm expert).
  One freeze occurs somewhere between two **systemd-logind: got pause for 
13:73** in syslog_gdm3.log

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.36.3-0ubuntu0.20.04.4
  ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
  Uname: Linux 5.4.0-81-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  2 12:23:57 2021
  InstallationDate: Installed on 2018-07-26 (1134 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANGUAGE=de_CH:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-10-07 (329 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2021-09-02T11:47:52.516792

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942432/+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 1942432] [NEW] third-party applications freeze gdm3 reproducibly

[Nicolas Herzog]

Public bug reported:

On my Ubuntu 20.04.3 LTS, I have reproducible freezes of gdm3 
(3.36.3-0ubuntu0.20.04.4) caused by third-party applications. The only thing I 
found describing my problem was https://unix.stackexchange.com/a/39855 (passage 
*GUI Glitches Causing Unresponsive WM or X11/Wayland*). This is exactly my 
experience ("**an application stops responding and prevents you from entering 
input with the keyboard or mouse to other application windows**"). Specifically:
- clicking on a hyperlink in (an open mail in) thunderbird freezes gdm3 at 90%.
- opening files via nemo (file manager) freezes gdm3 sometimes, regardless 
which file type.
- libreoffice freezes gdm3 a lot when switching windows via alt-tab, but not 
when I switch windows via super key.

Whenever a freeze occurs, the clock in my taskbar stops, the mouse and
keyboard still work, but no window responds. Switching to tty works.
Killing the last used application (e.g. thunderbird, nemo, soffice.bin)
via tty brings gdm3 to life again. The funny thing is that when e.g. I
open a link via thunderbird and gdm3 freezes, then I kill thunderbird
via tty and switch back to X, then thunderbird is gone but firefox has
opened the link.

I activated gdm3 debug output but could not find anything (I'm not an 
ubuntu/X/gdm expert).
One freeze occurs somewhere between two **systemd-logind: got pause for 13:73** 
in syslog_gdm3.log

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.36.3-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
Uname: Linux 5.4.0-81-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  2 12:23:57 2021
InstallationDate: Installed on 2018-07-26 (1134 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=de_CH:de
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-10-07 (329 days ago)
mtime.conffile..etc.gdm3.custom.conf: 2021-09-02T11:47:52.516792

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


** Tags: amd64 apport-bug focal

** Attachment added: "syslog_gdm3.log"
   
https://bugs.launchpad.net/bugs/1942432/+attachment/5522527/+files/syslog_gdm3.log

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

Title:
  third-party applications freeze gdm3 reproducibly

Status in gdm3 package in Ubuntu:
  New

Bug description:
  On my Ubuntu 20.04.3 LTS, I have reproducible freezes of gdm3 
(3.36.3-0ubuntu0.20.04.4) caused by third-party applications. The only thing I 
found describing my problem was https://unix.stackexchange.com/a/39855 (passage 
*GUI Glitches Causing Unresponsive WM or X11/Wayland*). This is exactly my 
experience ("**an application stops responding and prevents you from entering 
input with the keyboard or mouse to other application windows**"). Specifically:
  - clicking on a hyperlink in (an open mail in) thunderbird freezes gdm3 at 
90%.
  - opening files via nemo (file manager) freezes gdm3 sometimes, regardless 
which file type.
  - libreoffice freezes gdm3 a lot when switching windows via alt-tab, but not 
when I switch windows via super key.

  Whenever a freeze occurs, the clock in my taskbar stops, the mouse and
  keyboard still work, but no window responds. Switching to tty works.
  Killing the last used application (e.g. thunderbird, nemo,
  soffice.bin) via tty brings gdm3 to life again. The funny thing is
  that when e.g. I open a link via thunderbird and gdm3 freezes, then I
  kill thunderbird via tty and switch back to X, then thunderbird is
  gone but firefox has opened the link.

  I activated gdm3 debug output but could not find anything (I'm not an 
ubuntu/X/gdm expert).
  One freeze occurs somewhere between two **systemd-logind: got pause for 
13:73** in syslog_gdm3.log

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.36.3-0ubuntu0.20.04.4
  ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
  Uname: Linux 5.4.0-81-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  2 12:23:57 2021
  InstallationDate: Installed on 2018-07-26 (1134 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANGUAGE=de_CH:de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-10-07 (329 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2021-09-02T11:47:52.516792

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to   

[Desktop-packages] [Bug 1934218] [NEW] Ticklabels in graphs in dark theme are not visible

[Nicolas Bock]

Public bug reported:

The tickmarks in graphs, e.g. Laptop Battery/History/Charge, are not
visible while using the dark theme. The tickmarks are visible using the
standard and light theme.

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

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

Title:
  Ticklabels in graphs in dark theme are not visible

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  The tickmarks in graphs, e.g. Laptop Battery/History/Charge, are not
  visible while using the dark theme. The tickmarks are visible using
  the standard and light theme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1934218/+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 1928458] Re: inconsistent and unneeded password prompts

[Nicolas Damgaard Larsen]

I appreciate your reply.

> Are you using auto-logging?
On this machine I am using auto-login, yes.

> if you use password login and the keyring has the same secret then it's 
> automatically unlocked
As already stated, this behaviour has been observed both when the keyring has 
been unlocked and when not.

> the first software to try to use it is going to trigger the prompting
This behaviour has also been observed for applications not requesting for 
passwords.

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

Title:
  inconsistent and unneeded password prompts

Status in gnome-keyring package in Ubuntu:
  Incomplete

Bug description:
  On several occasions I have experienced that gnome-keyring prompts to be 
unlocked when I believe it should not.
  * I have Spotify installed as a .deb. When starting Spotify, on some 
occasions gnome-keyring prompts to be unlocked, on others not. This behaviour 
has been observed both when gnome-keyring has been unlocked in advance as well 
as when not. I have not added my Spotify password to gnome-keyring.
  * same behaviour as described above when starting Lutris. Did also not add 
any Lutris related passwords to gnome-keyring.
  * similar behaviour is observed with other applications where no passwords 
have been added to gnome-keyring.

  Whether or not I actually unlock the keyring, it has no functional
  impact in these cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 14 13:24:00 2021
  InstallationDate: Installed on 2020-05-09 (369 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1928458/+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 1929305] [NEW] [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all

[Nicolas Michel]

Public bug reported:

Inserting a headset jack is detected. I can slide the volume. But no
sound at all in the headset.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  fanchon1613 F pulseaudio
 /dev/snd/pcmC0D0p:   fanchon1613 F...m pulseaudio
 /dev/snd/controlC1:  fanchon1613 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat May 22 21:46:36 2021
InstallationDate: Installed on 2021-05-22 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=fr_BE:fr
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_BE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
Symptom_Card: Audio interne - HDA Intel MID
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  fanchon1613 F pulseaudio
 /dev/snd/pcmC0D0p:   fanchon1613 F...m pulseaudio
 /dev/snd/controlC1:  fanchon1613 F pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/06/2010
dmi.bios.release: 11.40
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1140Y8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.ec.firmware.release: 11.40
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:br11.40:efr11.40:svnSonyCorporation:pnVPCEB3E1E:pvrC606TWY5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCEB3E1E
dmi.product.sku: N/A
dmi.product.version: C606TWY5
dmi.sys.vendor: Sony Corporation

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Inserting a headset jack is detected. I can slide the volume. But no
  sound at all in the headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fanchon1613 F pulseaudio
   /dev/snd/pcmC0D0p:   fanchon1613 F...m pulseaudio
   /dev/snd/controlC1:  fanchon1613 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 22 21:46:36 2021
  InstallationDate: Installed on 2021-05-22 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fr_BE:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Audio interne - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fanchon1613 F pulseaudio
   /dev/snd/pcmC0D0p:   fanchon1613 F...m pulseaudio
   /dev/snd/controlC1:  fanchon1613 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [VPCEB3E1E, Realtek ALC269, Black Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2010
  dmi.bios.release: 11.40
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1140Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 11.40
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:br11.40:efr11.40:svnSonyCorporation:pnVPCEB3E1E:pvrC606TWY5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEB3E1E
  dmi.product.sku: N/A
  dmi.product.version: C606TWY5
  dmi.sys.vendor: Sony Corporation

To manage notifications about this 

[Desktop-packages] [Bug 1928458] [NEW] inconsistent and unneeded password prompts

[Nicolas Damgaard Larsen]

Public bug reported:

On several occasions I have experienced that gnome-keyring prompts to be 
unlocked when I believe it should not.
* I have Spotify installed as a .deb. When starting Spotify, on some occasions 
gnome-keyring prompts to be unlocked, on others not. This behaviour has been 
observed both when gnome-keyring has been unlocked in advance as well as when 
not. I have not added my Spotify password to gnome-keyring.
* same behaviour as described above when starting Lutris. Did also not add any 
Lutris related passwords to gnome-keyring.
* similar behaviour is observed with other applications where no passwords have 
been added to gnome-keyring.

Whether or not I actually unlock the keyring, it has no functional
impact in these cases.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-keyring 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 14 13:24:00 2021
InstallationDate: Installed on 2020-05-09 (369 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Auth.log from latest boot where I encounted the issue"
   https://bugs.launchpad.net/bugs/1928458/+attachment/5497464/+files/auth.log

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

Title:
  inconsistent and unneeded password prompts

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  On several occasions I have experienced that gnome-keyring prompts to be 
unlocked when I believe it should not.
  * I have Spotify installed as a .deb. When starting Spotify, on some 
occasions gnome-keyring prompts to be unlocked, on others not. This behaviour 
has been observed both when gnome-keyring has been unlocked in advance as well 
as when not. I have not added my Spotify password to gnome-keyring.
  * same behaviour as described above when starting Lutris. Did also not add 
any Lutris related passwords to gnome-keyring.
  * similar behaviour is observed with other applications where no passwords 
have been added to gnome-keyring.

  Whether or not I actually unlock the keyring, it has no functional
  impact in these cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-keyring 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 14 13:24:00 2021
  InstallationDate: Installed on 2020-05-09 (369 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1928458/+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 1917764] Re: profile gets deleted on startup due to account "no longer allowed as the primary account"

[Nicolas Richard]

I tried updating to latest/edge channel

$ sudo snap refresh chromium --channel=latest/edge
chromium (edge) 90.0.4421.5 par Canonical✓ mis à jour

Problem persists : I can't activate synchronization.

When I click on the "user" button (top right of the window, next to the 
vertical-dots menu) I see:
- a button to activate synchronization, when I'm on  version 88.0.4324.182
- no such button on version 89 (stable) et 90 (edge)

about://sync-internals shows "Disable Reasons" is "Not signed in".
Here's the full report :


Thu Mar 04 2021 14:30:21 GMT+0100 (heure normale d’Europe centrale)
==
Status
==
{
  "actionable_error": [
{
  "stat_name": "Error Type",
  "stat_status": "uninitialized",
  "stat_value": "Uninitialized"
},
{
  "stat_name": "Action",
  "stat_status": "uninitialized",
  "stat_value": "Uninitialized"
},
{
  "stat_name": "Error Description",
  "stat_status": "uninitialized",
  "stat_value": "Uninitialized"
}
  ],
  "actionable_error_detected": false,
  "details": [
{
  "data": [
{
  "stat_name": "Transport State",
  "stat_status": "",
  "stat_value": "Disabled"
},
{
  "stat_name": "Disable Reasons",
  "stat_status": "",
  "stat_value": "Not signed in"
},
{
  "stat_name": "Sync Feature Enabled",
  "stat_status": "",
  "stat_value": false
},
{
  "stat_name": "Setup In Progress",
  "stat_status": "",
  "stat_value": false
},
{
  "stat_name": "Auth Error",
  "stat_status": "",
  "stat_value": "OK since browser startup"
}
  ],
  "is_sensitive": false,
  "title": "Summary"
},
{
  "data": [
{
  "stat_name": "Client Version",
  "stat_status": "",
  "stat_value": "Chromium Linux 90.0.4421.5 
(6bb0ebcc9bbf6a347e4ed8f3dbc1811ba39efbb2-refs/branch-heads/4421@{#11}) unknown"
},
{
  "stat_name": "Server URL",
  "stat_status": "",
  "stat_value": "https://clients4.google.com/chrome-sync/dev;
}
  ],
  "is_sensitive": false,
  "title": "Version Info"
},
{
  "data": [
{
  "stat_name": "Requested Token",
  "stat_status": "",
  "stat_value": "n/a"
},
{
  "stat_name": "Received Token Response",
  "stat_status": "",
  "stat_value": "n/a"
},
{
  "stat_name": "Last Token Request Result",
  "stat_status": "",
  "stat_value": "OK"
},
{
  "stat_name": "Has Token",
  "stat_status": "",
  "stat_value": false
},
{
  "stat_name": "Next Token Request",
  "stat_status": "",
  "stat_value": "not scheduled"
}
  ],
  "is_sensitive": false,
  "title": "Credentials"
},
{
  "data": [
{
  "stat_name": "Server Connection",
  "stat_status": "",
  "stat_value": "not attempted"
},
{
  "stat_name": "Last Synced",
  "stat_status": "",
  "stat_value": "Never"
},
{
  "stat_name": "Sync First-Time Setup Complete",
  "stat_status": "",
  "stat_value": true
},
{
  "stat_name": "Sync Cycle Ongoing",
  "stat_status": "uninitialized",
  "stat_value": false
},
{
  "stat_name": "Local Sync Backend Enabled",
  "stat_status": "",
  "stat_value": false
},
{
  "stat_name": "Local Backend Path",
  "stat_status": "uninitialized",
  "stat_value": "Uninitialized"
}
  ],
  "is_sensitive": false,
  "title": "Local State"
},
{
  "data": [
{
  "stat_name": "Throttled or Backoff",
  "stat_status": "uninitialized",
  "stat_value": false
},
{
  "stat_name": "Retry Time",
  "stat_status": "uninitialized",
  "stat_value": "Uninitialized"
},
{
  "stat_name": "Notifications Enabled",
  "stat_status": "uninitialized",
  "stat_value": false
}
  ],
  "is_sensitive": false,
  "title": "Network"
},
{
  "data": [
{
  "stat_name": "Explicit Passphrase",
  "stat_status": "uninitialized",
  "stat_value": false
},
{
  "stat_name": "Passphrase Required",
  "stat_status": "uninitialized",
  "stat_value": false
},
{
  "stat_name": "Cryptographer Ready To Encrypt",
  "stat_status": "uninitialized",
  "stat_value": false
},
{
  "stat_name": "Cryptographer Has Pending Keys",
  "stat_status": "uninitialized",
  

[Desktop-packages] [Bug 1917764] [NEW] profile gets deleted on startup due to account "no longer allowed as the primary account"

[Nicolas Richard]

Public bug reported:

I had chromium installed via snap :

installed:  89.0.4389.72(1506) 145MB -

This morning I ran chromium and got the following message

Your account (...) is no longer allowed as the primary account.
Because this account is managed by (...), your bookmarks, history,
passwords and other settings will be cleared from this device.

and, indeed, it was all gone. Impossible to synchronize to the account.
I tried clearing ~/snap/chromium and ~/.config/chromium, but still could
not restart synchronization.

Then I tried reverting :

$ snap revert chromium 
chromium revenu à 88.0.4324.182

and things went working again : I can login to the account and the
bookmarks/history/etc. are synced again.

I'm running Ubuntu 20.04.2 LTS

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  profile gets deleted on startup due to account "no longer allowed as
  the primary account"

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I had chromium installed via snap :

  installed:  89.0.4389.72(1506) 145MB -

  This morning I ran chromium and got the following message

  Your account (...) is no longer allowed as the primary account.
  Because this account is managed by (...), your bookmarks, history,
  passwords and other settings will be cleared from this device.

  and, indeed, it was all gone. Impossible to synchronize to the
  account. I tried clearing ~/snap/chromium and ~/.config/chromium, but
  still could not restart synchronization.

  Then I tried reverting :

  $ snap revert chromium 
  chromium revenu à 88.0.4324.182

  and things went working again : I can login to the account and the
  bookmarks/history/etc. are synced again.

  I'm running Ubuntu 20.04.2 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917764/+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 1874578] Re: [wayland] dock has very long load time when show-mounts is enabled

[Nicolas Damgaard Larsen]

To be fair, this should probably be prioritized higher.
a) the specific configuration is more common than you might think
b) there is a fundamental problem with this extension representing itself as a 
whole slew of different issues.

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

Title:
  [wayland] dock has very long load time when show-mounts is enabled

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded from Ubuntu 18.04 to 20.04.

  When I boot my system I have to wait at least 10 to 15 seconds for the
  application icons to load on dock. Meanwhile everything else seems to
  be working properly. I didn't experience this behavior in Ubuntu
  18.04.

  Also the dock doesn't trigger when I move my cursor to the left of the 
screen. (I have set the docker to Auto-Hide mode and it's position is on the 
left of my screen).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2016-08-03 (1359 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags: focal third-party-packages wayland-session
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874578/+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 1890891] Re: Dock icons don't appear or appear delayed if you have none pinned

[Nicolas Damgaard Larsen]

To be fair, this should probably be prioritized higher.
a) the specific configuration is more common than you might think
b) there is a fundamental problem with this extension representing itself as a 
whole slew of different issues.

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

Title:
  Dock icons don't appear or appear delayed if you have none pinned

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged

Bug description:
  when no one program is pinned and no one open dock stop working
  normally. When I open program it appear only 10 sec later as well for
  closing. restarting with alt + f2 is solving problem until all
  programs again unpinned and closed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug  8 16:08:55 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2020-08-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H V2-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.:bvrF50:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H V2
  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.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1890891/+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 1846334] Re: cupsd assert failure: free(): invalid pointer

[Nicolas Joyard]

I confirm the hirsute version fixes the issue.

I created https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/
recently without having seen this bug report, and I'm pretty confident
it's the same issue.

I reinstalled groovy on a VM, confirmed the bug occurred (it did),
rebuilt 2.3.3op1 from hirsute and installed it. The problem no longer
occurs after that.

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

Title:
  cupsd assert failure: free(): invalid pointer

Status in cups package in Ubuntu:
  Fix Committed

Bug description:
  Just running in the background, no user action (printing)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-daemon 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  Date: Tue Oct  1 19:41:35 2019
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2019-02-09 (234 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: letter
  PpdFiles:
   HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere
   Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at 
malloc.c:5332
   _int_free (av=, p=, have_lock=0) at 
malloc.c:4173
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cupsd assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+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 1915181] Re: cups crashes with SIGABRT every other printing attempt

[Nicolas Joyard]

Looks like it may be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334. The
backtrace I got from the core dump locates the errorneous free() call in
ippDelete as well. Plus it's also a samsung printer.

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

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  Cuspd's error_log shows nothing happening around the crash (it does
  show some "org.freedesktop.ColorManager.AlreadyExists" error messages
  on restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

  ---

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  KernLog:
  Lpstat:
   device for Samsung_C48x_Series_SEC842519933D78_: 
implicitclass://Samsung_C48x_Series_SEC842519933D78_/
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission 
denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base
  Tags: groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: 
True

  dmi.bios.date: 09/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  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.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] Re: cups crashes with SIGABRT every other printing attempt

[Nicolas Joyard]

** Description changed:

  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).
  
  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.
  
  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd
  
  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump
  
  The service then proceeds to restart after a few seconds, and trying to
  print again succeeds. Trying to print once more thereafter triggers the
  issue again.
  
- I could not find a trace of the coredump, and cuspd's error_log shows
- nothing happening around the crash (it does show some
- "org.freedesktop.ColorManager.AlreadyExists" error messages on restart,
- but I figured this would be normal, I can see the same message on other
- machines that have no printing issues).
- 
- I would expect this kind of event to trigger an apport report, but there
- is no apport popup when it happens. Maybe because it's not a user
- process, not sure (this is not my usual setup, I've not been using
- Ubuntu for years).
+ Cuspd's error_log shows nothing happening around the crash (it does show
+ some "org.freedesktop.ColorManager.AlreadyExists" error messages on
+ restart, but I figured this would be normal, I can see the same message
+ on other machines that have no printing issues).
  
  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and nothing
  was configured on cups side or ubuntu print settings, everything is set
  up as it was autodetected on install.
  
  The same printer works flawlessly on a different computer using Arch and
  cups 2.3.3 as well (albeit without any ubuntu patches, obviously).
  
  ---
  
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2021-01-28 (12 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  KernLog:
  Lpstat:
-  device for Samsung_C48x_Series_SEC842519933D78_: 
implicitclass://Samsung_C48x_Series_SEC842519933D78_/
+  device for Samsung_C48x_Series_SEC842519933D78_: 
implicitclass://Samsung_C48x_Series_SEC842519933D78_/
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
  Package: cups 2.3.3-3ubuntu1
  PackageArchitecture: amd64
  Papersize: a4
  PpdFiles:
-  Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission 
denied
+  Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission 
denied
  ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
  ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
  RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base
  Tags: groovy
  Uname: Linux 5.8.0-41-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: 
True
  
  dmi.bios.date: 09/05/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX434DA_UM433DA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX434DA
  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.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX434DA_UM433DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.

[Desktop-packages] [Bug 1915181] Re: cups crashes with SIGABRT every other printing attempt

[Nicolas Joyard]

** Description changed:

  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).
  
  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.
  
  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd
  
  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump
  
  The service then proceeds to restart after a few seconds, and trying to
  print again succeeds. Trying to print once more thereafter triggers the
  issue again.
  
  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on restart,
  but I figured this would be normal, I can see the same message on other
  machines that have no printing issues).
  
  I would expect this kind of event to trigger an apport report, but there
  is no apport popup when it happens. Maybe because it's not a user
  process, not sure (this is not my usual setup, I've not been using
  Ubuntu for years).
  
  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and nothing
  was configured on cups side or ubuntu print settings, everything is set
  up as it was autodetected on install.
  
  The same printer works flawlessly on a different computer using Arch and
  cups 2.3.3 as well (albeit without any ubuntu patches, obviously).
+ 
+ ---
+ 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.5
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2021-01-28 (12 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ KernLog:
+ Lpstat:
+  device for Samsung_C48x_Series_SEC842519933D78_: 
implicitclass://Samsung_C48x_Series_SEC842519933D78_/
+ MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
+ Package: cups 2.3.3-3ubuntu1
+ PackageArchitecture: amd64
+ Papersize: a4
+ PpdFiles:
+  Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission 
denied
+ ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
+ ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
+ RebootRequiredPkgs: linux-image-5.8.0-43-generic linux-base
+ Tags: groovy
+ Uname: Linux 5.8.0-41-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: 
True
+ 
+ dmi.bios.date: 09/05/2019
+ dmi.bios.release: 5.14
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX434DA_UM433DA.302
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX434DA
+ 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.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: ZenBook
+ dmi.product.name: ZenBook UX434DA_UM433DA
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: 

[Desktop-packages] [Bug 1915181] Re: cups crashes with SIGABRT every other printing attempt

[Nicolas Joyard]

I managed to find a core dump for one of those crashes.

** Attachment added: "cupsd core dump"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+attachment/5462043/+files/_usr_sbin_cupsd.0.crash

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

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] acpidump.txt

[Nicolas Joyard]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461772/+files/acpidump.txt

** Description changed:

- Using ubuntu 20.04, cups 2.3.3-3ubuntu1, with a networked Samsung C480
+ Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).
  
  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.
  
  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd
  
  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump
  
  The service then proceeds to restart after a few seconds, and trying to
  print again succeeds. Trying to print once more thereafter triggers the
  issue again.
  
  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on restart,
  but I figured this would be normal, I can see the same message on other
  machines that have no printing issues).
  
  I would expect this kind of event to trigger an apport report, but there
  is no apport popup when it happens. Maybe because it's not a user
  process, not sure (this is not my usual setup, I've not been using
  Ubuntu for years).
  
  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and nothing
  was configured on cups side or ubuntu print settings, everything is set
  up as it was autodetected on install.
  
- The same printer works flawlessly on a different computer using Arch and cups 
2.3.3 as well (albeit without any ubuntu patches, obviously).
- --- 
- ProblemType: Bug
- ApportVersion: 2.20.11-0ubuntu50.5
- Architecture: amd64
- CasperMD5CheckResult: skip
- CurrentDesktop: ubuntu:GNOME
- DistroRelease: Ubuntu 20.10
- InstallationDate: Installed on 2021-01-28 (12 days ago)
- InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
- KernLog:
-  
- Lpstat: device for Samsung_C48x_Series_SEC842519933D78_: 
implicitclass://Samsung_C48x_Series_SEC842519933D78_/
- MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
- Package: cups 2.3.3-3ubuntu1
- PackageArchitecture: amd64
- Papersize: a4
- PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission 
denied
- ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
- ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
- ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
- RebootRequiredPkgs:
-  linux-image-5.8.0-43-generic
-  linux-base
- Tags:  groovy
- Uname: Linux 5.8.0-41-generic x86_64
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
- _MarkForUpload: True
- dmi.bios.date: 09/05/2019
- dmi.bios.release: 5.14
- dmi.bios.vendor: American Megatrends Inc.
- dmi.bios.version: UX434DA_UM433DA.302
- dmi.board.asset.tag: ATN12345678901234567
- dmi.board.name: UX434DA
- 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.:bvrUX434DA_UM433DA.302:bd09/05/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnZenBookUX434DA_UM433DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
- dmi.product.family: ZenBook
- dmi.product.name: ZenBook UX434DA_UM433DA
- dmi.product.version: 1.0
- dmi.sys.vendor: ASUSTeK COMPUTER INC.
+ The same printer works flawlessly on a different computer using Arch and
+ cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

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

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print 

[Desktop-packages] [Bug 1915181] ProcModules.txt

[Nicolas Joyard]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461770/+files/ProcModules.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] Lsusb-t.txt

[Nicolas Joyard]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461764/+files/Lsusb-t.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] UdevDb.txt

[Nicolas Joyard]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1915181/+attachment/5461771/+files/UdevDb.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] Lsusb-v.txt

[Nicolas Joyard]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461765/+files/Lsusb-v.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] ProcCpuinfoMinimal.txt

[Nicolas Joyard]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461768/+files/ProcCpuinfoMinimal.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] PrintingPackages.txt

[Nicolas Joyard]

apport information

** Attachment added: "PrintingPackages.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461766/+files/PrintingPackages.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] ProcInterrupts.txt

[Nicolas Joyard]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461769/+files/ProcInterrupts.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] ProcCpuinfo.txt

[Nicolas Joyard]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461767/+files/ProcCpuinfo.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] CupsErrorLog.txt

[Nicolas Joyard]

apport information

** Attachment added: "CupsErrorLog.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461757/+files/CupsErrorLog.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] Lsusb.txt

[Nicolas Joyard]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1915181/+attachment/5461763/+files/Lsusb.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] Lspci-vt.txt

[Nicolas Joyard]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461762/+files/Lspci-vt.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] Lspci.txt

[Nicolas Joyard]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1915181/+attachment/5461761/+files/Lspci.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] Locale.txt

[Nicolas Joyard]

apport information

** Attachment added: "Locale.txt"
   https://bugs.launchpad.net/bugs/1915181/+attachment/5461760/+files/Locale.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] Dependencies.txt

[Nicolas Joyard]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461759/+files/Dependencies.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] CurrentDmesg.txt

[Nicolas Joyard]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1915181/+attachment/5461758/+files/CurrentDmesg.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/1915181

Title:
  cups crashes with SIGABRT every other printing attempt

Status in cups package in Ubuntu:
  New

Bug description:
  Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).

  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.

  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd

  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump

  The service then proceeds to restart after a few seconds, and trying
  to print again succeeds. Trying to print once more thereafter triggers
  the issue again.

  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on
  restart, but I figured this would be normal, I can see the same
  message on other machines that have no printing issues).

  I would expect this kind of event to trigger an apport report, but
  there is no apport popup when it happens. Maybe because it's not a
  user process, not sure (this is not my usual setup, I've not been
  using Ubuntu for years).

  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and
  nothing was configured on cups side or ubuntu print settings,
  everything is set up as it was autodetected on install.

  The same printer works flawlessly on a different computer using Arch
  and cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1915181/+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 1915181] [NEW] cups crashes with SIGABRT every other printing attempt

[Nicolas Joyard]

Public bug reported:

Using ubuntu 20.10, cups 2.3.3-3ubuntu1, with a networked Samsung C480
printer (was automatically detected and set up on installation of the
system).

Every other attempt to print fails with a varying message depending on
the printing app (eg. on libreoffice write, "Cannot start printer").
Waiting a few minutes and retrying prints successfully.

Looking at cups.service journal messages while attempting to print, it
looks like the second printing attempt crashes cupsd

cupsd[]: free(): invalid pointer
systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
systemd[1]: cups.service: Failed with result core-dump

The service then proceeds to restart after a few seconds, and trying to
print again succeeds. Trying to print once more thereafter triggers the
issue again.

I could not find a trace of the coredump, and cuspd's error_log shows
nothing happening around the crash (it does show some
"org.freedesktop.ColorManager.AlreadyExists" error messages on restart,
but I figured this would be normal, I can see the same message on other
machines that have no printing issues).

I would expect this kind of event to trigger an apport report, but there
is no apport popup when it happens. Maybe because it's not a user
process, not sure (this is not my usual setup, I've not been using
Ubuntu for years).

This is a pretty standard (and recent) ubuntu install, with not much
customized; in particular no apport custom config was made, and nothing
was configured on cups side or ubuntu print settings, everything is set
up as it was autodetected on install.

The same printer works flawlessly on a different computer using Arch and
cups 2.3.3 as well (albeit without any ubuntu patches, obviously).

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


** Tags: apport-collected groovy

** Tags added: apport-collected groovy

** Description changed:

  Using ubuntu 20.04, cups 2.3.3-3ubuntu1, with a networked Samsung C480
  printer (was automatically detected and set up on installation of the
  system).
  
  Every other attempt to print fails with a varying message depending on
  the printing app (eg. on libreoffice write, "Cannot start printer").
  Waiting a few minutes and retrying prints successfully.
  
  Looking at cups.service journal messages while attempting to print, it
  looks like the second printing attempt crashes cupsd
  
  cupsd[]: free(): invalid pointer
  systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT
  systemd[1]: cups.service: Failed with result core-dump
  
  The service then proceeds to restart after a few seconds, and trying to
  print again succeeds. Trying to print once more thereafter triggers the
  issue again.
  
  I could not find a trace of the coredump, and cuspd's error_log shows
  nothing happening around the crash (it does show some
  "org.freedesktop.ColorManager.AlreadyExists" error messages on restart,
  but I figured this would be normal, I can see the same message on other
  machines that have no printing issues).
  
  I would expect this kind of event to trigger an apport report, but there
  is no apport popup when it happens. Maybe because it's not a user
  process, not sure (this is not my usual setup, I've not been using
  Ubuntu for years).
  
  This is a pretty standard (and recent) ubuntu install, with not much
  customized; in particular no apport custom config was made, and nothing
  was configured on cups side or ubuntu print settings, everything is set
  up as it was autodetected on install.
  
- The same printer works flawlessly on a different computer using Arch and
- cups 2.3.3 as well (albeit without any ubuntu patches, obviously).
+ The same printer works flawlessly on a different computer using Arch and cups 
2.3.3 as well (albeit without any ubuntu patches, obviously).
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.5
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2021-01-28 (12 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ KernLog:
+  
+ Lpstat: device for Samsung_C48x_Series_SEC842519933D78_: 
implicitclass://Samsung_C48x_Series_SEC842519933D78_/
+ MachineType: ASUSTeK COMPUTER INC. ZenBook UX434DA_UM433DA
+ Package: cups 2.3.3-3ubuntu1
+ PackageArchitecture: amd64
+ Papersize: a4
+ PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd'] failed with exit code 
2: grep: /etc/cups/ppd/Samsung_C48x_Series_SEC842519933D78_.ppd: Permission 
denied
+ ProcCmdline: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash resume=/dev/mapper/vgubuntu-root 
resume_offset=6731776
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic 

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

Hi Coiby

To answer your question in message #359
> In hybrid mode, does external monitor work for you?

The answer is yes, it works. I tested the hotplug of an HDMI external
monitor, it was detected by Ubuntu 20.04 and worked by default as an
extended desktop (both internal & external display used, not cloned).

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F.... pulseaudio
   /dev/snd/controlC1:  nicolas1567 F.... pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-02 (12 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  focal
  Uname: Linux 5.8.0-050800rc5-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions

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

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

Thanks a lot @Coiby Xu (coiby), amazing work. Let's hope the third patch
will be backported and 20.04.x LTS will work our the box after this.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion

[Desktop-packages] [Bug 1793334] Re: Chromium does not pick default pulseaudio sink

[Nicolas Göddel]

I just tested it with this version of Chrome on Ubuntu 20.04.1 LTS

Version 88.0.4324.41 (Offizieller Build) beta (64-Bit)

Normal soundouput like videos and phone rings (MS Teams) use my selected sink, 
in my case the headphones.
But as soon as I want to use the microphone it uses my internal speakers and 
microphone of the laptop instead of my USB headset which still is selected in 
the pulseaudio settings. I have to switch back and forth to finally be able to 
use my headset within the browser. And that procedure is needed for every call 
I make. Really annoying.

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

Title:
  Chromium does not pick default pulseaudio sink

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  When changing the default sink (builtin audio) to USB audio (PCM2902) 
headphone, all desktop uses the new default sink.
  All but Chromium (and Chrome).
  For both Chromium (and Chrome), I have to change the output device in the 
application tab (PA).  As soon as the audio pauses in Chrome/Chromium, it will 
resume in the builtin output audio device sink.  This happens on a per tab 
basis (probably different process).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Sep 19 11:54:57 2018
  Desktop-Session:
   'plasma'
   
'/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/usr/share/plasma:/home/raul/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-05-12 (1591 days ago)
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  Load-Avg-1min: 1.06
  Load-Processes-Running-Percent:   0.1%
  MachineType: Notebook P870KM_KM1
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-34-generic 
root=UUID=ba6a2d10-738f-42dc-9b8a-e68c8cc5d368 ro rootflags=subvol=@
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (145 days ago)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P870KM_KM1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P870KM_KM1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1793334/+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 1766775] Re: Notifications do not disappear

[Nicolas CHAPIT]

Arff I was too fast. It was ok, but it restarded 5 min ago >.>

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

Title:
  Notifications do not disappear

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I frequently have notifications that do not disappear after being
  shown.  This is particularly prevalent with power management
  notifications.  Most of the time when I wake my computer from suspend,
  I see the following notification at the top: "Automatic suspend -
  Computer will suspend very soon because of inactivity." that never
  goes away.  Presumably, this was shown before my computer went to
  sleep, and should have disappeared but didn't.  I have to either click
  on the notification, or click on the time to open the notification
  menu to get it to disappear.  Occasionally, the same behaviour occurs
  with other, random notifications.

  This is a long-standing issue for me, that I'm just now getting around
  to reporting.  I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and
  running the gnome-session (not Ubuntu).  I don't know if the issue is
  present on Gnome 3.28, but plan to find out once 18.04 final is
  released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+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 1766775] Re: Notifications do not disappear

[Nicolas CHAPIT]

Hello, me again.

I just did another update with headers (actually 5.4.0-58-generic).
I put back notifications from settings before rebooting, and it seems to 
working perfectly now.

I did apt autoremove after reboot, while I did it before the reboot the
first time (cf my post #7).

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

Title:
  Notifications do not disappear

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I frequently have notifications that do not disappear after being
  shown.  This is particularly prevalent with power management
  notifications.  Most of the time when I wake my computer from suspend,
  I see the following notification at the top: "Automatic suspend -
  Computer will suspend very soon because of inactivity." that never
  goes away.  Presumably, this was shown before my computer went to
  sleep, and should have disappeared but didn't.  I have to either click
  on the notification, or click on the time to open the notification
  menu to get it to disappear.  Occasionally, the same behaviour occurs
  with other, random notifications.

  This is a long-standing issue for me, that I'm just now getting around
  to reporting.  I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and
  running the gnome-session (not Ubuntu).  I don't know if the issue is
  present on Gnome 3.28, but plan to find out once 18.04 final is
  released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+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 1766775] Re: Notifications do not disappear

[Nicolas CHAPIT]

Hello, I think I just got this bug.

System: 18.04.5 LTS
Header's version: linux-headers-5.4.0-54-generic

I don't know what I did to reproduce it.

The gnome notifications can't be closed, even by clicking on the X or do
not disappear.

Right before, I was doing a system update with new headers. Then I
rebooted, and I got issues regarding pcieport for about 20 minutes.
Rebooted multiple times, and then, it went back normal except the
notifications...

I think you can deactivate the notification from the system's settings,
then reboot, it should not annoying you, but it's annoying to not having
the notification anymore :/

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

Title:
  Notifications do not disappear

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  I frequently have notifications that do not disappear after being
  shown.  This is particularly prevalent with power management
  notifications.  Most of the time when I wake my computer from suspend,
  I see the following notification at the top: "Automatic suspend -
  Computer will suspend very soon because of inactivity." that never
  goes away.  Presumably, this was shown before my computer went to
  sleep, and should have disappeared but didn't.  I have to either click
  on the notification, or click on the time to open the notification
  menu to get it to disappear.  Occasionally, the same behaviour occurs
  with other, random notifications.

  This is a long-standing issue for me, that I'm just now getting around
  to reporting.  I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and
  running the gnome-session (not Ubuntu).  I don't know if the issue is
  present on Gnome 3.28, but plan to find out once 18.04 final is
  released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+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 1793334] Re: Chromium does not pick default pulseaudio sink

[Nicolas Göddel]

I've got the same bug on Ubuntu 20.04 with Chromium 86.0.4240.183 when using 
Teams. Every time I call someone or someone calls me it switches source and 
sink to my internal laptop microphone and speakers. Then I have to go to the 
sound settings where it still shows my headphones as source and sink, and I 
need to switch to internal sink/source and back to headphones to make it work. 
It's really annoying.
Why is chromium even allowed to change my pulseaudio settings?

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

Title:
  Chromium does not pick default pulseaudio sink

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  When changing the default sink (builtin audio) to USB audio (PCM2902) 
headphone, all desktop uses the new default sink.
  All but Chromium (and Chrome).
  For both Chromium (and Chrome), I have to change the output device in the 
application tab (PA).  As soon as the audio pauses in Chrome/Chromium, it will 
resume in the builtin output audio device sink.  This happens on a per tab 
basis (probably different process).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Sep 19 11:54:57 2018
  Desktop-Session:
   'plasma'
   
'/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings'
   
'/usr/share/plasma:/home/raul/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2014-05-12 (1591 days ago)
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  Load-Avg-1min: 1.06
  Load-Processes-Running-Percent:   0.1%
  MachineType: Notebook P870KM_KM1
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-34-generic 
root=UUID=ba6a2d10-738f-42dc-9b8a-e68c8cc5d368 ro rootflags=subvol=@
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (145 days ago)
  dmi.bios.date: 02/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P870KM_KM1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P870KM_KM1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  etcconfigcpepperflashpluginnonfree:
   flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
   flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | 
sed -e "s/,/./g"`
   CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso 
--ppapi-flash-version=$flashversion"
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1793334/+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 1896102] Re: gnome-shell crashes

[Nicolas Bock]

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

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

Title:
  gnome-shell crashes

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Regularly emacs-gtk crashes (reported separately in LP: #1896100) and
  with it gnome-shell crashes as well. Since those two crashes happen at
  the same time I am assuming that those two events are related. I don't
  know what the causal relation is though.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.37.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4
  Uname: Linux 5.8.0-18-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 17 12:54:15 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-17 (153 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=screen
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  RelatedPackageVersions: mutter-common 3.37.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896102/+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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time

[Nicolas Frenay]

@vanvugt thanks for the tip.
Since disabling Ubuntu AppIndicators I didn't experience the problem.

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

Title:
  Desktop briefly becomes unresponsive when typing on 2 keyboards at the
  same time

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time

[Nicolas Frenay]

In my case the problem was the Discord app. When it's open I get severe
input lag (kb/mouse) on Chrome and other apps.

Don't know if it's the same bug as reported here but the symptoms match.

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

Title:
  Desktop briefly becomes unresponsive when typing on 2 keyboards at the
  same time

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time

[Nicolas Frenay]

After updating to Ubuntu 20.10 the problem is back.
Brazilian ABNT2 keyboard layout.

Commenting the modifier line is not a valid workaround anymore.
//modifier_map Mod3   { Scroll_Lock };

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

Title:
  Desktop briefly becomes unresponsive when typing on 2 keyboards at the
  same time

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates
  from the repos.

  If I connect 2 (or more) keyboards to my computer and type on both at
  the same time, the desktop briefly becomes unresponsive. More
  keypresses increase the time of unresponsiveness.

  E.g. when typing a full sentence in gedit or the terminal, only very
  few characters show up on the screen (I guess up until something is
  pressed on both keyboards at the same time), then everything freezes.
  Then after a while (some seconds), all the characters show up. And the
  desktop becomes responsive again.

  Symptoms: During the freeze, windows stop updating their content. If
  seconds are enabled on the clock at the top middle, these freeze too.
  But I'm still able to move the mouse pointer around during the freeze
  without any problems.

  The back story:

  I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and
  quickly noticed the issue. But initiallly I thought it was an issue
  with the keyboard, and the problem wasn't that bad. But as I've gotten
  more used to the keyboard since yesterday and started picking up a
  proper typing speed, things got worse.

  The keyboard is technically two separate cabled USB keyboards each
  with only about half of they keys of a normal keyboard (or at least
  that's very much my impression).

  After getting the suspicion that this was a software issue, not a
  hardware issue, I tried typing on my old Logitech keyboard (Unifying
  Receiver) along with one of the R-Go halves: Same issue. Then I tried
  each of the halves without the other (as in "single" keyboard typing):
  No issue. Then I connected another Logitech keyboard (separate UR),
  typed on both Logitechs: Same issue.

  Some further observations:

  1) Nothing of significance in my syslog.
  2) If I drop to a non-graphical shell, there's no problem. I suspect this 
issue is related to X.org or Gnome, but I'm in no position to say anything 
credible about that.
  3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS 
machine.

  Let me know if there are any logs I can provide or things I can run to
  produce useful debug output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1896102] Re: gnome-shell crashes together with emacs-gtk regularly

[Nicolas Bock]

I made bug 1896273 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/1896102

Title:
  gnome-shell crashes together with emacs-gtk regularly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Regularly emacs-gtk crashes (reported separately in LP: #1896100) and
  with it gnome-shell crashes as well. Since those two crashes happen at
  the same time I am assuming that those two events are related. I don't
  know what the causal relation is though.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.37.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4
  Uname: Linux 5.8.0-18-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 17 12:54:15 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-17 (153 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=screen
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  RelatedPackageVersions: mutter-common 3.37.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896102/+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 1896102] Re: gnome-shell crashes together with emacs-gtk regularly

[Nicolas Bock]

I uploaded another crash report at LP: #1896273. Hope this helps.

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

Title:
  gnome-shell crashes together with emacs-gtk regularly

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Regularly emacs-gtk crashes (reported separately in LP: #1896100) and
  with it gnome-shell crashes as well. Since those two crashes happen at
  the same time I am assuming that those two events are related. I don't
  know what the causal relation is though.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.37.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4
  Uname: Linux 5.8.0-18-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 17 12:54:15 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-17 (153 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=screen
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  RelatedPackageVersions: mutter-common 3.37.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896102/+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 1896102] [NEW] gnome-shell crashes together with emacs-gtk regularly

[Nicolas Bock]

Public bug reported:

Regularly emacs-gtk crashes (reported separately in LP: #1896100) and
with it gnome-shell crashes as well. Since those two crashes happen at
the same time I am assuming that those two events are related. I don't
know what the causal relation is though.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.37.91-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4
Uname: Linux 5.8.0-18-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 17 12:54:15 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-17 (153 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=screen
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
RelatedPackageVersions: mutter-common 3.37.91-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago)

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


** Tags: amd64 apport-bug groovy

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

Title:
  gnome-shell crashes together with emacs-gtk regularly

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Regularly emacs-gtk crashes (reported separately in LP: #1896100) and
  with it gnome-shell crashes as well. Since those two crashes happen at
  the same time I am assuming that those two events are related. I don't
  know what the causal relation is though.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.37.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4
  Uname: Linux 5.8.0-18-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 17 12:54:15 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-17 (153 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=screen
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  RelatedPackageVersions: mutter-common 3.37.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896102/+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 1896100] [NEW] emacs-gtk crashes regularly

[Nicolas Bock]

Public bug reported:

Every few days emacs crashes together with gnome-shell. At crash the
application is idle.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: emacs-gtk 1:26.3+1-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4
Uname: Linux 5.8.0-18-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 17 12:50:48 2020
InstallationDate: Installed on 2020-04-17 (153 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=screen
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
SourcePackage: emacs
UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago)

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


** Tags: amd64 apport-bug groovy

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

Title:
  emacs-gtk crashes regularly

Status in emacs package in Ubuntu:
  New

Bug description:
  Every few days emacs crashes together with gnome-shell. At crash the
  application is idle.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: emacs-gtk 1:26.3+1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4
  Uname: Linux 5.8.0-18-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 17 12:50:48 2020
  InstallationDate: Installed on 2020-04-17 (153 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=screen
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SourcePackage: emacs
  UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago)

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

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

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

Thanks Helmut and Francesco

I have a (bold ?) question.

As previously reported, it works (at least, moves and clicks as
expected, not talking gestures here) in the UEFI BIOS prior to the
loading of any operating system.

Does this mean there is a kind of working driver in code of the UEFI
BIOS ? If yes, any hope to get it from Lenovo or other vendors ?

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Confirmed
Status in linux package in Fedora:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnL

[Desktop-packages] [Bug 1864778] Re: Intel Drivers Artifacts after Mesa-Dev Update

[Nicolas]

I have the same issue on Thinkpad X250 on 20.04 with the following config:
```
Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "AccelMethod" "uxa"
   Option  "TearFree" "true"
EndSection
```

resulting in being unable to use plasma wayland sessions, random system
freezes and strong flickering in sddm. purging `xserver-xorg-video-
intel` solved the issue for me

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

Title:
  Intel Drivers Artifacts after Mesa-Dev Update

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  After the update from the 20.04 LTS fresh live image from 19.3.3-1ubuntu1 to 
20.0.0-1ubuntu1 mesa
  I get serious artifacts on startup when using the intel driver instead of 
modesetting.  These artifacts go away when I enable Option AccelMethod "uxa" 
but persist if the default, "sna" or the other modes are used "none", "off", 
"blt".

  These pixels appear throughout the experience of using Ubuntu and
  generate in sporadic places.  The font also looks completely broken.
  I've never had this issue before with the Intel drivers.  I have
  Skylake HD 530.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1864778/+subscriptions

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

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

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

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease:

[Desktop-packages] [Bug 1879649] Re: Since I updated to Ubuntu 20.04 my HP printer doesn't print

[Nicolas Rogues]

HPLIP 3.20.6 downloaded from developers.hp.com resolves all the issues

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

Title:
  Since I updated to Ubuntu 20.04 my HP printer doesn't print

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Incomplete
Status in notify-python package in Ubuntu:
  Confirmed
Status in pillow-python2 package in Ubuntu:
  Confirmed
Status in python-reportlab package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since I updated to Ubuntu 20.04, my printer does not print. I have installed 
and uninstalled the printer several times and test with different URI adresses 
which the PC found the printer.
  I uninstalled and installed again HPLIP but there are some dependencies that 
cannot be installed.
  The model of the printer is an HP OfficeJet 9650.
  The script HP-doctor didn't solve the problem. See the attached file for the 
output of the script hp-check.

  I look forward to hear from you soon

  For any question, don't hesitate to contact me.

  Kind regards,

  Biel Trobat
  cont...@bieltrobat.me

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1879649/+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 1879649] Re: Since I updated to Ubuntu 20.04 my HP printer doesn't print

[Nicolas Rogues]

Same issue issue with an OfficeJet 8010 here on a fresh Ubuntu 20.04
install. HPLIP downloaded from hp.com used to work on 16.04 & 18.04
setups with this printer.

No HPLIP installed from hp.com, just Ubuntu 20.04 installation.

I ran the command from post #4, no error. But it still does not work.
Please find attached hp-check log.

These comments from hp-check log are strange for packages from focal repos ?
1/ warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions 
dependencies to verify and install...
2/ warning: HPLIP-Installation: Auto installation is not supported for ubuntu 
distro  20.04 version
3/ Missing Required Dependencies
-
error: 'libcups2' package is missing/incompatible 
error: 'libdbus-1-dev' package is missing/incompatible 
error: 'libjpeg-dev' package is missing/incompatible 
error: 'libcups2-dev' package is missing/incompatible 
error: 'cups-bsd' package is missing/incompatible 
error: 'cups-client' package is missing/incompatible 
error: 'libcupsimage2-dev' package is missing/incompatible 
error: 'libusb-1.0.0-dev' package is missing/incompatible 
error: 'libusb-0.1-4' package is missing/incompatible 
error: 'libsane-dev' package is missing/incompatible 
error: 'libsnmp-dev' package is missing/incompatible 
error: 'snmp-mibs-downloader' package is missing/incompatible 
error: 'openssl' package is missing/incompatible 
error: 'python3-pyqt4' package is missing/incompatible 
error: 'gtk2-engines-pixbuf' package is missing/incompatible 
error: 'python3-dev' package is missing/incompatible 
error: 'libtool' package is missing/incompatible 
error: 'libtool-bin' package is missing/incompatible 

Missing Optional Dependencies
-
error: 'gtk2-engines-pixbuf' package is missing/incompatible 
error: 'xsane' package is missing/incompatible 
error: 'python3-dbus.mainloop.qt' package is missing/incompatible 

** Attachment added: "hp-check.log"
   
https://bugs.launchpad.net/hplip/+bug/1879649/+attachment/5395993/+files/hp-check.log

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

Title:
  Since I updated to Ubuntu 20.04 my HP printer doesn't print

Status in HPLIP:
  In Progress
Status in hplip package in Ubuntu:
  Incomplete
Status in notify-python package in Ubuntu:
  Confirmed
Status in pillow-python2 package in Ubuntu:
  Confirmed
Status in python-reportlab package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  Since I updated to Ubuntu 20.04, my printer does not print. I have installed 
and uninstalled the printer several times and test with different URI adresses 
which the PC found the printer.
  I uninstalled and installed again HPLIP but there are some dependencies that 
cannot be installed.
  The model of the printer is an HP OfficeJet 9650.
  The script HP-doctor didn't solve the problem. See the attached file for the 
output of the script hp-check.

  I look forward to hear from you soon

  For any question, don't hesitate to contact me.

  Kind regards,

  Biel Trobat
  cont...@bieltrobat.me

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

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

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

Thanks Helmut and Ben. These are very precise information and better than any 
post elsewhere.
I got no reply from the email contacts provided by Kai-Heng yet...
Anyone with a Lenovo connection ?

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersio

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

It's a good question.

In my understanding, the Legion R7000 is the name for China of the
Legion-5 15ARH05. In the Lenovo forum, the Lenovo employee has no access
to the equipment and indicates it's a kernel issue, suggesting it used
to work prior to 5.4 kernel. That looks strange.

https://forums.lenovo.com/topic/view/2713/5020793

Also in this thread a member of the Lenovo forum points out to a blog,
unfortunately in Chinese, of a guy who may have found a workaround. I
tried to google translate it but was not sure of the result to try
anything :

https://www.cnblogs.com/mikeguan/p/13126497.html

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dm

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

Hello Didi,

The issue we face could be different : on the Lenovo Legion-5 15ARH05
(which is the object of this bug report) there is no working trick to
boot on Windows then Ubuntu : it just never worked under Linux on the
two BIOS tested (factory I think EUCN16WW and June update EUCN19WW), in
UEFI mode, no matters if Windows was used before reboot and grub to
Ubuntu (I have a dual-boot setup).

As a remark, the touchpad does work in the UEFI BIOS, before any OS is
loaded.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnL

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

done today

got an error from vger.kernel.org (policy analysis reported: your
address is not liked source for email) but not from other recipients, so
if any of the other affected users has an approved email address with
this server, I will be glad to provide the initial email for forwarding

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.versi

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

** Attachment added: "Capture d’écran de 2020-07-15 13-46-14.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5392809/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-07-15%2013-46-14.png

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  ---

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

AMDI0010:03 and pinctrl_amd are present but the count does not move when
I move finger or click on the touchpad.

Please note I tried to remove my USB Mouse which is responsible for the
high counts on one of xhci_hcd. For this mouse it's moving rapidly.

Two screen captures enclosed.

** Attachment added: "Capture d’écran de 2020-07-15 13-39-38.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5392808/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-07-15%2013-39-38.png

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvn

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

Here you go
Nicolas

** Attachment added: "dmesg 5.4.42 kernel.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5392768/+files/dmesg%205.4.42%20kernel.txt

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion:

[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

[Nicolas Rogues]

Hello,

The kernel 5.4.0-42-generic from
https://people.canonical.com/~khfeng/lp1887190/ does not work either.

Thanks

Nicolas

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-input-libinput package in Ubuntu:
  New

Bug description:
  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic 
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-40-generic N/A
   linux-backports-modules-5.4.0-40-generic  N/A
   linux-firmware1.187.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN19WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckRe

Re: [Desktop-packages] [Bug 1883981] Re: dash-to-dock extension gets buggy after lock

[Nicolas Caparroz]

Thank you! That solved the problem..

Regards

El jue., 18 de jun. de 2020 a la(s) 04:15, Daniel van Vugt (
1883...@bugs.launchpad.net) escribió:

> Please run 'gnome-shell-extension-prefs' and ensure you only have one
> dock extension enabled.
>
> If you have multiple docks enabled then we should reword this bug to be
> about any remaining issue that occurs when only one dock is enabled.
>
>
> ** Also affects: gnome-shell-extension-dashtodock (Ubuntu)
>Importance: Undecided
>Status: New
>
> ** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1883981
>
> Title:
>   dash-to-dock extension gets buggy after lock
>
> Status in gnome-shell-extension-dashtodock package in Ubuntu:
>   Incomplete
> Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Works perfect on boot.
>   After 1st lock both dash-to-dock and ubuntu-gnome-dock appear on
> Activities Overview.
>   On 2nd lock, dash-to-dock appears on lockscreen.
>   After 2nd lock, two docks appear (overlapped) on the homescreen
> (desktop).
>
>   Dash to dock - version 68
>   Gnome 3.36.2
>   Ubuntu 20.04 LTS x64
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
>   ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
>   Uname: Linux 5.4.0-37-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.2
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Jun 17 23:27:58 2020
>   InstallationDate: Installed on 2020-06-15 (2 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   PackageArchitecture: all
>   SourcePackage: gnome-shell-extension-ubuntu-dock
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1883981/+subscriptions
>


-- 
Nicolas Caparroz

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

Title:
  dash-to-dock extension gets buggy after lock

Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  Works perfect on boot.
  After 1st lock both dash-to-dock and ubuntu-gnome-dock appear on Activities 
Overview.
  On 2nd lock, dash-to-dock appears on lockscreen.
  After 2nd lock, two docks appear (overlapped) on the homescreen (desktop).

  Dash to dock - version 68
  Gnome 3.36.2
  Ubuntu 20.04 LTS x64

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 17 23:27:58 2020
  InstallationDate: Installed on 2020-06-15 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1883981/+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 1883981] [NEW] dash-to-dock extension gets buggy after lock

[Nicolas Caparroz]

Public bug reported:

Works perfect on boot.
After 1st lock both dash-to-dock and ubuntu-gnome-dock appear on Activities 
Overview.
On 2nd lock, dash-to-dock appears on lockscreen.
After 2nd lock, two docks appear (overlapped) on the homescreen (desktop).

Dash to dock - version 68
Gnome 3.36.2
Ubuntu 20.04 LTS x64

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 17 23:27:58 2020
InstallationDate: Installed on 2020-06-15 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  dash-to-dock extension gets buggy after lock

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Works perfect on boot.
  After 1st lock both dash-to-dock and ubuntu-gnome-dock appear on Activities 
Overview.
  On 2nd lock, dash-to-dock appears on lockscreen.
  After 2nd lock, two docks appear (overlapped) on the homescreen (desktop).

  Dash to dock - version 68
  Gnome 3.36.2
  Ubuntu 20.04 LTS x64

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 17 23:27:58 2020
  InstallationDate: Installed on 2020-06-15 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1883981/+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 1854676] Re: [snap] Web Midi API doesn't work

[Nicolas Clavaud]

I can confirm that since I updated from Ubuntu 18.04 (Chromium deb) to
Ubuntu 20.04 (Chromium snap), I can no longer connect to my device using
WebMIDI (nor WebUSB).

For information, the web app asks permission to "Use your MIDI devices",
but the call to "navigator.requestMIDIAccess()" fails.

In /var/log/syslog I get the same log entries as in the previous post:

chromium_chromium.desktop[11556]: ALSA lib conf.c:3916:(snd_config_update_r) 
Cannot access file /usr/share/alsa/alsa.conf
chromium_chromium.desktop[11556]: ALSA lib seq.c:935:(snd_seq_open_noupdate) 
Unknown SEQ hw

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

Title:
  [snap] Web Midi API doesn't work

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm 
trying to test out the Web Midi API:
  https://www.w3.org/TR/webmidi/

  Although it is supposed to be supported in Chromium, none of these samples 
work in Ubuntu 19.10's snap-package installation of Chromium:
  https://webaudio.github.io/demo-list/

  In the meantime, please recommend a work-around of how I can work with
  the Web Midi API while using Ubuntu Linux as my operating system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+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 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment

[Nicolas DERIVE]

@seb128: it's broken again in latest 3.36.0 release: Failed to load
backend for 'application/pdf': libnss3.so: échec d'adressage (mapping)
du segment de l'objet partagé

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

Title:
  Opening a pdf from Zotero in evince, I got "failed to load backend for
  'application/pdf': libnss3.so: failed to load shared object mapping
  segment

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Opening a pdf file from Zotero in evince, I got "failed to load
  backend for 'application/pdf': libnss3.so: failed to load shared
  object mapping segment" and the file won't open. When opening the file
  from its location in Nautilus, that works properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 10:17:17 2020
  InstallationDate: Installed on 2019-02-21 (398 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159/+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 1874578] Re: [wayland] dock has very long load time

[Nicolas Damgaard Larsen]

Confirming this issue on an 19.10 to 20.04 upgrade (originally 18.04).
Problem persisted after a dconf reset. Problem also oberserved on a
fresh 20.04 with old profile. Problem also observed on fresh install in
virtualbox with a fresh user profile. All were minimal installs if that
matters which I highly doubt. Reproducible by running

'gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts
false'

and restarting gnome. Toggling it back to 'true' and restarting gnome
clears the issue for me.

Running X11.

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

Title:
  [wayland] dock has very long load time

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I just upgraded from Ubuntu 18.04 to 20.04.

  When I boot my system I have to wait at least 10 to 15 seconds for the
  application icons to load on dock. Meanwhile everything else seems to
  be working properly. I didn't experience this behavior in Ubuntu
  18.04.

  Also the dock doesn't trigger when I move my cursor to the left of the 
screen. (I have set the docker to Auto-Hide mode and it's position is on the 
left of my screen).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2016-08-03 (1359 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags: focal third-party-packages wayland-session
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874578/+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 1869572] Re: Dock icons are shown very slow

[Nicolas Damgaard Larsen]

In addition to post #10:

Reproducible by running

'gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts
false'

and restarting gnome. Toggling it back to 'true' and restarting gnome
clears the issue for me.

Running X11.

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

Title:
  Dock icons are shown very slow

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  When I open a new app (e.g a terminal window) in the dock does not
  appear nothing for about 15 seconds, when the icon of the terminal
  appears. It is incredibly annoying since I work open and closing apps
  and don't know where they are since the dock is updated every 15
  seconds

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Uname: Linux 5.4.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 13:19:25 2020
  InstallationDate: Installed on 2020-02-20 (37 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2020-03-25T18:04:30.897651

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1869572/+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 1869572] Re: Dock icons are shown very slow

[Nicolas Damgaard Larsen]

Confirming this issue on an 19.10 to 20.04 upgrade (originally 18.04).
Problem persisted after a dconf reset. Problem also oberserved on a
fresh 20.04 with old profile. Problem also observed on fresh install in
virtualbox with a fresh user profile. All were minimal installs if that
matters which I highly doubt. Problem seems to occur inconsistently
across boots/logins.

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

Title:
  Dock icons are shown very slow

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  When I open a new app (e.g a terminal window) in the dock does not
  appear nothing for about 15 seconds, when the icon of the terminal
  appears. It is incredibly annoying since I work open and closing apps
  and don't know where they are since the dock is updated every 15
  seconds

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Uname: Linux 5.4.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 13:19:25 2020
  InstallationDate: Installed on 2020-02-20 (37 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2020-03-25T18:04:30.897651

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1869572/+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 1780310] Re: Option 'finishings' has value '3' and cannot be edited

[Nicolas Damgaard Larsen]

Confirming issue. Using the Ricoh Aficio MP C3502 PS driver.

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

Title:
  Option 'finishings' has value '3' and cannot be edited

Status in System Config Printer:
  New
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Whenever I open the print queue for my local printer, I get a dialog
  box with the message:

  Option 'finishings' has value '3' and cannot be edited

  I can dismiss the dialog box and everything seems to work normally,
  but it is annoying.  However, it's possible that some obscure printer
  feature does not work for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: system-config-printer 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  5 12:30:50 2018
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationDate: Installed on 2018-07-03 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  Lpstat: device for Ricoh-Aficio-MP-C3500: 
lpd://hqnvprint02.nvidia.com/secureprint
  MachineType: ASUS X299-A
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd: Permission denied
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=d418cc23-14fc-41cf-b75f-29644c2a16be ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnASUS:pnX299-A:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X299-A
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1780310/+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 1780310] Re: Option 'finishings' has value '3' and cannot be edited

[Nicolas Damgaard Larsen]

According to https://github.com/OpenPrinting/system-config-
printer/issues/122 it should be temporarily fixed in 1.5.12 which is
included in 20.04. Will this be be released into 18.04?

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

Title:
  Option 'finishings' has value '3' and cannot be edited

Status in System Config Printer:
  New
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Whenever I open the print queue for my local printer, I get a dialog
  box with the message:

  Option 'finishings' has value '3' and cannot be edited

  I can dismiss the dialog box and everything seems to work normally,
  but it is annoying.  However, it's possible that some obscure printer
  feature does not work for me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: system-config-printer 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  5 12:30:50 2018
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationDate: Installed on 2018-07-03 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterpreterPath: /usr/bin/python3.6
  Lpstat: device for Ricoh-Aficio-MP-C3500: 
lpd://hqnvprint02.nvidia.com/secureprint
  MachineType: ASUS X299-A
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Ricoh-Aficio-MP-C3500.ppd: Permission denied
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=d418cc23-14fc-41cf-b75f-29644c2a16be ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X299-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/07/2018:svnASUS:pnX299-A:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: X299-A
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1780310/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Nicolas Damgaard Larsen]

I can confirm this is still an issue. The odd part is, however, that I
did not have this issue on 19.10 with the nvidia drivers from the ppa.
Upgrading to 20.04 introduced this issue to me.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 34813] Re: gedit fails to save files over smbfs/cifs

[Nicolas Göddel]

This bug also affects Ubuntu 19.10 with

$ gedit -V
gedit - Version 3.34.0

$ sshfs -V
SSHFS version 2.10.0
FUSE library version: 2.9.9
fusermount version: 2.9.9
using FUSE kernel interface version 7.19

$ uname -r
5.3.0-46-generic

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename:   eoan

I can not confirm what @elatllat was saying 2 years ago.

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

Title:
  gedit fails to save files over smbfs/cifs

Status in gedit:
  Expired
Status in Samba Server:
  Invalid
Status in SSHFS Mounter:
  Confirmed
Status in gedit package in Ubuntu:
  Triaged
Status in gedit package in CentOS:
  New

Bug description:
  Saving files over a cifs/smbfs server doesnt work.  You can open file,
  edit then save perfectly.  But repeated saves after give you this
  error:

  "The file /home/dhonn/website/arrays.php has been modified since
  reading it.  If you save it, all the external changes could be lost.
  Save it anyway?"

  The think is lying to me because I havent made any external changes.

  When I click "Save Anyway", i get this error:

  "Could not save the file /home/dhonn/website/arrays.php."

  But on the third try it works just fine.

  Here are the error messages, btw there are also GUI glitches too:
  http://dhonn.com/images/gedit-0.jpg
  http://dhonn.com/images/gedit-1.jpg

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/34813/+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 1846334] Re: cupsd assert failure: free(): invalid pointer

[Nicolas DERIVE]

It seems to be the third time I encounter this bug in a week...

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

Title:
  cupsd assert failure: free(): invalid pointer

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Just running in the background, no user action (printing)

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-daemon 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AssertionMessage: free(): invalid pointer
  Date: Tue Oct  1 19:41:35 2019
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2019-02-09 (234 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  Lpstat:
   device for HP_LaserJet_CM1415fn_44A808_: 
implicitclass://HP_LaserJet_CM1415fn_44A808_/
   device for Samsung_C48x_Series_SEC84251900EE44_: 
implicitclass://Samsung_C48x_Series_SEC84251900EE44_/
  MachineType: Dell Inc. Latitude E6530
  Papersize: letter
  PpdFiles:
   HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere
   Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic 
root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at 
malloc.c:5332
   _int_free (av=, p=, have_lock=0) at 
malloc.c:4173
   ?? () from /lib/x86_64-linux-gnu/libcups.so.2
   ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2
  Title: cupsd assert failure: free(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/30/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.sku: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+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 1869913] Re: "Click or press a key to unlock" string not translated into french

[Nicolas DERIVE]

Date format in lockscreen is also wrong, (Day Month Day Number)

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

Title:
  "Click or press a key to unlock" string not translated into french

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On the lockscreen, the "Click or press a key to unlock" string is not
  translated, at least in french.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 14:56:11 2020
  InstallationDate: Installed on 2019-02-21 (404 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869913/+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 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment

[Nicolas DERIVE]

That's seems to be fixed in latest version, probably through this
modification:

  * d/apparmor-profile.abstraction:
Allow running dash/bash with inherited AppArmor profile.
GDesktopAppInfo in GLib 2.64.x uses a one-line shell script to carry
out some setup when launching .desktop files, for example as a
URL handler. (Closes: #954013)

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

Title:
  Opening a pdf from Zotero in evince, I got "failed to load backend for
  'application/pdf': libnss3.so: failed to load shared object mapping
  segment

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Opening a pdf file from Zotero in evince, I got "failed to load
  backend for 'application/pdf': libnss3.so: failed to load shared
  object mapping segment" and the file won't open. When opening the file
  from its location in Nautilus, that works properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 10:17:17 2020
  InstallationDate: Installed on 2019-02-21 (398 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159/+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 1869913] [NEW] "Click or press a key to unlock" string not translated into french

[Nicolas DERIVE]

Public bug reported:

On the lockscreen, the "Click or press a key to unlock" string is not
translated, at least in french.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 31 14:56:11 2020
InstallationDate: Installed on 2019-02-21 (404 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago)

** Affects: gdm3 (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 gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1869913

Title:
  "Click or press a key to unlock" string not translated into french

Status in gdm3 package in Ubuntu:
  New

Bug description:
  On the lockscreen, the "Click or press a key to unlock" string is not
  translated, at least in french.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 14:56:11 2020
  InstallationDate: Installed on 2019-02-21 (404 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-03-20 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869913/+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 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment

[Nicolas DERIVE]

Zotero is a bibliography tool (https://www.zotero.org/). When I double
click on a pdf in it, it opens the pdf file using the default system
tool, here evince, and triggers that evince error.

Here is the tail of journalctl -b 0 output with the relevant lines:

mars 27 11:53:08 darwin audit[52507]: AVC apparmor="DENIED" 
operation="file_mmap" profile="/usr/bin/evince" 
name="/home/nicolas/Zotero_linux-x86_64/libnss3.so" pid=52507 
comm="EvJobScheduler" requested_mask="m" denied_mask="m" fsuid=1000 ouid=1000
mars 27 11:53:08 darwin kernel: audit: type=1400 audit(1585306388.116:3096): 
apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" 
name="/home/nicolas/Zotero_linux-x86_64/libnss3.so" pid=52507 
comm="EvJobScheduler" requested_mask="m" denied_mask="m" fsuid=1000 ouid=1000
mars 27 11:53:08 darwin kernel: audit: type=1400 audit(1585306388.116:3097): 
apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" 
name="/home/nicolas/Zotero_linux-x86_64/libnss3.so" pid=52507 
comm="EvJobScheduler" requested_mask="m" denied_mask="m" fsuid=1000 ouid=1000
mars 27 11:53:08 darwin audit[52507]: AVC apparmor="DENIED" 
operation="file_mmap" profile="/usr/bin/evince" 
name="/home/nicolas/Zotero_linux-x86_64/libnss3.so" pid=52507 
comm="EvJobScheduler" requested_mask="m" denied_mask="m" fsuid=1000 ouid=1000

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

Title:
  Opening a pdf from Zotero in evince, I got "failed to load backend for
  'application/pdf': libnss3.so: failed to load shared object mapping
  segment

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Opening a pdf file from Zotero in evince, I got "failed to load
  backend for 'application/pdf': libnss3.so: failed to load shared
  object mapping segment" and the file won't open. When opening the file
  from its location in Nautilus, that works properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 10:17:17 2020
  InstallationDate: Installed on 2019-02-21 (398 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159/+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 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment

[Nicolas DERIVE]

@seb128 Please find these output:

$ dpkg -l | grep evince
ii  evince 3.36.0-1 
   amd64Document (PostScript, PDF) viewer
ii  evince-common  3.36.0-1 
   all  Document (PostScript, PDF) viewer - common files

$ dpkg -l | grep nss
ii  libconfig-model-openssh-perl   2.8.0.1-1
   all  configuration editor for OpenSsh
ii  libcurl4-openssl-dev:amd64 7.68.0-1ubuntu1  
   amd64development files and documentation for libcurl 
(OpenSSL flavour)
ii  libevent-openssl-2.1-7:amd64   2.1.11-stable-1  
   amd64Asynchronous event notification library (openssl)
ii  libjansson4:amd64  2.12-1build1 
   amd64C library for encoding, decoding and manipulating 
JSON data
ii  libnss-mdns:amd64  0.14.1-1ubuntu1  
   amd64NSS module for Multicast DNS name resolution
ii  libnss-myhostname:amd64245.2-1ubuntu2   
   amd64nss module providing fallback resolution for the 
current hostname
ii  libnss-systemd:amd64   245.2-1ubuntu2   
   amd64nss module providing dynamic user and group name 
resolution
ii  libnss3:amd64  2:3.49.1-1ubuntu1
   amd64Network Security Service libraries
ii  libxmlsec1-nss:amd64   1.2.28-2 
   amd64Nss engine for the XML security library
ii  openssh-client 1:8.1p1-5
   amd64secure shell (SSH) client, for secure access to 
remote machines
ii  openssh-server 1:8.1p1-5
   amd64secure shell (SSH) server, for secure access from 
remote machines
ii  openssh-sftp-server1:8.1p1-5
   amd64secure shell (SSH) sftp server module, for SFTP 
access from remote machines
ii  openssl1.1.1d-2ubuntu6  
   amd64Secure Sockets Layer toolkit - cryptographic utility
ii  perl-openssl-defaults:amd644
   amd64version compatibility baseline for Perl OpenSSL 
packages
ii  python-openssl 19.0.0-1build1   
   all  Python 2 wrapper around the OpenSSL library

And there's no libpdfdocument.sos but I suppose you meant
libpdfdocument.so :

$ ldd -v /usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so 
linux-vdso.so.1 (0x7ffe9ca13000)
libevdocument3.so.4 => /usr/lib/x86_64-linux-gnu/libevdocument3.so.4 
(0x7fd470424000)
libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fd46fd18000)
libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fd46fcc9000)
libgdk_pixbuf-2.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fd46fca1000)
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fd46fac1000)
libpoppler-glib.so.8 => /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8 
(0x7fd46fa61000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fd46f9ff000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fd46f8d6000)
libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 
(0x7fd46f71c000)
libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fd46f5f9000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd46f407000)
libsynctex.so.2 => /usr/lib/x86_64-linux-gnu/libsynctex.so.2 
(0x7fd46f3e9000)
libgdk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fd46f2e2000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7fd46f2dc000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fd46f18d000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fd46f16a000)
libpangocairo-1.0.so.0 => 
/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7fd46f158000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x7fd46f01b000)
libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7fd46f007000)
libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 
(0x7fd46ee01000)
libcairo-gobject.so.2 => 
/usr/lib/x86_64-linux-gnu/libcairo-gobject.so.2 (0x7fd46edf5000)
libatk-1.0.so.0 => 

[Desktop-packages] [Bug 1869159] [NEW] Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment

[Nicolas DERIVE]

Public bug reported:

Opening a pdf file from Zotero in evince, I got "failed to load backend
for 'application/pdf': libnss3.so: failed to load shared object mapping
segment" and the file won't open. When opening the file from its
location in Nautilus, that works properly.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: evince 3.36.0-1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 26 10:17:17 2020
InstallationDate: Installed on 2019-02-21 (398 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago)

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


** Tags: amd64 apparmor apport-bug focal

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1869159/+attachment/5341792/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-03-26%2010-16-46.png

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

Title:
  Opening a pdf from Zotero in evince, I got "failed to load backend for
  'application/pdf': libnss3.so: failed to load shared object mapping
  segment

Status in evince package in Ubuntu:
  New

Bug description:
  Opening a pdf file from Zotero in evince, I got "failed to load
  backend for 'application/pdf': libnss3.so: failed to load shared
  object mapping segment" and the file won't open. When opening the file
  from its location in Nautilus, that works properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evince 3.36.0-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 10:17:17 2020
  InstallationDate: Installed on 2019-02-21 (398 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago)

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

[Nicolas DERIVE]

@alexmurray: same pattern for me. It probably happened at shutdown
according to timestamp, and Apport popped up just after login with
Nautilus crash.

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