from:"Sergio"

** Description changed:

  [ Impact ]
  
  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.
  
  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases because it returned the local path that corresponded to the remote
  file when exported by Gvfs using FUSE, so this behaviour is not only a
  serious bug, but also a regression.
  
- The old behavior has been now "set on stone" in the XDG portal
+ The old behavior has now been "set on stone" in the XDG portal
  specification, mandating that the backends must always return local
  paths, no matter if the chosen file is a local or remote one, by using
  FUSE.
  
  [ Test plan]
  Steps to reproduce:
  
  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share
  
  Actual behavior:
  
  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown
  
  Expected behavior:
  
  * File is saved to selected network share location
  * No error is shown
  
  [ Where problems could occur ]
  
  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than now.
  
  - Any hidden  bug in g_file_get_path() when managing remote drives could
  be triggered by this patch.
  
  [ Additional information ]
  
  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Fix Committed
Status in xdg-desktop-portal-gnome source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases because it returned the local path that corresponded to the
  remote file when exported by Gvfs using FUSE, so this behaviour is not
  only a serious bug, but also a regression.

  The old behavior has now been "set on stone" in the XDG portal
  specification, mandating that the backends must always return local
  paths, no matter if the chosen file is a local or remote one, by using
  FUSE.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  F

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

** Description changed:

  [ Impact ]
  
  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.
  
  The previous backend, xdg-desktop-portal-gtk, did work fine in these
- cases, because it returned the local path that corresponded to the local
- file exported by Gvfs using FUSE, so this behaviour is not only a
+ cases because it returned the local path that corresponded to the remote
+ file when exported by Gvfs using FUSE, so this behaviour is not only a
  serious bug, but also a regression.
+ 
+ The old behavior has been now "set on stone" in the XDG portal
+ specification, mandating that the backends must always return local
+ paths, no matter if the chosen file is a local or remote one, by using
+ FUSE.
  
  [ Test plan]
  Steps to reproduce:
  
  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share
  
  Actual behavior:
  
  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown
  
  Expected behavior:
  
  * File is saved to selected network share location
  * No error is shown
  
  [ Where problems could occur ]
  
  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than now.
  
  - Any hidden  bug in g_file_get_path() when managing remote drives could
  be triggered by this patch.
  
  [ Additional information ]
  
  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Fix Committed
Status in xdg-desktop-portal-gnome source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases because it returned the local path that corresponded to the
  remote file when exported by Gvfs using FUSE, so this behaviour is not
  only a serious bug, but also a regression.

  The old behavior has been now "set on stone" in the XDG portal
  specification, mandating that the backends must always return local
  paths, no matter if the chosen file is a local or remote one, by using
  FUSE.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occu

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

** Changed in: xdg-desktop-portal-gnome (Ubuntu Jammy)
   Status: Triaged => Fix Committed

** Changed in: xdg-desktop-portal-gnome (Ubuntu Jammy)
 Assignee: (unassigned) => Sergio Costas (rastersoft-gmail)

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Fix Committed
Status in xdg-desktop-portal-gnome source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168] Re: [snap] Files on local network shares are not opened / written

The patch is still queued https://salsa.debian.org/gnome-team/xdg-
desktop-portal-gnome/-/merge_requests/10

I'll ping again.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Won't Fix

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 2054162] [NEW] package install-info 6.8-4build1 failed to install/upgrade: el subproceso instalado paquete install-info script post-installation devolvió el código de salida de

2024-02-16 Thread Sergio Fuentes

Public bug reported:

ackage install-info 6.8-4build1 failed to install/upgrade: el subproceso
instalado paquete install-info script post-installation devolvió el
código de salida de error 1

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: install-info 6.8-4build1
Uname: Linux 6.7.4-2-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Feb 16 21:13:43 2024
ErrorMessage: el subproceso instalado paquete install-info script 
post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2024-01-29 (18 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
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.11
SourcePackage: texinfo
Title: package install-info 6.8-4build1 failed to install/upgrade: el 
subproceso instalado paquete install-info script post-installation devolvió el 
código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package install-info 6.8-4build1 failed to install/upgrade: el
  subproceso instalado paquete install-info script post-installation
  devolvió el código de salida de error 1

Status in texinfo package in Ubuntu:
  New

Bug description:
  ackage install-info 6.8-4build1 failed to install/upgrade: el
  subproceso instalado paquete install-info script post-installation
  devolvió el código de salida de error 1

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: install-info 6.8-4build1
  Uname: Linux 6.7.4-2-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Feb 16 21:13:43 2024
  ErrorMessage: el subproceso instalado paquete install-info script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2024-01-29 (18 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  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.11
  SourcePackage: texinfo
  Title: package install-info 6.8-4build1 failed to install/upgrade: el 
subproceso instalado paquete install-info script post-installation devolvió el 
código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/2054162/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile

2024-02-08 Thread Sergio Durigan Junior

Hello Hui,

The changes look good to me, but I have a few minor requests:

- Could you please expand the changelog entry and explain what the patch
fixes?  It doesn't need to be a long text or anything like that; just a
small sentence is enough.

- Could you add DEP-3 headers to the patch, please?  You can find more
information here:

https://dep-team.pages.debian.net/deps/dep3/

but basically, I'm looking for something like:

Origin: upstream, 
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/d7dc04e8f5c404b1fa16409f69dcde7c56312f02
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2051895

I'm unsubscribing ubuntu-sponsors from the bug for now.  Please
resubscribe it once you've addressed the points above.

Thanks.

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

Title:
  Lenovo XT99 BT headset can't work in HFP profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Jammy:
  In Progress
Status in pulseaudio source package in Mantic:
  In Progress
Status in pulseaudio source package in Noble:
  In Progress

Bug description:
  [Summary]
  When use the ThinkPluse xt99 bluetooth head set to run the test 
com.canonical.certification::bluetooth/audio_record_playback, it cannot record 
the sound and playback.
  It seems this device cannot switch to Hand free mode in this platform.

  [Steps to reproduce]
  Connect the ThinkPluse xt99, use the Handfree mode, then try to record some 
voice.

  [Expected result]
  The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound.

  [Actual result]
  The bluetooth headset xt99 cannot work in the Handfree mode.

  [Failure rate]
  100%

  
  [Impact]
  With the current Ubuntu 22.04 oem image, we try to connect the LENOVO
  XT99 bt headset and let it work in HFP mode, we select HFP profile
  from gnome sound-setting, but the microphone will not auto change to
  bt microphone and the bt output could not work too. So this BT headset
  could only work in A2DP mode with the current 22.04 OEM image.

  And we tried ubuntu 22.04 generic image, mantic image and noble image,
  none of them could make the headset work in HFP mode.
   
  [Fix]
  Cherry-pick a pulseaudio commit from upstream.

  [Test]
  Install the patched pulseaudio and reboot, connect to the LENOVO XT99
  bt headset, select it to work in HFP mode, tested playback and capture,
  all worked well.

  [Where problems could occur]
  This change will impact bt headset negotiation process in the pulseaudio,
  so the possiblity of regression is limited to bt headset, it could make
  the bt headset fail to connect, but this possibility is very low, we tested
  the patch with different bt headset and bt speaker, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2016013] Re: New windows don't get centered if Desktop Icons NG is loaded

2024-02-06 Thread Sergio Costas

Sorry for the delay. Yes, it is because of that. In Gnome 46 is a new
API that allows to mark a window as "desktop window" and should fix it,
and I want to use it, but I'm waiting for 24.04 to go out because it
would be a big change, and I don't want to risk a LTS.

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

Title:
  New windows don't get centered if Desktop Icons NG is loaded

Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  New windows don't get centered if Desktop Icons NG is loaded.

  With vanilla GNOME, if an app window is too large for tiling (larger
  than a quarter of the screen) then it will be centered by default. But
  this doesn't happen when DING is loaded, probably because DING is
  incorrectly treated as an app window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2016013/+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 2051504] Re: 0.4.17-1ubuntu1 removes all output and input sinks in gnome settings

2024-01-29 Thread Sergio Costas

Added pipewire to the affected packages because the patch is for it.

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

** Changed in: pipewire (Ubuntu)
 Assignee: (unassigned) => Sergio Costas (rastersoft-gmail)

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

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

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

Title:
  0.4.17-1ubuntu1 removes all output and input sinks in gnome settings

Status in pipewire package in Ubuntu:
  Confirmed
Status in wireplumber package in Ubuntu:
  Confirmed

Bug description:
  After the changes committed as part of
  https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1995707
  (wireplumber 0.4.17-1ubuntu1), all input and output sinks are removed
  from gnome settings on reboot.

  Playing audio through celluloid (mpv) still works with the default
  sink, while Firefox Nightly refuses to play anything.

  I've tested this on two machines now;
  - One running on nvidia+X11, without snapd installed.
  - Another running on intel+wayland, also without snapd.

  Reverting to 0.4.17-1 works fine, and gnome settings lists all output
  and input sinks again.

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

2024-01-18 Thread Sergio Costas

For 23.10, as soon as version 45.1 enters, it will be fixed. For 22.04 I
prepared a SRU, but since it's a LTS version, it's a slow process.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

2024-01-18 Thread Sergio Costas

Yes, this can be considered as fixed. It was merged in upstream (gnome
46), and also backported to Gnome 45.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 2037604] Re: Backport packages for 22.04.4 HWE stack

2024-01-09 Thread Sergio Costas

Can somebody modify the description to specify exactly how to do those
tests, please? (which commands/parameters, and expected results).

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 1971168] Re: [snap] Files on local network shares are not opened / written

2024-01-08 Thread Sergio Costas

Ok, I think that the problem is that the bug report is in "firefox"
instead of "xdg-desktop-portal-gnome". I'll prepare a new bug report
there with the patch from Bas van den Heuvel. Sorry for the mistake.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 2048390] [NEW] Desktop icons doesn't support accessibility (specifically Orca)

Public bug reported:

[ Impact ]

Currently, the Desktop Icons NG (DING) extension included in Ubuntu
doesn't support integration with screen readers like Orca. This is a
disadvantage for visually impaired users.

Since DING is implemented as a classic GTK application, it should be
easy to wire it up to make use of the accessibility functions already
available thanks to the ATK library. A patch for that has been recently
uploaded to upstream, after a fix for this was requested by an user.

The patch takes advantage of the already implemented keyboard
navigation, and just makes these little changes:

* sets a readable accessible description for the Desktop Icons window
(because the application uses the invisible title bar to communicate
with the extension, thus it contains just "odd characters and numbers")

* sets an accessible description for each icon with the type and the
visible name of the file, and marks each icon as focusable

* when an icon is marked as selected, it gives the focus to it, thus
triggering the screen reader to read the accessible description

Also, the code for keyboard navigation is moved from the "key-press"
event to the "key-release" event, because that's the event used by the
accessibility subsystem, and not doing this results in an incorrect icon
being read by it.

[ Test plan ]

