from:"Athos Ribeiro"

[Desktop-packages] [Bug 1993356] Re: udisks doesn't make sense from cdrom

2023-07-03 Thread Athos Ribeiro

No progress in the upstream bug so far.

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

Title:
  udisks doesn't make sense from cdrom

Status in udisks:
  Unknown
Status in qemu package in Ubuntu:
  Triaged
Status in udisks2 package in Ubuntu:
  Triaged

Bug description:
  udisks doesn't make sense from cdrom

  there are journal errors from sending ATA command IDENTIFY, maybe
  incomplete kernel or qemu support?

To manage notifications about this bug go to:
https://bugs.launchpad.net/udisks/+bug/1993356/+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 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution

2023-07-07 Thread Athos Ribeiro

Thanks, Dirk.

I wonder why only the jammy debdiff contains the second patch. Is it
applied in the other series (kk and ll) already?

Also, as per the SRU guidelines in
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template, regarding
the "[ Where problems could occur ]" section,

>  * This must '''never''' be "None" or "Low", or entirely an argument as to why
   your upload is low risk.

Describing where problems could occur and how they would manifest is a
nice way to show to the SRU team that we did consider possible unwanted
outcomes for the SRU and that we'd be ready to address them in case they
do occur. It also helps people testing the SRU, guiding them on what to
look for when checking for regressions.

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

Title:
  gnome-control-center crashed when switching to mirror mode and
  monitors don't have matched resolution

Status in OEM Priority Project:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  gnome-control-center crashed when switching to mirror mode and monitors don't 
have matched resolution

  [Test case]
  1. Connected monitors to system which don't have same resolution.
  2. Switch to mirror mode through gnome-control-center
  3. gnome-control-center won't crash

  [Where problems could occur]
  It only modified the code related to mirror mode in Displays panel. And won't 
affect other part. The risk will be low.

  [Other info]
  Two Merge Request are related
  1. Check best_mode exist before adding flag 
(https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835)
  2. Use virtual clone modes when mirroring  
(https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2026228/+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-11-22 Thread Athos Ribeiro

Thanks, Nathan.

Would you mind filing the SRU paperwork as per the template at
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ?

I am unsure if this would be suitable for an SRU, but that's for the SRU
team to assess and decide.

Moreover, I see that you are using the same version for all the proposed
patches. If you check item 4.1 in
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure, it states that,
for SRUs, the version number should not conflict with any later and
future version in other Ubuntu releases.

Could you please fix the version numbers for each release? Check the
versions in jammy and focal for an example of how this could be done.

-- 
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:
  New
Status in chromium-browser source package in Jammy:
  New
Status in chromium-browser source package in Lunar:
  New
Status in chromium-browser source package in Mantic:
  New

Bug description:
  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 2062377] Re: Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

2024-04-19 Thread Athos Ribeiro

Attaching a screenshot of what I am looking at when using DMZ-black

** Attachment added: "noble-cursor.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2062377/+attachment/5768211/+files/noble-cursor.jpg

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

Title:
  Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1)Go to xorg
  2)Download Gnome Tweak Tool
  3)Select DMZ-white
  4)crash from the system

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 
22:55:48 UTC 2024
   GCC version:
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:38:02 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2024-04-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  MachineType: Acer Aspire A715-42G
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2062377/+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 2062377] Re: Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

2024-04-19 Thread Athos Ribeiro

FWIW, I am also affected in wayland, all packages up-to-date. Changing
the cursor to adwaita fixes it for me was in DMZ-black).

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

Title:
  Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  1)Go to xorg
  2)Download Gnome Tweak Tool
  3)Select DMZ-white
  4)crash from the system

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.161.07  Sat Feb 17 
22:55:48 UTC 2024
   GCC version:
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:38:02 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2024-04-17 (1 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2)
  MachineType: Acer Aspire A715-42G
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic 
root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2062377/+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 2056760] Re: [snap]Thunderbird doesn't authenticate with sssd-kcm

2024-04-24 Thread Athos Ribeiro

Marking the sssd tracker as invalid then.

** Tags removed: server-traige-discuss

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

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

Title:
  [snap]Thunderbird doesn't authenticate with sssd-kcm

Status in sssd package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  New

