date:20220726

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  ubuntu-22.04 could not run firefox -safe-mofe

Status in firefox package in Ubuntu:
  Expired

Bug description:
  Hi,

  I download and install ubuntu-22.04-desktop-amd64.iso( 2022-04-19 )
  and I want to set firefox peformance option changing off to use safemode.
  but do not work.

  nakasima@nakasima-pc:~$ uname -a
  Linux nakasima-pc 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

  nakasima@nakasima-pc:~$ firefox -safe-mode
  update.go:85: cannot change mount namespace according to change mount 
(/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help 
none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": 
permission denied
  Gtk-Message: 07:00:45.360: Failed to load module "canberra-gtk-module"
  Gtk-Message: 07:00:45.399: Failed to load module "canberra-gtk-module"

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


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

[Desktop-packages] [Bug 1982611] Re: GNOME Desktop Clashes when I close PiP of Firefox's

Also next time the crash happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

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

Title:
  GNOME Desktop Clashes when I close PiP of Firefox's

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1. Start Firefox
  2. Open youtube.com
  3. Click a video
  4. Open a PiP
  5. Click "Show all workspace" in Context menu
 (However, Change workspace, and It was back workspace before)
  6. Close PiP to use left below button.
  7. GNOME desktop was logouted

  Environment:
  Ubuntu 22.04
  GNOME 42
  Wayland
  Firefox(Snap)
  User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 
Firefox/102.0

  https://bugzilla.mozilla.org/show_bug.cgi?id=1780768

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


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

[Desktop-packages] [Bug 1982611] Re: GNOME Desktop Clashes when I close PiP of Firefox's

Unfortunately that's the wrong crash ID, not related to GNOME desktop.

Next time the crash happens, please repeat the steps in comment #2.

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

Title:
  GNOME Desktop Clashes when I close PiP of Firefox's

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1. Start Firefox
  2. Open youtube.com
  3. Click a video
  4. Open a PiP
  5. Click "Show all workspace" in Context menu
 (However, Change workspace, and It was back workspace before)
  6. Close PiP to use left below button.
  7. GNOME desktop was logouted

  Environment:
  Ubuntu 22.04
  GNOME 42
  Wayland
  Firefox(Snap)
  User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 
Firefox/102.0

  https://bugzilla.mozilla.org/show_bug.cgi?id=1780768

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


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

[Desktop-packages] [Bug 1980831] Re: GUI freezes randomly, mouse still moving, nothing else works

Thanks. That shows it's the amdgpu kernel driver getting stuck:

iul 26 20:24:46 alexb kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* 
Waiting for fences timed out!
iul 26 20:24:46 alexb kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring 
sdma0 timeout, signaled seq=1334, emitted seq=1336
iul 26 20:24:46 alexb kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process  pid 0 thread  pid 0
iul 26 20:24:46 alexb kernel: amdgpu :08:00.0: amdgpu: GPU recovery 
disabled.
iul 26 20:24:46 alexb kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring 
gfx_0.0.0 timeout, signaled seq=12220, emitted seq=12221
iul 26 20:24:46 alexb kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* 
Process information: process Xorg pid 2753 thread Xorg:cs0 pid 2782
iul 26 20:24:46 alexb kernel: amdgpu :08:00.0: amdgpu: GPU recovery 
disabled.

** Summary changed:

- GUI freezes randomly, mouse still moving, nothing else works
+ GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* 
Waiting for fences timed out!

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

** Tags added: amdgpu

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

Title:
  GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]]
  *ERROR* Waiting for fences timed out!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object havi

21.04 is is not supported anymore, but maybe you meant 22.04?

Regardless, please open a new bug so we can track whatever the more
recent cause of the message is:

  ubuntu-bug gnome-shell

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

Title:
  Syslog is flooded with Object St.Bin (0x565425162c80), has been
  already deallocated — impossible to set any property on it. This might
  be caused by the object having been destroyed from C code using
  something such as destroy(), dispose(), or remove() vfuncs.

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  The syslog is full of these messages, continuously written all day
  long

  Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has 
been already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 
0x56541fffb220 ==
  Nov 25 07:46:42 pc1 gnome-shell[2980]: #0   7ffddbfa1940 b   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 