* Enable the Orca screen reader by pressing Mod+Alt+S. A voice will say
"Screen reader enabled" (or a similar, translated message).

* Click on the desktop to give the focus to it.

* Press the arrow keys to navigate with the keyboard through the icons.
Only one icon should be highlighted, and it should change when the
arrows are moved.

* After the test, the screen reader can be disabled by pressing the same
keys combination.

Expected results:

The screen reader should say the type and name of the selected icon,
every time the arrow keys are pressed to change the selected icon.

Current results:

The screen reader remains silent while navigating with the keyboard.

[ Where problems could occur ]

A change in the way GTK manages the focus could result in the keyboard
navigation to work incorrectly.

** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Importance: Undecided
Status: New

** Patch added: "Patch to add accessibility support"

https://bugs.launchpad.net/bugs/2048390/+attachment/5736866/+files/add-accessibility-support.diff

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

Title:
Desktop icons doesn't support accessibility (specifically Orca)

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

Bug description:
[ Impact ]

Currently, the Desktop Icons NG (DING) extension included in Ubuntu
doesn't support integration with screen readers like Orca. This is a
disadvantage for visually impaired users.

Since DING is implemented as a classic GTK application, it should be
easy to wire it up to make use of the accessibility functions already
available thanks to the ATK library. A patch for that has been
recently uploaded to upstream, after a fix for this was requested by
an user.

The patch takes advantage of the already implemented keyboard
navigation, and just makes these little changes:

* sets an accessible description for each icon with the type and the
visible name of the file, and marks each icon as focusable

* when an icon is marked as selected, it gives the focus to it, thus
triggering the screen reader to read the accessible description

[ Test plan ]

* Enable the Orca screen reader by pressing Mod+Alt+S. A voice will
say "Screen reader enabled" (or a similar, translated message).

* Click on the desktop to give the focus to it.

* Press the arrow keys to navigate with the keyboard through the
icons. Only one icon should be highlighted, and it should change when
the arrows are moved.

* After the test, the screen reader can be disabled by pressing the
same keys combination.

Expected results:

The screen reader should say the type and name of the selected icon,
every time the arrow keys are pressed to change the selected icon.

Current results:

The screen reader remains silent while navigating with the keyboard.

[ Where problems could occur ]

A change in the way GTK manages the focus could result in the keyboard
navigation to work incorrectly.

To manage notifications about

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

Oh, you mean if it will be backported to LTS! I'm not sure... I'll check
it.

(sorry, I read the numbers wrong and interpreted 24.04)

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 1968513] Re: GNOME login fails to stay in the overview if DING is enabled

After checking that extension, I think that I can use the same trick for
DING.

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

Title:
  GNOME login fails to stay in the overview if DING is enabled

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 (April 9 daily, latest)

  If you either disable the ubuntu-dock or remove it all together. On
  every login after that, the Activities window appears for just a few
  seconds. After those few seconds the Activities window automatically
  closes, which exposes the desktop.

  What I expected to happen is no Activity window to appear on login. I
  just want the desktop to appear, no dock, no Activities. More or less,
  I'm going for a "kiosk" type of desktop.

  Thanks for your time!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 10 19:42:00 2022
  InstallationDate: Installed on 2022-04-11 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/+bug/1968513/+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 1971168] Re: [snap] Files on local network shares are not opened / written

I have to check it, but probably the reason is that it still is using
the current version of gnome shell, so it won't be fixed until Gnome 46
is added to the repositories.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168] Re: [snap] Files on local network shares are not opened / written

Yes, it should, because the patch has been merged in upstream.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 2007702] Re: [SRU] Deb version numbering is misleading

2023-12-07 Thread Sergio Durigan Junior

While I see Julian's point, I believe it's better to stick to the same
versioning scheme used in the Firefox deb, which is exactly what you did
for Noble:

 firefox | 1:1snap1-0ubuntu2   | jammy   | source, amd64, 
arm64, armhf
 firefox | 1:1snap1-0ubuntu3   | lunar   | source, amd64, 
arm64, armhf
 firefox | 1:1snap1-0ubuntu3   | mantic  | source, amd64, 
arm64, armhf
 firefox | 1:1snap1-0ubuntu3   | noble   | source, amd64, 
arm64, armhf

As Athos said above, I'm not entirely sure how "SRU-able" this is, but
either way, I went ahead and uploaded the debdiffs (after a minor typo
fix).

I'm unsubscribing ubuntu-sponsors from this bug; feel free to
resubscribe it if needed.

Thanks!

** Changed in: chromium-browser (Ubuntu Focal)
   Status: New => In Progress

** Changed in: chromium-browser (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: chromium-browser (Ubuntu Lunar)
   Status: New => In Progress

** Changed in: chromium-browser (Ubuntu Mantic)
   Status: New => In Progress

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

Title:
  [SRU] Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Lunar:
  In Progress
Status in chromium-browser source package in Mantic:
  In Progress

Bug description:
  [Impact]
  For Ubuntu >= Focal the transitional debs are frozen at the version number 
1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [Test plan]

  Install the package and confirm the version change with e.g.

    dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'

  [Regression potential]

  If the version were incorrectly constructed the deb build could fail.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 2044654] Re: No debugging symbols found in libgdk-3.so.0

2023-11-28 Thread Sergio Durigan Junior

I've added ubuntu-debuginfod as an affected project and marked the bug
as Invalid for gtk-3.

BTW, this is a known issue that's being worked on.  Hopefully it should
be resolved in the next days.

Thanks for reporting the bug!

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  No debugging symbols found in libgdk-3.so.0

Status in ubuntu-debuginfod:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Attach gdb to a running yelp process!

  (gdb) share libgdk
  Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0...
  (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk-3-0 3.24.33-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16
  Uname: Linux 6.2.0-1016-azure x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 13:11:15 2023
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2023-11-22 Thread Sergio Costas

(In reply to Sergio Costas from comment #52)
> The patch has landed in upstream today.

I mean: it has been merged today.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

2023-11-22 Thread Sergio Costas

The patch has landed in upstream today.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168] Re: [snap] Files on local network shares are not opened / written

2023-11-21 Thread Sergio Costas

The patch has been merged, and also has been backported to GNOME 45, so
it is possible that it can make it to Mantic.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 2044156] [NEW] Firefox "window" freezes visuals after tiling

2023-11-21 Thread Sergio Schvezov

Public bug reported:

The firefox window view freezes, the window is actually still taking
input as I can press ctrl+L and type something in the address bar,
minimize and maximize to see the view _refreshed_.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell-extension-ubuntu-tiling-assistant 44-1ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
Uname: Linux 6.1.0-1025-oem x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 21 13:19:40 2023
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-20220504-33
InstallationDate: Installed on 2023-07-09 (136 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
PackageArchitecture: all
SourcePackage: gnome-shell-extension-tiling-assistant
UpgradeStatus: Upgraded to mantic on 2023-11-17 (5 days ago)

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


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

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

Title:
  Firefox "window" freezes visuals after tiling

Status in gnome-shell-extension-tiling-assistant package in Ubuntu:
  New

Bug description:
  The firefox window view freezes, the window is actually still taking
  input as I can press ctrl+L and type something in the address bar,
  minimize and maximize to see the view _refreshed_.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell-extension-ubuntu-tiling-assistant 44-1ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-1025.25-oem 6.1.57
  Uname: Linux 6.1.0-1025-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 13:19:40 2023
  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-20220504-33
  InstallationDate: Installed on 2023-07-09 (136 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - 
somerville-jammy-amd64-20220504-33
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-tiling-assistant
  UpgradeStatus: Upgraded to mantic on 2023-11-17 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2044156/+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 2038834] Re: GPU acceleration via VirGL is broken in qemu

2023-11-16 Thread Sergio Durigan Junior

Hello Mate,

I see that the debdiff you provided applies to Noble, but this bug is
also marked as affecting Mantic.  Could you provide an updated debdiff
for the Mantic version?  Thanks!

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

Title:
  GPU acceleration via VirGL is broken in qemu

Status in Release Notes for Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Mantic:
  New
Status in mesa source package in Noble:
  Fix Released

Bug description:
  
  [ Impact ] 
   * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs 

   * This was reported by someone else upstream and is already fixed by 
 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580.

  [ Test Plan ]

   * I've tested the patch on an affected macOS host running Ubuntu in UTM with 
 OpenGL enabled on both Mantic and Noble VMs.

   * Anyone else can do the same on an affected host by simply installing the 
 patched package and booting to the desktop.

  [ Where problems could occur ]

   * This patch fixes an upstream mesa regression which caused libvirglrendrer 
to 
 crash on the host side.

   * This makes a non-working use case work, VirGL on affected hosts cannot 
 regress as it simply didn't work before.

   * Risk of breakage is mainly from other packages possible affected by a mesa 
 rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 1798400]

2023-11-12 Thread Sergio Callegari

Noticed that in the forthcoming LibO 24.2, the "remote" is being given
prominence, by moving its settings from the Tools ▸ Options ▸
LibreOffice Impress configuration dialog to the Slide Show ▸ Slide Show
Settings menu.

IMHO this makes it quite important to have this feature working as
intended on all the supported platforms.

The remote is meant to work either with a WIFI connection or a Bluetooth
one.

The current bug is about the Bluetooth connection.

Bluetooth Connection


As of today, because of the issue at hand, the Bluetooth connection is
completely unusable on standard Linux distributions that use Pulseaudio
(a detailed discussion why is in the previous comments).

Notwithstanding the fact that this but is about the Bluetooth
connection, I am providing also a few notes about the Wifi connection to
highlight why the Bluetooth connection is so important and should be
fixed.

WIFI Connection
---

Unfortunately, the WIFI option is practically unusable in almost every
professional working environment, including universities and
conferencing sites. This is because in all these environments the
network is completely out of the user control, restricted in any
possible way, heavily firewalled, with the wifi framework consisting of
multiple access points under the same SSID. In a similar arrangement the
possibility of the remote to reach LibO at a non-standard TCP port is
erratic if not negligible.

The impossibility to use the WIFI connection precisely in those real
world environments where the usage of the remote would be most important
is the reason why a working Bluetooth connection is needed.

Note that in practice the WIFI connection situation could be improved by
suggesting the possibility to let the presenter laptop connect to the
internet via the mobile phone hotspot. This would need the remote app to
try to connect to LibO not just via the phone default interface, but
also on the network used for the hotspot.

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

Title:
  [upstream] Regression: cannot use impress remote over bluetooth with
  ubuntu bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

2023-11-09 Thread Sergio Costas

The patch for xdg-desktop-portal-gnome is continuing its way towards
being mainlined: https://gitlab.gnome.org/GNOME/xdg-desktop-portal-
gnome/-/merge_requests/67

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

2023-10-18 Thread Sergio Costas

That's right. I'm working on landing this on upstream. As commented, the
problem is in xdg-desktop-portal-gnome.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 2039475] Re: Desktop icons in Mantic doesn't honor dock margins

2023-10-16 Thread Sergio Costas

This patch fixes the problem.