Bug description:
  I have Kerberos authentication set up in Thunderbird for my mailbox.

  My environment contains:

  helga@helga-rashomon:~$ env | grep KRB
  KRB5CCNAME=KCM:

  This means that Kerberos authentication should work through the sssd-
  kcm server.

  I initialize Kerberos and verify that it functions correctly:

  helga@helga-rashomon:~$ klist
  Ticket cache: KCM:1000
  Default principal: he...@example.org

  Valid starting  Expires Service principal
  03/11/24 04:14:24   03/12/24 04:14:24   krbtgt/example@example.org
  03/11/24 04:15:24   03/12/24 04:14:24   HTTP/redmine.example.org@
  Ticket server: HTTP/redmine.example@example.org

  (listing redacted to say example.org instead of the real address. the
  redmine listing shows that Firefox works correctly with this address)

  However, when I open the Snap Thunderbird, it does not recognize this
  Kerberos setup, showing me "The Kerberos/GSSAPI ticket was not
  accepted by the IMAP server". klist -A likewise shows no changes.

  The exact same setup works when I specify KRB5CCNAME=DIR:${HOME}/krb5cc in 
.profile instead.
  The sssd-kcm setup also works in Thunderbird native and Flatpak profiles.

  Considering the Flatpak specifically permits access to
  /run/.heim_org.h5l.kcm-socket, could it be that the Thunderbird Snap
  is not allowed to access this socket?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2056760/+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 2075138] Re: net usershare » a retourné l'erreur 255 net usershare add: share name /home/path/file/contains invalid characters (any of %<>*?|/\+=;:",)

2024-08-06 Thread Athos Ribeiro

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

This seems to be a regression after samba 4.15 was introduced in focal.
This same issue was found and fixed in jammy in LP: #1967245.

I will mark this as a duplicate of the other one and target that to
focal as well.