(1839cb6a2420 @ 208)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 07:42:45 2020
  InstallationDate: Installed on 2014-06-03 (2366 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions


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

[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

** Description changed:

  [Impact]
  
-  * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
+  * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
  
-  * The GIF loader runs out of memory with specifically crafted files
+  * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer limit.
  
-  * After gdk-pixbuf-thum runs out of memory, other apps can and on low
+  * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.
  
-  * Or, in other ways, bad gif files in other applications can open the
+  * Or, in other ways, bad gif files in other applications can open the
  door for exploits.
  
-  * Any app using gdk-pixbuf is affected, mainly file managers and image
+  * Any app using gdk-pixbuf is affected, mainly file managers and image
  viewers.
  
  [Test Plan]
  
-  * Take the POC's - they can be found in the issue in the GNOME repo
+  * Take the POC's - they can be found in the issue in the GNOME repo
  
-  * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
-  - Nautilus, GNOME's file manager
-  - Nemo, Cinnamon's file manager
-  - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
-  - PCManFM, LXDE's file manager which straight up crashes
-  I have not been able to produce any results with Caja (MATE's file manager) 
but have personally experienced issues with Nautilus. POC logs and crashes are 
attached.
+  * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
+  - Nautilus, GNOME's file manager
+  - Nemo, Cinnamon's file manager
+  - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
+  - PCManFM, LXDE's file manager which straight up crashes
+  - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app 
still usable, no memory issues)
+  - Eye of GNOME (eog) triggers the segfault in syslog
  
-  * If you or the system couldn't tell something is wrong, cat
+  * If you or the system couldn't tell something is wrong, cat
  /var/log/syslog and enjoy the segfaults or out of memory warnings or
  even kernel spam.
  
  [Where problems could occur]
  
-  * The patch itself is simple, but since gdk-pixbuf is often used with
+  * The patch itself is simple, but since gdk-pixbuf is often used with
  GTK apps a mistake here could be problematic.
  
-  * It is possible, and has happened in the past (which has been patched)
+  * It is possible, and has happened in the past (which has been patched)
  that other bad GIFs can cause other crashes.
  
-  * That patch is essentially overflow checks -  changes with GLib
+  * That patch is essentially overflow checks -  changes with GLib
  (GNOME's, not to be confused with glibc) and the functions used in not
  only the patch but all of gdk-pixbuf can cause problems
  
-  * Other failures to properly handle GIFs and broken or intentionally
+  * Other failures to properly handle GIFs and broken or intentionally
  tampered GIFs can continue and always will open the door for security
  holes for other bugs
  
  * Again, overall a simple patch but as long as the GIFs remain handled
  properly, and no changes to the GLib functions are made and to other
  apps that use gdk-pixbuf (and assuming are not affected by the change
  and still work), the patch does not have much regression potential.
  
  [Other Info]
-  
-  * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
-  * Files attached are examples or crashes
-  * Again, all apps using gdk-pixbuf are affected
-  * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
-  * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
+ 
+  * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
+  * Files attached are examples or crashes
+  * Again, all apps using gdk-pixbuf are affected
+  * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
+  * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh

[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

** Description changed:

- There is a buffer overwrite in gdk-pixbuf. I will eventually create a
- whole SRU document with how to reproduce and all, but I'll just say it
- is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
- causes the entire system to run out of memory. (With firefox, 1612/3922
- MB - which says something.)
+ [Impact]
  
- It may be possible all apps using gdk-pixbuf can have a problem handling
- files like the PoC.
+  * A buffer overwrite exists in gdk-pixbuf's thumbnailer.
  
- https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190
+  * The GIF loader runs out of memory with specifically crafted files
+ with bad frame data (and images with its sizes) over the integer limit.
+ 
+  * After gdk-pixbuf-thum runs out of memory, other apps can and on low
+ RAM systems like my old iMac, the system can completely run out of
+ memory.
+ 
+  * Or, in other ways, bad gif files in other applications can open the
+ door for exploits.
+ 
+  * Any app using gdk-pixbuf is affected, mainly file managers and image
+ viewers.
+ 
+ [Test Plan]
+ 
+  * Take the POC's - they can be found in the issue in the GNOME repo
+ 
+  * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
+  - Nautilus, GNOME's file manager
+  - Nemo, Cinnamon's file manager
+  - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that 
also inevitably fails and crashes
+  - PCManFM, LXDE's file manager which straight up crashes
+  I have not been able to produce any results with Caja (MATE's file manager) 
but have personally experienced issues with Nautilus. POC logs and crashes are 
attached.
+ 
+  * If you or the system couldn't tell something is wrong, cat
+ /var/log/syslog and enjoy the segfaults or out of memory warnings or
+ even kernel spam.
+ 
+ [Where problems could occur]
+ 
+  * The patch itself is simple, but since gdk-pixbuf is often used with
+ GTK apps a mistake here could be problematic.
+ 
+  * It is possible, and has happened in the past (which has been patched)
+ that other bad GIFs can cause other crashes.
+ 
+  * That patch is essentially overflow checks -  changes with GLib
+ (GNOME's, not to be confused with glibc) and the functions used in not
+ only the patch but all of gdk-pixbuf can cause problems
+ 
+  * Other failures to properly handle GIFs and broken or intentionally
+ tampered GIFs can continue and always will open the door for security
+ holes for other bugs
+ 
+ * Again, overall a simple patch but as long as the GIFs remain handled
+ properly, and no changes to the GLib functions are made and to other
+ apps that use gdk-pixbuf (and assuming are not affected by the change
+ and still work), the patch does not have much regression potential.
+ 
+ [Other Info]
+  
+  * Besides Buffer overwrite/overflow issues, as aforementioned out of memory 
errors can happen.
+  * Files attached are examples or crashes
+  * Again, all apps using gdk-pixbuf are affected
+  * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/
+  * 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * A buffer overwrite exists in gdk-pixbuf's thumbnailer.

   * The GIF loader runs out of memory with specifically crafted files
  with bad frame data (and images with its sizes) over the integer
  limit.

   * After gdk-pixbuf-thum runs out of memory, other apps can and on low
  RAM systems like my old iMac, the system can completely run out of
  memory.

   * Or, in other ways, bad gif files in other applications can open the
  door for exploits.

   * Any app using gdk-pixbuf is affected, mainly file managers and
  image viewers.

  [Test Plan]

   * Take the POC's - they can be found in the issue in the GNOME repo

   * Open them in an application that uses gdk-pixbuf. I have managed to 
produce reactions with:
   - Nautilus, GNOME's file manager
   - Nemo, Cinnamon's file manager
   - Thunar, XFCE's file manager, which has its own

[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

Here's proposal focal patch - I noticed some whitespaces but those are
in the code and not introduced by me.

** Patch added: "Proposed focal patch"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605438/+files/gdk-pixbuf_2.40.0+dfsg-3ubuntu0.3.debdiff

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => In Progress

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  In Progress

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

PCManFM crashed to this.

that's my last POC - I'm going to create the patch

** Attachment added: "pcmanfmcrash.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605437/+files/pcmanfmcrash.tar.gz

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

Thunar, which uses tumbler for thumbnailing, produced a crash.

** Attachment added: "Tumbler (xfce thumbnailer crash)"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605436/+files/libgdkpixbufloader-gif-crash.tar.gz

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

Here is what it did to my iMac.

** Attachment added: "OldiMacSyslog"
   
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+attachment/5605435/+files/OldiMacSyslog

** Changed in: gdk-pixbuf (Ubuntu)
 Assignee: (unassigned) => Joshua Peisach (itzswirlz)

** Tags removed: jammy
** Tags added: bionic xenial

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1982898] [NEW] CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf

*** This bug is a security vulnerability ***

Public security bug reported:

There is a buffer overwrite in gdk-pixbuf. I will eventually create a
whole SRU document with how to reproduce and all, but I'll just say it
is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
causes the entire system to run out of memory. (With firefox, 1612/3922
MB - which says something.)

It may be possible all apps using gdk-pixbuf can have a problem handling
files like the PoC.

https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Tue Jul 26 19:33:41 2022
InstallationDate: Installed on 2021-11-24 (244 days ago)
InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
SourcePackage: gdk-pixbuf
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Assignee: Joshua Peisach (itzswirlz)
 Status: New


** Tags: amd64 apport-bug bionic focal xenial

** Information type changed from Private Security to Public Security

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

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

Title:
  CVE-2021-46829: Buffer overwrite in  io-gif-animation.c
  composite_frame() in gdk-pixbuf

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a buffer overwrite in gdk-pixbuf. I will eventually create a
  whole SRU document with how to reproduce and all, but I'll just say it
  is a nasty one. Opening it on my old iMac from about 2007/2009 in Nemo
  causes the entire system to run out of memory. (With firefox,
  1612/3922 MB - which says something.)

  It may be possible all apps using gdk-pixbuf can have a problem
  handling files like the PoC.

  https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Tue Jul 26 19:33:41 2022
  InstallationDate: Installed on 2021-11-24 (244 days ago)
  InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1958019]

2022-07-26 Thread baipush

Hello everybody

I can confirm it works for me too (thx Gervasio for pushing forward on
me :) ).

How do we get the patches for all these different Lenovo models that
have been touched in this thread into the original Kernel so that
everybody can have them by default when installing their favorite
distro?

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Desktop-packages] [Bug 1978890] Re: FIPS/OEM installation compatibility is unclear to the end-user

2022-07-26 Thread Lucas Albuquerque Medeiros de Moura

We discussed this on the UA team and we believe we can warn the user of
the potential problems of enabling FIPS we using a OEM kernel, but we
don't think we should block this on the UA side, since users could still
be aware of the risk and follow through with the procedure.

However, before we deliver this through UA, we believe we need to sort
the GRUB_FLAVOUR_ORDER scenario. Otherwise we will warn the user and
even if they want to proceed with FIPS, the will end up in the OEM
kernel regardless.

But let us know if you think we should definitely block enabling FIPS on
a machine running a OEM kernel.

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

Title:
  FIPS/OEM installation compatibility is unclear to the end-user

Status in subiquity package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  [Overall Summary]

  Converting to cover all oem/fips compatibility issues with
  ua/installers/update-manager. These projects are mostly silo'd, so
  when they all converge it creates a confusing and frustrating
  experience for the user.

  At it's core, the problem is that both fips and oem us
  GRUB_FLAVOUR_ORDER to select the preferred kernel to boot from,
  disregarding versioning.

  The main issues are:
  1. ubuntu-drivers should not attempt to `oem-ify` a `fipsified` machine
  2. ua tool should not attempt to `fipsify` an oem machine
  3. subiquity should mention that drivers page is potentially making machine 
realtime & fips incompatible

  
  Below are some reproducible examples of issues:

  ---
  (Subiquity installer case)
  [Summary]
  A recent change to the subiquity snap adds support for installing oem drivers 
at time of instance install. If the user installs these packages, then attempts 
to install the fips packages post-install, fips will install as expected, but 
the system will always boot to the oem kernel.

  [Expected Behavior]
  Messaging should clearly indicate that installing the oem packages will make 
the environment incompatible with fips/RT kernel/ etc. 

  [Observed Behavior]
  Subiquity just offers additional drivers, without clarifying the 
compatibility complications.

  [Replication Steps]
  (Using Dell Inc. Precision 7920 Tower/060K5C)
  1. Install from current focal ISO
  2. Confirm driver installation on the oem gui page
  3. Install ua client/fips
  4. Reboot
  5. Observe kernel version (oem)

  ---
  (update-manager case)
  [Summary]
  A feature was added to allow for post-install enablement for oem-enabled 
devices via update manager:
  https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1908050

  While this works great for some situations, it can lead to users
  unexpectedly installing the oem meta package + associated kernel,
  overwriting an existing fips installation, as the "Improved hardware
  support" bundle may not be noticed when operating update-manager

  [Expected Behavior]
  For non linux-generic running installs, the post-install oem enablement 
functionality should not trigger, nor should it add the additional repositories 
to the client's sources.list.d.

  [Observed Behavior]
  sources.list.d is updated and "Improved hardware support" is allowed as an 
option in update-manager, which leads to clients unexpectedly losing compliance 
in fips environments.

  [Replication Steps]
  (Using Dell Inc. Precision 7920 Tower/060K5C)
  1. Install from current focal ISO
  2. Attach a ua subscription
  3. Enable the fips-updates service
  4. Reboot the system, login the desktop and wait for a while. The 
notification will pop up and it will show "Improved hardware support" on the 
certified machines that has the OEM metapackage support.
  5. Click through the update-manager prompt and install the oem packages
  6. Reboot check fips status

  oem's config in /etc/default/grub.d/* does not have a number prefix,
  and thus will always override 99-ubuntu-fips.cfg when calling update-
  grub.

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


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

[Desktop-packages] [Bug 1905458] Re: [snap] Chromium USB enumeration fails when usbmon module is loaded

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  [snap] Chromium USB enumeration fails when usbmon module is loaded

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Version:

  chromium 87.0.4280.66 1411

  Steps to reproduce:

  1. Have Chromium snap, with raw-usb plug connected.
  2. sudo modprobe usbmon.
  3. Open Chromium and try to use a webpage that has webusb.

  Result:

  Chromium cannot see any USB devices on the system, regardless of
  whether it has raw-usb or not.

  The following errors are printed on dmesg:

  ```
  [3701471.283584] audit: type=1400 audit(1606101844.664:6015): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c508:4" pid=3120526 comm="ThreadPoolForeg" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [3701471.283636] audit: type=1400 audit(1606101844.664:6016): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c508:2" pid=3120526 comm="ThreadPoolForeg" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [3701471.283700] audit: type=1400 audit(1606101844.664:6017): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c508:0" pid=3120526 comm="ThreadPoolForeg" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [3701471.283786] audit: type=1400 audit(1606101844.664:6018): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c508:7" pid=3120526 comm="ThreadPoolForeg" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [3701471.283869] audit: type=1400 audit(1606101844.664:6019): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c508:5" pid=3120526 comm="ThreadPoolForeg" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [3701471.283982] audit: type=1400 audit(1606101844.664:6020): 
apparmor="DENIED" operation="open" profile="snap.chromium.chromium" 
name="/run/udev/data/c508:3" pid=3120526 comm="ThreadPoolForeg" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  ```

  Chromium will then print this on stderr:

  
  ```
  [3121487:3121626:1123/032552.888385:ERROR:udev_watcher.cc(97)] Failed to 
begin udev enumeration.
  ```

  Why this happens:

  Chromium enumerates USB devices by querying udev. Specifically by
  using udev_enumerate_scan_devices. When usbmon module is loaded, some
  new device nodes are created for the monitor endpoints. They are only
  readable by root. When Chromium scans for normal USB devices, it finds
  the monitors and tries to probe them. Apparmor blocks it, which causes
  udev_enumerate_scan_devices to fail.

  Impact:

  There is no way for the user to know this error has occurred unless
  they happen to be watching dmesg or the stderr of Chromium (which
  requires they ran it from a terminal). Unless they check both of these
  places and realize that the error messages are connected, Chromium
  will just appear to behave as if there are no USB devices connected to
  the system at all. If the user does realize that usbmon is causing a
  problem, they must restart Chromium after unloading it, because it
  will not retry if enumeration ever fails.

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


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

[Desktop-packages] [Bug 1982879] Re: Multiple problems when using screenshot

2022-07-26 Thread sameer

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

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

Title:
  Multiple problems when using screenshot

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  Sometimes the preinstalled applications for screenshots causing panic in X11. 
alt+tab gets disabled.
  when using interactive window of browser and selecting clip it captures full 
screen even though I select shift+prnt or it picks a random square.

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


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

[Desktop-packages] [Bug 1982879] [NEW] Multiple problems when using screenshot

You have been subscribed to a public bug:

Sometimes the preinstalled applications for screenshots causing panic in X11. 
alt+tab gets disabled.
when using interactive window of browser and selecting clip it captures full 
screen even though I select shift+prnt or it picks a random square.

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


** Tags: bot-comment
-- 
Multiple problems when using screenshot
https://bugs.launchpad.net/bugs/1982879
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-screenshot in Ubuntu.

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

[Desktop-packages] [Bug 1982885] [NEW] Firefox does not scroll with touch input

2022-07-26 Thread Matthew Lovibond

Public bug reported:

Firefox does not scroll with the usual touch gesture of swiping up or
down on the screen. This action just selects text on the page as though
the left mouse button was depressed and the cursor moved across the
page.

lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04

Snapstore version 103.0-1 latest stable

Possibly related to being packaged as a snap (have noticed this
behaviour on Fedora using the firefox snap).

It's still possible to scroll by dragging the scrollbar but this
essentially breaks firefox on touch systems

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

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

** No longer affects: systemd (Ubuntu)

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

Title:
  Firefox does not scroll with touch input

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox does not scroll with the usual touch gesture of swiping up or
  down on the screen. This action just selects text on the page as
  though the left mouse button was depressed and the cursor moved across
  the page.

  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  Snapstore version 103.0-1 latest stable

  Possibly related to being packaged as a snap (have noticed this
  behaviour on Fedora using the firefox snap).

  It's still possible to scroll by dragging the scrollbar but this
  essentially breaks firefox on touch systems

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


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

[Desktop-packages] [Bug 1982867] Re: Missing translations for About window

2022-07-26 Thread Gunnar Hjalmarsson

@Sebastien: I noticed your remark about gtk translations here:

https://discourse.ubuntu.com/t/desktop-team-updates-monday-25th-
july-2022/29660/9

Can that possibly be related to this bug?

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

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

Title:
  Missing translations for About window

Status in Ubuntu Translations:
  New
Status in gtk4 package in Ubuntu:
  New

Bug description:
  Hello,
  I use Amberol, the music player via flatpak.
  Either on 20.04 or 22.04 I get the About window with words in French whereas 
my system is set to Occitan, then French, then English.
  "Credits" and "About" are not part of Amberol itself.
  Things I found were translated into Occitan.
  Maybe some template to refresh?

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


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

[Desktop-packages] [Bug 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04

2022-07-26 Thread Symax

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

For me, on Ubuntu 22.04, when I try to save a file, and then try to
rename that file, As soon as I start typing, it moves to the Search
field in the File Save As dialog.

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

Title:
  Save As Dialog Box does not get focus in Ubuntu 22.04

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When using a browser to right click a file and save as, the save as
  window does not get focus, which means you can't just type the name of
  the file you want, you have to force focus onto the window to use it
  by clicking it.

  This defeats the entire purpose of 2 built in features, 1 being the
  pre-selected original file name (since you can't rename until you re-
  aquire focus for that window, thereby undoing the pre-selection
  programmed in) and 2, the ability to quickly save the file with a
  keystroke.

  A side note to this, ubuntu-bug should have an option to report bugs
  with other WITHOUT having to specify a package. This is a bug in
  ubuntu-bug. Not a feature. Because we don't always know what
  package(s) are involved. This needs to be addressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.8
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 07:55:24 2022
  InstallationDate: Installed on 2022-03-31 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  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/1968887/+subscriptions


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

[Desktop-packages] [Bug 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid

2022-07-26 Thread Sami Pietila

I found an old printer certificate from /etc/cups/ssl/ folder. Deleting
the certificate made cups to download the new one from printer and now
printing seems to work. Perhaps cups does not update the certificates.

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

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

Status in cups package in Ubuntu:
  Confirmed

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

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

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


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

[Desktop-packages] [Bug 1982867] [NEW] Missing translations for About window

2022-07-26 Thread Quentin PAGÈS

Public bug reported:

Hello,
I use Amberol, the music player via flatpak.
Either on 20.04 or 22.04 I get the About window with words in French whereas my
system is set to Occitan, then French, then English.
"Credits" and "About" are not part of Amberol itself.
Things I found were translated into Occitan.
Maybe some template to refresh?

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

** Attachment added: "Screenhot with words in French such as "À propos" and
"Crédits" when the Occitan for these is "A prepaus" and "Crèdits"

https://bugs.launchpad.net/bugs/1982867/+attachment/5605400/+files/Captura%20del%202022-07-26%2019-57-26.png

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

Title:
Missing translations for About window

Status in gtk4 package in Ubuntu:
New

Bug description:
Hello,
I use Amberol, the music player via flatpak.
Either on 20.04 or 22.04 I get the About window with words in French whereas
my system is set to Occitan, then French, then English.
"Credits" and "About" are not part of Amberol itself.
Things I found were translated into Occitan.
Maybe some template to refresh?

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

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

[Desktop-packages] [Bug 1980831] Re: GUI freezes randomly, mouse still moving, nothing else works

2022-07-26 Thread Alexandru Bolboaca

I didn't have to wait too long...

** Attachment added: "Result of running `journalctl -b-1 > prevboot.txt` after 
freeze"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1980831/+attachment/5605397/+files/prevboot.txt

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

Title:
  GUI freezes randomly, mouse still moving, nothing else works

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When working normally, random freezes happen. Everything freezes,
  except the mouse cursor.

  I tried from keyboard to: switch to another window, start a terminal,
  run a command to restart gnome, enabled ctrl+alt+backspace and tried
  it to restart X windows, ctrl+alt+delete, switch to another session
  with ctrl+alt+F1-F9 - nothing works.

  If I'm listening to something, the sound goes on for a while;
  sometimes it stops by itself, other times it keeps going.

  The only way to recover that I've found is to stop the laptop from the
  power button.

  For a while I thought it was due to firefox; I installed the deb
  version and then switched to chrome - same behavior.

  It didn't happen when I was playing Hollow Knight in Steam, or when
  I've used the terminal and nothing else.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:27:36 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-06-16 (19 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1970449] Re: GPG keys are not shown in Software and Updates

This bug was fixed in the package software-properties - 0.99.25

---
software-properties (0.99.25) kinetic; urgency=medium

  * Fix GPG keys are not shown in Software and Updates (LP: #1970449)
  * Remove trailing spaces
  * Drop obsolete imports from __future__
  * Remove duplicate keys in desktop files
  * d/copyright: Use https URLs instead of http
  * d/copyright: Correct path to add-apt-repository.1
  * Drop obsolete Conflicts & Replaces
  * Fix spelling mistake of repository
  * Set Rules-Requires-Root: no
  * Bump Standards-Version to 4.6.1
  * Add Vcs-Browser

 -- Benjamin Drung   Tue, 26 Jul 2022 13:03:28 +0200

** Changed in: software-properties (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  software-properties-gtk does not show the registered apt gpg keys in
  the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.

  [Test Plan]

  1. Launch software-properties-gtk
  2. Click on the "Authentication" tab
  3. At least one key should be listed

  [Where problems could occur]

  I fail to come up with possible problems. The failures was a
  regression and the fixed version has a test case.

  [Other Infos]

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+subscriptions


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

[Desktop-packages] [Bug 1962135] Re: [SRU] gstreamer 1.16.3 series

2022-07-26 Thread Ashton Nelson

I tested a variety of audio/video formats (x264, x265, MP4, MKV, flac,
MP3, etc.) as well as streaming audio/video and everything seems to work
as intended with no issues.

Tested on a Focal VM with the latest updates including this patch.

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

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

Title:
  [SRU] gstreamer 1.16.3 series

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 source package in Focal:
  Fix Committed
Status in gst-plugins-base1.0 source package in Focal:
  Fix Committed
Status in gst-plugins-good1.0 source package in Focal:
  Fix Committed
Status in gstreamer1.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.16 series
  that 20.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

  ---


  On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2,
  though gstreamer has subsequent minor version gst-1.16.3 with fixes
  incorporated.

  Hence, Ideally default gstreamer-1.16 minor version support with
  ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1962135/+subscriptions


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

[Desktop-packages] [Bug 1905519] Re: Syslog is flooded with Object St.Bin (0x565425162c80), has been already deallocated — impossible to set any property on it. This might be caused by the object havi

2022-07-26 Thread Joona-M Heikkilä

gnome-shell[2660]: Object St.Bin (0x5563a04d98d0), has been already
deallocated — impossible to set any property on it. This might be caused
by the object having been destroyed from C code using something such as
destroy(), dispose(), or r>


Still an issue on 21.04 Ubuntu.

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

Title:
  Syslog is flooded with Object St.Bin (0x565425162c80), has been
  already deallocated — impossible to set any property on it. This might
  be caused by the object having been destroyed from C code using
  something such as destroy(), dispose(), or remove() vfuncs.

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  The syslog is full of these messages, continuously written all day
  long

  Nov 25 07:46:42 pc1 gnome-shell[2980]: Object St.Bin (0x565425162c80), has 
been already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Nov 25 07:46:42 pc1 gnome-shell[2980]: == Stack trace for context 
0x56541fffb220 ==
  Nov 25 07:46:42 pc1 gnome-shell[2980]: #0   7ffddbfa1940 b   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 
(1839cb6a2420 @ 208)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 07:42:45 2020
  InstallationDate: Installed on 2014-06-03 (2366 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1905519/+subscriptions


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

[Desktop-packages] [Bug 1969291] Re: apport-collect & ubuntu-bug failing to switch to firefox

2022-07-26 Thread Benjamin Drung

There are two possible reasons:
1. Firefox or no other browser is installed
2. Firefox or another browser is installed, but xdg-open fails to open it.

Assuming it is point 2, I re-assign this ticket to xdg-utils which
provides /usr/bin/xdg-open.

** Package changed: apport (Ubuntu) => xdg-utils (Ubuntu)

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

Title:
  apport-collect & ubuntu-bug failing to switch to firefox

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  In attempting to file a bug report on Lubuntu jammy ISO 
  (QA-test installed yesterday using ISO 2020-04-15)

  --
  guiverc@dc7700-2re:~$ apport-collect 1969290
  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Waiting to hear from Launchpad about your decision...
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION'
  ---

  On attempting to file using `ubuntu-bug apport`

  ---
  guiverc@dc7700-2re:~$ ubuntu-bug apport

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  . 

   


   
  *** Send problem report to the developers?

   


   
  After the problem report has been sent, please fill out the form in the   

   
  automatically opened web browser. 

   


   
  What would you like to do? Your options are:  

   
S: Send report (5.0 KB) 

   
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  96%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?'
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sun Apr 17 12:34:57 2022
  InstallationDate: Installed on 2022-04-16 (0 days ago)
  InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 
(20220415)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1969291/+subscriptions


-- 
Mailing list:

[Desktop-packages] [Bug 1982340] Re: Clients of the WebExtensions portal see the FDs as closed when the portal is used for the first time

This bug was fixed in the package xdg-desktop-portal -
1.14.4-1ubuntu2~22.04.1

---
xdg-desktop-portal (1.14.4-1ubuntu2~22.04.1) jammy; urgency=medium

  * Update the native messaging portal patch to pick up a new commit
(LP: #1982340)
- debian/patches/webextensions-portal.patch

 -- Olivier Tilloy   Wed, 20 Jul 2022
14:02:36 +0200

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

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

Title:
  Clients of the WebExtensions portal see the FDs as closed when the
  portal is used for the first time

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Without this patch, the WebExtensions portal won't allow native
  connectors to communicate with a browser the first time they are
  spawned by the portal. Closing and restarting the browser won't do,
  only killing the portal and letting it restart.

   * This patch is being backported to jammy as this is currently the
  primary target for the effort of enabling native messaging in the
  firefox snap (not widely available yet, but the portal is available in
  jammy, and once the firefox implementation lands in the snap, we want
  this to work seamlessly).

   * The patch is trivial, it adds a missing variable initialization,
  which fixes the problem.

  
  [Test Plan]

   * Steps to reproduce the bug:
 - in a fully up-to-date jammy VM, install the chrome-gnome-shell package, 
and download and side-load the latest test snap from 
https://launchpad.net/~osomon/+snap/firefox-native-messaging (because the 
firefox implementation hasn't landed upstream yet)
 - if it exists, delete ~/.local/share/flatpak/db/webextensions and reboot 
to ensure a pristine state
 - run the firefox snap, browse to 
https://addons.mozilla.org/firefox/addon/gnome-shell-integration/, and click 
the "Add to Firefox" blue button
 - accept the firefox prompt to install the extension
 - you will soon be prompted by GNOME Shell (with a modal dialog) to allow 
firefox to use the WebExtensions portal to start the native connector, click 
"Allow"
 - browse to https://extensions.gnome.org/local/
 - without the patch, you'll get a message that "an unexpected error 
occurred"
 - with the patch, firefox is able to talk to the native connector and 
displays a page with the currently installed GNOME Shell extensions

   * Note that this can also be tested with another extension that uses
  native messaging to talk to a native connector on the system, e.g.
  https://github.com/keepassxreboot/keepassxc-browser

  
  [Where problems could occur]

   * The patch is trivial and it's hard to imagine that initializing an
  uninitialized variable could have undesirable side effects.

   * In any case, the WebExtensions portal isn't currently used by any
  piece of software (this is being tested for firefox but isn't merged
  and therefore not widely available yet), so possible side effects
  wouldn't be noticed until the native messaging portal support lands in
  the firefox snap (see
  https://phabricator.services.mozilla.com/D140803).

  
  [Other Info]
   
   * We are still hoping to get the native messaging portal support in the 
firefox snap in time for Ubuntu 22.04.1, so for it to be a seamless experience 
this patch needs to land for the .1 release too.

  
  [Original Description]

  (this was initially reported here: https://github.com/flatpak/xdg-
  desktop-portal/pull/705#issuecomment-1123392120)

  When testing the WebExtensions portal against the only known client so
  far (firefox snap + the corresponding upstream patch
  https://phabricator.services.mozilla.com/D140803), I'm consistently
  seeing the following problem: the first time the user is prompted for
  authorization and accepts, the portal will spawn the native connector
  and pass the file descriptors to the client (firefox snap), but the
  client sees the file descriptors as closed. Closing the client and re-
  opening it doesn't help. Only when the portal is terminated and
  restarted does communication through FDs start working normally.

  It turns out this is caused by a missing variable initialization,
  which is trivially fixed by https://github.com/jhenstridge/xdg-
  desktop-portal/pull/2.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.4-1ubuntu1~22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 20 14:03:15 2022
  InstallationDate: Installed on 2020-09-16 (671

[Desktop-packages] [Bug 1982340] Update Released

2022-07-26 Thread Brian Murray

The verification of the Stable Release Update for xdg-desktop-portal has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Clients of the WebExtensions portal see the FDs as closed when the
  portal is used for the first time

Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Without this patch, the WebExtensions portal won't allow native
  connectors to communicate with a browser the first time they are
  spawned by the portal. Closing and restarting the browser won't do,
  only killing the portal and letting it restart.

   * This patch is being backported to jammy as this is currently the
  primary target for the effort of enabling native messaging in the
  firefox snap (not widely available yet, but the portal is available in
  jammy, and once the firefox implementation lands in the snap, we want
  this to work seamlessly).

   * The patch is trivial, it adds a missing variable initialization,
  which fixes the problem.

  
  [Test Plan]

   * Steps to reproduce the bug:
 - in a fully up-to-date jammy VM, install the chrome-gnome-shell package, 
and download and side-load the latest test snap from 
https://launchpad.net/~osomon/+snap/firefox-native-messaging (because the 
firefox implementation hasn't landed upstream yet)
 - if it exists, delete ~/.local/share/flatpak/db/webextensions and reboot 
to ensure a pristine state
 - run the firefox snap, browse to 
https://addons.mozilla.org/firefox/addon/gnome-shell-integration/, and click 
the "Add to Firefox" blue button
 - accept the firefox prompt to install the extension
 - you will soon be prompted by GNOME Shell (with a modal dialog) to allow 
firefox to use the WebExtensions portal to start the native connector, click 
"Allow"
 - browse to https://extensions.gnome.org/local/
 - without the patch, you'll get a message that "an unexpected error 
occurred"
 - with the patch, firefox is able to talk to the native connector and 
displays a page with the currently installed GNOME Shell extensions

   * Note that this can also be tested with another extension that uses
  native messaging to talk to a native connector on the system, e.g.
  https://github.com/keepassxreboot/keepassxc-browser

  
  [Where problems could occur]

   * The patch is trivial and it's hard to imagine that initializing an
  uninitialized variable could have undesirable side effects.

   * In any case, the WebExtensions portal isn't currently used by any
  piece of software (this is being tested for firefox but isn't merged
  and therefore not widely available yet), so possible side effects
  wouldn't be noticed until the native messaging portal support lands in
  the firefox snap (see
  https://phabricator.services.mozilla.com/D140803).

  
  [Other Info]
   
   * We are still hoping to get the native messaging portal support in the 
firefox snap in time for Ubuntu 22.04.1, so for it to be a seamless experience 
this patch needs to land for the .1 release too.

  
  [Original Description]

  (this was initially reported here: https://github.com/flatpak/xdg-
  desktop-portal/pull/705#issuecomment-1123392120)

  When testing the WebExtensions portal against the only known client so
  far (firefox snap + the corresponding upstream patch
  https://phabricator.services.mozilla.com/D140803), I'm consistently
  seeing the following problem: the first time the user is prompted for
  authorization and accepts, the portal will spawn the native connector
  and pass the file descriptors to the client (firefox snap), but the
  client sees the file descriptors as closed. Closing the client and re-
  opening it doesn't help. Only when the portal is terminated and
  restarted does communication through FDs start working normally.

  It turns out this is caused by a missing variable initialization,
  which is trivially fixed by https://github.com/jhenstridge/xdg-
  desktop-portal/pull/2.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xdg-desktop-portal 1.14.4-1ubuntu1~22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 20 14:03:15 2022
  InstallationDate:

[Desktop-packages] [Bug 1969291] [NEW] apport-collect & ubuntu-bug failing to switch to firefox

You have been subscribed to a public bug:

In attempting to file a bug report on Lubuntu jammy ISO 
(QA-test installed yesterday using ISO 2020-04-15)

--
guiverc@dc7700-2re:~$ apport-collect 1969290
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
/usr/bin/xdg-open: 882: firefox: not found
/usr/bin/xdg-open: 882: firefox: not found
xdg-open: no method available for opening 
'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION'
---

On attempting to file using `ubuntu-bug apport`

---
guiverc@dc7700-2re:~$ ubuntu-bug apport

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.   

 


 
*** Send problem report to the developers?  

 


 
After the problem report has been sent, please fill out the form in the 

 
automatically opened web browser.   

 


 
What would you like to do? Your options are:

 
  S: Send report (5.0 KB)   

 
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): s

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.
96%

*** To continue, you must visit the following URL:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?

You can launch a browser now, or copy this URL into a browser on another
computer.


Choices:
  1: Launch a browser now
  C: Cancel
Please choose (1/C): 1
/usr/bin/xdg-open: 882: firefox: not found
/usr/bin/xdg-open: 882: firefox: not found
xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?'
---

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Sun Apr 17 12:34:57 2022
InstallationDate: Installed on 2022-04-16 (0 days ago)
InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xdg-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy lubuntu
-- 
apport-collect & ubuntu-bug failing to switch to firefox
https://bugs.launchpad.net/bugs/1969291
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xdg-utils in Ubuntu.

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

[Desktop-packages] [Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)

2022-07-26 Thread Olivier Tilloy

This appears to have regressed. I'm suspecting the changes in
https://github.com/snapcore/snapd/commit/5abb3aab6b74db5a9e9920c537d673806603349a.

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

Title:
  libreoffice help doesn't open in firefox (404 error on
  file:///tmp/lu417531j7po.tmp/NewHelp0.html)

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Jammy:
  Fix Released

Bug description:
  Ubuntu jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  Opened LibreOffice Writer as random apps in QA-test.
  Hit F1 to call help, and all I get is an error

  URL:  file:///tmp/lu417531j7po.tmp/NewHelp0.html

  ---
  File not found

  Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  Firefox opens as a snap; but it isn't accessing the data from
  LibreOffice.

  Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks-
  libreoffice-deb/27537

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465+canary3.3
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 17 04:46:33 2021
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1982852] Re: software hangs on "checking for updates"

2022-07-26 Thread Henning Sprang

And at the same time there are quite a lot of log entried from snapd:

$ journalctl --reverse _COMM=snapd
Jul 26 16:19:21 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:19:21 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:19:16 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:19:15 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:19:11 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:19:10 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:19:07 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:19:07 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:19:01 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:19:01 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:18:59 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:18:59 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:55 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:54 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:51 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:50 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:49 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:48 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:46 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:46 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:40 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:39 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:39 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:13:39 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:08:49 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:08:46 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:08:27 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium", "clion", "code", 
"core", "core18", "c>
Jul 26 16:08:21 tp-x1e snapd[2468]: storehelpers.go:722: cannot refresh: snap 
has no updates available: "bare", "blender", "chromium",

[Desktop-packages] [Bug 1982852] Re: software hangs on "checking for updates"

2022-07-26 Thread Henning Sprang

Here the journalctl entries for the app itself in this run:

$ journalctl --reverse _COMM=gnome-software 
Jul 26 16:29:06 tp-x1e gnome-software[5637]: user: Pulled appstream2/x86_64 
from flathub
Jul 26 16:29:06 tp-x1e gnome-software[5637]: libostree pull from 'flathub' for 
appstream2/x86_64 complete
 security: GPG: summary+commit 
 security: SIGN: disabled http: TLS
 non-delta: meta: 2 content: 0
 transfer: secs: 43 size: 592 bytes
Jul 26 16:28:28 tp-x1e gnome-software[5637]: user: Pulled appstream2/x86_64 
from flathub
Jul 26 16:28:28 tp-x1e gnome-software[5637]: libostree pull from 'flathub' for 
appstream2/x86_64 complete
 security: GPG: summary+commit 
 security: SIGN: disabled http: TLS
 non-delta: meta: 7 content: 31
 transfer: secs: 1207 size: 6,0 MB
Jul 26 16:09:24 tp-x1e gnome-software[5637]: failed to get featured apps: 
Timeout was reached as flatpak took too long to return results
Jul 26 16:09:24 tp-x1e gnome-software[5637]: failed to get popular apps: 
Timeout was reached as flatpak took too long to return results
Jul 26 16:09:24 tp-x1e gnome-software[5637]: failed to get recent apps: Timeout 
was reached as flatpak took too long to return results
Jul 26 16:09:19 tp-x1e gnome-software[5637]: 
/var/tmp/flatpak-cache-834JP1/org.freedesktop.Platform.GL.nvidia-515-48-07-ST4JP1/repo-xUp2pI:
 Pulled runtime/org.freedesktop.P>
Jul 26 16:08:18 tp-x1e gnome-software[5637]: libostree pull from 'flathub' for 
runtime/org.freedesktop.Platform.GL.nvidia-515-48-07/x86_64/1.4 complete
 security: GPG: summary+commit 
 security: SIGN: disabled http: TLS
 delta: parts: 1 loose: 3
 transfer: secs: 0 size: 592 bytes
Jul 26 16:08:15 tp-x1e gnome-software[5637]: user: Updated 
runtime/org.freedesktop.Platform.GL.nvidia-515-48-07/x86_64/1.4 from flathub
Jul 26 16:07:38 tp-x1e gnome-software[5637]: user: Pulled 
runtime/org.freedesktop.Platform.GL.nvidia-515-48-07/x86_64/1.4 from flathub
Jul 26 16:06:46 tp-x1e gnome-software[5637]: libostree pull from 'flathub' for 
runtime/org.freedesktop.Platform.GL.nvidia-515-48-07/x86_64/1.4 complete
 security: GPG: summary+commit 
 security: SIGN: disabled http: TLS
 delta: parts: 1 loose: 3
 transfer: secs: 0 size: 592 bytes
Jul 26 16:06:46 tp-x1e gnome-software[5637]: user: Updated 
runtime/org.freedesktop.Platform.GL.nvidia-510-73-05/x86_64/1.4 from flathub
Jul 26 16:06:12 tp-x1e gnome-software[5637]: user: Pulled 
runtime/org.freedesktop.Platform.GL.nvidia-510-73-05/x86_64/1.4 from flathub
Jul 26 16:05:24 tp-x1e gnome-software[5637]: libostree pull from 'flathub' for 
runtime/org.freedesktop.Platform.GL.nvidia-510-73-05/x86_64/1.4 complete
 security: GPG: summary+commit 
 security: SIGN: disabled http: TLS
 delta: parts: 1 loose: 3
 transfer: secs: 0 size: 592 bytes
Jul 26 16:05:24 tp-x1e gnome-software[5637]: user: Updated 
runtime/org.freedesktop.Platform.GL.nvidia-510-60-02/x86_64/1.4 from flathub
Jul 26 16:04:50 tp-x1e gnome-software[5637]: user: Pulled 
runtime/org.freedesktop.Platform.GL.nvidia-510-60-02/x86_64/1.4 from flathub
Jul 26 16:04:03 tp-x1e gnome-software[5637]: libostree pull from 'flathub' for 
runtime/org.freedesktop.Platform.GL.nvidia-510-60-02/x86_64/1.4 complete
 security: GPG: summary+commit 
 security: SIGN: disabled http: TLS
 delta: parts: 1 loose: 3
 transfer: secs: 0 size: 592 bytes
Jul 26 16:04:02 tp-x1e gnome-software[5637]: user: Updated 
runtime/org.freedesktop.Platform.GL.nvidia-470-86/x86_64/1.4 from flathub
Jul 26 16:03:34 tp-x1e gnome-software[5637]: user: Pulled 
runtime/org.freedesktop.Platform.GL.nvidia-470-86/x86_64/1.4 from flathub
Jul 26 16:02:54 tp-x1e gnome-software[5637]: libostree pull from 'flathub' for 
runtime/org.freedesktop.Platform.GL.nvidia-470-86/x86_64/1.4 complete
 security: GPG: summary+commit 
 security: SIGN: disabled http: TLS
 delta: parts: 1

[Desktop-packages] [Bug 1982852] [NEW] software hangs on "checking for updates"

2022-07-26 Thread Henning Sprang

Public bug reported:

Gnome software regularly seems to have problems with getting it's
updates or handle them properly.

It's not clearly reproducible, as sometimes it sems to work.

This time, the steps to get there were:

* open the gnome software app
* see some updates being offered
* click on update all
* wait a while
* return to the computer and see the application saying "checking..." at the 
top left
* wait for 10, 20, 30 minutes - but nothing changes, it keeps trying to fetch 
some updates, but I dont get any information from where and what and why it 
takes so long to just look if there are any updates or my installed 
applications are current

There are a bunch of journalctl entries maybe related to that, that I
will add in the comments for their size

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-software 41.5-2
ProcVersionSignature: Ubuntu 5.15.0-41.44-lowlatency 5.15.39
Uname: Linux 5.15.0-41-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 26 16:20:41 2022
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2020-04-12 (834 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InstalledPlugins:
 gnome-software-plugin-flatpak 41.5-2
 gnome-software-plugin-snap41.5-2
SourcePackage: gnome-software
UpgradeStatus: Upgraded to jammy on 2022-04-28 (88 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  software hangs on "checking for updates"

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Gnome software regularly seems to have problems with getting it's
  updates or handle them properly.

  It's not clearly reproducible, as sometimes it sems to work.

  This time, the steps to get there were:

  * open the gnome software app
  * see some updates being offered
  * click on update all
  * wait a while
  * return to the computer and see the application saying "checking..." at the 
top left
  * wait for 10, 20, 30 minutes - but nothing changes, it keeps trying to fetch 
some updates, but I dont get any information from where and what and why it 
takes so long to just look if there are any updates or my installed 
applications are current

  There are a bunch of journalctl entries maybe related to that, that I
  will add in the comments for their size

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-software 41.5-2
  ProcVersionSignature: Ubuntu 5.15.0-41.44-lowlatency 5.15.39
  Uname: Linux 5.15.0-41-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 26 16:20:41 2022
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2020-04-12 (834 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak 41.5-2
   gnome-software-plugin-snap41.5-2
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to jammy on 2022-04-28 (88 days ago)

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


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

[Desktop-packages] [Bug 1875937] Re: Download of vol1 in validate_encryption_settings() fails when using S3 glacier

2022-07-26 Thread Kenneth Loafman

Yes, this was fixed for boto+s3, but then we changed the default for
s3:// from boto to boto3.  Boto3 does not support glacier yet, so you
may just need to specify boto+s3:// instead.

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

Title:
  Download of vol1 in validate_encryption_settings() fails when using S3
  glacier

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Committed

Bug description:
  Duplicity version: 0.8.12.1612
  ubuntu 20.04 LTS
  python 3.8.2

  When i try to restart a backup which goes to S3 (via boto3) (use of:
  --s3-use-deep-archive or --s3-use-glacier) it fails:

  Last full backup date: Wed Apr 29 17:45:32 2020
  RESTART: Volumes 2 to 2 failed to upload before termination.
   Restarting backup at volume 2.
  Attempt 1 failed. ClientError: An error occurred (InvalidObjectState) when 
calling the GetObject operation: The operation is not valid for the object's 
storage class
  Attempt 2 failed. ClientError: An error occurred (InvalidObjectState) when 
calling the GetObject operation: The operation is not valid for the object's 
storage class

  This is because a file stored in glacier cannot be downloaded. I dont
  know if this known?

  To solve this: either skip validate_encryption_settings() when using
  any of this storage backends or introduce an option to skip the
  download manually (e.g. --skip-download-on-restart)

  I fixed it for me with manully skipping the
  validate_encryption_settings() function.

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


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

[Desktop-packages] [Bug 1982611] Re: GNOME Desktop Clashes when I close PiP of Firefox's

2022-07-26 Thread Oyamada Jun

This is a clash report's link.
https://errors.ubuntu.com/oops/112d520c-0ce5-11ed-96b0-fa163e993415

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

Title:
  GNOME Desktop Clashes when I close PiP of Firefox's

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:

  1. Start Firefox
  2. Open youtube.com
  3. Click a video
  4. Open a PiP
  5. Click "Show all workspace" in Context menu
 (However, Change workspace, and It was back workspace before)
  6. Close PiP to use left below button.
  7. GNOME desktop was logouted

  Environment:
  Ubuntu 22.04
  GNOME 42
  Wayland
  Firefox(Snap)
  User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 
Firefox/102.0

  https://bugzilla.mozilla.org/show_bug.cgi?id=1780768

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


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

[Desktop-packages] [Bug 1981716] Re: bbswitch fails to build on 5.19 kernel (kinetic)

2022-07-26 Thread Dimitri John Ledkov

This bug was fixed in the package bbswitch - 0.8-13
Sponsored for Andrea Righi (arighi)

---
bbswitch (0.8-13) unstable; urgency=medium

  * Use experimental dkms feature BUILD_EXCLUSIVE_CONFIG="CONFIG_ACPI".
  * Add patch for Linux 5.18 from Arch Linux.  (Closes: #1012560, #1012779)
  * Update Standards version to 4.6.1, no changes required.

 -- Andreas Beckmann   Sat, 18 Jun 2022 14:09:20 +0200

bbswitch (0.8-12) unstable; urgency=medium

  [ Andrea Righi ]
  * Drop support for armhf and ppc64el (LP: #1956434)

  [ Andreas Beckmann ]
  * Drop ACPI patch from 0.8-11.
  * Restrict the autopkgtest to supported architectures.

 -- Andreas Beckmann   Mon, 11 Apr 2022 16:05:04 +0200

bbswitch (0.8-11) unstable; urgency=medium

  [ Andrea Righi ]
  * Fix build error on architectures that don't have ACPI enabled
(LP: #1951583)

  [ Andreas Beckmann ]
  * Switch to dh-sequence-dkms.

  [ Debian Janitor ]
  * Remove constraints unnecessary since buster:
+ Build-Depends: Drop versioned constraint on tar.
  * Update watch file format version to 4.
  * Update standards version to 4.6.0, no changes needed.

 -- Andreas Beckmann   Thu, 10 Feb 2022 00:18:18 +0100

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

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

Title:
  bbswitch fails to build on 5.19 kernel (kinetic)

Status in bbswitch package in Ubuntu:
  Fix Released
Status in bbswitch source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  bbswitch fails to build with the latest 5.19 kernel, the error is the
  following:

  /var/lib/dkms/bbswitch/0.8/build/bbswitch.c:273:13: error: implicit 
declaration of function ‘acpi_bus_get_device’; did you mean 
‘acpi_is_pnp_device’? [-Werror=implicit-function-declaration]
273 | r = acpi_bus_get_device(dis_handle, );
| ^~~
| acpi_is_pnp_device
  cc1: some warnings being treated as errors

  
  [Test case]

  $ sudo apt install bbswitch-dkms

  [Fix]

  Replace acpi_bus_get_device() with the equivalent interface -
  acpi_fetch_acpi_dev() - in 5.19 kernels.

  [Regression potential]

  We may see bbswitch regressions in kernels >= 5.19 (fix isn't
  affecting older kernels).

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


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

[Desktop-packages] [Bug 1956916] Re: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session

2022-07-26 Thread Alex Boiko

Same issue with Alt+Shift on Ubuntu 22.04

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

Title:
  Using certain xkb-options, e.g. Alt+Shift, for switching input sources
  not reflected by the input source indicator in a wayland session

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

Bug description:
  Currently, there is no way to define Left Alt + Left Shift key combination to 
change keyboard layouts in Ubuntu 22.04. In previous versions there was a 
convenient "Keyboard Layout Options" window in which there was able to set 
required key combination. Since 22.04 release I can't find a way to do that 
because useless "Keyboard Shortcuts" window opens instead in which unable to 
set Left Alt + Left Shift as "Switch to the next source" shortcut.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-01-07 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  jammy wayland-session ubiquity-22.04.3
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1981966] Re: [SRU] libreoffice 7.3.5 for jammy

2022-07-26 Thread Rico Tzschichholz

Upgraded libreoffice from 1:7.3.4-0ubuntu0.22.04.1 to
1:7.3.5-0ubuntu0.22.04.1 from jammy-proposed in a clean and up-to-date
jammy amd64 VM, and successfully ran test plan at
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice.

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

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

Title:
   [SRU] libreoffice 7.3.5 for jammy

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 7.3.5 is in its fifth bugfix release of the 7.3 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.5_release

   * Version 7.3.4 is currently released in jammy. For a list of fixed bugs 
compared to 7.3.4 see the list of bugs fixed in the release candidates of 7.3.5 
(that's a total of 83 bugs):
   https://wiki.documentfoundation.org/Releases/7.3.5/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.3.5/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_73/1797/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220719_091411_74233@/log.gz
  * [arm64] ...
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220719_110142_388ca@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220719_082728_0b9aa@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220719_080609_7c067@/log.gz
   * General smoke testing of all the applications in the office suite were 
carried out by going through the manual testplan as documented by: 
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

  [Regression Potential]

   * A minor release with a total of 83 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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


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

[Desktop-packages] [Bug 1967121] Update Released

2022-07-26 Thread Łukasz Zemczak

The verification of the Stable Release Update for gnome-shell-extension-
ubuntu-dock has completed successfully and the package is now being
released to -updates.  Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report.  In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.

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

Title:
  Dock auto-hides when a right click context menu is opened while a
  window is under the dock

Status in Dash to dock:
  Fix Released
Status in ubuntu-dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  If the dock is set to auto-hide and a window is under the dock, then
  the dock hides prematurely when a menu is opened from one of its
  icons. This only seems to happen with GNOME 42.

  [Test Plan]

  1. Set the dock to auto hide.
  2. Move a window under the dock's position so that it wants to auto-hide.
  3. Open the dock and right click on one of the icons to open a menu.

  Expected: Dock stays open while the menu is open.
  Observed: Dock closes while the menu is open.

  [Where problems could occur]

  This fix may affect any scenarios relating to the dock auto-hiding.

  [Other Info]

  Upstream fixes:
  ubuntu-dock: https://github.com/micheleg/dash-to-dock/pull/1739
  dash-to-dock: https://github.com/micheleg/dash-to-dock/pull/1751

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+subscriptions


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

[Desktop-packages] [Bug 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock

This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
72~ubuntu5.22.04.1

---
gnome-shell-extension-ubuntu-dock (72~ubuntu5.22.04.1) jammy; urgency=medium

  [ Daniel van Vugt ]
  * Ignore loss of the hover state while a menu is open (LP: #1967121):
- dash: Add a 'menu-opened' signal
- appIcons: Remember to emit menu-state-changed for _previewMenu
- docking: Ignore loss of the hover state while a menu is open

  [ Marco Trevisan (Treviño) ]
  * debian: Update references for jammy branching

 -- Marco Trevisan (Treviño)   Fri, 08 Jul 2022
06:08:23 +0200

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Dock auto-hides when a right click context menu is opened while a
  window is under the dock

Status in Dash to dock:
  Fix Released
Status in ubuntu-dock:
  Unknown
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  If the dock is set to auto-hide and a window is under the dock, then
  the dock hides prematurely when a menu is opened from one of its
  icons. This only seems to happen with GNOME 42.

  [Test Plan]

  1. Set the dock to auto hide.
  2. Move a window under the dock's position so that it wants to auto-hide.
  3. Open the dock and right click on one of the icons to open a menu.

  Expected: Dock stays open while the menu is open.
  Observed: Dock closes while the menu is open.

  [Where problems could occur]

  This fix may affect any scenarios relating to the dock auto-hiding.

  [Other Info]

  Upstream fixes:
  ubuntu-dock: https://github.com/micheleg/dash-to-dock/pull/1739
  dash-to-dock: https://github.com/micheleg/dash-to-dock/pull/1751

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+subscriptions


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

[Desktop-packages] [Bug 1970013] Update Released

2022-07-26 Thread Łukasz Zemczak

The verification of the Stable Release Update for gstreamer-vaapi has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Totem Video player displays distorted video (Intel Ivy Bridge)

Status in Gstreamer1.0:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid
Status in gstreamer-vaapi source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Videos are unplayable in apps like Ubuntu's default video player for people 
using some Intel graphics cards including Ivy Bridge.

  Test Case
  -
  On an affected system, install the update.
  Then try playing the video.
  It should display normally.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

  Original Bug Report
  ---
  Ubuntu 22.04 freshly installed along with ubuntu-restricted-extra package. 
Default totem player unable to play videos properly. videos looks distorted. 
Forwarding videos does not work. Video get stopped once forwarded.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 23 11:02:49 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2022-04-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 34601F4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.release: 2.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34601F4
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 34601F4
  dmi.product.sku: LENOVO_MT_3460
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1970013/+subscriptions


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

[Desktop-packages] [Bug 1970013] Re: Totem Video player displays distorted video (Intel Ivy Bridge)

This bug was fixed in the package gstreamer-vaapi - 1.20.1-1ubuntu1

---
gstreamer-vaapi (1.20.1-1ubuntu1) jammy; urgency=medium

  * Cherry-pick 1.20.3 fix for scrambled videos for some Intel systems
(LP: #1970013)

 -- Jeremy Bicha   Mon, 11 Jul 2022 09:39:43 +0200

** Changed in: gstreamer-vaapi (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Totem Video player displays distorted video (Intel Ivy Bridge)

Status in Gstreamer1.0:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid
Status in gstreamer-vaapi source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Videos are unplayable in apps like Ubuntu's default video player for people 
using some Intel graphics cards including Ivy Bridge.

  Test Case
  -
  On an affected system, install the update.
  Then try playing the video.
  It should display normally.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

  Original Bug Report
  ---
  Ubuntu 22.04 freshly installed along with ubuntu-restricted-extra package. 
Default totem player unable to play videos properly. videos looks distorted. 
Forwarding videos does not work. Video get stopped once forwarded.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 23 11:02:49 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2022-04-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 34601F4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.release: 2.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34601F4
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 34601F4
  dmi.product.sku: LENOVO_MT_3460
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer1.0/+bug/1970013/+subscriptions


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

[Desktop-packages] [Bug 1966911] Re: Cannot enroll finger on Jammy

This bug was fixed in the package libfprint -
1:1.94.3+tod1-0ubuntu2~22.04.01

---
libfprint (1:1.94.3+tod1-0ubuntu2~22.04.01) jammy; urgency=medium

  * debian/patches: Ensure that identify works with old goodix driver
(LP: #1966911)
  * debian: Update references to jammy branch

 -- Marco Trevisan (Treviño)   Sun, 17 Jul 2022
17:39:59 +0200

** Changed in: libfprint (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Cannot enroll finger on Jammy

Status in libfprint-2-tod1-goodix:
  Fix Committed
Status in OEM Priority Project:
  Confirmed
Status in fprintd package in Ubuntu:
  Won't Fix
Status in libfprint package in Ubuntu:
  Fix Released
Status in fprintd source package in Jammy:
  Invalid
Status in libfprint source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  Cannot enroll finger on Jammy (goodix tod driver)

  [Test plan]
  1. Install Jammy on XPS-9310
  2. Open Gnome-control-center and select `User`
  3. Enroll fingerprint

  1. Find another Laptop with fingerprint device and test on Jammy

  [Where problems could occur]
  * This change will only affect fingerprint tod driver

  The changes are mostly in the wrapper for the goodix driver so the
  focus should be on testing if finger print enrollment and
  identification is working on those devices during both authentication
  and finger enrollment (especially when no other fingerprints have been
  already enrolled).

  The only possible regression may happen in goodix devices using the
  TOD driver that may not been able to enroll or log-in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions


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

[Desktop-packages] [Bug 1648319] Re: Failed to use bus name org.freedesktop.DisplayManager

2022-07-26 Thread Pedro Serrano

Folks,

I get the Same error.

lightdm --test-mode 
Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate 
permissions?

It's been a few years without activity...  Thanks for your attention.

Regards

Pedro

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

Title:
  Failed to use bus name org.freedesktop.DisplayManager

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I have implemented the command lightdm --test-mode --debug and I happened 
here such error:
  ==
  [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Using Xephyr for X servers
  [+0.01s] DEBUG: Registered seat module xlocal
  [+0.01s] DEBUG: Registered seat module xremote
  [+0.01s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Registered seat module surfaceflinger
  [+1.13s] DEBUG: Adding default seat
  [+1.13s] DEBUG: Seat: Starting
  [+1.13s] DEBUG: Seat: Creating greeter session
  [+1.17s] DEBUG: Seat: Creating display server of type x
  [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+1.20s] DEBUG: Using VT 7
  [+1.20s] DEBUG: Seat: Starting local X display on VT 7
  [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+1.36s] DEBUG: DisplayServer x-1: Launching X Server
  [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+1.36s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  Failed to use bus name org.freedesktop.DisplayManager, do you have 
appropriate permissions?
  =
  On the Internet I have the exact solution to this problem is not found. The 
computer I have is only one graphics card and built-in The controller is not 
present. Somebody help than you can!

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


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

[Desktop-packages] [Bug 1648319] Re: Failed to use bus name org.freedesktop.DisplayManager

2022-07-26 Thread Pedro Serrano

BTW..
root@###:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename:   jammy
root@###:~# apt list lightdm --installed
Listing... Done
lightdm/jammy,now 1.30.0-0ubuntu5 amd64 [installed,automatic]

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

Title:
  Failed to use bus name org.freedesktop.DisplayManager

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I have implemented the command lightdm --test-mode --debug and I happened 
here such error:
  ==
  [+0.01s] DEBUG: Logging to /var/log/lightdm/lightdm.log
  [+0.01s] DEBUG: Starting Light Display Manager 1.10.3, UID=0 PID=1683
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/var/lib/menu-xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/gdm/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
  [+0.01s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration dirs from 
/etc/xdg/lightdm/lightdm.conf.d
  [+0.01s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
  [+0.01s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
  [+0.01s] DEBUG: Using Xephyr for X servers
  [+0.01s] DEBUG: Registered seat module xlocal
  [+0.01s] DEBUG: Registered seat module xremote
  [+0.01s] DEBUG: Registered seat module unity
  [+0.01s] DEBUG: Registered seat module surfaceflinger
  [+1.13s] DEBUG: Adding default seat
  [+1.13s] DEBUG: Seat: Starting
  [+1.13s] DEBUG: Seat: Creating greeter session
  [+1.17s] DEBUG: Seat: Creating display server of type x
  [+1.20s] DEBUG: Could not run plymouth --ping: Failed to execute child 
process "plymouth" (No such file or directory)
  [+1.20s] DEBUG: Using VT 7
  [+1.20s] DEBUG: Seat: Starting local X display on VT 7
  [+1.20s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+1.36s] DEBUG: DisplayServer x-1: Writing X server authority to 
/var/run/lightdm/root/:1
  [+1.36s] DEBUG: DisplayServer x-1: Launching X Server
  [+1.36s] DEBUG: Launching process 1687: /usr/bin/Xephyr :1 -seat seat0 -auth 
/var/run/lightdm/root/:1 -nolisten tcp vt7 -novtswitch
  [+1.36s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
  [+1.36s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+1.36s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  Failed to use bus name org.freedesktop.DisplayManager, do you have 
appropriate permissions?
  =
  On the Internet I have the exact solution to this problem is not found. The 
computer I have is only one graphics card and built-in The controller is not 
present. Somebody help than you can!

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


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

[Desktop-packages] [Bug 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()

Upstream says the crash is caused by a leak and reviewing the Mesa code
seems to support that theory. The fix is:

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17731

** Tags added: gnome-shell-leak

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

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Committed

** Tags added: fixed-in-23 fixed-upstream

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

Title:
  gnome-shell crashed with SIGSEGV in crocus_begin_query() from
  crocus_begin_query() from crocus_end_query() from crocus_end_query()
  from tc_call_end_query()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Committed

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

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


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

[Desktop-packages] [Bug 1972977] Re: gnome-shell crashed with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query()

Only fixed in Mesa 23 right now but I would expect to see it in 22.x

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

Title:
  gnome-shell crashed with SIGSEGV in crocus_begin_query() from
  crocus_begin_query() from crocus_end_query() from crocus_end_query()
  from tc_call_end_query()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Committed

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

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


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

[Desktop-packages] [Bug 1959469] Re: [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

2022-07-26 Thread Bug Watch Updater

** Changed in: nettle (Debian)
   Status: Unknown => New

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

Title:
  [22.10 FEAT] Upgrade nettle to latest version >= 3.7.4 (crypto)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in nettle package in Ubuntu:
  In Progress
Status in nettle package in Debian:
  New

Bug description:
  Upgrade nettle to latest version >= 3.7.4 (crypto)

  Description

  Upgrade nettle to latest version >= 3.7.4 to provide CPACF Support for
  Crypto Libraries.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1959469/+subscriptions


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

[Desktop-packages] [Bug 1980934] Re: Backup fail with unknown error

2022-07-26 Thread Dash

Michael, I still have this issue. Do you will do something ?

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

Title:
  Backup fail with unknown error

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  I removed the cache and start a backup in console like

  DEJA_DUP_DEBUG=1 deja-dup

  and got during verification the Unknown Error with following final
  outputs

  DUPLICITY: DEBUG 1
  DUPLICITY: . Found manifest volume 845

  DUPLICITY: INFO 1
  DUPLICITY: . Found 845 volumes in manifest

  DUPLICITY: DEBUG 1
  DUPLICITY: . Releasing lockfile 
b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile'

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-7zeqbwou-tempdir/mkstemp-oc2otu7o-1

  DUPLICITY: DEBUG 1
  DUPLICITY: . Releasing lockfile 
b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile'

  DUPLICITY: DEBUG 1
  DUPLICITY: . Releasing lockfile 
b'/home/dh/.cache/deja-dup/5ed9f811abd16462101b9c5a817fde92/lockfile'

  I than checked the cache which still contains all files including the
  lockfile

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: deja-dup 40.7-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  7 10:55:01 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  InstallationDate: Installed on 2019-12-07 (942 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to focal on 2020-10-04 (640 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1980934/+subscriptions


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

[Desktop-packages] [Bug 1982813] Re: My 16G of ram is fully consumed, GNOME is accused for that

** Description changed:

  MiB Mem :  15416.8 total,153.8 free,  13968.0 used,   1294.9 buff/cache
- MiB Swap:   1000.0 total,436.7 free,563.2 used.948.8 avail Mem 
+ MiB Swap:   1000.0 total,436.7 free,563.2 used.948.8 avail Mem
  
- PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
COMMAND  
-4802 yazid 20   0 5857452 190408  63240 S  31.9   1.2   0:45.75 
gnome-s+ 
-4605 yazid 20   0 1784448  81320  25656 S   9.3   0.5   0:15.39 Xorg   
  
-5651 yazid 20   0   40.7g 210336  53800 S   7.3   1.3   0:31.98 slack  
  
-5669 yazid 20   0   32.9g 335208 129884 S   3.0   2.1   1:10.58 chrome 
  
-   10208 yazid 20   0   44.5g 167836 100656 S   2.7   1.1   0:06.01 chrome 
  
-5742 yazid 20   0   32.9g 170944  83368 S   2.3   1.1   0:28.23 chrome 
  
-8590 yazid 20   0  818376  44772  32136 S   2.3   0.3   0:02.28 
gnome-t+ 
- 177 root  20   0   0  0  0 S   1.0   0.0   0:05.48 
kswapd0  
- 725 root  -2   0   0  0  0 S   1.0   0.0   0:01.43 gfx
  
-1754 elastic+  20   0   16.1g   8.1g  15664 S   1.0  53.5   1:12.76 java   
  
-4326 yazid 20   0  198920  35848   6696 S   1.0   0.2   0:20.51 
python3  
-5226 root  20   0   0  0  0 I   1.0   0.0   0:01.11 
kworker+ 
-5502 root  20   0   0  0  0 I   1.0   0.0   0:01.74 
kworker+ 
-5743 yazid 20   0   32.4g 104040  63900 S   1.0   0.7   0:24.34 chrome 
  
-  14 root  20   0   0  0  0 I   0.3   0.0   0:01.58 
rcu_sch+ 
-  22 root  20   0   0  0  0 I   0.3   0.0   0:00.53 
kworker+ 
- 188 root  20   0   0  0  0 I   0.3   0.0   0:01.49 
kworker+
+ PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
+    4802 yazid 20   0 5857452 190408  63240 S  31.9   1.2   0:45.75 
gnome-s+
+    4605 yazid 20   0 1784448  81320  25656 S   9.3   0.5   0:15.39 Xorg
+    5651 yazid 20   0   40.7g 210336  53800 S   7.3   1.3   0:31.98 slack
+    5669 yazid 20   0   32.9g 335208 129884 S   3.0   2.1   1:10.58 chrome
+   10208 yazid 20   0   44.5g 167836 100656 S   2.7   1.1   0:06.01 chrome
+    5742 yazid 20   0   32.9g 170944  83368 S   2.3   1.1   0:28.23 chrome
+    8590 yazid 20   0  818376  44772  32136 S   2.3   0.3   0:02.28 
gnome-t+
+ 177 root  20   0   0  0  0 S   1.0   0.0   0:05.48 kswapd0
+ 725 root  -2   0   0  0  0 S   1.0   0.0   0:01.43 gfx
+    1754 elastic+  20   0   16.1g   8.1g  15664 S   1.0  53.5   1:12.76 java
+    4326 yazid 20   0  198920  35848   6696 S   1.0   0.2   0:20.51 python3
+    5226 root  20   0   0  0  0 I   1.0   0.0   0:01.11 
kworker+
+    5502 root  20   0   0  0  0 I   1.0   0.0   0:01.74 
kworker+
+    5743 yazid 20   0   32.4g 104040  63900 S   1.0   0.7   0:24.34 chrome
+  14 root  20   0   0  0  0 I   0.3   0.0   0:01.58 
rcu_sch+
+  22 root  20   0   0  0  0 I   0.3   0.0   0:00.53 
kworker+
+ 188 root  20   0   0  0  0 I   0.3   0.0   0:01.49 
kworker+
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 26 10:00:02 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-09-10 (318 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2022-07-06T00:07:26.728431

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

Title:
  My 16G of ram is fully consumed, GNOME is accused for that

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  MiB Mem :  15416.8 total,153.8 free,  13968.0 used,   1294.9 buff/cache
  MiB Swap:   1000.0 total,436.7 free,563.2 used.948.8 avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
     4802 yazid 20   0 5857452 190408  63240 S  31.9   1.2   0:45.75 
gnome-s+
     4605 yazid 20   0 1784448  81320  25656 S   9.3   0.5   0:15.39 Xorg
     5651 yazid 20   0   40.7g 210336  53800 S   7.3   1.3   0:31.98 slack
     5669 yazid 20   0   32.9g 335208 129884 S   3.0   2.1   1:10.58 chrome
    10208 yazid 20   0   44.5g 167836 100656 S   2.7   1.1   0:06.01 chrome
     5742 yazid 20   0   32.9g

[Desktop-packages] [Bug 1982813] Re: My 16G of ram is fully consumed, GNOME is accused for that