** Patch added: "patch.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2039475/+attachment/5709973/+files/patch.diff

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

Title:
  Desktop icons in Mantic doesn't honor dock margins

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

Bug description:
  The port to Gnome Shell 45 of Desktop Icons had a bug that prevents it
  from honoring the Dock size when in "IntelliHide" mode, thus allowing
  to put icons under it. This bug has been fixed in upstream, so it
  should be ported to Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2039475/+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 2039475] [NEW] Desktop icons in Mantic doesn't honor dock margins

2023-10-16 Thread Sergio Costas

Public bug reported:

The port to Gnome Shell 45 of Desktop Icons had a bug that prevents it
from honoring the Dock size when in "IntelliHide" mode, thus allowing to
put icons under it. This bug has been fixed in upstream, so it should be
ported to Mantic.

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

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

Title:
  Desktop icons in Mantic doesn't honor dock margins

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

Bug description:
  The port to Gnome Shell 45 of Desktop Icons had a bug that prevents it
  from honoring the Dock size when in "IntelliHide" mode, thus allowing
  to put icons under it. This bug has been fixed in upstream, so it
  should be ported to Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/2039475/+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 2035228] Re: ruby-gsl dep8 fails on ppc64el

2023-09-12 Thread Sergio Durigan Junior

I built a version of gsl using -O2 instead of -O3 on ppc64el and
confirmed that the problem went away.

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

Title:
  ruby-gsl dep8 fails on ppc64el

Status in gsl package in Ubuntu:
  In Progress

Bug description:
  With the latest update of gsl from Debian, ruby-gsl's dep8 test start
  failing on ppc64el:

  421s 
===
  421s Failure: test_random32_bsd_0(RngTest):
  421s   random32-bsd, 1 steps (852261210 observed vs 1663114331 expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.007176)
  421s test_random32_glibc2_0:  .: (0.001215)
  421s test_random32_libc5_0:   F
  421s 
===
  421s Failure: test_random32_libc5_0(RngTest):
  421s   random32-libc5, 1 steps (367802360 observed vs 1967452027 
expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002615)
  421s test_random64_bsd_0: F
  421s 
===
  421s Failure: test_random64_bsd_0(RngTest):
  421s   random64-bsd, 1 steps (210970120 observed vs 864469165 expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002551)
  421s test_random64_glibc2_0:  .: (0.001151)
  421s test_random64_libc5_0:   F
  421s 
===
  421s Failure: test_random64_libc5_0(RngTest):
  421s   random64-libc5, 1 steps (221021662 observed vs 2106639801 
expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002627)

  This looks like a precision problem caused by excessive optimization
  in the architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsl/+bug/2035228/+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 2035228] [NEW] ruby-gsl dep8 fails on ppc64el

2023-09-12 Thread Sergio Durigan Junior

Public bug reported:

With the latest update of gsl from Debian, ruby-gsl's dep8 test start
failing on ppc64el:

421s 
===
421s Failure: test_random32_bsd_0(RngTest):
421s   random32-bsd, 1 steps (852261210 observed vs 1663114331 expected).
421sis not true.
421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block (3 
levels) in '
421s 
===
421s : (0.007176)
421s test_random32_glibc2_0:.: (0.001215)
421s test_random32_libc5_0: F
421s 
===
421s Failure: test_random32_libc5_0(RngTest):
421s   random32-libc5, 1 steps (367802360 observed vs 1967452027 expected).
421sis not true.
421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block (3 
levels) in '
421s 
===
421s : (0.002615)
421s test_random64_bsd_0:   F
421s 
===
421s Failure: test_random64_bsd_0(RngTest):
421s   random64-bsd, 1 steps (210970120 observed vs 864469165 expected).
421sis not true.
421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block (3 
levels) in '
421s 
===
421s : (0.002551)
421s test_random64_glibc2_0:.: (0.001151)
421s test_random64_libc5_0: F
421s 
===
421s Failure: test_random64_libc5_0(RngTest):
421s   random64-libc5, 1 steps (221021662 observed vs 2106639801 expected).
421sis not true.
421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block (3 
levels) in '
421s 
===
421s : (0.002627)

This looks like a precision problem caused by excessive optimization in
the architecture.

** Affects: gsl (Ubuntu)
 Importance: High
 Assignee: Sergio Durigan Junior (sergiodj)
 Status: In Progress


** Tags: update-excuse

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

Title:
  ruby-gsl dep8 fails on ppc64el

Status in gsl package in Ubuntu:
  In Progress

Bug description:
  With the latest update of gsl from Debian, ruby-gsl's dep8 test start
  failing on ppc64el:

  421s 
===
  421s Failure: test_random32_bsd_0(RngTest):
  421s   random32-bsd, 1 steps (852261210 observed vs 1663114331 expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.007176)
  421s test_random32_glibc2_0:  .: (0.001215)
  421s test_random32_libc5_0:   F
  421s 
===
  421s Failure: test_random32_libc5_0(RngTest):
  421s   random32-libc5, 1 steps (367802360 observed vs 1967452027 
expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002615)
  421s test_random64_bsd_0: F
  421s 
===
  421s Failure: test_random64_bsd_0(RngTest):
  421s   random64-bsd, 1 steps (210970120 observed vs 864469165 expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002551)
  421s test_random64_glibc2_0:  .: (0.001151)
  421s test_random64_libc5_0:   F
  421s 
===
  421s Failure: test_random64_libc5_0(RngTest):
  421s   random64-libc5, 1 steps (221021662 observed vs 2106639801 
expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002627)

  This looks like a precision problem caused by excess

[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written

2023-07-18 Thread Sergio Costas

** Description changed:

+ Impact:
+ 
+ When the user is running a containerized application (like the snapped
+ Firefox or Chromium), and tries to save a document, the xdg-desktop-
+ portal-gnome backend does show remote drives (like SMB or SFTP ones),
+ and allows to choose them, but then the save operation fails.
+ 
+ The previous backend, xdg-desktop-portal-gtk, did work fine in these
+ cases, because it returned the local path that corresponded to the local
+ file exported by Gvfs using FUSE, so this behaviour is not only a
+ serious bug, but also a regression.
+ 
+ [ Test plan]
  Steps to reproduce:
  
  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share
  
  Actual behavior:
  
  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown
  
  Expected behavior:
  
  * File is saved to selected network share location
  * No error is shown
  
- Additional information:
+ [ Where problems could occur ]
+ 
+ - If the remote drives aren't exported as local files by Gvfs using
+ FUSE, the patch won't work and the behaviour will be the same than now.
+ 
+ - Any hidden  bug in g_file_get_path() when managing remote drives could
+ be triggered by this patch.
+ 
+ [ Additional information ]
  
  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

** Description changed:

- Impact:
+ [ Impact ]
  
  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.
  
  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the local
  file exported by Gvfs using FUSE, so this behaviour is not only a
  serious bug, but also a regression.
  
  [ Test plan]
  Steps to reproduce:
  
  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share
  
  Actual behavior:
  
  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown
  
  Expected behavior:
  
  * File is saved to selected network share location
  * No error is shown
  
  [ Where problems could occur ]
  
  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than now.
  
  - Any hidden  bug in g_file_get_path() when managing remote drives could
  be triggered by this patch.
  
  [ Additional information ]
  
  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox packag

[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list

2023-07-13 Thread Sergio Durigan Junior

I'm unsubscribing Ubuntu Sponsors.

** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
   Status: Confirmed => In Progress

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

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  In Progress
Status in ubuntu-drivers-common source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
    "branch": "510",
    "features": [
  "runtimepm"
    ]
  }
    ]
  }
  ```
  5. make sure the hook works
  ```
  $ ubuntu-drivers list
  nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta

  [ Where problems could occur ]

   * This feature only impact target system has a custom file
  "/etc/custom_supported_gpus.json". And it won't generate automatically
  which should not impact normal users

  [ Other Info ]

   * the patches are picked from
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
   * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list

2023-07-13 Thread Sergio Durigan Junior

Hello Dirk,

I took the liberty to fix a nit in the changelog entry:

 18[ Jeremy Szu ]   

   
 19* README, README.md, 

   
 20  UbuntuDrivers/detect.py,   

   
 21  tests/test_ubuntu_drivers.py:  

   
 22  - Let OEM images locally extend the NVIDIA driver  

   
 23supported PCI IDs for cutting edge silicons by specifying

   
 24related information in /etc/custom_supported_gpus.json file. 

   
 25(LP: #1990341)   

   
 26  - Fix pkg.candidate.record retired from apt_pkg library

   
 27  - Support autopkgtest for force install Nvidia and update  

   
 28related section in README.   

   

I changed the "- Let OEM..." sentence, and made sure that "LP" is
uppercase.

Otherwise I believe everything has been properly addressed so I'm
uploading this package:

$ dput ubuntu-drivers-common_0.9.6.2~0.22.04.5_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: 
/home/sergio/work/ubuntu-drivers-common/ubuntu-drivers-common_0.9.6.2~0.22.04.5_source.changes:
 Valid signature from 106DA1C8C3CBBF14
Checking signature on .dsc
gpg: 
/home/sergio/work/ubuntu-drivers-common/ubuntu-drivers-common_0.9.6.2~0.22.04.5.dsc:
 Valid signature from 106DA1C8C3CBBF14
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading ubuntu-drivers-common_0.9.6.2~0.22.04.5.dsc: done.
  Uploading ubuntu-drivers-common_0.9.6.2~0.22.04.5.tar.xz: done.  
  Uploading ubuntu-drivers-common_0.9.6.2~0.22.04.5_source.buildinfo: done. 
  Uploading ubuntu-drivers-common_0.9.6.2~0.22.04.5_source.changes: done.
Successfully uploaded packages.

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

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  In Progress
Status in ubuntu-drivers-common source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features&q

[Desktop-packages] [Bug 2024064] [NEW] libssh dep8 fails on ppc64el/s390x

2023-06-15 Thread Sergio Durigan Junior

Public bug reported:

Reporting this bug for documentation purposes.  libssh's dep8 test is
failing on ppc64el/s390x.

I tried reproducing it in a ppc64el canonistack box, but the test always
passes there.  migration-reference/0 didn't help.

It's interesting to notice that the test succeeds on debci, which leads
me to believe that this is something really particular to our
autopkgtest infra.

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


** Tags: update-excuse

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

Title:
  libssh dep8 fails on ppc64el/s390x

Status in libssh package in Ubuntu:
  New

Bug description:
  Reporting this bug for documentation purposes.  libssh's dep8 test is
  failing on ppc64el/s390x.

  I tried reproducing it in a ppc64el canonistack box, but the test
  always passes there.  migration-reference/0 didn't help.

  It's interesting to notice that the test succeeds on debci, which
  leads me to believe that this is something really particular to our
  autopkgtest infra.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/2024064/+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 1990444] Re: firefox snap took 20 minutes to update

2023-06-07 Thread Sergio Cazzolato

I tried to reproduce breaking the connection to the snap store but the
issue was not reproduced.