** Also affects: nautilus-share (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: nautilus-share (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** This bug has been marked a duplicate of bug 1967245
   'net usershare' returned error 255 on jammy-desktop-amd64

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

Title:
  net usershare » a retourné l'erreur 255 net usershare add: share name
  /home/path/file/contains invalid characters (any of %<>*?|/\+=;:",)

Status in nautilus-share package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Invalid
Status in nautilus-share source package in Focal:
  New
Status in samba source package in Focal:
  Invalid

Bug description:
  unable to share a folder with nautilus. I have an error: "net usershare" 
returned error 255: [2024/07/30 01:35:10, 0] 
../../lib/util/debug.c:1100(reopen_one_log)
  reopen_one_log: Unable to open new log file 'toto/log.net': No such file or 
folder
  net usershare add: share name /home/olivier/documents/toto contains invalid 
characters (any of %<>*?|/\+=;:",)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/2075138/+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 1967245] Re: 'net usershare' returned error 255 on jammy-desktop-amd64

2024-08-06 Thread Athos Ribeiro

As described in LP: #2075138, this now affects focal as well.

It seems that samba 4.15.x was introduced to focal due to some needed
security updates, which caused a regressing in nautilus-share. It seems
all we need here is to backport the patch introduced in jammy into
focal.

** Changed in: nautilus-share (Ubuntu Focal)
   Status: Confirmed => Triaged

** Tags removed: jammy
** Tags added: server-todo

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

Title:
  'net usershare' returned error 255 on jammy-desktop-amd64

Status in nautilus-share package in Ubuntu:
  Fix Released
Status in nautilus-share source package in Focal:
  Triaged

Bug description:
  jammy-desktop-amd64.iso 2022-03-26 08:25

  'net usershare' returned error 255: net usershare add: cannot convert
  name "Everyone" to a SID. Access denied.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1967245/+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 1967245] Re: 'net usershare' returned error 255 on jammy-desktop-amd64

2024-08-06 Thread Athos Ribeiro

** Also affects: nautilus-share (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  'net usershare' returned error 255 on jammy-desktop-amd64

Status in nautilus-share package in Ubuntu:
  Fix Released
Status in nautilus-share source package in Focal:
  Triaged

Bug description:
  jammy-desktop-amd64.iso 2022-03-26 08:25

  'net usershare' returned error 255: net usershare add: cannot convert
  name "Everyone" to a SID. Access denied.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1967245/+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 1647285] Re: SSL trust not system-wide

2023-02-15 Thread Athos Ribeiro

** Tags added: server-triage-discuss

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Fix Released
Status in sssd package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

2023-03-03 Thread Athos Ribeiro

** Changed in: pixman (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 2014136] Re: gnome-shell[957]: message repeated 2 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native

2023-05-11 Thread Athos Ribeiro

I am currently seeing the same message in my logs (mantic).

I am not entirely sure if this is related yet, but this happens when I
re-size terminal windows to fit half of my leftmost workspaces (and then
I experience a few seconds freeze when this happens).

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

Title:
  gnome-shell[957]: message repeated 2 times: [
  (../src/backends/native/meta-onscreen-
  native.c:283):page_flip_feedback_ready: runtime check failed:
  (!onscreen_native->gbm.next_fb)]

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Just got on inactivity

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu2
  Uname: Linux 6.2.0-18-generic x86_64
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 31 22:13:08 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1679944760
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/sem33
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 11
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2014136/+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 1988786] [NEW] system does not boot after full-upgrade on kinetic

2022-09-05 Thread Athos Ribeiro

Public bug reported:

Hi,

After a full upgrade on a kinetic system, the system no longer boots
normally.

When I power the computer on, I get a prompt to decrypt my disk. I
insert the password, and am redirected to a screen saying a fschk is
running. It spend hours in that screen with apparently no activity.
Pressing ctrl+C does not help at that point.

Booting through recovery mode and then requesting to proceed to boot
works fine. A regular fschk also suceeds.

Here is what I could extract from my journal:

Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.Shell.desktop' failed to register before timeout
Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 
comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined")
Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 
'ca.desrt.dconf'
Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 
pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined")
Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 
comm="/usr/libexec/gsd-sharing" label="unconfined")
Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service...
Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
Sep 05 16:10:57 castor systemd[1]: Started Hostname Service.
Sep 05 16:10:57 castor kernel: rfkill: input handler disabled
Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated 
successfully.
Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout
Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to 
register before timeout
Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to 
register before timeout
Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to 
register before timeout
Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to 
register before timeout
Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Power.desktop
Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout
Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.MediaKeys.desktop
Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout
Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Keyboard.desktop
Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Color.desktop
Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Wacom.desktop' failed to register before timeout
Sep 05 16:12:27

[Desktop-packages] [Bug 1939916] [NEW] 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 Athos Ribeiro

Public bug reported:

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

** Affects: sane-airscan (Ubuntu)
 Importance: Undecided
 Assignee: Athos Ribeiro (athos-ribeiro)
 Status: New


** Tags: ftbfs

-- 
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:
  New

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

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

2021-08-19 Thread Athos Ribeiro

** Also affects: python-debian (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed already
  ceph- not affected in Ubuntu's version
  circlator   - not affected, just test data
  cowdancer   - not affected, just documentation
  eccodes - skip, just orig-data.tar.xz
  eckit   - skip, just ...orig-data.tar.xz
  firefox

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

2021-08-19 Thread Athos Ribeiro

dh-cmake currently FTBFS [1].

While investigating the issue, I realized that, now dpkg-deb defaults to
compressing with zstd, python-debian can no longer decompress the
compressed data into the binary package archive.

I am proposing a patch for python-debian in the following MP:
https://code.launchpad.net/~athos-ribeiro/ubuntu/+source/python-
debian/+git/python-debian/+merge/407413

A PPA with the proposed fix is available at
https://launchpad.net/~athos-ribeiro/+archive/ubuntu/lp-1923845-python-
debian/+packages

[1] https://launchpadlibrarian.net/552708462/buildlog_ubuntu-impish-
amd64.dh-cmake_0.6.1_BUILDING.txt.gz

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  New
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  New
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archi

[Desktop-packages] [Bug 2056760] Re: [snap]Thunderbird doesn't authenticate with sssd-kcm

2024-03-13 Thread Athos Ribeiro

I am adding a server-triage-discuss here so we can ensure this is the
correct place for this report.

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

** Tags added: server-traige-discuss

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

Title:
  [snap]Thunderbird doesn't authenticate with sssd-kcm

Status in sssd package in Ubuntu:
  Incomplete
Status in thunderbird package in Ubuntu:
  New

Bug description:
  I have Kerberos authentication set up in Thunderbird for my mailbox.

  My environment contains:

  helga@helga-rashomon:~$ env | grep KRB
  KRB5CCNAME=KCM:

  This means that Kerberos authentication should work through the sssd-
  kcm server.

  I initialize Kerberos and verify that it functions correctly:

  helga@helga-rashomon:~$ klist
  Ticket cache: KCM:1000
  Default principal: he...@example.org

  Valid starting  Expires Service principal
  03/11/24 04:14:24   03/12/24 04:14:24   krbtgt/example@example.org
  03/11/24 04:15:24   03/12/24 04:14:24   HTTP/redmine.example.org@
  Ticket server: HTTP/redmine.example@example.org

  (listing redacted to say example.org instead of the real address. the
  redmine listing shows that Firefox works correctly with this address)

  However, when I open the Snap Thunderbird, it does not recognize this
  Kerberos setup, showing me "The Kerberos/GSSAPI ticket was not
  accepted by the IMAP server". klist -A likewise shows no changes.

  The exact same setup works when I specify KRB5CCNAME=DIR:${HOME}/krb5cc in 
.profile instead.
  The sssd-kcm setup also works in Thunderbird native and Flatpak profiles.

  Considering the Flatpak specifically permits access to
  /run/.heim_org.h5l.kcm-socket, could it be that the Thunderbird Snap
  is not allowed to access this socket?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2056760/+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 1988786] Re: system does not boot after full-upgrade on kinetic

2022-09-27 Thread Athos Ribeiro

I am attaching the boot logs with gdm and gnome-session debug modes on.
I hope this helps.

I am also targeting the bug to gdm3, since replacing it with lightdm
does fix the issue for me.

Finally, I tried reproducing the issue by performing a clean jammy
installation and upgrading to kinetic. I could not reproduce the issue.

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

Title:
  system does not boot after full-upgrade on kinetic

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New

Bug description:
  Hi,

  After a full upgrade on a kinetic system, the system no longer boots
  normally.

  When I power the computer on, I get a prompt to decrypt my disk. I
  insert the password, and am redirected to a screen saying a fschk is
  running. It spend hours in that screen with apparently no activity.
  Pressing ctrl+C does not help at that point.

  Booting through recovery mode and then requesting to proceed to boot
  works fine. A regular fschk also suceeds.

  Here is what I could extract from my journal:

  Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
  Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.Shell.desktop' failed to register before timeout
  Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 
comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 
'ca.desrt.dconf'
  Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 
pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 
comm="/usr/libexec/gsd-sharing" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
  Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
  Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service...
  Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Sep 05 16:10:57 castor systemd[1]: Started Hostname Service.
  Sep 05 16:10:57 castor kernel: rfkill: input handler disabled
  Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated 
successfully.
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Power.desktop
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.MediaKeys.desktop
  Sep 05 16:12:27

[Desktop-packages] [Bug 1988786] Re: system does not boot after full-upgrade on kinetic

2022-09-27 Thread Athos Ribeiro

** Attachment added: "gnome-boot-debug.logs"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1988786/+attachment/5619578/+files/gnome-boot-debug.logs

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

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

Title:
  system does not boot after full-upgrade on kinetic

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New

Bug description:
  Hi,

  After a full upgrade on a kinetic system, the system no longer boots
  normally.

  When I power the computer on, I get a prompt to decrypt my disk. I
  insert the password, and am redirected to a screen saying a fschk is
  running. It spend hours in that screen with apparently no activity.
  Pressing ctrl+C does not help at that point.

  Booting through recovery mode and then requesting to proceed to boot
  works fine. A regular fschk also suceeds.

  Here is what I could extract from my journal:

  Sep 05 16:10:57 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout
  Sep 05 16:10:57 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.Shell.desktop' failed to register before timeout
  Sep 05 16:10:57 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='ca.desrt.dconf' requested by ':1.2' (uid=127 pid=2000 
comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Successfully activated service 
'ca.desrt.dconf'
  Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Activating via systemd: 
service name='org.freedesktop.hostname1' 
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.54' (uid=127 
pid=3239 comm="/usr/libexec/gsd-rfkill" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activating service 
name='org.freedesktop.systemd1' requested by ':1.7' (uid=127 pid=3227 
comm="/usr/libexec/gsd-sharing" label="unconfined")
  Sep 05 16:10:57 castor /usr/libexec/gdm-wayland-session[1986]: 
dbus-daemon[1986]: [session uid=127 pid=1986] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
  Sep 05 16:10:57 castor gsd-sharing[3227]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.freedesktop.systemd1 exited with status 1
  Sep 05 16:10:57 castor systemd[1]: Starting Hostname Service...
  Sep 05 16:10:57 castor dbus-daemon[1221]: [system] Successfully activated 
service 'org.freedesktop.hostname1'
  Sep 05 16:10:57 castor systemd[1]: Started Hostname Service.
  Sep 05 16:10:57 castor kernel: rfkill: input handler disabled
  Sep 05 16:11:27 castor systemd[1]: systemd-hostnamed.service: Deactivated 
successfully.
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Power.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Power.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session[2000]: gnome-session-binary[2000]: 
WARNING: Application 'org.gnome.SettingsDaemon.Wacom.desktop' failed to 
register before timeout
  Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.Power.desktop
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.MediaKeys.desktop' failed to register before timeout
  Sep 05 16:12:27 castor gnome-session-binary[2000]: Unrecoverable failure in 
required component org.gnome.SettingsDaemon.MediaKeys.desktop
  Sep 05 16:12:27 castor gnome-session-binary[2000]: WARNING: Application 
'org.gnome.SettingsDaemon.Ke

[Desktop-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

2022-10-07 Thread Athos Ribeiro

Hi Benjamin,

Thanks for taking the time to provide this fix!

Would you be willing to file the SRU template [1] for this bug so we can
proceed here?

It would also be nice to add dep3 headers [2] to that patch.

[1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
[2] https://dep-team.pages.debian.net/deps/dep3/

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  New

Bug description:
  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

2022-10-14 Thread Athos Ribeiro

** Description changed:

+ [ Impact ]
+ 
+ OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering backend,
+ always with CAIRO_OPERATOR_SATURATE and sometimes with subpixel
+ positioning (when reading certain file formats), and Cairo in turn
+ invokes this code. As a result, some slides incorrectly render with
+ large blank spaces and with some pixels rendered on top of other pixels.
+ This effectively makes OpenSlide unusable for several of the file
+ formats it supports. No workaround is believed possible within the
+ OpenSlide codebase.
+ 
+ [ Test Plan ]
+ 
+ Compile and run the pixman.c test program uploaded to this bug. It
+ should report "OK".
+ 
+ [ Where problems could occur ]
+ 
+ Problems would show up as incorrect pixel output from software that
+ renders via Cairo or pixman.
+ 
+ [ Other Info ]
+ 
+ While I'm not a pixman expert, it appears that the change should only
+ affect the broken code path, and it seems unlikely that anything else
+ depends on the incorrect math fixed by this patch. This bug hasn't
+ previously been reported in Ubuntu, which may imply that this code path
+ is not exercised by other packages in the distro.
+ 
+ The affected source file has had no further commits upstream since this
+ patch was applied in April 2019, and some basic commit grepping didn't
+ turn up any followup fixes elsewhere in the tree.
+ 
+ [ Original message ]
+ 
  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some circumstances.
  This can be triggered by the use of cairo with CAIRO_OPERATOR_SATURATE
  and subpixel positioning, and causes OpenSlide 
  to produce incorrect output.
  
  The attached test program will print "Failed" if the bug exists, or "OK"
  if it doesn't.
  
  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which is
  in pixman 0.40.0.
  
  See https://github.com/openslide/openslide/issues/278 for more context.

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

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

** Changed in: pixman (Ubuntu Focal)
   Status: New => Triaged

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  Triaged

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

2022-10-14 Thread Athos Ribeiro

Thanks, Benjamin!

I uploaded a patched package to the following PPA:
https://launchpad.net/~athos-ribeiro/+archive/ubuntu/lp1988796-pixman

Please, test it to ensure everything works as expected before we proceed
with the SRU process here.

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  Triaged

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
  <https://openslide.org/> to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

2022-10-17 Thread Athos Ribeiro

Thanks. Uploaded!

** Changed in: pixman (Ubuntu Focal)
   Status: Triaged => In Progress

** Changed in: pixman (Ubuntu Focal)
 Assignee: (unassigned) => Athos Ribeiro (athos-ribeiro)

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  In Progress

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
  <https://openslide.org/> to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

2022-10-21 Thread Athos Ribeiro

The first upload was rejected due to some cruft in my upload. This is a
1.0 format source package and I was dealing with some issues when
handling git (git ubuntu) being considered during the package build.
Thanks for spotting that one, Timo :) I re-uploaded the package.

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

2022-10-27 Thread Athos Ribeiro

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with
  subpixel positioning

Status in pixman package in Ubuntu:
  Fix Released
Status in pixman source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  OpenSlide (libopenslide0 in Ubuntu) uses Cairo as its rendering
  backend, always with CAIRO_OPERATOR_SATURATE and sometimes with
  subpixel positioning (when reading certain file formats), and Cairo in
  turn invokes this code. As a result, some slides incorrectly render
  with large blank spaces and with some pixels rendered on top of other
  pixels. This effectively makes OpenSlide unusable for several of the
  file formats it supports. No workaround is believed possible within
  the OpenSlide codebase.

  [ Test Plan ]

  Compile and run the pixman.c test program uploaded to this bug. It
  should report "OK".

  [ Where problems could occur ]

  Problems would show up as incorrect pixel output from software that
  renders via Cairo or pixman.

  [ Other Info ]

  While I'm not a pixman expert, it appears that the change should only
  affect the broken code path, and it seems unlikely that anything else
  depends on the incorrect math fixed by this patch. This bug hasn't
  previously been reported in Ubuntu, which may imply that this code
  path is not exercised by other packages in the distro.

  The affected source file has had no further commits upstream since
  this patch was applied in April 2019, and some basic commit grepping
  didn't turn up any followup fixes elsewhere in the tree.

  [ Original message ]

  pixman 0.38.4-0ubuntu1 in focal (and actually pixman 0.38.x generally)
  has a regression that causes incorrect rendering in some
  circumstances.  This can be triggered by the use of cairo with
  CAIRO_OPERATOR_SATURATE and subpixel positioning, and causes OpenSlide
   to produce incorrect output.

  The attached test program will print "Failed" if the bug exists, or
  "OK" if it doesn't.

  This is fixed upstream in
  https://gitlab.freedesktop.org/pixman/pixman/-/commit/8256c235, which
  is in pixman 0.40.0.

  See https://github.com/openslide/openslide/issues/278 for more
  context.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1988796/+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 1993356] Re: udisks doesn't make sense from cdrom

[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution

[Desktop-packages] [Bug 2007702] Re: [SRU] Deb version numbering is misleading

[Desktop-packages] [Bug 2062377] Re: Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

[Desktop-packages] [Bug 2062377] Re: Ubuntu 24.04. Xorg crash when dmz-white cursor is selected

[Desktop-packages] [Bug 2056760] Re: [snap]Thunderbird doesn't authenticate with sssd-kcm

[Desktop-packages] [Bug 2075138] Re: net usershare » a retourné l'erreur 255 net usershare add: share name /home/path/file/contains invalid characters (any of %<>*?|/\+=;:",)

[Desktop-packages] [Bug 1967245] Re: 'net usershare' returned error 255 on jammy-desktop-amd64

[Desktop-packages] [Bug 1967245] Re: 'net usershare' returned error 255 on jammy-desktop-amd64

[Desktop-packages] [Bug 1647285] Re: SSL trust not system-wide

[Desktop-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Desktop-packages] [Bug 2014136] Re: gnome-shell[957]: message repeated 2 times: [ (../src/backends/native/meta-onscreen-native.c:283):page_flip_feedback_ready: runtime check failed: (!onscreen_native

[Desktop-packages] [Bug 1988786] [NEW] system does not boot after full-upgrade on kinetic

[Desktop-packages] [Bug 1939916] [NEW] FTBFS 0.99.25-0ubuntu1 error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=]

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default

[Desktop-packages] [Bug 2056760] Re: [snap]Thunderbird doesn't authenticate with sssd-kcm

[Desktop-packages] [Bug 1988786] Re: system does not boot after full-upgrade on kinetic

[Desktop-packages] [Bug 1988786] Re: system does not boot after full-upgrade on kinetic

[Desktop-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Desktop-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Desktop-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Desktop-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Desktop-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

[Desktop-packages] [Bug 1988796] Re: Incorrect rendering triggered by cairo CAIRO_OPERATOR_SATURATE with subpixel positioning

25 matches

Site Navigation

Mail list logo

Footer information