Please, in case it happens again, 
 . run the 
https://github.com/snapcore/snapd/blob/master/debug-tools/snap-debug-info.sh if 
that happens again
 . provide the output of snap change ` with that update's ID


** Changed in: snapd
   Status: New => Incomplete

** Changed in: snapd
   Importance: Undecided => Medium

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

Title:
  firefox snap took 20 minutes to update

Status in snapd:
  Incomplete
Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I logged and firefox was unavailable, no indication of update, nothing.
  When I tried to launch firefox I was invited to install it BUT I klnow it's 
installed, so I tried to install it but it said to me I needed to 'snap 
refresh', I tried to snap refresh but it indicated that everything was up to 
date. I tried to uninstall/reinstall the firefox snap and at this moment, 
  I got the indication that the update was in progress since 15 MINUTES ! Then 
I tried to remove the snap because I was sure it's bugged : in 20.04 firefox 
never took more than 2 mins to update and my machine BUT after 20 minutes 
firefox launched... wtf ?

  I'm an ubuntu user since circa 2005 and I believe firefox was already
  the default browser then, this is the worse user experience I've ever
  had.

  1/ I never selected auto-update, let me update when I want : being blocked 15 
MINUTES by the OS is not a good user experience, I know this is accepted by 
Windows users but I prefer to use Ubuntu
  2/ If you want to update tell me you're updating not that the application is 
not installed : really not a good idea if you want your users to trust you

  I've waited 6 months after 22.04 release to migrate from 20.04 because
  I don't want to have this kind of bugs, I hope you do something really
  quick because this is not at the level of quality expected by your
  users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1990444/+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 1790608] Re: [snap] Libreoffice/Firefox do not open files from thunderbird (more general: from /tmp)

2023-05-15 Thread Sergio Cazzolato

** Changed in: snapd
   Status: New => Confirmed

** Changed in: snapd
   Importance: Undecided => Medium

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

Title:
  [snap] Libreoffice/Firefox do not open files from thunderbird (more
  general: from /tmp)

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

Bug description:
  I received a document via e-mail in Thunderbird. I have the
  Libreoffice snap package installed. When I want to open the document
  from Thunderbird, I see the Libreoffice splash screen, and then a
  dialog stating "/tmp/mozilla_0/.docx does not exist."

  The same dialog appears when I navigate to the folder in Files and
  want to open it.

  When I copy the file to my desktop, however, I can open it without
  problems.

  I guess the source of the issue is confinement, that the Libreoffice
  snap can only access files from $HOME. But this breaks the case where
  thunderbird creates a temporary copy in /tmp.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1790608/+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 1971168]

2023-04-11 Thread Sergio Costas

The patch is sent, but it seems that there were some changes in the
maintainers of xdg-desktop-portal-gnome, so I suspect that it will need
some time until it is merged upstream... :-(

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

(In reply to Alexandre LISSY :gerard-majax from comment #44)
> Sergio, I applied the patch locally on `xdg-desktop-portal-gnome` package, 
> and it is fixing the issue.

Thanks!

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

> > Have you tested the new patch?

> Sorry, I was on leave, is testing the patch still required ?

It would be great if you can test it. In fact, I've been working on it
yesterday and today, doing some changes requested by Bastien.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

I discovered a simpler way of fixing this. I sent this patch for XDG-
desktop-portal-gnome. https://gitlab.gnome.org/GNOME/xdg-desktop-portal-
gnome/-/merge_requests/67

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

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

(In reply to Alexandre LISSY :gerard-majax [PTO 12/12/2022-28/02/2023] from 
comment #38)
> (In reply to tc from comment #37)
> > What's the overview of this ? It seems like it would solve a problem of 
> > "can't save there" in a general way ? 
> > 
> 
> Still blocked on upstream ...

Have you tested the new patch?

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 2008919] [NEW] [FFe] Implement support for "buttercup_eval"

2023-03-01 Thread Sergio Durigan Junior

Public bug reported:

dh-elpa supports the "ert_eval" directive inside d/elpa-test, which
allows the package to provide custom Elisp code to be executed before
ERT is invoked.  Unfortunately, a similar feature is missing for
buttercup tests.  This means that, whenever a package uses buttercup to
run its tests, the maintainer needs to override dh_elpa_test and invoke
buttercup by hand.  This, however, only works during build time; dh-elpa
is also used to run autopkgtest, and in that specific scenario it's not
possible to execute custom Elisp code using buttercup at all.

Why is this important, you might ask.  Well, I've been investigating a
bug in Emacs 28.2's native compilation mechanism which affects a bunch
of packages (see bug #2006963 for more details).  One of those affected
packages is flycheck, which uses buttercup.  I uploaded a fix for a
flycheck FTBFS which addresses the problem, but the package still fails
its autopkgtest because of the problem mentioned above.

Long story short, I've implemented the support for a new dh-elpa
directive called "buttercup_eval" and would like it to Lunar.  I also
proposed the feature to Debian here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1032202

** Affects: dh-elpa (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: dh-elpa (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: dh-elpa (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032202
   Importance: Unknown
   Status: Unknown

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

Title:
  [FFe] Implement support for "buttercup_eval"

Status in dh-elpa package in Ubuntu:
  New
Status in dh-elpa package in Debian:
  Unknown

Bug description:
  dh-elpa supports the "ert_eval" directive inside d/elpa-test, which
  allows the package to provide custom Elisp code to be executed before
  ERT is invoked.  Unfortunately, a similar feature is missing for
  buttercup tests.  This means that, whenever a package uses buttercup
  to run its tests, the maintainer needs to override dh_elpa_test and
  invoke buttercup by hand.  This, however, only works during build
  time; dh-elpa is also used to run autopkgtest, and in that specific
  scenario it's not possible to execute custom Elisp code using
  buttercup at all.

  Why is this important, you might ask.  Well, I've been investigating a
  bug in Emacs 28.2's native compilation mechanism which affects a bunch
  of packages (see bug #2006963 for more details).  One of those
  affected packages is flycheck, which uses buttercup.  I uploaded a fix
  for a flycheck FTBFS which addresses the problem, but the package
  still fails its autopkgtest because of the problem mentioned above.

  Long story short, I've implemented the support for a new dh-elpa
  directive called "buttercup_eval" and would like it to Lunar.  I also
  proposed the feature to Debian here: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1032202

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-elpa/+bug/2008919/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share

2023-02-22 Thread Sergio Costas

I found something odd... Setting KRB5CCNAME in /etc/environment does
work, but setting "default_ccache_name" in /etc/krb5.conf doesn't. In
theory, when KRB5CCNAME isn't set, kerberos should use that value for
the cache file. And although the command line tools do use it, it seems
that gvfsd doesn't...

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

Title:
  Nautilus does not use a valid Kerberos ticket when accessing Samba
  share

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Nautilus prompts for username and password when accessing a Samba
  share on a network drive, despite having a perfectly valid unexpired
  Kerberos ticket. The Kerberos ticket is obtained automatically at
  logon by authentication against a Samba Active Directory server (Samba
  AD-DC).

  Accessing the same Samba share with the same Kerberos ticket via
  "smbclient //host/sharename -k" works fine.

  One known workaround is: "nautilus -q", and then "killall gvfsd".
  After that, accessing the Samba share with Nautilus works normally as
  it should.

  I did not experience this issue in Ubuntu 16.04. It appears that a
  regression was introduced somewhere between 16.04 and 18.04.

  The issue is quite annoying and confusing for the users who are used
  to accessing Samba shares on the network drive without being prompted
  for their username and password.

  The issue appears to manifest itself usually not on the first access
  to a Samba share, but on subsequent accesses after a system reboot or
  upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry
  file before user login appears to fix the issue for the current user
  session, but then the problem reappears upon subsequent user logins or
  after a system reboot.

  Nemo appears to have the same problem as Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-daemons 1.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul  3 11:12:06 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd
  InstallationDate: Installed on 2018-04-27 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANG=en_CA.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share

2023-02-17 Thread Sergio Costas

If you try my line, be sure to create the folder ~/kerberos before, so
maybe a better alternative would be the line

KRB5CCNAME=${HOME}/.config/krb5cc_${LOGNAME}

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

Title:
  Nautilus does not use a valid Kerberos ticket when accessing Samba
  share

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Nautilus prompts for username and password when accessing a Samba
  share on a network drive, despite having a perfectly valid unexpired
  Kerberos ticket. The Kerberos ticket is obtained automatically at
  logon by authentication against a Samba Active Directory server (Samba
  AD-DC).

  Accessing the same Samba share with the same Kerberos ticket via
  "smbclient //host/sharename -k" works fine.

  One known workaround is: "nautilus -q", and then "killall gvfsd".
  After that, accessing the Samba share with Nautilus works normally as
  it should.

  I did not experience this issue in Ubuntu 16.04. It appears that a
  regression was introduced somewhere between 16.04 and 18.04.

  The issue is quite annoying and confusing for the users who are used
  to accessing Samba shares on the network drive without being prompted
  for their username and password.

  The issue appears to manifest itself usually not on the first access
  to a Samba share, but on subsequent accesses after a system reboot or
  upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry
  file before user login appears to fix the issue for the current user
  session, but then the problem reappears upon subsequent user logins or
  after a system reboot.

  Nemo appears to have the same problem as Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-daemons 1.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul  3 11:12:06 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd
  InstallationDate: Installed on 2018-04-27 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANG=en_CA.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1779890/+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 1779890] Re: Nautilus does not use a valid Kerberos ticket when accessing Samba share

2023-02-17 Thread Sergio Costas

I found a workaround for this: to define the KRB5CCNAME environment
variable at /etc/environment.d/91kerberos.conf

In my case, I store the cache file at ~/kerberos, so I set the content
of that file to:

KRB5CCNAME=${HOME}/kerberos/krb5cc_${LOGNAME}

So, if my username is "username", this results in the environment
variable set to

/home/username/kerberos/krb5cc_username

After doing this, the tickets are preserved between reboots.

Can anybody test this to ensure that it fixes the problem, please?

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

Title:
  Nautilus does not use a valid Kerberos ticket when accessing Samba
  share

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Nautilus prompts for username and password when accessing a Samba
  share on a network drive, despite having a perfectly valid unexpired
  Kerberos ticket. The Kerberos ticket is obtained automatically at
  logon by authentication against a Samba Active Directory server (Samba
  AD-DC).

  Accessing the same Samba share with the same Kerberos ticket via
  "smbclient //host/sharename -k" works fine.

  One known workaround is: "nautilus -q", and then "killall gvfsd".
  After that, accessing the Samba share with Nautilus works normally as
  it should.

  I did not experience this issue in Ubuntu 16.04. It appears that a
  regression was introduced somewhere between 16.04 and 18.04.

  The issue is quite annoying and confusing for the users who are used
  to accessing Samba shares on the network drive without being prompted
  for their username and password.

  The issue appears to manifest itself usually not on the first access
  to a Samba share, but on subsequent accesses after a system reboot or
  upon user logout/login. Strangely, removing ~/.cache/ibus/bus/registry
  file before user login appears to fix the issue for the current user
  session, but then the problem reappears upon subsequent user logins or
  after a system reboot.

  Nemo appears to have the same problem as Nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-daemons 1.36.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul  3 11:12:06 2018
  ExecutablePath: /usr/lib/gvfs/gvfsd
  InstallationDate: Installed on 2018-04-27 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANG=en_CA.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1779890/+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 2006674] Re: GTK-3.0 themes not working with 22.04

2023-02-09 Thread Sergio Durigan Junior

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

** No longer affects: sssd (Ubuntu)

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

Title:
  GTK-3.0 themes not working with 22.04

Status in gtk4 package in Ubuntu:
  New

Bug description:
  I am trying to migrate my customized theme on ubuntu 22.04 , but it is not 
taking effect .
  I read through different portals and found that in 22.04 themes are migrated 
to gtk-4.0 and there should be a folder present with the name gtk-4.0 inside 
the theme.

  I tried migrating my gtk-3.0 to gtk-4.0 but still not able to apply
  the theme .

  Can you please help me out are their any specific steps which needs to
  be done for migrating my customized theme.

  
  I am trying to change the color of the dialog which comes if we are closing 
any unsaved file from red to blue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2006674/+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 1855711] Re: Add keyboard navigation to desktop icons

2023-01-31 Thread Sergio Costas

This is fixed in the upstream version; as soon as it's ported to Ubuntu,
it will work.

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

Title:
  Add keyboard navigation to desktop icons

Status in gnome-shell-extension-desktop-icons:
  New
Status in Gnome Shell Extension Desktop Icons Ng:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Pressing tab does not allow the user to select UI elements. If tab is
  pressed "Activities" should be selected. Left or right arrow to select
  items on Activities bar. If tab is pressed again, select top icon on
  Dock. Press down arrow to navigate down the dock. Press enter to start
  app. If tab is pressed instead of enter, Desktop icons should be
  selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1855711/+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 2003104] Re: gnome-terminal transparency ignored in full screen mode

2023-01-18 Thread Sergio Costas

Yes, it is. I tested it in a VM, and can reproduce it.

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

Title:
  gnome-terminal transparency ignored in full screen mode

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003104/+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 2003104] Re: Transparency ignored in full screen mode

2023-01-18 Thread Sergio Costas

It's not random, at least in my system. Also, the tricks in that bug
report don't work: I tried changing the transparency value, disabling
and enabling again, but no dice.

If I had to bet, I would say that the problem is in the fullscreen
redirection to avoid composition overload with games... but I don't know
if Wayland has that...

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

Title:
Transparency ignored in full screen mode

Status in gnome-terminal package in Ubuntu:
Confirmed

Bug description:
Ubuntu 23.04 running wayland
gnome-terminal 3.46.7-1ubuntu1

In gnome-terminal, I have set the transparency to some amount. When I
go to full screen (F11), the transparency is lost and the default
transparency is used. When I exit full screen, the transparency comes
back and I can see in the profile settings that the transparency has
not changed.

It seems that tranparency was accidentally removed, and then re-added via

https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

However, maybe something was missed with regards to full screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+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 2003104] Re: Transparency ignored in full screen mode

2023-01-18 Thread Sergio Costas

Confirmed that this happens when libmutter/mutter-common are updated to
version 11.

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

Title:
  Transparency ignored in full screen mode

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 23.04 running wayland
  gnome-terminal 3.46.7-1ubuntu1

  In gnome-terminal, I have set the transparency to some amount. When I
  go to full screen (F11), the transparency is lost and the default
  transparency is used. When I exit full screen, the transparency comes
  back and I can see in the profile settings that the transparency has
  not changed.

  It seems that tranparency was accidentally removed, and then re-added via
  
https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

  However, maybe something was missed with regards to full screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+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 2003104] Re: Transparency ignored in full screen mode

2023-01-17 Thread Sergio Costas

Installing a fresh install of Lunar, everything works fine. Updating
Gtk3, LibVTE, Cairo and other libraries doesn't make it fail. But doing
a dist-upgrade makes it fail like described.

There is no new version neither of Gnome Terminal, nor of Gnome Shell,
so it doesn't seem a problem there.

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

Title:
Transparency ignored in full screen mode

Status in gnome-terminal package in Ubuntu:
New

Bug description:
Ubuntu 23.04 running wayland
gnome-terminal 3.46.7-1ubuntu1

It seems that tranparency was accidentally removed, and then re-added via

https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel

However, maybe something was missed with regards to full screen.

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

[Desktop-packages] [Bug 1798400]

2023-01-12 Thread Sergio Callegari

Noticed that among the many tips of the day, LibO also suggests to use
Android or IPhone to remotely control an Impress presentation.  The
"more info" page then excplicitly declares that the feature is cross
platform "GNU/Linux, Windows or macOS." either via Bluetooth or Wifi.

However to use the feature with bluetooth on linux has been impossible
for the last 5 years, because the feature is broken on this platform
(this bug provides a diagnosis of the underlying issue). Using the
feature with wifi is equally problematic, because those places where you
need to deliver a presentation are typically those very places where you
do not control the wifi network that may make it impossible for the
computer and the phone to communicate.

As a consequence, this tip of the day looks inappropriate on linux,
making many users waste a significant amount of time trying to use a
feature that simply cannot work. May I suggest removing this tip of the
day on linux?

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

Title:
  [upstream] Regression: cannot use impress remote over bluetooth with
  ubuntu bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

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


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

[Desktop-packages] [Bug 1994141] Re: incompatible versions of network-manager-openvpn and openvpn delivered in ubuntu22.10

2022-10-31 Thread Sergio Durigan Junior

Thank you for your bug report.  This seems to be a problem with network-
manager-openvpn, so I took the liberty to remove Ubuntu and the openvpn
package from the list of affected projects.  I also pinged the person
that backported the upstream fixes to Kinetic.

** No longer affects: ubuntu

** No longer affects: openvpn (Ubuntu)

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

Title:
  incompatible versions of network-manager-openvpn and openvpn delivered
  in ubuntu22.10

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

Bug description:
  After installing  network-manager-openvpn(1.10.0-1ubuntu2),
  openvpn(2.6.0~git20220818-1ubuntu1) is installed as a dependency.

  Mentioned NM plugin uses openvpn option `--cipher` instead of `--data-
  ciphers`. With openvpn2.6.0+ this breaks existing setups - connection
  never establishes and fails with message like:

  ```
  DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in 
--data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores 
--cipher for cipher negotiations.
  ```
  and
  ```
  Connection reset, restarting [0]
  ```

  reproducer: configure openVPN client against openVPN server with
  cipher set to 'AES-256-CBC'.

  workaround: manually install openvpn 2.5.x from sources and mask
  distribution-provided openvpn 2.6.x.

  proposed solution:

  deliver compatible combination of network-manager-openvpn and openvpn.

  
  system info:
  Description:Ubuntu 22.10
  Release:22.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1994141/+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 1995196] [NEW] package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote bluez, o script post-installation retornou erro do status de saída 1

2022-10-30 Thread Sergio Schvezov

Public bug reported:

From a release upgrade from 22.04 to 22.10

(many moons ago) I had previously enabled pipewire on the 22.04 install
with the following:

sudo apt install pipewire-audio-client-libraries libspa-0.2-bluetooth 
libspa-0.2-jack
sudo apt install wireplumber pipewire-media-session-
sudo apt remove pulseaudio-module-bluetooth
systemctl --user --now enable wireplumber.service

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: bluez 5.65-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Oct 28 07:09:19 2022
ErrorMessage: o subprocesso instalado, do pacote bluez, o script 
post-installation retornou erro do status de saída 1
InstallationDate: Installed on 2022-10-19 (9 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20V9
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.9ubuntu1
 apt  2.5.3
SourcePackage: bluez
Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso 
instalado, do pacote bluez, o script post-installation retornou erro do status 
de saída 1
UpgradeStatus: Upgraded to kinetic on 2022-10-28 (0 days ago)
dmi.bios.date: 05/10/2022
dmi.bios.release: 1.50
dmi.bios.vendor: LENOVO
dmi.bios.version: F9CN50WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: ThinkBook 13s G2 ITL
dmi.ec.firmware.release: 1.44
dmi.modalias: 
dmi:bvnLENOVO:bvrF9CN50WW:bd05/10/2022:br1.50:efr1.44:svnLENOVO:pn20V9:pvrThinkBook13sG2ITL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrThinkBook13sG2ITL:skuLENOVO_MT_20V9_BU_idea_FM_ThinkBook13sG2ITL:
dmi.product.family: ThinkBook 13s G2 ITL
dmi.product.name: 20V9
dmi.product.sku: LENOVO_MT_20V9_BU_idea_FM_ThinkBook 13s G2 ITL
dmi.product.version: ThinkBook 13s G2 ITL
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 64:79:F0:9D:09:A8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:21280 acl:17 sco:0 events:3348 errors:0
TX bytes:816597 acl:17 sco:0 commands:3319 errors:0

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


** Tags: amd64 apport-package kinetic

** Attachment added: "bt journal"
   https://bugs.launchpad.net/bugs/1995196/+attachment/5627802/+files/bt.log

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

Title:
  package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso
  instalado, do pacote bluez, o script post-installation retornou erro
  do status de saída 1

Status in bluez package in Ubuntu:
  New

Bug description:
  From a release upgrade from 22.04 to 22.10

  (many moons ago) I had previously enabled pipewire on the 22.04
  install with the following:

  sudo apt install pipewire-audio-client-libraries libspa-0.2-bluetooth 
libspa-0.2-jack
  sudo apt install wireplumber pipewire-media-session-
  sudo apt remove pulseaudio-module-bluetooth
  systemctl --user --now enable wireplumber.service

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: bluez 5.65-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Oct 28 07:09:19 2022
  ErrorMessage: o subprocesso instalado, do pacote bluez, o script 
post-installation retornou erro do status de saída 1
  InstallationDate: Installed on 2022-10-19 (9 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20V9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-52-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: bluez
  Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: o subprocesso 
instalado, do pacote bluez, o script post-installation retornou erro do status 
de saída 1
  UpgradeSta

[Desktop-packages] [Bug 1989587] [NEW] Cannot print to autodiscovered printers

2022-09-14 Thread Sergio Callegari

Public bug reported:

I have issues when trying to print on autodiscovered printers.

In some cases, cups reports a "permission denied".

In other cases, the local queue is not created at all, so that it is
impossible to print.

However, these printers do appear in the kde print dialog for
applications like okular, etc.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups-browsed 1.28.15-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Sep 14 15:53:59 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-02-16 (941 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/VG_NVMe-root ro quiet splash zswap.enabled=1 vt.handoff=7
SourcePackage: cups-filters
UpgradeStatus: Upgraded to jammy on 2022-06-03 (103 days ago)
dmi.bios.date: 10/02/2019
dmi.bios.release: 7.4
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.04RTR1
dmi.board.asset.tag: Tag 12345
dmi.board.name: N141CU
dmi.board.vendor: SCHENKER
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.2
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: SCHENKER_SLIM14_SSL14L19
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: SCHENKER
modified.conffile..etc.cups.cups-browsed.conf: [modified]
mtime.conffile..etc.cups.cups-browsed.conf: 2022-09-14T15:52:48.888330

** Affects: cups-filters (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 cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1989587

Title:
  Cannot print to autodiscovered printers

Status in cups-filters package in Ubuntu:
  New

Bug description:
  I have issues when trying to print on autodiscovered printers.

  In some cases, cups reports a "permission denied".

  In other cases, the local queue is not created at all, so that it is
  impossible to print.

  However, these printers do appear in the kde print dialog for
  applications like okular, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups-browsed 1.28.15-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Sep 14 15:53:59 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (941 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/VG_NVMe-root ro quiet splash zswap.enabled=1 vt.handoff=7
  SourcePackage: cups-filters
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (103 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER
  modified.conffile..etc.cups.cups-browsed.conf: [modified]
  mtime.conffile..etc.cups.cups-browsed.conf: 2022-09-14T15:52:48.888330

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1989587/+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 1855711] Re: Add keyboard navigation to desktop icons

2022-09-06 Thread Sergio Costas

Oh... :-(

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

Title:
  Add keyboard navigation to desktop icons

Status in gnome-shell-extension-desktop-icons:
  New
Status in Gnome Shell Extension Desktop Icons Ng:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed

Bug description:
  Pressing tab does not allow the user to select UI elements. If tab is
  pressed "Activities" should be selected. Left or right arrow to select
  items on Activities bar. If tab is pressed again, select top icon on
  Dock. Press down arrow to navigate down the dock. Press enter to start
  app. If tab is pressed instead of enter, Desktop icons should be
  selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1855711/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding

2022-08-04 Thread Sergio Schvezov

Snapcraft 7.1.1 is now on the stable channel

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  0. If you have Nvidia GPU, you need Snapcraft >=7.1.1. Check `snap
  info snapcraft`. At the time of writing,

 sudo snap refresh --channel 7.x/beta snapcraft

  1. Install the Chromium snap,

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
    - If failed, the video used for testing, including codec and resolution if 
possible;
  - Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
  - Distro version (`grep VERSION= /etc/os_release`);
  - GPU (`lscpu`);
  - CPU generation (`lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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

2022-07-25 Thread Sergio Costas

Sorry for the delay. We are ATM working on trying to find a solution for
that review.

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox / Chromium
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  Additional information:

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 1979079] [NEW] Can print to (brother) driverless printer only using aa-complain cupsd

2022-06-17 Thread Sergio Callegari

Public bug reported:

The apparmor configuration for cupsd is incorrect and makes it
impossible to print to driverless printers (at least to the brother
printer I am trying). Cups cannot obtain the IP address of the printer.

You get "No suitable Destination Host found by cups-browsed"

There are multiple reports of this issue on the network, also wrt
debian.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups-daemon 2.4.1op1-1ubuntu4.1
ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
Uname: Linux 5.15.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Jun 17 18:19:32 2022
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-02-16 (852 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-06-03 (14 days ago)
dmi.bios.date: 10/02/2019
dmi.bios.release: 7.4
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.04RTR1
dmi.board.asset.tag: Tag 12345
dmi.board.name: N141CU
dmi.board.vendor: SCHENKER
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.2
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: SCHENKER_SLIM14_SSL14L19
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: SCHENKER

** Affects: cups (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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1979079

Title:
  Can print to (brother) driverless printer only using aa-complain cupsd

Status in cups package in Ubuntu:
  New

Bug description:
  The apparmor configuration for cupsd is incorrect and makes it
  impossible to print to driverless printers (at least to the brother
  printer I am trying). Cups cannot obtain the IP address of the
  printer.

  You get "No suitable Destination Host found by cups-browsed"

  There are multiple reports of this issue on the network, also wrt
  debian.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups-daemon 2.4.1op1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Jun 17 18:19:32 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (852 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SCHENKER SCHENKER_SLIM14_SSL14L19
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/VG_NVMe-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (14 days ago)
  dmi.bios.date: 10/02/2019
  dmi.bios.release: 7.4
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.04RTR1
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N141CU
  dmi.board.vendor: SCHENKER
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.04RTR1:bd10/02/2019:br7.4:efr7.2:svnSCHENKER:pnSCHENKER_SLIM14_SSL14L19:pvrNotApplicable:rvnSCHENKER:rnN141CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: SCHENKER_SLIM14_SSL14L19
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SCHENKER

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1979079/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2022-06-14 Thread Sergio Durigan Junior

This has been fixed since sssd 2.4.0.

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

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  In Progress
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Fix Released
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Fix Released
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Incomplete
Status in zsh package in Debian:
  Confirmed

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

2022-06-11 Thread Sergio Callegari

Is 2:2.10-6ubuntu2 the same as 2:2.10-9ubuntu1 in #76?

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Fix Committed
Status in wpa package in Debian:
  New

Bug description:
  * Impact
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  * Test case
  try to connect to a TLS <= 1.1 access point

  * Regression potential
  the patch lowers the security level in some situation for compatibility, it 
shouldn't prevent connecting to newer hardware, still try to connect to 
different type of wifi with different security levels

  ---

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1978331] [NEW] DING shows several errors when no monitor is attached

2022-06-10 Thread Sergio Costas

Public bug reported:

Recent version of gnome shell or extension has been emitting large
numbers of identical, or quote similar, entries in the system journal,
when the monitor is turned off or physically disconnected.

The error is: DING: (gjs:10210): Gdk-CRITICAL **: 09:58:45.854:
gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)'
failed

** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  DING shows several errors when no monitor is attached

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

Bug description:
  Recent version of gnome shell or extension has been emitting large
  numbers of identical, or quote similar, entries in the system journal,
  when the monitor is turned off or physically disconnected.

  The error is: DING: (gjs:10210): Gdk-CRITICAL **: 09:58:45.854:
  gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)'
  failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1978331/+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 1978330] [NEW] Extension does odd things when other extension is disabled

2022-06-10 Thread Sergio Costas

Public bug reported:

When an extension that was enabled before DING is disabled, the desktop
with the icons stops behaving like a desktop, and instead they behave
like a transparent window that can be over other windows, be moved by
pressing the "Windows" key, and so on.

** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
 Importance: Undecided
 Assignee: Sergio Costas (rastersoft-gmail)
 Status: New

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

Title:
  Extension does odd things when other extension is disabled

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

Bug description:
  When an extension that was enabled before DING is disabled, the
  desktop with the icons stops behaving like a desktop, and instead they
  behave like a transparent window that can be over other windows, be
  moved by pressing the "Windows" key, and so on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1978330/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

2022-06-03 Thread Sergio Callegari

#76 works here too

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1974040] Re: Cannot connect to PEAP wifi (eduroam)

2022-06-03 Thread Sergio Callegari

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

Same issue here:

the updated 2:2.10-6ubuntu1 version of wpasupplicant still gives

wpa_supplicant[33522]: SSL: SSL3 alert: write (local SSL3 detected an 
error):fatal:internal error
wpa_supplicant[33522]: OpenSSL: openssl_handshake - SSL_connect 
error:0A0C0103:SSL routines::internal error
wpa_supplicant[33522]: wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed

Similarly, the workarounds in comments #22 and #36 in bug #1958267 do
not work

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

Title:
  Cannot connect to PEAP wifi (eduroam)

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Connection to wifi fails with

  May 18 15:08:55 attila wpa_supplicant[9698]: OpenSSL:
  openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal
  error

  
  Description:Ubuntu 22.04 LTS
  Release:22.04


  wpasupplicant:
Installed: 2:2.10-6ubuntu1
Candidate: 2:2.10-6ubuntu1
Version table:
   *** 2:2.10-6ubuntu1 1 (phased 40%)
  500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:2.10-6 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-6ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed May 18 15:13:41 2022
  InstallationDate: Installed on 2019-10-22 (938 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1974040/+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 1886322] Re: Unable to move all selected files on desktop

2022-04-21 Thread Sergio Costas

This should be already fixed. Can we close this?

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

Title:
  Unable to move all selected files on desktop

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  This bug started to happen like 1-2 months ago, and as I remember I
  didn't do any customizations like installing any external plugins and
  etc, but I have some stuff already like custom icons, shell, theme...
  but it worked normaly before.

  What is happening is that when I select more than 1 file on desktop,
  no matter which file it is (folder, .txt, image.. anything), and when
  I try to move around desktop from one place to another, it will move
  only 1 file and not the rest. So, unable to move selected files on
  desktop (drag and drop using cursor's rectangle). Its simple issue, no
  need for video or screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  5 14:18:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 
/ R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB 
GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221]
  InstallationDate: Installed on 2020-03-24 (103 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: MSI MS-7693
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G46 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  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 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1886322/+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 1798400]

2022-03-19 Thread Sergio Callegari

The bug is still there as of LibO 7.3.x. Up in comment 12
(https://bugs.documentfoundation.org/show_bug.cgi?id=120663#c12) there
is a nice analysis of the underlying problem why the remote cannot work.

Established that, I think that most users go used to the fact that the
remote functionality does not work in linux. Personally, I have
uninstalled the android app on the phone so I do not have an unfortunate
reminder about it. In fact, the real issue is probably the advertisement
of a functionality that is not there.

For the time being I suggest disabling the remote-via-bluetooth
functionality in linux and closing the bug by simply saying that the
remote via bluetooth cannot be supported on linux where there are
evidently issues that span other software pieces such as the bluetooth
stack and pulse audio. To the best of my understanding, these involve
the hijacking of the default rfcomm channel by pulse audio before it
even needs it and the lack of a standard approach to let other
applications find a free channel to use and advertise it to their
counterparts.

Alternatively (but I would not consider this a good solution), the
configuration options could be enhanced to add the possibility to choose
a bluetooth channel in libreoffice and in the mobile phone application,
so that the user can manually work around the fact that the predefined
channel is locked by some other application.

As a final point, note that even if the remote-via-wifi may seem a good
alternative, in fact in most cases it is practically useless.  In most
cases, presentations will not be given at a place where you control the
network, but at sites with site-provided wifi, such as universities,
schools, conference places, business sites, etc. All these locations
tend to have wifi deployments that block stuff on the ports used by
impress remote.

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

Title:
  [upstream] Regression: cannot use impress remote over bluetooth with
  ubuntu bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.versi

[Desktop-packages] [Bug 1965113] Re: Desktop snaps don't start at all in Xorg sessions if a Wayland session has been used

2022-03-18 Thread Sergio Schvezov

Is there a better way to detect a wayland session?

** Changed in: snapcraft
   Status: New => Incomplete

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

Title:
  Desktop snaps don't start at all in Xorg sessions if a Wayland session
  has been used

Status in gnome-session:
  Unknown
Status in Snapcraft:
  Incomplete
Status in gnome-session package in Ubuntu:
  Triaged

Bug description:
  Firefox 98.0.1-2 snap doesn't start at all in Xorg sessions.

  $ /snap/bin/firefox
  Error: cannot open display: :0

  $ echo $DISPLAY
  :0

  And other X11 apps still work just fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1965113/+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 1964418] Re: firefox just circles jig 2022-03-09

2022-03-18 Thread Sergio Schvezov

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

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

Title:
  firefox just circles jig 2022-03-09

Status in Snapcraft:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  2022-03-09-firefox-snapshot-cmd.txt

This file is saved with "windoz" file endings so it can be read by any 
computer. I was running Thunderbird downloading my e-mails when I had one 
e-mail to renew a magazine subscription which loads an HTML file to fill out my 
information for renewal. At this point Firefox locked up and was just doing 
it's little circle jig! After several minutes there appeared an empty message 
box (probably to say  that Firefox was not responding!), but it was empty!
After pulling the plug, and restarting Ubuntu 21.10 64-bit Desktop on 
my Raspberry Pi 400 computer I tried to start Firefox again and 20 minutes 
later it was still doing it's little circle jig. At this time I opened the 
System Monitor and looked at the fluctuating CPU cores with one usually reading 
0%, another 1%, another around 10%, and the fourth around 25%, with all of the 
cores swapping in and out, none were static.
I am really not impressed with "Snaps"! It appears to me to be nothing 
more than "Microsoft Spaghetti Code"! When I tried to load "Geany" the snap 
version was over 100 MB and would not even run. When I loaded it with "sudo apt 
install geany" I ended up getting two 1 MB files and that program has run 
flawlessly! I have been having a lot of trouble with "Firefox" snap locking up 
and even just quitting at any random point, with it being around 160 MB. The 
normal apt version is only 56 MB and runs smoothly! Again, I am not impressed 
with "SNAPS"!

  I am going to post: 2022-03-09-firefox-snapshot-cmd.txt,
  2022-03-09-firefox-snapshot as well as 2022-03-09-firefox-snap.zip
  which will contain both and want to download. My internet connection
  is only 2 Mb/sec down and 1 Mb/sec up so the maximum speed will
  probably max out around 125 kB/sec. My web site is
  http://162.250.19.7/ and will come up with a green screen and a
  directory listing. I am now running my site with "thttpd" from
  Acme.com, which used to be the number 7 web server software, on a
  Raspberry Pi 4B with 4 GB RAM and a 128 GB micro-SD card, using the
  new Raspberry Pi 64-bit OS. I found the 2 GB file limit size that
  would be served was caused by using a 32-bit OS, (2**31 =
  2,147,483,647 or 7fff). Using a 64-bit OS I have tested files up
  to 5 GB and have had no problems with them not showing up on the
  internet. This software is bullet proof out of the box because it is
  using a read-only file system but can do CGI programs by adding the
  CGI information. The "cut and paste" directions for building this site
  are under: http://162.250.19.7/ in "Freedom/" and in "freedom.zip"
  which I need to redo for the 64-bit Raspberry Pi OS.

  So anybody can access these files I am posting them to:
  http://162.250.19.7/ with the files being: 2022-03-09-firefox-
  snapshot-cmd.txt, 2022-03-09-firefox-snapshot, and 2022-03-09-firefox-
  snapshot.zip.

  For more information about a command, run 'snap help '.
  frank@frank-desktop:~$ snap saved
  No snapshots found.
  frank@frank-desktop:~$ snap refresh
  All snaps up to date.
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ snap changes
  ID   Status  Spawn   Ready   Summary
  10   Doneyesterday at 10:54 MST  yesterday at 10:58 MST  Auto-refresh 
snap "firefox"
  11   Donetoday at 09:33 MST  today at 09:33 MST  Refresh all 
snaps: no updates

  frank@frank-desktop:~$ snap get
  error: the required argument `` was not provided
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ snap get firefox
  error: access denied (try with sudo)
  frank@frank-desktop:~$ sudo snap get firefox
  [sudo] password for frank: 
  error: snap "firefox" has no configuration
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ snap save firefox
  Set  Snap AgeVersion  Rev   SizeNotes
  1firefox  2m52s  98.0-3   1083   943MB  -
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ snap help export-snapshot
  Usage:
snap export-snapshot  

  Export a snapshot to the given filename.

  [export-snapshot command arguments]
:   Set id of snapshot to export
: The filename of the export
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ 
  frank@frank-desktop:~$ snap export-snapshot 1 ~/2022-03-09-firefox-snapshot
  error: unexpected status code: 401 Unauthorized
  frank@frank-desktop:~$ sudo snap export-snapshot 1 
~/2022-03-09-firefox-snapshot
  Exported snapshot #1 into "/home/frank/2022-03-09-

[Desktop-packages] [Bug 1965545] [NEW] Cannot present on Google Meet

2022-03-18 Thread Sergio Schvezov

Public bug reported:

Steps to reproduce:
- Open https://meet.google.com and join a meeting
- Click on present and select "A tab"

Expected result:
- list of tabs to share from is shown

Actual result:
- The present icon grays out
- no list of tabs shown

Output from chromium while running:
[1042818:1042818:0318/114624.826544:ERROR:service_worker_task_queue.cc(213)] 
DidStartWorkerFail nkeimhogjdpnpccoofpliimaahmaaome: 5
...
[1042818:1042818:0318/114633.590229:ERROR:service_worker_task_queue.cc(213)] 
DidStartWorkerFail nkeimhogjdpnpccoofpliimaahmaaome: 5

Addtional information:
➜  ~ snap list chromium 
Nome  VersãoRev   A seguir   Editor  Notas
chromium  99.0.4844.51  1926  latest/stable  canonical✓  -
➜  ~ snap version
snap2.54.4
snapd   2.54.4
series  16
ubuntu  22.04
kernel  5.15.0-22-generic
➜  ~ cat /etc/os-release 
PRETTY_NAME="Ubuntu Jammy Jellyfish (development branch)"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
UBUNTU_CODENAME=jammy "&scope=" (url-hexify-string 
org-gcal-resource-url)))

** 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/1965545

Title:
  Cannot present on Google Meet

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  - Open https://meet.google.com and join a meeting
  - Click on present and select "A tab"

  Expected result:
  - list of tabs to share from is shown

  Actual result:
  - The present icon grays out
  - no list of tabs shown

  Output from chromium while running:
  [1042818:1042818:0318/114624.826544:ERROR:service_worker_task_queue.cc(213)] 
DidStartWorkerFail nkeimhogjdpnpccoofpliimaahmaaome: 5
  ...
  [1042818:1042818:0318/114633.590229:ERROR:service_worker_task_queue.cc(213)] 
DidStartWorkerFail nkeimhogjdpnpccoofpliimaahmaaome: 5

  Addtional information:
  ➜  ~ snap list chromium 
  Nome  VersãoRev   A seguir   Editor  Notas
  chromium  99.0.4844.51  1926  latest/stable  canonical✓  -
  ➜  ~ snap version
  snap2.54.4
  snapd   2.54.4
  series  16
  ubuntu  22.04
  kernel  5.15.0-22-generic
  ➜  ~ cat /etc/os-release 
  PRETTY_NAME="Ubuntu Jammy Jellyfish (development branch)"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  UBUNTU_CODENAME=jammy "&scope=" (url-hexify-string 
org-gcal-resource-url)))

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1965545/+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 1798400] Re: [upstream] Regression: cannot use impress remote over bluetooth with ubuntu bionic

2022-03-18 Thread Sergio Callegari

Bug still there. In most situations the remote cannot be used at all.
Not via bluetooth (because of this issue), neither via wifi (because you
typically do presentations at sites where you do not control the wifi
network and traffic to the relevant ports gets blocked). Suggested
upstream some possible solutions including stop advertising the
functionality. Consider closing as Wontfix because I think there is
really nothing that downstream can do about it.

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

Title:
  [upstream] Regression: cannot use impress remote over bluetooth with
  ubuntu bionic

Status in LibreOffice:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+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 1962389] Re: Sync upower 0.99.16-2 (main) from Debian unstable (main)

2022-02-27 Thread Sergio Durigan Junior

This bug was fixed in the package upower - 0.99.16-2
Sponsored for Rik Mills (rikmills)

---
upower (0.99.16-2) unstable; urgency=medium

  * Cherry-pick FD handling fixes from upstream (Closes: #1006368)

 -- Michael Biebl   Sat, 26 Feb 2022 10:43:19 +0100

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

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

Title:
  Sync upower 0.99.16-2 (main) from Debian unstable (main)

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  Please sync upower 0.99.16-2 (main) from Debian unstable (main)

  Changelog entries since current jammy version 0.99.16-1:

  upower (0.99.16-2) unstable; urgency=medium

* Cherry-pick FD handling fixes from upstream (Closes: #1006368)

   -- Michael Biebl   Sat, 26 Feb 2022 10:43:19 +0100

  As per https://gitlab.freedesktop.org/upower/upower/-/issues/174

  this should fix KDE not registering and acting on laptop lid closure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1962389/+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 1927071] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)

2021-12-20 Thread Sergio Zanchetta

I confirm this bug. It happens using desktop installer iso system (I
don't have any connectivity issue).

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

Title:
   Fresh install of chromium-browser during installer-like process, in a
  chroot fails (when preparing machines prior to first boot)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Here is the first bug report :
  https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1882232

  It seems that there is a regression, pre-installation script of apt
  installed chromium-browser package doesn't detect that it is running
  in a chroot anymore.

  => Installing the chromium snap
  ==> Checking connectivity with the snap store
  ===> Unable to contact the store, trying every minute for the next 30 
minutes
  ===> Still unable to contact the store, trying for another 20 minutes
  ===> Still unable to contact the store, trying for another 10 minutes
  ===> Still unable to contact the store, aborting
  dpkg: error processing archive 
/var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb
 (--unpack):
   new chromium-browser package pre-installation script subprocess returned 
error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927071/+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 1767431] Re: restore type-ahead find, again

2021-11-26 Thread Sergio

I really miss the old behaviour. When I want to search I press ctrl+F
like most applications. Please bring back the old behaviour.

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

Title:
  restore type-ahead find, again

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  The dropping of the type-ahead find patch in 17.10 might deeply affect
  non-technical users, as pointed out, this is possibly a bad HCI
  design. As there is a patch exists from the Arch community[1], and the
  at least some people managed to patch it in 17.10[2], might it be
  possible to add such patch back before 18.04.1 so that it won't affect
  people upgraded from 16.04?

  [1]: https://aur.archlinux.org/nautilus-typeahead.git
  [2]: https://askubuntu.com/a/1002521

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767431/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-11-24 Thread Sergio Durigan Junior

** Tags removed: server-todo

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Fix Released
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil

2021-11-10 Thread Sergio Durigan Junior

hplip has also built successfully:

https://launchpad.net/ubuntu/+source/hplip/3.21.8+dfsg0-2

So I'm marking this bug as Fix Released for it.

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

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

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Status in hplip package in Ubuntu:
  Fix Released
Status in ssl-cert package in Ubuntu:
  Fix Released
Status in ssl-cert package in Debian:
  Fix Released

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

  Package: openssl
  Version: 3.0.0~~alpha16-1
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: piuparts

  Hi,

  during a test with piuparts I noticed your package causes other package
  to fail installation/upgrading.

  From the attached log (scroll to the bottom...):

  ...
Setting up openssl (3.0.0~~alpha16-1) ...
Setting up libbsd0:amd64 (0.11.3-1) ...
Setting up readline-common (8.1-2) ...
Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ...
Setting up libgdbm6:amd64 (1.19-2) ...
Setting up postgresql-client-common (226) ...
Setting up libedit2:amd64 (3.1-20210522-1~exp1) ...
Setting up libreadline8:amd64 (8.1-2) ...
Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ...
Setting up libllvm11:amd64 (1:11.0.1-2) ...
Setting up ssl-cert (1.1.0+nmu1) ...
Could not create certificate. Openssl output was:
Generating a RSA private key

..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+

..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+
Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
-
Warning: No -copy_extensions given; ignoring any extensions in the request
Cannot write random bytes:
8022CB35777F:error:127A:random number generator:RAND_write_file:Not 
a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
dpkg: error processing package ssl-cert (--configure):
 installed ssl-cert package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of postgresql-common:
 postgresql-common depends on ssl-cert (>= 1.0.11); however:
  Package ssl-cert is not configured yet.
  ...

  Hmm, well, yes, /dev/urandom is not a regular file. It's a character
  device node.

  
  cheers,

  Andreas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945774/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-10-14 Thread Sergio Durigan Junior

MR for the Debian postfix package also submitted:

https://salsa.debian.org/postfix-team/postfix-dev/-/merge_requests/13

** Changed in: postfix (Ubuntu)
   Status: New => Triaged

** Changed in: postfix (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Triaged
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-10-13 Thread Sergio Durigan Junior

I've also submitted a Merge Request against the Debian clamav package:

https://salsa.debian.org/clamav-team/clamav/-/merge_requests/4

Hopefully it will be accepted & merged into Ubuntu soon. If not, I will
submit an MP to add this change as a delta to our package.

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-10-13 Thread Sergio Durigan Junior

FWIW, I submitted a Merge Request against the Debian nss-pam-ldapd here:

https://salsa.debian.org/debian/nss-pam-ldapd/-/merge_requests/2

Hopefully it will be accepted & merged into Ubuntu soon.  If not, I will
submit an MP to add this change as a delta to our package.

** Changed in: nss-pam-ldapd (Ubuntu)
   Status: New => Triaged

** Changed in: nss-pam-ldapd (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: https:/

[Desktop-packages] [Bug 1945713] Re: Flaky test brotli/basic on focal amd64?

2021-10-06 Thread Sergio Durigan Junior

I spent some time trying to get to the bottom of the issue, but
unfortunately I was not able to make much progress here.

As expected, the very first thing to do here is to reproduce the bug
locally.  I tried many things:

- I built the package locally and ran autopkgtest against it.  Passed.

- I built the package inside a Focal LXD container and then ran
autopkgtest there.  Passed.

- Still inside the Focal LXD container, I tried to invoke the failing
test manually.  Passed.

- I know that Ubuntu's autopkgtest infra uses a Bionic host to run the
tests.  I created a Bionic VM, and inside it I git cloned the
development version of autopkgtest.  Then, I invoked autopkgtest against
the Focal source package for libsoup2.4, using a Focal LXD container as
the testbed.  Passed.

I ran out of ideas on what to try locally, and given that Bryce was able
to add a hint for the failure and unblock apache2, I am giving up (at
least for now).  The way I see it, a person interested in continuing
debugging this could:

- Add debugging statements to the libsoup2.4 code, upload the modified
package to a PPA, and run autopkgtests using the Ubuntu infra.  This
should be able to provide more useful information regarding the array
manipulation that's happening in the test.

- If the above doesn't work, one could try to add debugging statements
to the libglib code that's responsible for array manipulations.


Lastly, it's important to mention that this may very well be something 
unrelated to libsoup2.4/glib.  It can even be a hardware issue, who knows...

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

Title:
  Flaky test brotli/basic on focal amd64?

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  The brotli/basic test case periodically fails.  It appears that a few
  retriggers can result in a pass:

  https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

  The failures look like this in autopkgtest logs:

  ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
  assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
  "***\n")

  I've replaced most of the text with '***' to highlight the difference
  is a 'U' character appended.

  The test case is essentially doing a decompression of 'brotli-
  data/compressed.br' and comparing that it matches 'brotli-
  data/uncompressed.txt'.  I've done this manually using the brotli cli,
  and the files do indeed have the same content.  I've also built the
  package and run the test case locally in a focal lxc container on
  amd64:

  $ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
  $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

  I left that to run several hundred cycles but no failures reported at
  all.

  There are a bunch of instances of this failure, here's a few for
  reference:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

  That last link is the earliest instance I've been able to find.

  You'll notice in the second two links they also have a failure "not ok
  2 /ssl/tls-interaction", but the first link shows only the brotli
  failure.

  Interestingly, I've not found instances of this failure against other
  architectures than amd64, nor have I seen it on releases other than
  focal.  No dice from googling for bug reports or other reports of test
  failures with libsoup2.4 + brotli.

  The test's code is doing this, basically:

  SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
  do {
  result = g_converter_convert (G_CONVERTER (dec), in_buf, 
length, out_buf, sizeof out_buf, 0,
&bytes_read, &bytes_written, 
&error);
  g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
  length -= bytes_read;

  } while (result == G_CONVERTER_CONVERTED);

  soup_brotli_decompressor's code is here:

  https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
  decoder/soup-brotli-decompressor.c

  But I'm not spotting anything that would obviously cause a 'U' to be
  randomly appended sometimes.  And why 'U'?  UINT? Unknown? User error?

  There are some interesting bug reports in GNOME about brotli in
  libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
  match this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+subscriptions


-- 
Mailing list: https

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-10-06 Thread Sergio Durigan Junior

** Changed in: clamav (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1883174] Re: Some (or all) desktop icons are missing

2021-09-14 Thread Sergio Costas

I think that the only solution is to uninstall Desktop Icons and install
Desktop Icons NG. Although current versions are for Gnome Shell 3.38 and
later, there are active versions in extensions.gnome.org that do work
with Gnome Shell 3.36.

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

Title:
  Some (or all) desktop icons are missing

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  OS: Ubuntu 20.04
  GNOME: 3.36.2
  Extension: 3.36.2

  Sometimes, some icons in my Desktop folder just don't appear on the
  desktop. The missing icons aren't invisible, it's like they're not in
  the folder. Clicking on the empty space where they should be does
  nothing. Mousing over the empty space does nothing. See attached
  screenshot. As you can see, there are many missing.

  Not consistently reproducible, but frequent.

  This isn't great info, I know. Let me know what else I can provide.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+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 1939916] Re: FTBFS 0.99.25-0ubuntu1 error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=]

2021-08-13 Thread Sergio Durigan Junior

Thanks for the investigative work, Athos.

As we discussed in private, I'm going to do a sync of sane-airscan from
Debian experimental, which contains the patch necessary for this fix.
The sync should also close this bug.

Cheers.

** Changed in: sane-airscan (Ubuntu)
   Status: New => Fix Released

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

Title:
  FTBFS 0.99.25-0ubuntu1 error: ‘__builtin_memcpy’ writing 5 bytes into
  a region of size 0 overflows the destination [-Werror=stringop-
  overflow=]

Status in sane-airscan package in Ubuntu:
  Fix Released

Bug description:
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html

  https://launchpadlibrarian.net/552666330/buildlog_ubuntu-impish-
  amd64.sane-airscan_0.99.25-0ubuntu1_BUILDING.txt.gz

  In function ‘strcpy’,
  inlined from ‘trace_open’ at airscan-trace.c:113:5:
  /usr/include/x86_64-linux-gnu/bits/string_fortified.h:79:10: error: 
‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the 
destination [-Werror=stringop-overflow=]
 79 |   return __builtin___strcpy_chk (__dest, __src, __glibc_objsize 
(__dest));
|  ^
  lto1: all warnings being treated as errors
  make[2]: *** [/tmp/ccRt7B21.mk:2: /tmp/cc0DKpF3.ltrans0.ltrans.o] Error 1
  lto-wrapper: fatal error: make returned 2 exit status
  compilation terminated.
  /usr/bin/ld: error: lto-wrapper failed
  collect2: error: ld returned 1 exit status
  make[1]: *** [Makefile:167: test-zeroconf] Error 1

  Upstream patch is available at https://github.com/alexpevzner/sane-
  airscan/commit/0b9be6d0c5cce6f8717eae51c218d4e8f967e79b

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

Re: [Desktop-packages] [Bug 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-13 Thread Sergio Durigan Junior

On Friday, August 13 2021, Graham Inggs wrote:

> libvpx was added to the '# packages not in main:' section.
>
> Please only use lto-disabled-list for packages not in main. Packages in
> main should either be fixed or worked around in the package itself.

Sorry about that.  doko had pinged me about this mistake as well.  I
have removed libvpx from lto-disabled-list and uploaded the package
again.  I will fix the issue on libvpx.

Thanks,

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

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

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  Fix Released

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

Thanks for the review, Lucas.

Uploaded:

$ dput lto-disabled-list_15_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /home/sergio/work/lto-disabled-list/lto-disabled-list_15_source.changes: 
Valid signature from 106DA1C8C3CBBF14
Checking signature on .dsc
gpg: /home/sergio/work/lto-disabled-list/lto-disabled-list_15.dsc: Valid 
signature from 106DA1C8C3CBBF14
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading lto-disabled-list_15.dsc: done.
  Uploading lto-disabled-list_15.tar.xz: done.  
  Uploading lto-disabled-list_15_source.buildinfo: done.
  Uploading lto-disabled-list_15_source.changes: done.
Successfully uploaded packages.

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

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

Actually, I *can* reproduce the bug using git HEAD.  As it turns out I
was using an incomplete set of build flags that didn't trigger the
problem.  So yeah, the problem is still present in git HEAD.

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

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

Good point, Oibaf.  I've just tested git HEAD and verified that the bug
seems to have been fixed there, indeed.  I commented on the bug report.
Thanks.

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

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

I have filed an upstream bug report:

https://bugs.chromium.org/p/webm/issues/detail?id=1736

Unfortunately it seems like a Google account is needed in order to
view/comment on it.

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

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

This patch adds libvpx to the lto-disabled-list package, thus working
around the problem and disabling LTO for libvpx.

** Patch added: "fix-ftbfs-libvpx-lto.patch"
   
https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1939640/+attachment/5517532/+files/fix-ftbfs-libvpx-lto.patch

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

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled