date:20220511

I'm guessing this was fixed at some point between extension v33 (focal)
and v42 (jammy). Not sure where though.

** Tags added: focal

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

Title:
  Crash of gnome shell potentially from "JS ERROR: too much recursion"
  from app indicators

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

Bug description:
  What Happened:
  1) Have gnome-shell-extensions-appindicator enabled
  2) The only running app using the indicator was charmtimetracker ( 
https://github.com/KDAB/Charm )
  3) At some point usually within 1-2 days of office usage gnome shell crashes
  4) Notice "JS ERROR: too much recursion" and then a stacktrace coming from 
appindicator extension in journalctl

  
  What I expected to happen:
  For gnome-shell not to crash :-)

  
  Full logs:
- Recursion warnings - https://pastebin.ubuntu.com/p/hfKMmH4Dpx/
- Stack trace - https://pastebin.ubuntu.com/p/2TC6WFVcsG/

  
  Short Summary of Logs:
  === First sign of incoming crash ===

  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: too much recursion
set 
active@resource:///org/gnome/shell/ui/popupMenu.js:199:29

_init@resource:///org/gnome/shell/ui/popupMenu.js:104:18

_init@resource:///org/gnome/shell/ui/popupMenu.js:273:15

createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:498:29

createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60

  === This continues many times, last instance is like this ===

  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: Exception in 
callback for signal: child-added: too much recursion

PopupSubMenu@resource:///org/gnome/shell/ui/popupMenu.js:1017:9

_init@resource:///org/gnome/shell/ui/popupMenu.js:1201:21

createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:494:29

createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60

  === Then there is a stacktrace (shortened repeats) ===

  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: The offending signal was 
notify on StLabel 0x5615bd3eee80.
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: == Stack trace for context 
0x56159bbee930 ==
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #0   7ffca7535bb0 b   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:620
 (1c7e392cc2e0 @ 100)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #1   7ffca7535c80 b   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:510
 (1c7e392cae98 @ 357)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #2   5615a5c69340 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:771
 (1c7e392cc880 @ 41)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #3   7ffca7536b70 b   
self-hosted:1013 (264b03e13e20 @ 492)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #4   7ffca7536c60 b   
self-hosted:1013 (264b03e13e20 @ 492)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #5   7ffca7536d70 b   
resource:///org/gnome/gjs/modules/core/_signals.js:133 (1c7e392a84c0 @ 427)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #6   5615a5c69290 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:134
 (1c7e392c5c40 @ 74)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #7   7ffca7537c80 b   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:365
 (1c7e392ca718 @ 837)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #8   5615a5c690d0 i   
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:326
 (1c7e392ca6a0 @ 423)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #9   7ffca7538970 b   
self-hosted:1013 (264b03e13e20 @ 492)
  Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #10   5615a5c69018 i   
resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2784371926a0 @ 312)

  
  Versions:
  $ lsb_r

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => Daniel van Vugt (vanvugt)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Triaged => In Progress

-- 
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 gnome-shell-extension-ubuntu-dock package in Ubuntu:
  In Progress
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Triaged

Bug description:
  Currently testing a fresh install of the beta for 22.04.
  All packages are up to date.

  When having the dock auto-hide option enabled, a glitch occurs when opening 
the windows selector (when multiple instances of the same program are opened).
  The selector does open, but the dock will hide itself immediately instead of 
waiting for a selection. Selecting a window will then cause a glitch where the 
selector will align with the hidden dock in a non natural way before 
disappearing.

  A proposed fix would be to prevent the dock from auto-hiding when the
  miniatures selector opens and wait for a second input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-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 1973122] Re: Desktop freezes with infinite recursion in createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1910613, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1910613
   Crash of gnome shell potentially from "JS ERROR: too much recursion" from 
app indicators

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

Title:
  Desktop freezes with infinite recursion in
  createItem@/usr/share/gnome-shell/extensions/ubuntu-
  appindicat...@ubuntu.com/dbusMenu.js:520:60

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

Bug description:
  My desktop froze two times in the last couple of days.

  I have no clue which action led to this.

  All windows are frozen then, I still can move the mouse and I finally
  need to hit the power button for a hard reset.

  /var/crash does not show anything from this week:

  ```
  ❯ ls -la /var/crash/
  total 1020
  drwxrwsrwt  2 rootwhoopsie4096 Mai 11 07:36 .
  drwxr-xr-x 15 rootroot4096 Jan 21 17:32 ..
  -rw-r-  1 systemd-resolve whoopsie 1030995 Mai  4 18:20 
_usr_lib_systemd_systemd-resolved.101.crash
  -rw-r--r--  1 rootwhoopsie   0 Mai  4 19:17 
_usr_lib_systemd_systemd-resolved.101.upload
  -rw---  1 whoopsiewhoopsie  37 Mai  4 19:17 
_usr_lib_systemd_systemd-resolved.101.uploaded
  ```

  The logfile shows the following suspiscous line:
  Mai 12 06:57:12 XPS-13-9310 gnome-shell[12865]: JS ERROR: too much recursion

  I am running Ubuntu 20.04 on a Dell XPS - but I'd guess this
  information is included in some data.

  Thanks for having a look,
  Jürgen
  Launchpad team

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
  Uname: Linux 5.14.0-1034-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 12 07:25:55 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X55.1
  InstallationDate: Installed on 2021-09-15 (238 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  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-extension-appindicator/+bug/1973122/+subscriptions


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

[Desktop-packages] [Bug 1973122] Re: Desktop freezes without conscious action from my side

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

Yes the recursion error looks like the issue. It's coming from:
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com

so please open the Extensions app (from package gnome-shell-extension-
prefs) and disable 'Ubuntu AppIndicators'.

** Summary changed:

- Desktop freezes without conscious action from my side
+ Desktop freezes with infinite recursion in 
createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60

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

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

Title:
  Desktop freezes with infinite recursion in
  createItem@/usr/share/gnome-shell/extensions/ubuntu-
  appindicat...@ubuntu.com/dbusMenu.js:520:60

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

Bug description:
  My desktop froze two times in the last couple of days.

  I have no clue which action led to this.

  All windows are frozen then, I still can move the mouse and I finally
  need to hit the power button for a hard reset.

  /var/crash does not show anything from this week:

  ```
  ❯ ls -la /var/crash/
  total 1020
  drwxrwsrwt  2 rootwhoopsie4096 Mai 11 07:36 .
  drwxr-xr-x 15 rootroot4096 Jan 21 17:32 ..
  -rw-r-  1 systemd-resolve whoopsie 1030995 Mai  4 18:20 
_usr_lib_systemd_systemd-resolved.101.crash
  -rw-r--r--  1 rootwhoopsie   0 Mai  4 19:17 
_usr_lib_systemd_systemd-resolved.101.upload
  -rw---  1 whoopsiewhoopsie  37 Mai  4 19:17 
_usr_lib_systemd_systemd-resolved.101.uploaded
  ```

  The logfile shows the following suspiscous line:
  Mai 12 06:57:12 XPS-13-9310 gnome-shell[12865]: JS ERROR: too much recursion

  I am running Ubuntu 20.04 on a Dell XPS - but I'd guess this
  information is included in some data.

  Thanks for having a look,
  Jürgen
  Launchpad team

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
  Uname: Linux 5.14.0-1034-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 12 07:25:55 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X55.1
  InstallationDate: Installed on 2021-09-15 (238 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  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-extension-appindicator/+bug/1973122/+subscriptions


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

[Desktop-packages] [Bug 1973122] [NEW] Desktop freezes without conscious action from my side

2022-05-11 Thread Jürgen Gmach

Public bug reported:

My desktop froze two times in the last couple of days.

I have no clue which action led to this.

All windows are frozen then, I still can move the mouse and I finally
need to hit the power button for a hard reset.

/var/crash does not show anything from this week:

```
❯ ls -la /var/crash/
total 1020
drwxrwsrwt  2 rootwhoopsie4096 Mai 11 07:36 .
drwxr-xr-x 15 rootroot4096 Jan 21 17:32 ..
-rw-r-  1 systemd-resolve whoopsie 1030995 Mai  4 18:20 
_usr_lib_systemd_systemd-resolved.101.crash
-rw-r--r--  1 rootwhoopsie   0 Mai  4 19:17 
_usr_lib_systemd_systemd-resolved.101.upload
-rw---  1 whoopsiewhoopsie  37 Mai  4 19:17 
_usr_lib_systemd_systemd-resolved.101.uploaded
```

The logfile shows the following suspiscous line:
Mai 12 06:57:12 XPS-13-9310 gnome-shell[12865]: JS ERROR: too much recursion

I am running Ubuntu 20.04 on a Dell XPS - but I'd guess this information
is included in some data.

Thanks for having a look,
Jürgen
Launchpad team

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
Uname: Linux 5.14.0-1034-oem x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 12 07:25:55 2022
DisplayManager: gdm3
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X55.1
InstallationDate: Installed on 2021-09-15 (238 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/bugs/1973122/+attachment/5588901/+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/1973122

Title:
  Desktop freezes without conscious action from my side

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  My desktop froze two times in the last couple of days.

  I have no clue which action led to this.

  All windows are frozen then, I still can move the mouse and I finally
  need to hit the power button for a hard reset.

  /var/crash does not show anything from this week:

  ```
  ❯ ls -la /var/crash/
  total 1020
  drwxrwsrwt  2 rootwhoopsie4096 Mai 11 07:36 .
  drwxr-xr-x 15 rootroot4096 Jan 21 17:32 ..
  -rw-r-  1 systemd-resolve whoopsie 1030995 Mai  4 18:20 
_usr_lib_systemd_systemd-resolved.101.crash
  -rw-r--r--  1 rootwhoopsie   0 Mai  4 19:17 
_usr_lib_systemd_systemd-resolved.101.upload
  -rw---  1 whoopsiewhoopsie  37 Mai  4 19:17 
_usr_lib_systemd_systemd-resolved.101.uploaded
  ```

  The logfile shows the following suspiscous line:
  Mai 12 06:57:12 XPS-13-9310 gnome-shell[12865]: JS ERROR: too much recursion

  I am running Ubuntu 20.04 on a Dell XPS - but I'd guess this
  information is included in some data.

  Thanks for having a look,
  Jürgen
  Launchpad team

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21
  Uname: Linux 5.14.0-1034-oem x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 12 07:25:55 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X55.1
  InstallationDate: Installed on 2021-09-15 (238 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2
  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/1973122/+subscriptions


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

[Desktop-packages] [Bug 1936254]

2022-05-11 Thread Ilmari-lauhakangas

Probably this should be discussed on the developer mailing list

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

Title:
  [snap] 7.2.0.1 build from tarball fails to find modules

Status in LibreOffice:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  The LO snap builds from the upstream tarballs. In this case, we're building 
from (in the snapcraft.yaml):
  
http://download.documentfoundation.org/libreoffice/src/7.2.0/libreoffice-7.2.0.1.tar.xz

  The snap repo commit being built:
  https://git.launchpad.net/~hellsworth/+git/libreoffice-
  snap/commit/?id=d8a871e0d330928885201dcaafdec30dfb0c7b61

  The build failure:
  
https://launchpadlibrarian.net/548455036/buildlog_snap_ubuntu_focal_amd64_libreoffice-7.2-wip_BUILDING.txt.gz

  Locally, I've reproduced this failure and the modules are there, just
  not in the expected place.

  snapcraft-libreoffice # find . -name Module_helpcontent2.mk
  
./parts/libreoffice/build/src/libreoffice-help-7.2.0.1/helpcontent2/Module_helpcontent2.mk

  Looking through the libreoffice source changes, I believe this commit is the 
culprit:
  
https://cgit.freedesktop.org/libreoffice/core/commit/?id=f3b7dc649bc384be6000d98a87763cab26fe3f32

  Reverting this commit in a patch gets past the issue and the build
  resumes.

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


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

[Desktop-packages] [Bug 1069056] Re: Vdpau doesn't work.

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

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

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

Title:
  Vdpau doesn't work.

Status in libvdpau package in Ubuntu:
  Expired

Bug description:
  When I try to see video through SMplayer using vdpau playback not
  starts.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libvdpau1 0.4.1-6ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  304.48  Sun Sep  9 20:22:29 PDT 
2012
   GCC version:  gcc version 4.6.3 20120918 (prerelease) (Ubuntu/Linaro 
4.6.3-10ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  CompositorRunning: compiz
  Date: Sat Oct 20 14:55:40 2012
  DistUpgraded: 2012-10-18 21:44:12,436 DEBUG enabling apt cron job
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-experimental-304, 304.48, 3.5.0-17-generic, i686: installed
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8600M GS] [10de:0425] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: LG Electronics, Inc. Device [1854:0094]
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  JockeyStatus:
   kmod:nvidia_current - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
   kmod:nvidia_experimental_304 - nvidia_experimental_304 (Proprietary, 
Enabled, Not in use)
   kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library 
(Proprietary, Disabled, Not in use)
   kmod:nvidia_current_updates - NVIDIA binary Xorg driver, kernel module and 
VDPAU library (Proprietary, Disabled, Not in use)
   kmod:nvidia_173_updates - NVIDIA binary Xorg driver, kernel module and VDPAU 
library (Proprietary, Disabled, Not in use)
  MachineType: LG Electronics R500-U.CP21R1
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=2fef8c52-728a-472a-adf2-2d0850497714 ro quiet splash vt.handoff=7
  SourcePackage: libvdpau
  UpgradeStatus: Upgraded to quantal on 2012-10-18 (1 days ago)
  dmi.bios.date: 08/29/2007
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: COLSSF10
  dmi.board.name: COLUMBIA
  dmi.board.vendor: LG Electronics
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrCOLSSF10:bd08/29/2007:svnLGElectronics:pnR500-U.CP21R1:pvrNotApplicable:rvnLGElectronics:rnCOLUMBIA:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A:
  dmi.product.name: R500-U.CP21R1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: LG Electronics
  version.compiz: compiz 1:0.9.8.4-0ubuntu3
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3

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


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

[Desktop-packages] [Bug 1395271] Re: USB 1 and USB 2 scanners fail when connected to USB 3 ports

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

** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  USB 1 and USB 2 scanners fail when connected to USB 3 ports

Status in sane-backends package in Ubuntu:
  Expired

Bug description:
  Plugging a number of USB 1 and USB 2 scanners into the USB 2 port of
  various computers works as expected. Moving the scanners to the USB 3
  port of the same computers causes the scanners to stop working. The
  scanners are recognized by sane-find-scanner, but fail to scan. The
  difference appears to be the USB 2 ports using ehci-pci and the USB 3
  ports using xhci_hcd.

  The problem is becoming more serious as new computers come out with
  only USB 3 ports and no option to disable xhci_hcd in the bios.

  Is there a workaround or fix for this problem?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1395271/+subscriptions


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

[Desktop-packages] [Bug 1395003] Re: Plug n play support for Epson Scanners (supported by epson2 backend)

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

** Changed in: sane-backends (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Plug n play support for Epson Scanners (supported by epson2 backend)

Status in sane-backends package in Ubuntu:
  Expired

Bug description:
  Most of the Epson scanners nowadays are supported by the epson2 backend :
  http://www.sane-project.org/lists/sane-backends-cvs.html#S-EPSON2

  But the needed udev rules and peson2 config file are not present to
  enable OOTB experience like for HP products.

  How to reproduce :
  - install ubuntu 14.04
  - Plug an epson scanner like the XP-405 ( 0x04b8 0x0898)
  - Launch Simple scan : the scanner is not recognized.

  WORKAROUND: Add in the /lib/udev/rules.d/40-libsane.rules file:
  ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0898", ENV{libsane_matched}="yes"

  Add in the /etc/sane.d/epson2.conf file:
  usb 04b8 0898
  usb /dev/usbscanner0
  usb /dev/usb/scanner0

  We should enable all those epson models to be plug n play by shipping
  the needed config files like we do for HP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1395003/+subscriptions


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

[Desktop-packages] [Bug 1403418] Re: Graphic issues on the VLC media player with VDPAU

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

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

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

Title:
  Graphic issues on the VLC media player with VDPAU

Status in libvdpau package in Ubuntu:
  Expired
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  I'm using Ubuntu 15.04 dev with vlc 2.2.0~rc2-1 and on enabling VDPAU
  in the VLC media player (by going to the menu bar -> Tools ->
  Preferences -> Video -> Display -> Output and setting it to "VDPAU
  output" (on my system this seems also to be the default from
  "Automatic")) I'm seeing for a short time heavy graphic issues if I'm
  going to a new playing position in the video. In the attachments is an
  example video which causes this issue if the playing position is
  changed.

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


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

[Desktop-packages] [Bug 1972983] Re: File dialog in snap firefox does not have keyboard focus

2022-05-11 Thread Ilya Bobyr

I've observed a similar issue, since the Ubuntu 22.04 upgrade.
Though, I can not confirm 100% that the issue happened exactly on the updated 
date.
It might have been caused by one of the Firefox upgrades.  I am currently on 
version 100.

For me, the focus in the save dialog constantly switches to the file list area.
It makes it almost impossible to type the file name.
When I type one character, this character is inserted into the file name edit 
field.
But then the focus changes to the file list area.  And the next character I 
type is used as a file list filter command.

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

Title:
  File dialog in snap firefox does not have keyboard focus

Status in firefox package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the issue.

  After first log in into Ubuntu Desktop 22.04

  1. Launch Firefox and open a website (e.g. www.ubuntu.com)
  2. Hit Ctrl+S to open the Save file dialog.
  3. Type "Ubuntu" to replace the default file name ("Enterprise Open Source 
and Linux | Ubuntu.html"). Hit Enter. It works the first time round.
  4. Hit Ctrl+S to open the Save file dialog again.
  5. Type "Ubuntu - 2" to replace the default file name ("Enterprise Open 
Source and Linux | Ubuntu.html"). This time, your typing fails: the file dialog 
is not in focus.

  Expected behavior anytime when opening a File dialog: the file dialog
  should have keyboard focus.

  Observed behavior: the file dialog does not have focus, except the
  very first time in the session.

  Same observations also for File Open dialogs.

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


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

[Desktop-packages] [Bug 1972983] Re: File dialog in snap firefox does not have keyboard focus

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

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

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

Title:
  File dialog in snap firefox does not have keyboard focus

Status in firefox package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the issue.

  After first log in into Ubuntu Desktop 22.04

  1. Launch Firefox and open a website (e.g. www.ubuntu.com)
  2. Hit Ctrl+S to open the Save file dialog.
  3. Type "Ubuntu" to replace the default file name ("Enterprise Open Source 
and Linux | Ubuntu.html"). Hit Enter. It works the first time round.
  4. Hit Ctrl+S to open the Save file dialog again.
  5. Type "Ubuntu - 2" to replace the default file name ("Enterprise Open 
Source and Linux | Ubuntu.html"). This time, your typing fails: the file dialog 
is not in focus.

  Expected behavior anytime when opening a File dialog: the file dialog
  should have keyboard focus.

  Observed behavior: the file dialog does not have focus, except the
  very first time in the session.

  Same observations also for File Open dialogs.

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


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

[Desktop-packages] [Bug 1972983] Re: File dialog in snap firefox does not have keyboard focus

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

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

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

Title:
  File dialog in snap firefox does not have keyboard focus

Status in firefox package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the issue.

  After first log in into Ubuntu Desktop 22.04

  1. Launch Firefox and open a website (e.g. www.ubuntu.com)
  2. Hit Ctrl+S to open the Save file dialog.
  3. Type "Ubuntu" to replace the default file name ("Enterprise Open Source 
and Linux | Ubuntu.html"). Hit Enter. It works the first time round.
  4. Hit Ctrl+S to open the Save file dialog again.
  5. Type "Ubuntu - 2" to replace the default file name ("Enterprise Open 
Source and Linux | Ubuntu.html"). This time, your typing fails: the file dialog 
is not in focus.

  Expected behavior anytime when opening a File dialog: the file dialog
  should have keyboard focus.

  Observed behavior: the file dialog does not have focus, except the
  very first time in the session.

  Same observations also for File Open dialogs.

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


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

[Desktop-packages] [Bug 27867]

2022-05-11 Thread Marketingbaba78

Video marketing is using videos to promote and market your product or service, 
increase engagement on your digital and social channels, educate...
https://multitechguru.com/advertise-with-us/

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

Title:
  Background color is always white, top banner is never displayed in
  Firefox

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Problem shows whatever the version of Epiphany (before and after today's 
upodate
  ie).

  Whatever the website I visit, the background colour is always white, and the
  logo/banner at the top of the page, is not displayed.

  I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and
  no yellow background.

  http://bugzilla.gnome.org/show_bug.cgi?id=121118:
  http://bugzilla.gnome.org/show_bug.cgi?id=121118

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


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

[Desktop-packages] [Bug 1972983] Re: File dialog in snap firefox does not have keyboard focus

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

** Tags added: focus

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

Title:
  File dialog in snap firefox does not have keyboard focus

Status in firefox package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Steps to reproduce the issue.

  After first log in into Ubuntu Desktop 22.04

  1. Launch Firefox and open a website (e.g. www.ubuntu.com)
  2. Hit Ctrl+S to open the Save file dialog.
  3. Type "Ubuntu" to replace the default file name ("Enterprise Open Source 
and Linux | Ubuntu.html"). Hit Enter. It works the first time round.
  4. Hit Ctrl+S to open the Save file dialog again.
  5. Type "Ubuntu - 2" to replace the default file name ("Enterprise Open 
Source and Linux | Ubuntu.html"). This time, your typing fails: the file dialog 
is not in focus.

  Expected behavior anytime when opening a File dialog: the file dialog
  should have keyboard focus.

  Observed behavior: the file dialog does not have focus, except the
  very first time in the session.

  Same observations also for File Open dialogs.

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


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

[Desktop-packages] [Bug 1972984] Re: Cannot paste filename into File Save dialog of Firefox Snap

** Tags added: focus jammy

** Tags removed: focus

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

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

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

Title:
  Cannot paste filename into File Save dialog of Firefox Snap

Status in firefox package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the problem:

  1. Copy a file name or a file path to the clipboard
  2. Open Firefox
  3. Hit Ctrl+S to open the File Save dialog.
  4. Make sure that the "Name" field has focus (which it may not because of 
another bug) and attempt to paste: Ctrl+V

  Expected behavior: the contents of the clipboard is entered into the "Name" 
field.
  Observed behaviour: a dialog box appears with error message:

  "
  The folder contents could not be displayed
  Operation not supported 
  "
  In the same spirit, editing an existing name by e.g. copying/cutting part of 
the name/path and pasting it back elsewhere in the field does not work.

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


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

[Desktop-packages] [Bug 1972983] Re: File dialog in snap firefox does not have keyboard focus

** Tags added: jammy

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

Title:
  File dialog in snap firefox does not have keyboard focus

Status in mutter package in Ubuntu:
  New

Bug description:
  Steps to reproduce the issue.

  After first log in into Ubuntu Desktop 22.04

  1. Launch Firefox and open a website (e.g. www.ubuntu.com)
  2. Hit Ctrl+S to open the Save file dialog.
  3. Type "Ubuntu" to replace the default file name ("Enterprise Open Source 
and Linux | Ubuntu.html"). Hit Enter. It works the first time round.
  4. Hit Ctrl+S to open the Save file dialog again.
  5. Type "Ubuntu - 2" to replace the default file name ("Enterprise Open 
Source and Linux | Ubuntu.html"). This time, your typing fails: the file dialog 
is not in focus.

  Expected behavior anytime when opening a File dialog: the file dialog
  should have keyboard focus.

  Observed behavior: the file dialog does not have focus, except the
  very first time in the session.

  Same observations also for File Open dialogs.

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


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

[Desktop-packages] [Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

Title:
  The operating system does not ask for a password after unlocking the
  screen.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I found a security vulnerability in Ubuntu 22.04 LTS operating system 
(Laptops only) It is reproduced like this (in steps):
  1. I lock the screen Win + L
  2. Close the laptop lid
  3. Then I open the lid of the laptop
  4. I get a vulnerability, the operating system does not ask for a password, 
but immediately shows the desktop without the need to unlock it. that is, 
closing and opening the laptop lid leads to unlocking the screen without asking 
for a password.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:20:28 2022
  InstallationDate: Installed on 2022-04-21 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  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/1972812/+subscriptions


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

[Desktop-packages] [Bug 1971149] Re: Wayland session: Internal display is black after sleep

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

Thanks.

Comment #8 confirms this is a duplicate of bug 1968040.
Workaround: Add MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment. Although 
you only need that while using Wayland sessions...

Comment #9 is being tracked in bug 1970291.
Workaround: Select a Xorg session on the login screen instead of Wayland.


** This bug has been marked a duplicate of bug 1968040
   Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument 
invalide] [drmModeAtomicCommit: Invalid argument]

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

Title:
  Wayland session: Internal display is black after sleep

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop with Intel 630 and NVIDIA 1050 Ti, I have connected an
  external display via HDMI. I have set this external display as
  primary. I also chose a Wayland session. My Ubuntu 22.04 has all the
  latest updates as of today.

  When my laptop sleeps after I re-login the internal display (connected
  to Intel 630 AFAIK) is black. It appears enabled in the settings and
  if I change it to be the primary it lights up.

  I don't remember seeing this in an X.org session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  2 15:29:43 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2022-05-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/ubuntu/+source/linux/+bug/1971149/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-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

We are aware this is the most popular desktop bug being reported in
22.04. It's already been assigned to the ubuntu-dock author.

-- 
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 gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Triaged

Bug description:
  Currently testing a fresh install of the beta for 22.04.
  All packages are up to date.

  When having the dock auto-hide option enabled, a glitch occurs when opening 
the windows selector (when multiple instances of the same program are opened).
  The selector does open, but the dock will hide itself immediately instead of 
waiting for a selection. Selecting a window will then cause a glitch where the 
selector will align with the hidden dock in a non natural way before 
disappearing.

  A proposed fix would be to prevent the dock from auto-hiding when the
  miniatures selector opens and wait for a second input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-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 1972991] Re: 22.04 Totem crashes on launch (segmentation fault)

Those log messages are from Mesa. I'm seeing them come from other apps
like Firefox and Thunderbird in other peoples' bug reports. But in all
likelihood the log messages are not related to any crash...

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

Title:
  22.04 Totem crashes on launch (segmentation fault)

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Since upgrading (fresh reinstall) to 22.04, I have had issues with
  Totem crashing.

  I have not been able to pin down when it works and when it doesn't, as
  playing the same videos seems to work sometimes and not work others.
  After it crashes, trying to open it again normally does not work and
  trying to launch totem from the commandline gives a segmentation
  fault.

  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  Segmentation fault (core dumped)

  $ totem
  Segmentation fault (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: totem 42.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 11 13:10:48 2022
  InstallationDate: Installed on 2022-04-24 (16 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1972991/+subscriptio

[Desktop-packages] [Bug 1973014] Re: gnome-shell crashes on resume or session change

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

** Tags added: hybrid i915 radeon

** Summary changed:

- gnome-shell crashes on resume or session change
+ gnome-shell crashes with SIGSEGV in libgbm.so.1.0.0 on resume or session 
change

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

Title:
  gnome-shell crashes with SIGSEGV in libgbm.so.1.0.0 on resume or
  session change

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Trying to change session with ctrl-alt f1 or suspend-resume the computer 
systematically leads to a crash on my system :
  -First i can see the screen, but mouse an keyboard are not responsive.
  -Then many visual artifacts appear on my secondary monitor.
  -Then i get a new login prompt.

  After that in dmesg i can see errors such as :

  [ 6574.079637] gnome-shell[5525]: segfault at 55713299a720 ip 
7f7c0af012e7 sp 7ffc8932bdb8 error 4 in 
libgbm.so.1.0.0[7f7c0af0+8000]
  [ 6574.079660] Code: 18 c3 90 f3 0f 1e fa 48 8b 07 ff a0 c0 00 00 00 0f 1f 00 
f3 0f 1e fa 48 8b 07 ff a0 a8 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07  a0 b0 
00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 b8 00 00 00

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30
  Uname: Linux 5.15.0-27-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 11 15:05:07 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-04-23 (1114 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (10 days ago)

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


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

[Desktop-packages] [Bug 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

** Tags added: wayland wayland-session

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.

  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

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


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

[Desktop-packages] [Bug 1969893] Re: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9]

Fixed upstream in mutter 43, but 42 is coming:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2410

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

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

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

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

Title:
  gnome-shell crashes with SIGSEGV just after logging "JS ERROR:
  TypeError: window is null" from _destroyWindow()
  [windowManager.js:1543:9]

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  gnome-shell crashes with SIGSEGV just after logging:

  gnome-shell[3117]: JS ERROR: TypeError: window is null
  _destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
  _initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16

  Examples:

  https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
  https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206

  Tracking in:

  https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470
  ^^^ this is the second most common gnome-shell crash on errors.ubuntu.com

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


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

[Desktop-packages] [Bug 1973093] [NEW] xmessage loses text area as buttons are added and -g

2022-05-11 Thread Ian! D. Allen

Public bug reported:

xmessage text gets obscured with option combinations using buttons and
geometry specifications.

Quick background: xmessage creates a new grey window with a white text
box inside it.  Without -buttons, the white text box usually spans the
full width of the grey window that contains it, leaving no margins.
Things start going wrong when you start specifying -buttons or -g
(geometry), and text can end up being obscured.

Problem #1:

If the width of all the buttons you specify makes the grey window wider
than the text, the white text box does not increase in width to match.
You end up with an undesirable wide grey margin on the right side of the
white text box.  If you resize the window, making it less wide, the grey
margin does not narrow; it moves in and covers and obscures the text,
even though there is plenty of room for the text.

Suggested Fix #1: The white text box must always be created the same width
as the window that contains it, with no useless grey margin to the right.
Narrowing the width of the window should not cause text to be obscured
by a wide and useless fixed grey margin.

Reproduce:

xmessage -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20
"123456789"

Problem #2:

If you add a -g (geometry) option and specify just the width (not the
height) for a window with buttons wider than the text box, the obscuring
grey margin persists.

If you add a "-g NNN" option, where NNN is the width that xmessage would
have chosen itself, then you get exactly the same unpleasant behaviour
as Problem #1 above.

If you increase the NNN to be wider that what xmessage would have used,
then both the window and the text box width are created increased by
that amount, as if you had resized the window with a mouse.  The useless
grey margin to the right of the text box stays the same width, just as
in Problem #1.

If you decrease the NNN to be narrower that what xmessage would have used,
then both the window and the text box width are created decreased by that
amount, as if you had resized the window with a mouse.  Not all buttons
will show; this is expected.  What is not expected is that the useless
grey margin to the right of the text box stays the same width, and so
it now overwrites and obscures the text, even though there is plenty
of room for the text.  If you resize the window back so that all the
buttons show, all the text also shows and we're back to Problem #1 above.

Suggested Fix #2: Same as above.

Reproduce (width 541 is my xmessage chosen width for font "fixed"):

xmessage -g 400 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 
"123456789"
xmessage -g 541 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 
"123456789"
xmessage -g 700 -buttons 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 
"123456789"

Problem #3:

If you add a -g option and specify both the width *and* the height for
a window with buttons wider than the text, things get much worse.

If you add a "-g NNNx55" option, where NNN is the width that xmessage
would have chosen itself and "55" is about the same height, you would
expect to get exactly the same results as if you didn't specify any
geometry at all.  That's not what happens.  You get a fixed-width text
window about 12 characters wide, with a huge grey margin on the right.
It doesn't matter what size text you specify; the white text box will be
created about 12 characters wide and any text to the right of that will
be masked and obscured by the wide grey margin.  Changing the width of
the window has all the problems of Problems #1 and #2 above.

Suggested Fix #3: Same as above.
Specifying a geometry that is identical to what xmessage would have chosen
itself should create an identical window.  Text should not be obscured.

Reproduce (width 541 is my xmessage chosen width for font "fixed"):

xmessage -g 541x55 -buttons
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20 "123456789-123 YOU
DON'T SEE THIS"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: x11-utils 7.7+5build2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 11 17:12:52 2022
DistUpgraded: 2022-04-04 16:21:26,723 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback/0.12.5, 5.15.0-29-generic, x86_64: installed
 v4l2loopback/0.12.5, 5.15.0-30-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family Integrated 
Graphics Controller [10cf:15f5]
InstallationDate: Installed on 2020-09-08 (610 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (2

[Desktop-packages] [Bug 1973091] Re: Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

2022-05-11 Thread Markus Heinz

** Package changed: linux (Ubuntu) => libusb-1.0 (Ubuntu)

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

Title:
  Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

Status in libusb-1.0 package in Ubuntu:
  Confirmed

Bug description:
  The following packages are installed:

  1. libusb-1.0-0/jammy,now 2:1.0.25-1ubuntu1 amd64
  2. libinklevel5/jammy,now 0.9.3-3 amd64
  3. ink/jammy,now 0.5.3-3 amd64

  Command invoked is:

  ink -p usb

  Result is a segmentation fault. Backtrace in gdb:

  gdb) bt
  #0  0x77dfcf74 in pthread_mutex_lock () from 
/lib/x86_64-linux-gnu/libc.so.6
  #1  0x77d52879 in libusb_get_device_list () from 
/lib/x86_64-linux-gnu/libusb-1.0.so.0
  #2  0x77f96c90 in find_printer () from 
/lib/x86_64-linux-gnu/libinklevel.so.5
  #3  0x77f963e5 in get_device_id () from 
/lib/x86_64-linux-gnu/libinklevel.so.5
  #4  0x77f90d55 in get_ink_level () from 
/lib/x86_64-linux-gnu/libinklevel.so.5
  #5  0x554e in ?? ()
  #6  0x77d8ed90 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
  #7  0x77d8ee40 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
  #8  0x5795 in ?? ()

  I have compiled libusb-1.0.26 into my $HOME and pointed
  LD_LIBRARY_PATH to it. Then I get the expected result:

  ink -p usb
  ink 0.5.3 (c) 2018 Markus Heinz

  hp deskjet 5550

  Black:   0%
  Color:   0%

  ldd /usr/bin/ink 
linux-vdso.so.1 (0x7ffe6e47b000)
libinklevel.so.5 => /lib/x86_64-linux-gnu/libinklevel.so.5 
(0x7f479dd44000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f479db1c000)
libusb-1.0.so.0 => 
/home/markus/privat/programmieren/c/printer/libusb-dist/libusb-1.0.26/libusb/.libs/libusb-1.0.so.0
 (0x7f479dafc000)
/lib64/ld-linux-x86-64.so.2 (0x7f479dd79000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f479dad2000)

  So I have the assumption that there is a regression in libusb-1.0.25
  which has been fixed in libusb-1.0.26.

  On Ubuntu 20.04 there was no problem with libusb and libinklevel /
  ink. It just appeared after the update to Ubuntu 22.04 which I did
  today.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libusb-1.0/+bug/1973091/+subscriptions


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

[Desktop-packages] [Bug 1973091] [NEW] Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink

You have been subscribed to a public bug:

The following packages are installed:

1. libusb-1.0-0/jammy,now 2:1.0.25-1ubuntu1 amd64
2. libinklevel5/jammy,now 0.9.3-3 amd64
3. ink/jammy,now 0.5.3-3 amd64

Command invoked is:

ink -p usb

Result is a segmentation fault. Backtrace in gdb:

gdb) bt
#0  0x77dfcf74 in pthread_mutex_lock () from 
/lib/x86_64-linux-gnu/libc.so.6
#1  0x77d52879 in libusb_get_device_list () from 
/lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x77f96c90 in find_printer () from 
/lib/x86_64-linux-gnu/libinklevel.so.5
#3  0x77f963e5 in get_device_id () from 
/lib/x86_64-linux-gnu/libinklevel.so.5
#4  0x77f90d55 in get_ink_level () from 
/lib/x86_64-linux-gnu/libinklevel.so.5
#5  0x554e in ?? ()
#6  0x77d8ed90 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x77d8ee40 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#8  0x5795 in ?? ()

I have compiled libusb-1.0.26 into my $HOME and pointed LD_LIBRARY_PATH
to it. Then I get the expected result:

ink -p usb
ink 0.5.3 (c) 2018 Markus Heinz

hp deskjet 5550

Black:   0%
Color:   0%

ldd /usr/bin/ink 
linux-vdso.so.1 (0x7ffe6e47b000)
libinklevel.so.5 => /lib/x86_64-linux-gnu/libinklevel.so.5 
(0x7f479dd44000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f479db1c000)
libusb-1.0.so.0 => 
/home/markus/privat/programmieren/c/printer/libusb-dist/libusb-1.0.26/libusb/.libs/libusb-1.0.so.0
 (0x7f479dafc000)
/lib64/ld-linux-x86-64.so.2 (0x7f479dd79000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f479dad2000)

So I have the assumption that there is a regression in libusb-1.0.25
which has been fixed in libusb-1.0.26.

On Ubuntu 20.04 there was no problem with libusb and libinklevel / ink.
It just appeared after the update to Ubuntu 22.04 which I did today.

** Affects: libusb-1.0 (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
Ubuntu 22.04: libusb-1.0.25 breaks libinklevel and ink
https://bugs.launchpad.net/bugs/1973091
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libusb-1.0 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 1879137] Re: The snap-store is using hundreds of MiBs of RAM.

2022-05-11 Thread laurent

$ find /proc -maxdepth 2 -path "/proc/[0-9]*/status" -readable -exec awk
-v FS=":" '{process[$1]=$2;sub(/^[ \t]+/,"",process[$1]);} END
{if(process["VmSwap"] && process["VmSwap"] != "0 kB") printf "%10s %-30s
%20s\n",process["Pid"],process["Name"],process["VmSwap"]}' '{}' \; | awk
'{print $(NF-1),$0}' | sort -h | cut -d " " -f2-


snap-store eating my swap file

:(

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

Title:
  The snap-store is using hundreds of MiBs of RAM.

Status in GNOME Software:
  Unknown
Status in snap-store-desktop:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  The snap-store process is intermittently using hundreds of megabytes
  of RAM.  Is this normal? Is there a solution?

  Ubuntu 20.04

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


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

[Desktop-packages] [Bug 1884299] Re: Chromium snap won't run with nfs home drive

2022-05-11 Thread tylerecouture

I think I'm using 4, but I am set up using autofs and haven't touched
NFS directly:

# /etc/auto.home
* -fstype=nfs,rw,async servername:/nfshome/&


`nfsstat -c` tells me: "Client nfs v4"

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

Title:
  Chromium snap won't run with nfs home drive

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

Bug description:
  My physical computer lab uses AutoFS home drives (per
  https://help.ubuntu.com/community/Autofs#Wildcard_characters).   If
  any user tries to run chromium browser, it fails.

  I assume it is related to these:
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
  But that says a fix was released, but seems toi only work for NFS home drives
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873
  That ones is reported as a dupe but it's not, AutoFS home drives still don't 
work.

  $ chromium -v
  cannot create user data directory: /home/test.student2/snap/chromium/1193: 
Stale file handle

  $ tail -f /var/log/syslog
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 
audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 
audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS

  $ apt policy chromium-browser
  chromium-browser:
    Installed: 81.0.4044.129-0ubuntu0.20.04.1
    Candidate: 81.0.4044.129-0ubuntu0.20.04.1
    Version table:
   *** 81.0.4044.129-0ubuntu0.20.04.1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   80.0.3987.163-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

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


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

[Desktop-packages] [Bug 1970424] Re: Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome

This bug was fixed in the package gnome-session - 42.0-1ubuntu3

---
gnome-session (42.0-1ubuntu3) kinetic; urgency=medium

  * debian/gnome-session-common.install: Don't install gnome-mimeapps.list
(installed by desktop-file-utils in Ubuntu) (LP: #1970248)
  * Have gnome-session and ubuntu-session depend on
xdg-desktop-portal-gnome | xdg-desktop-portal-backend (LP: #1970424)

 -- Jeremy Bicha   Sun, 01 May 2022 11:35:12 -0400

** Changed in: gnome-session (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome

Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  Because ubuntu-desktop-minimal only recommends xdg-desktop-portal-gnome, it 
is easy for users to accidentally not have it installed. If it (Or another 
desktop portal backend are not installed), it breaks critical functionality for 
both the Firefox snap and Chromium snaps. It also breaks countless other snaps.

  Test Case
  -
  ubuntu-session and gnome-session should depend on xdg-desktop-portal-gnome

  It should be possible to uninstall xdg-desktop-portal-gnome and keep
  xdg-desktop-portal-gtk. (This allows someone to keep using GTK3 and
  avoid the libadwaita dialogs which may be easier for third party
  themes.)

  What Could Go Wrong
  ---
  This just adds an additional dependency.

  I believe the portal backends currently open by default in the locale
  sort order, so xdg-desktop-portal-gnome is preferred if installed,
  then xdg-desktop-portal-gtk, then xdg-desktop-portal-kde, then xdg-
  desktop-portal-wlr. Which coincidentally is the order we would want.

  How This Was Fixed
  --
  ubuntu-desktop-minimal is a special germinate package and doesn't accept 
alternate dependencies. An alternate dependency is needed because we want to 
allow people to use a different portal backend and the easiest way to use a 
different portal backend is to install the backend you want and uninstall the 
ones you don't want.

  Therefore, we are handling this with a dependency in ubuntu-session.
  We are also doing this with gnome-session since that's a popular
  alternative for people who want a vanilla GNOME experience.

  
  Original Bug Report
  ---
  With ubuntu 22.04 firefox comes as snap package by default.

  it is not possible to open any file dialog. save graphics as, save
  html page, import certificate never opens a file dialog.

  firefox is completly useless without that file dialog.

  (the root case is ubuntu uses snap)

  further: in snap store firefox has no icon and it's called firefox not
  "Firefox".

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


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

[Desktop-packages] [Bug 1970248] Re: .deb files open with Archive Manager by default

This bug was fixed in the package gnome-session - 42.0-1ubuntu3

---
gnome-session (42.0-1ubuntu3) kinetic; urgency=medium

  * debian/gnome-session-common.install: Don't install gnome-mimeapps.list
(installed by desktop-file-utils in Ubuntu) (LP: #1970248)
  * Have gnome-session and ubuntu-session depend on
xdg-desktop-portal-gnome | xdg-desktop-portal-backend (LP: #1970424)

 -- Jeremy Bicha   Sun, 01 May 2022 11:35:12 -0400

** Changed in: gnome-session (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  .deb files open with Archive Manager by default

Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-session source package in Jammy:
  Incomplete
Status in desktop-file-utils package in Baltix:
  New

Bug description:
  Impact
  --
  Someone who downloads a .deb file usually wants to install the .deb when they 
open it. Opening it with Archive Manager is really confusing.

  Test Case
  -
  Download a .deb
  Open your Downloads folder with the file manager.
  Double click on the .deb
  The Ubuntu Software app should open with a button that says Install.

  More Details
  
  desktop-file-utils provides /etc/gnome/defaults.list
  In that file, there is this line (and several other lines also referring to 
the same .desktop)

  application/vnd.debian.binary-package=snap-store_ubuntu-software-
  local-file.desktop

  But when I look at /snap/snap-store/575/usr/share/applications/
  there is gnome-software-local-file.desktop

  which is a different file name.

  I believe this issue can be fixed in either snap-store or with
  desktop-file-utils.

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


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

[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage

2022-05-11 Thread aramaicus

** Attachment removed: "Crash reports from ubuntu server 22.04 running on 
Raspberry Pi 4"
   
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+attachment/5588753/+files/ubuntu%20server%20crash%2001-may-2022.7z

** Attachment added: "/var/log files after a crash"
   
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+attachment/5588754/+files/ubuntu%20server%20crash%2024-apr-2022.7z

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  New

Bug description:
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign
  on a Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  
  Description:Ubuntu 22.04 LTS
  Release:22.04

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


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

[Desktop-packages] [Bug 1973084] [NEW] transmission-daemon high RAM usage

2022-05-11 Thread aramaicus

Public bug reported:

Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on
a Raspberry Pi 4.

It "eats" RAM and the RAM usage grows each hour until it crashes the
system.

I sideloaded transmission-daemon and its dependancies from debian 11
(arm64) locked the packages so apt won't update them and, ever since,
this issue hasn't happened.


Description:Ubuntu 22.04 LTS
Release:22.04

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

** Attachment added: "Crash reports from ubuntu server 22.04 running on 
Raspberry Pi 4"
   
https://bugs.launchpad.net/bugs/1973084/+attachment/5588753/+files/ubuntu%20server%20crash%2001-may-2022.7z

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  New

Bug description:
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign
  on a Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  
  Description:Ubuntu 22.04 LTS
  Release:22.04

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


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

Re: [Desktop-packages] [Bug 1972037] Re: Stack Overflow - gnome-control-center

2022-05-11 Thread Stan Tomlinson

Sebastian,

Just turned off Xinerama (for a few minutes).
For some reason, the system is unable to use both screens without Xinerama.
Played with this a lot when I upgraded to 20.04 from 16.04 (worked nicely
before upgrade).
FWIW, cursor is a big X on second screen, but no background and no moving
windows onto it.

Stan

On Tue, May 10, 2022 at 11:52 AM Stan Tomlinson 
wrote:

> Turned off COMPOSITE, and am getting the same reaction.
> See attached Xorg.0.log
>
> On Tue, May 10, 2022 at 3:20 AM Sebastien Bacher <
> 1972...@bugs.launchpad.net> wrote:
>
>> The Xorg log was sent via email and contains
>>
>> (WW) NVIDIA: The Composite and Xinerama extensions are both enabled, which
>> (WW) NVIDIA: is an unsupported configuration.  The driver will
>> continue
>> (WW) NVIDIA: to load, but may behave strangely.
>> (WW) NVIDIA: Xinerama is enabled, so RandR has likely been disabled by the
>> (WW) NVIDIA: X server.
>>
>> gnome-control-center should handle the situation better but that's a bit
>> of a special graphical display configuration, did you try to do without
>> xinerama?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1972037
>>
>> Title:
>>   Stack Overflow - gnome-control-center
>>
>> Status in gnome-control-center package in Ubuntu:
>>   New
>>
>> Bug description:
>>
>>   Program: gnome-control-center
>>   Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download)
>>   OS: ubuntu 20.04.4 LTS
>>   GNOME Version: 3.36.8 (ubuntu default download)
>>   Windowing System: X11
>>   Graphics: GeForce 8400GS/PCIe/SSE2
>>   Driver: Using NVIDIA binary driver version 340.108
>>   Source: download version from ubuntu
>>
>>   Steps to reproduce:
>>
>>   Reset GNOME settings with:
>> dconf reset -f /org/gnome/control-center/
>>   Open GNOME Settings with:
>> /usr/bin/gnome-control-center
>>   Click on "Displays" and receive:
>> Xlib:  extension "RANDR" missing on display ":0".
>> Xlib:  extension "RANDR" missing on display ":0".
>> Segmentation fault (core dumped)
>>
>>   Repeated using gdb with package symbols.
>>   Output of "bt -full" in attachment (with a few comments).
>>
>>   (Submitted to gnome.org, but they said it is out of date and not
>>   supported by them.)
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.04
>>   Package: gnome-control-center 1:3.36.5-0ubuntu4
>>   ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
>>   Uname: Linux 5.4.0-100-generic x86_64
>>   NonfreeKernelModules: nvidia
>>   ApportVersion: 2.20.11-0ubuntu27.23
>>   Architecture: amd64
>>   CasperMD5CheckResult: skip
>>   CurrentDesktop: GNOME-Flashback:GNOME
>>   Date: Fri May  6 20:38:55 2022
>>   InstallationDate: Installed on 2011-07-11 (3952 days ago)
>>   InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64
>> (20110426)
>>   SourcePackage: gnome-control-center
>>   UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago)
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1972037/+subscriptions
>>
>>

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

Title:
  Stack Overflow - gnome-control-center

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

Bug description:
  
  Program: gnome-control-center
  Installed version: 1:3.36.5-0ubuntu4 (ubuntu default download)
  OS: ubuntu 20.04.4 LTS
  GNOME Version: 3.36.8 (ubuntu default download)
  Windowing System: X11
  Graphics: GeForce 8400GS/PCIe/SSE2
  Driver: Using NVIDIA binary driver version 340.108
  Source: download version from ubuntu

  Steps to reproduce:

  Reset GNOME settings with:
dconf reset -f /org/gnome/control-center/
  Open GNOME Settings with:
/usr/bin/gnome-control-center
  Click on "Displays" and receive:
Xlib:  extension "RANDR" missing on display ":0".
Xlib:  extension "RANDR" missing on display ":0".
Segmentation fault (core dumped)

  Repeated using gdb with package symbols.
  Output of "bt -full" in attachment (with a few comments).

  (Submitted to gnome.org, but they said it is out of date and not
  supported by them.)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Fri May  6 20:38:55 2022
  InstallationDate: Installed on 2011-07-11 (3952 days ago)
  InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 
(20110426)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2022-02-01 (94 days ago)

To manage notifications about t

[Desktop-packages] [Bug 1892559] Re: [MIR] ccid opensc pcsc-lite

2022-05-11 Thread Steve Beattie

** Tags added: sec-407

** Tags added: sec-408 sec-409

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

Title:
  [MIR] ccid opensc pcsc-lite

Status in ccid package in Ubuntu:
  In Progress
Status in opensc package in Ubuntu:
  Incomplete
Status in pam-pkcs11 package in Ubuntu:
  Invalid
Status in pcsc-lite package in Ubuntu:
  New
Status in pcsc-perl package in Ubuntu:
  Invalid
Status in pcsc-tools package in Ubuntu:
  Invalid

Bug description:
  ==> ccid <==
  [Availability]
  ccid is in universe, and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs for ccid are listed in our database.
  Doesn't appear to bind to a socket.
  No privileged executables, but does have udev rules.
  Probably needs a security review.

  [Quality assurance]
  No test suite.
  Does require odd hardware that we'll probably need to buy.
  I don't see debconf questions.
  ccid is well maintained in Debian by upstream author.
  One open wishlist bug in BTS, harmless.

  One open bug in launchpad, not security, but looks very frustrating
  for the users. The upstream author was engaged but it never reached
  resolution.  https://bugs.launchpad.net/ubuntu/+source/ccid/+bug/1175465

  Has a debian/watch file.
  Quilt packaging.

  P: ccid source: no-dep5-copyright
  P: ccid source: package-uses-experimental-debhelper-compat-version 13

  [Dependencies]
  Minimal dependencies, in main

  [Standards compliance]
  Appears to satisfy FHS and Debian policy

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  ccid provides drivers to interact with usb-connected smart card readers.

  ==> libpam-pkcs11 <==
  [Availability]
  Source package pam-pkcs11 is in universe and builds on all architectures.

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  No CVEs in our database.
  Doesn't appear to bind to sockets.
  No privileged executables (but is a PAM module).
  As a PAM module this will require a security review.

  [Quality assurance]
  The package does not call pam-auth-update in its postinst #1650366
  Does not ask questions during install.
  One Ubuntu bug claims very poor behaviour if a card isn't plugged in.
  No Debian bugs.
  Occasional updates in Debian by long-term maintainer.
  Does require odd hardware that we'll probably need to buy.
  Does not appear to run tests during build.
  Has scary warnings in the build logs.
  Has a debian/watch file.

  Ancient standards version; other smaller lintian messages, mostly
  documentation problems.

  Quilt packaging.

  [Dependencies]
  Depends on libcurl4, libldap-2.4-2, libpam0g, libpcsclite1, libssl1.1
  All are in main.

  [Standards compliance]
  The package does not call pam-auth-update in its postinst #1650366
  Otherwise looks to conform to FHS and Debian policies

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  This PAM module can use CRLs and full-chain verification of certificates.
  It can also do LDAP, AD, and Kerberos username mapping.

  ==> libpcsc-perl <==
  [Availability]
  Source package pcsc-perl is in universe, builds for all architectures,
  plus i386

  [Rationale]
  The desktop team and security team are interested in bringing smartcard
  authentication to enterprise desktop environments.

  [Security]
  There are no cves for pcsc-perl in our database.
  No privileged executables.
  Doesn't appear to bind to sockets.
  Probably needs a security review.

  [Quality assurance]
  Library package not intended to be used directly.
  No debconf questions.
  No bugs in Debian.
  No bugs in Ubuntu.
  Does require odd hardware that we'll probably need to buy.
  Tests exist, not run during the build; probably can't run during the build.
  Includes debian/watch file.
  A handful of lintian issues
  Quilt packaging.

  [Dependencies]
  libpcsc-perl depends upon libpcsclite1, libc6, perl, perlapi-5.30.0.
  All are in main.

  [Standards compliance]
  One oddity, Card.pod is stored in 
/usr/lib/x86_64-linux-gnu/perl5/5.30/Chipcard/PCSC/
  Many other perl packages have .pod files in these directory trees so maybe
  it's fine, but it seems funny all the same.

  Otherwise appears to satisfy FHS and Debian policy.

  [Maintenance]
  The desktop team will subscribe to bugs, however it is expected that the
  security team will assist with security-relevant questions.

  [Background information]
  Dependency of pcsc-tools; this library provides an API to wo

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

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

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

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

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

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

This was a contributing factor for LP: #1971415

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

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

It should show the service as "Active: inactive"

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

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

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

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

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

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

What could go wrong
---
The technical fix seems minimal, correct, and targeted to me.

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

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

[Desktop-packages] [Bug 1969838] Update Released

2022-05-11 Thread Brian Murray

The verification of the Stable Release Update for gjs 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/1969838

Title:
  Ubuntu-dock does not work when using Turkish Language

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

Bug description:
  [ Impact ]

  Ubuntu dock doesn't work when Turkish language is selected.

  Issue on dash-to-dock's github: 
https://github.com/micheleg/dash-to-dock/issues/1687
  Ubuntu version: Ubuntu 22.04 LTS
  gnome-shell-extension-ubuntu-dock version: 72~ubuntu5

  
  [ Test case ]
  - Run ubuntu session
  - Ubuntu dock should be visible on a screen edge

  Alternatively:

  Save this test case in a file (i.e. /tmp/test.js):

  const { GLib, GObject } = imports.gi;
  const ImplicitProp = GObject.registerClass({
  Properties: {
  "prop-int": GObject.ParamSpec.uint(
  "prop-int", "prop-int", "prop-int",
  GObject.ParamFlags.READWRITE | GObject.ParamFlags.CONSTRUCT_ONLY,
  0, GLib.MAXUINT32, 55),
  },
  }, class DashToDock extends GObject.Object { });
  if (new ImplicitProp().propInt === undefined)
  throw new Error("Missing property")
  print('All good');

  In a terminal run:
   LC_ALL=tr_TR gjs /tmp/test.js

  The script should work without throwing any error.

  [ Regression potential ]

  Implicit properties on GJS may be wrongly computed, and further
  objects could have undefined properties.

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


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

[Desktop-packages] [Bug 1969838] Re: Ubuntu-dock does not work when using Turkish Language

This bug was fixed in the package gjs - 1.72.0-3~ubuntu22.04.1

---
gjs (1.72.0-3~ubuntu22.04.1) jammy; urgency=medium

  * No-change backport to jammy

gjs (1.72.0-3) unstable; urgency=medium

  * debian/patches: Correctly generate camelCase properties on all locales.
And particularly looking at Turkish one. (LP: #1969838)

gjs (1.72.0-2) unstable; urgency=medium

  * Upload to unstable

 -- Marco Trevisan (Treviño)   Thu, 28 Apr 2022
22:31:00 +0200

** Changed in: gjs (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/1969838

Title:
  Ubuntu-dock does not work when using Turkish Language

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

Bug description:
  [ Impact ]

  Ubuntu dock doesn't work when Turkish language is selected.

  Issue on dash-to-dock's github: 
https://github.com/micheleg/dash-to-dock/issues/1687
  Ubuntu version: Ubuntu 22.04 LTS
  gnome-shell-extension-ubuntu-dock version: 72~ubuntu5

  
  [ Test case ]
  - Run ubuntu session
  - Ubuntu dock should be visible on a screen edge

  Alternatively:

  Save this test case in a file (i.e. /tmp/test.js):

  const { GLib, GObject } = imports.gi;
  const ImplicitProp = GObject.registerClass({
  Properties: {
  "prop-int": GObject.ParamSpec.uint(
  "prop-int", "prop-int", "prop-int",
  GObject.ParamFlags.READWRITE | GObject.ParamFlags.CONSTRUCT_ONLY,
  0, GLib.MAXUINT32, 55),
  },
  }, class DashToDock extends GObject.Object { });
  if (new ImplicitProp().propInt === undefined)
  throw new Error("Missing property")
  print('All good');

  In a terminal run:
   LC_ALL=tr_TR gjs /tmp/test.js

  The script should work without throwing any error.

  [ Regression potential ]

  Implicit properties on GJS may be wrongly computed, and further
  objects could have undefined properties.

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


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

[Desktop-packages] [Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.

2022-05-11 Thread Nick

Hello.

I don't have installed extensions. i added a screenshot.


** Attachment added: "gnome-shell.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+attachment/5588740/+files/gnome-shell.png

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

Title:
  The operating system does not ask for a password after unlocking the
  screen.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I found a security vulnerability in Ubuntu 22.04 LTS operating system 
(Laptops only) It is reproduced like this (in steps):
  1. I lock the screen Win + L
  2. Close the laptop lid
  3. Then I open the lid of the laptop
  4. I get a vulnerability, the operating system does not ask for a password, 
but immediately shows the desktop without the need to unlock it. that is, 
closing and opening the laptop lid leads to unlocking the screen without asking 
for a password.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:20:28 2022
  InstallationDate: Installed on 2022-04-21 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  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/1972812/+subscriptions


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

[Desktop-packages] [Bug 1971149] Re: Wayland session: Internal display is black after sleep

2022-05-11 Thread Zingam

This maybe unrelated but I'll write it here too:

Since 22.04 the mouse movement on my external monitor feels laggy,
jerky, while on the internal display it feels ok. I think on Ubuntu
20.04 there was not such an issue. I use Windows (same configuration)
and macOS too with this monitor and they are smooth.

After performing the above sleep experiment I think the mouse movement
got smoother. Now only my external monitor is turned on.

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

Title:
  Wayland session: Internal display is black after sleep

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop with Intel 630 and NVIDIA 1050 Ti, I have connected an
  external display via HDMI. I have set this external display as
  primary. I also chose a Wayland session. My Ubuntu 22.04 has all the
  latest updates as of today.

  When my laptop sleeps after I re-login the internal display (connected
  to Intel 630 AFAIK) is black. It appears enabled in the settings and
  if I change it to be the primary it lights up.

  I don't remember seeing this in an X.org session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  2 15:29:43 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2022-05-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/ubuntu/+source/linux/+bug/1971149/+subscriptions


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

[Desktop-packages] [Bug 1971149] Re: Wayland session: Internal display is black after sleep

2022-05-11 Thread Zingam

Some additional information + the included log.

1. During "sleep" the internal display appears to be powered off but the 
external is blank but powered on (which means it glows in the dark).
2. I tried to reproduce the behavior by "suspending". When I resumed both 
displays turned on but instead of a mouse cursor there was a huge white 
rectangle on the login screen. After I clicked, moved it around the normal 
cursor appeared.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971149/+attachment/5588739/+files/journal.txt

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

Title:
  Wayland session: Internal display is black after sleep

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a laptop with Intel 630 and NVIDIA 1050 Ti, I have connected an
  external display via HDMI. I have set this external display as
  primary. I also chose a Wayland session. My Ubuntu 22.04 has all the
  latest updates as of today.

  When my laptop sleeps after I re-login the internal display (connected
  to Intel 630 AFAIK) is black. It appears enabled in the settings and
  if I change it to be the primary it lights up.

  I don't remember seeing this in an X.org session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  2 15:29:43 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2022-05-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=19e3ad11-d1ce-49ce-8809-80fc68612eb3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 065C71
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrX02:cvnDellInc.:ct10:cvr:sku0798:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/ubuntu/+source/linux/+bug/1971149/+subscriptions


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

[Desktop-packages] [Bug 1973070] [NEW] package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: installed libreoffice-common package post-installation script subprocess returned error ex

2022-05-11 Thread Wouter Depuydt

Public bug reported:

do-release-upgrade from 20.04 to 22.04

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libreoffice-common 1:7.3.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
Uname: Linux 5.4.0-110-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed May 11 20:59:29 2022
ErrorMessage: installed libreoffice-common package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-03-24 (1874 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt  2.4.5
SourcePackage: libreoffice
Title: package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: 
installed libreoffice-common package post-installation script subprocess 
returned error exit status 1
UpgradeStatus: Upgraded to jammy on 2022-05-11 (0 days ago)

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


** Tags: amd64 apport-package jammy need-duplicate-check third-party-packages

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

Title:
  package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade:
  installed libreoffice-common package post-installation script
  subprocess returned error exit status 1

Status in libreoffice package in Ubuntu:
  New

Bug description:
  do-release-upgrade from 20.04 to 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-common 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181
  Uname: Linux 5.4.0-110-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed May 11 20:59:29 2022
  ErrorMessage: installed libreoffice-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-03-24 (1874 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: libreoffice
  Title: package libreoffice-common 1:7.3.2-0ubuntu2 failed to install/upgrade: 
installed libreoffice-common package post-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-05-11 (0 days ago)

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


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

[Desktop-packages] [Bug 1971042] Re: remap Fn+F3 to gnome-power-statistics instead of no-use OSD ( L322X 22.04 )

2022-05-11 Thread Bib

It works now. Can't remember if I reboot.

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

Title:
  remap Fn+F3 to gnome-power-statistics instead of no-use OSD ( L322X
  22.04 )

Status in xwayland package in Ubuntu:
  New

Bug description:
  Hi
  I migrated my Dell XPS L322X to 22.04
  Fn+F3 combo won't trigger gnome-power-statistics anymore the way it did since 
the sputnik project up to the last upgrade to Trusty. I can't remap with 
keyboard settings custom shortcuts: when I do this the combo keystroke is 
detected fine by the GUI that displays "Batterie" (Battery), but the keystroke 
still brings up the useless OSD (redundant as we already have the battery/mains 
indicator in the top bar) and won't launch the application.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xwayland 2:22.1.1-1
  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: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 30 14:19:22 2022
  InstallationDate: Installed on 2013-07-05 (3220 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: xwayland
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (5 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2014-05-09T18:19:35.484888

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


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

[Desktop-packages] [Bug 1970442] Re: ubuntu-standard shouldn't depend on transitional mime-support package

** Description changed:

  $ apt show mime-support
-  This is a transitional package. It will be possible to remove it
-  safely once its dependency chain has adjusted to depend on mailcap
-  or media-types directly.
+  This is a transitional package. It will be possible to remove it
+  safely once its dependency chain has adjusted to depend on mailcap
+  or media-types directly.
  
  I didn't update this dependency because I don't know if we need mailcap
  as an ubuntu-standard Depends or not. I believe we do want media-types.
+ 
+ https://salsa.debian.org/dbnpolicy/policy/-/commit/fddc302fd

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

Title:
  ubuntu-standard shouldn't depend on transitional mime-support package

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  $ apt show mime-support
   This is a transitional package. It will be possible to remove it
   safely once its dependency chain has adjusted to depend on mailcap
   or media-types directly.

  I didn't update this dependency because I don't know if we need
  mailcap as an ubuntu-standard Depends or not. I believe we do want
  media-types.

  https://salsa.debian.org/dbnpolicy/policy/-/commit/fddc302fd

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


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

[Desktop-packages] [Bug 1165609] Re: There is no apparent way to stop Orca

2022-05-11 Thread Yuan-Chen Cheng

** Tags added: oem-priority

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

Title:
  There is no apparent way to stop Orca

Status in OEM Priority Project:
  Invalid
Status in gnome-orca package in Ubuntu:
  Confirmed

Bug description:
  The "Orca Screen Reader" icon in the Dash is a trap. If a user
  accidentally opens it, the only apparent recourse for the incessant
  jabber is to either mute the volume system-wide or log out. This makes
  for a very poor user experience.

  Orca could avoid this situation by providing at least one of the
  following:

1) A notification of how to stop it, if there is a way to stop it.
2) A confirmation prompt prior to starting.
3) A quit option in a standard location such as the indicator menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-orca 3.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sat Apr  6 18:35:02 2013
  InstallationDate: Installed on 2013-04-06 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-orca
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1165609] Re: There is no apparent way to stop Orca

2022-05-11 Thread Evan

I had the most nightmarish experience yet: Somehow (probably by
accidentally typing the shortcut) I turned on Orca, but because my
computer's sound was muted, I only got mysterious symptoms. PDF files in
Firefox kept returning to the first page, TeXstudio would crash with a
segmentation fault when I opened the file manager, and I feared that my
CPU was about to die. Finally, after plugging in headphones to listen to
a video, I heard the jabbering and opened the System Monitor to find out
the name of the program causing it. Please add an Orca icon to the
system tray to help users to fix this faster!

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

Title:
  There is no apparent way to stop Orca

Status in OEM Priority Project:
  Invalid
Status in gnome-orca package in Ubuntu:
  Confirmed

Bug description:
  The "Orca Screen Reader" icon in the Dash is a trap. If a user
  accidentally opens it, the only apparent recourse for the incessant
  jabber is to either mute the volume system-wide or log out. This makes
  for a very poor user experience.

  Orca could avoid this situation by providing at least one of the
  following:

1) A notification of how to stop it, if there is a way to stop it.
2) A confirmation prompt prior to starting.
3) A quit option in a standard location such as the indicator menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-orca 3.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sat Apr  6 18:35:02 2013
  InstallationDate: Installed on 2013-04-06 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-orca
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1965439] Re: software-properties-qt can no longer launch when called by kdesu

2022-05-11 Thread Daniele Inglisa

Sorry for my ignorance, but I'm afraid the source of the bug is deeper
(and not intrinsic to software-properties-qt), as the same bug also
occurs when trying to start, for example, KSystemLog.

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

Title:
  software-properties-qt can no longer launch when called by kdesu

Status in kdesu package in Ubuntu:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in policykit-1 package in Ubuntu:
  Invalid
Status in software-properties package in Ubuntu:
  Confirmed
Status in sudo package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kdesu source package in Impish:
  Invalid
Status in kubuntu-settings source package in Impish:
  Invalid
Status in policykit-1 source package in Impish:
  Invalid
Status in software-properties source package in Impish:
  Invalid
Status in sudo source package in Impish:
  Invalid
Status in ubuntustudio-default-settings source package in Impish:
  Invalid
Status in kdesu source package in Jammy:
  Confirmed
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in policykit-1 source package in Jammy:
  Invalid
Status in software-properties source package in Jammy:
  Confirmed
Status in sudo source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

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


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

[Desktop-packages] [Bug 1967626] Re: 22.04 beta Network Manager still sets wrong IPv6 routing

2022-05-11 Thread Marc Deslauriers

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #840
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/840

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/840
   Importance: Unknown
   Status: Unknown

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  22.04 beta Network Manager still sets wrong IPv6 routing

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  that's a bug I've already reported earlier both to ubuntu and network-
  manager upstream, and nobody seems to care about.

  I'm using an AVM FritzBox, a router family very common in Germany and
  Europe for DSL and DOCSIS, but saw reports of people confirming the
  problem with other routers.

  The router sends ICMPv6 router advertisements, which contain for both
  the configured site-local address and the provider-assigned world-
  routable address range both a

  * prefix information 
  * router advertisement on itself

  All other OS and machines I have, including

  * Debian
  * Ubuntu Server
  * Ubuntu Core
  * Raspberry Pi OS
  * Other Linuxes
  * MacOS
  *...

  correctly set a link route on the network device for both the official
  and the site local address.

  Only Ubuntu Desktop machines with that damned Network Manager set a
  route to the router instead of a link route.

  The consequence is, that IPv6 still works, but significantly to slow,
  since packages are not switched on the network switch, but routed on
  the router, which dramatically decreases speed.

  
  I've reported this upstream to Network Manager, see the discussion on 

  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/840

  but they do not even seem to understand the issue (Network Manager
  written by people not really understanding routing...)

  Their point of view is that the router will fix things by sending
  redirects. However, ICMPv6 redirects are considered a security problem
  and usually recommended to be turned off.

  The answer from NetworkManager developers is to fix the router, not
  the Network Manager to stop sending router advertisings, but can't
  explain why all other OS and other Linux distributions, including
  Ubuntu server and Ubuntu core do it correctly, and just NM doing it
  wrong.

  So Ubuntu/NetworkManagers unability to fix or even notice this
  essential problem forces people to either accept terribly slow IPv6
  traffic in local networks, or to leave the machine open for ICMPv6
  redirects, which, in general, is a security flaw and vulnerable.

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


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

[Desktop-packages] [Bug 1942951] Re: devhelp doesn't display any help pages

2022-05-11 Thread Xavier Claessens

I can confirm that `mv ~/.local/share/mime ~/.local/share/mime-back`
worked for me.

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

Title:
  devhelp doesn't display any help pages

Status in webkit2gtk package in Ubuntu:
  Triaged
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  webkit2gtk 2.33.3-1ubuntu3

  Test Case
  -
  1. sudo apt install devhelp libgtk-3-doc
  2. Open devhelp and click the GTK+ 3 Reference Manual link in the left 
sidebar.
  3. The manual should show in the main view area.

  What Happens
  
  The main viewing area stays blank.

  Other Info
  --
  I manually installed webkit2gtk from Ubuntu 21.04 and Devhelp worked normally 
again.
  The Epiphany web browser works fine with the broken webkit2gtk version.
  Ubuntu's packaging diverges slightly from Debian's. The changelog mentions 
some dependency changes and disabling lto.
  I haven't done any further investigation.

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


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

[Desktop-packages] [Bug 1972984] Re: Cannot paste filename into File Save dialog of Firefox Snap

2022-05-11 Thread Anatoliy

This error is repeated if you try to save files from app telegram-
desktop

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

Title:
  Cannot paste filename into File Save dialog of Firefox Snap

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the problem:

  1. Copy a file name or a file path to the clipboard
  2. Open Firefox
  3. Hit Ctrl+S to open the File Save dialog.
  4. Make sure that the "Name" field has focus (which it may not because of 
another bug) and attempt to paste: Ctrl+V

  Expected behavior: the contents of the clipboard is entered into the "Name" 
field.
  Observed behaviour: a dialog box appears with error message:

  "
  The folder contents could not be displayed
  Operation not supported 
  "
  In the same spirit, editing an existing name by e.g. copying/cutting part of 
the name/path and pasting it back elsewhere in the field does not work.

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


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

[Desktop-packages] [Bug 1972984] Re: Cannot paste filename into File Save dialog of Firefox Snap

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

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

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

Title:
  Cannot paste filename into File Save dialog of Firefox Snap

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce the problem:

  1. Copy a file name or a file path to the clipboard
  2. Open Firefox
  3. Hit Ctrl+S to open the File Save dialog.
  4. Make sure that the "Name" field has focus (which it may not because of 
another bug) and attempt to paste: Ctrl+V

  Expected behavior: the contents of the clipboard is entered into the "Name" 
field.
  Observed behaviour: a dialog box appears with error message:

  "
  The folder contents could not be displayed
  Operation not supported 
  "
  In the same spirit, editing an existing name by e.g. copying/cutting part of 
the name/path and pasting it back elsewhere in the field does not work.

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


-- 
Mailing list: https://launchpad.net/~desktop-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

2022-05-11 Thread Miguel Máiquez

Pinning an app to the dock (or removing it), displaying its details,
open it in a new window (for browsers, for example), and other functions
normally available with the right click, are all tasks very hard to
complete right now when the dock is set to auto-hide at the bottom (like
trying to hit a target on a video game). They might be specific, but
also very basic circumstances. I just experienced it right now. I was
trying to open a new window of my browser via right click on the app in
the dock, but the menu shifted, or moved down, when clicked, and I ended
up exiting the browser.

--
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 gnome-shell-extension-ubuntu-dock package in Ubuntu:
Triaged
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
Triaged

Bug description:
Currently testing a fresh install of the beta for 22.04.
All packages are up to date.

When having the dock auto-hide option enabled, a glitch occurs when opening
the windows selector (when multiple instances of the same program are opened).
The selector does open, but the dock will hide itself immediately instead of
waiting for a selection. Selecting a window will then cause a glitch where the
selector will align with the hidden dock in a non natural way before
disappearing.

A proposed fix would be to prevent the dock from auto-hiding when the
miniatures selector opens and wait for a second input.

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

[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe

2022-05-11 Thread ysfr

Hi,

did it reverting to ubuntu-drivers-common 1:0.8.1 (focal) >
XXX_before.txt logs in ZIP

accountname@hostname:~$ systemd-analyze time
 Startup finished in 5.469s (kernel) + 5.395s (userspace) = 10.864s 
 graphical.target reached after 4.814s in userspace
accountname@hostname:~$ systemd-analyze blame
 2.343s dev-sda3.device 
 
 2.285s man-db.service  
 
 ... 

& updating to:
ubuntu-drivers-common 1:0.9.0~0.20.04.7 (focal-updates)

accountname@hostname:~$ systemd-analyze time
  Startup finished in 5.557s (kernel) + 14.014s (userspace) = 19.572s 
  graphical.target reached after 13.983s in userspace
accountname@hostname:~$ systemd-analyze blame
  10.488s gpu-manager.service   
   
  10.142s plymouth-quit-wait.service
   
  2.704s dev-sda3.device
  
  ...
  
Hope it helps !

** Attachment added: "requested log"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1958488/+attachment/5588604/+files/logs.zip

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

Title:
  [nvidia][xorg] display hangs on boot LOGO due to race of gdm and
  nvidia driver probe

Status in OEM Priority Project:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Focal:
  Triaged
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in gdm3 source package in Impish:
  Triaged
Status in ubuntu-drivers-common source package in Impish:
  Fix Released

Bug description:
  [Impact]

   * In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg 
with proprietary nvidia driver), in some cases, the nvidia driver will probe 
later than launching gdm.
   * If above race condition happens in iGPU + nvidia cases and monitor 
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg. 
Which may lead the monitor stuck in black-screen or boot LOGO.

  [Test Plan]

   * The environment:
    1. A desktop or workstation which containing an iGPU.
    2. Plug a nvidia graphic card to the system and installing proprietary
    nvidia driver (470 in my case)
    3. Attach a monitor to dGPU and leave iGPU connect to nothing.
    (in my test environment, there is the other ethernet card and TBT4 cards)
   * Setup a cronjob,
     e.g. @reboot /home/u/test.sh
   * Have a test script in something like /home/u/test.sh as

  #!/bin/bash

  sleep 20
  count="$(cat /home/ubuntu/count)"
  count=$((count+1))
  echo $count | tee /home/ubuntu/count
  journalctl -b | grep -q -i wayland || sudo reboot

   * the system will probably stuck in black-screen or boot LOGO.
   * Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
   * After applying the fix, it got pass within 1000+ reboot cycles.
   * Test PPA can be found here 
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488

  [Fix]
   * The patch makes gpu-manager to probe nvidia (if needed) first and waiting 
for the /run/u-d-c-nvidia-drm-was-loaded be touched by 
71-u-d-c-gpu-detection.rules.
   * Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking 
the nvidia driver presents or not.
   * gpu-manager is before display-manager. Thus, gpu-manager will wait for 
nvidia uevent be processed and then continue to work. When gdm be launched, the 
targeted nvidia uevent has been processed already. 
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）

  [Where problems could occur]
   * there is not potential regression from my mind but it will lead the boot 
time be longer.
   * In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms. 
Worst case, over 1 s in 8xx runs (of 1000).
   * I think the stability is important than performance in this case.

  [Other Info]
   * For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm 
will meet this issue still. The other potential fix (from either gdm or logind) 
is under discussion in 
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
   * u-d-c upstream fix: 
https://github.com/tseliot/ubuntu-drivers-common/pull/67

  ---

  Test environment/steps:
  1. A desktop or workstation which containing an iGPU.
  2. Plug a nvidia graphic card to the system and installing proprietary nvidia 
driver (470 in my case)
  3. Attach a monitor to dGPU and leave iGPU connect to nothing.
  (in my test environment, there is the other ethernet card and TBT4 cards)
  4. Reboot system.

  Based on:
  $ cat /lib/udev/rules.d/61-gdm.rules
  # disable Wayland on Hi17

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

2022-05-11 Thread Timmy Braun

Specific circumstances? I guess, but once you enable auto-hide and dock
at the bottom it feels like it affects everything you try to do. Even
clicking the preview sometimes makes the preview jump to the other
screen.

-- 
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 gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Triaged
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Triaged

Bug description:
  Currently testing a fresh install of the beta for 22.04.
  All packages are up to date.

  When having the dock auto-hide option enabled, a glitch occurs when opening 
the windows selector (when multiple instances of the same program are opened).
  The selector does open, but the dock will hide itself immediately instead of 
waiting for a selection. Selecting a window will then cause a glitch where the 
selector will align with the hidden dock in a non natural way before 
disappearing.

  A proposed fix would be to prevent the dock from auto-hiding when the
  miniatures selector opens and wait for a second input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-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 1725814] Re: The Activities top left button reacts to a mouse-up (e.g. drag and drop) instead of a click

2022-05-11 Thread João Pedro Seara

Daniel,

I have corrected my last post. Thanks!

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

Title:
  The Activities top left button reacts to a mouse-up (e.g. drag and
  drop) instead of a click

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  Honestly I have no idea which package this is in and I could not
  identify it by following the wiki page for identifying packages. I had
  no luck with the ubuntu-bug command either. Feel free to migrate at
  your discretion.

  The Activities menu/button at the top left in the desktop menu(?) bar
  seems to listen to left-mouse-up instead of a full click with the
  mouse.

  If I want to e.g. select all my files on the desktop by click-and-
  dragging a selection box and then end the selection at the top left of
  the screen I will then also activate the Activities button if I
  release the mouse button over it.

  I expect most button-like UI controls to only trigger on complete
  mouse clicks: mouse down, mouse up.

  Pretty much the *only* exception to this expectation -- that I can
  think of -- is when a click is initiated on one menu item and finishes
  on a menu item that is its peer.

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


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

[Desktop-packages] [Bug 1972856] Re: Cannot add printer

2022-05-11 Thread Till Kamppeter

@maxroby, could you run the following command:

ipptool -tv ipps://HPF80DAC5CDC21.local:631/ipp/print get-printer-
attributes.test > attrs.txt

and attach attrs.txt. Please also post the screen output of this ipptool
command. Thanks.

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

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

Title:
  Cannot add printer

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  When I try to add a HP OfficeJet the system cannot find drivers, it
  shows an error.

  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu12
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 15:25:16 2022
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2022-03-21 (49 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1972717] Re: Online accounts crashes on sign in

2022-05-11 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1965702, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1972717/+attachment/5587954/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1972717/+attachment/5587956/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1972717/+attachment/5587960/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1972717/+attachment/5587961/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1972717/+attachment/5587962/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1972717/+attachment/5587963/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1972717/+attachment/5587964/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1965702

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Online accounts crashes on sign in

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

Bug description:
  As requested by bug 1972123.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.4-1ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  8 15:15:28 2022
  ExecutablePath: /usr/bin/gnome-control-center
  ExecutableTimestamp: 1650481335
  InstallationDate: Installed on 2022-04-23 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: gnome-control-center online-accounts
  ProcCwd: /home/jason
  SegvAnalysis:
   Segfault happened at: 0x7f40d6c4f2eb:mov0x8,%rax
   PC (0x7f40d6c4f2eb) ok
   source "0x8" (0x0008) not located in a known VMA region (needed readable 
region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libffi.so.8
   ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
   ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare ssh-users 
sudo
  separator:

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


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

[Desktop-packages] [Bug 1939344] Re: Bluetooth, when turned off, does not disconnect from connected headphones

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth, when turned off, does not disconnect from connected
  headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  It seems like there is some sort of "disconnect" message that other
  operating systems (Android, MacOS) send to all connected bluetooth
  devices when the computer/phone's bluetooth system is turned off,
  which Ubuntu 20.04.02LTS does not.

  When I connect my headphones (Aftershokz Aeropex) to my 20.04.02LTS
  Ubuntu system (running on a Thinkpad X1 Carbon 3rd Gen), and then turn
  off bluetooth entire from Ubuntu settings, the headphones act as if
  the connection to its source device (i.e., the computer) has been lost
  unexpectedly, exactly in the same way they would if I'd walked out of
  range: they give a periodic "out of range" beep until I power-cycle
  them.

  If I specifically go into Ubuntu bluetooth settings and disconnect
  just the headphones, then the headphones do a quick beep to
  acknowledge the disconnection, and do not give "out of range"
  notifications.

  The expected behavior, which my two main other source devices do (a
  Macbook, my Android phone), is that when one turns off the bluetooth
  system, the source device sends that "disconnect" message to the
  headphones (headphones beep once), and there is no "out of range"
  beeping afterward.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-63-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  joe   400296 F pulseaudio
   /dev/snd/controlC0:  joe   400296 F pulseaudio
   /dev/snd/controlC1:  joe   400296 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  9 13:18:56 2021
  InstallationDate: Installed on 2021-03-10 (151 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Aeropex by AfterShokz
  Symptom_Type: None of the above
  Title: [Aeropex by AfterShokz, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2018
  dmi.bios.release: 1.26
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET48W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET48W(1.26):bd06/11/2018:br1.26:efr1.9:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BSCTO1WW
  dmi.product.sku: LENOVO_MT_20BS_BU_Think_FM_ThinkPad X1 Carbon 3rd
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1939344/+subscriptions


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

[Desktop-packages] [Bug 1884299] Re: Chromium snap won't run with nfs home drive

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

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

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

Title:
  Chromium snap won't run with nfs home drive

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

Bug description:
  My physical computer lab uses AutoFS home drives (per
  https://help.ubuntu.com/community/Autofs#Wildcard_characters).   If
  any user tries to run chromium browser, it fails.

  I assume it is related to these:
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
  But that says a fix was released, but seems toi only work for NFS home drives
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873
  That ones is reported as a dupe but it's not, AutoFS home drives still don't 
work.

  $ chromium -v
  cannot create user data directory: /home/test.student2/snap/chromium/1193: 
Stale file handle

  $ tail -f /var/log/syslog
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 
audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 
audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS

  $ apt policy chromium-browser
  chromium-browser:
    Installed: 81.0.4044.129-0ubuntu0.20.04.1
    Candidate: 81.0.4044.129-0ubuntu0.20.04.1
    Version table:
   *** 81.0.4044.129-0ubuntu0.20.04.1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   80.0.3987.163-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

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


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

[Desktop-packages] [Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

2022-05-11 Thread Andrew Conway

I got exactly the same errors as Miles above; a simple permission denied
error stopping things before AppArmor got involved.

I.e., the answer to Markus Kuhn's question is no, in fact even in
enforce mode there are no denied apparmor complaints.

I don't know whether this is because the gating problem is not being
able to read the ticket in /tmp, or whether being in the kernel solves
some of the apparmor issues, but the greater pickiness of kerberos user
definition is an issue. Do snaps run as a different uid?

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

Title:
  snapd is not autofs aware and fails with nfs home dir

Status in snapd:
  Fix Released
Status in firefox package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Fix Released

Bug description:
  This is similar to bugs 1662552 and 1782873. In 1782873, jdstrand
  asked me to open a new bug for this specific issue.

  In 1662552, snapd fails for nfs mounted home directories as network
  permissions are not enabled. A work around was implemented that works
  if the mount is done via a /home mount at boot. However this does not
  work if people mount home directories via autofs. This is probably the
  fundamental problem for 1782873 although there may be other issues.

  [ Why use autofs? If some but not all of users want to use nfs homes.
  In particular, I have a local user on all my accounts that does not
  require the nfs server to be up or the kerberos server to be up, or
  kerberos working on the client machines, etc. It is very useful when
  something goes wrong. It means I mount /home/user rather than /home
  (for several users). ]

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


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

[Desktop-packages] [Bug 1884299] Re: Chromium snap won't run with nfs home drive

2022-05-11 Thread Andrew Conway

Firefox also doesn't work now it is a snap in 22.04.

I think there are still multiple issues here. The original poster seems
to be using NVSv3 I believe based on the RPC errors (NFSv3 uses multiple
ports, one of which is called something like RPC, but I am not an expert
in this as I have only used NFSv4, which uses a single port). Is this
correct tylerecouture?

NFSv3 has no user authentication; NFSv4 uses Kerberos for authentication
(and privacy and tamper resistance). I think this brings in additional
problems as snaps don't appear to work with Kerberos

e.g.

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346

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

I get a very different error - a simple permission denied error rather
than an AppArmor problem.



** Bug watch added: Mozilla Bugzilla #1734791
   https://bugzilla.mozilla.org/show_bug.cgi?id=1734791

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

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

Title:
  Chromium snap won't run with nfs home drive

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

Bug description:
  My physical computer lab uses AutoFS home drives (per
  https://help.ubuntu.com/community/Autofs#Wildcard_characters).   If
  any user tries to run chromium browser, it fails.

  I assume it is related to these:
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
  But that says a fix was released, but seems toi only work for NFS home drives
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873
  That ones is reported as a dupe but it's not, AutoFS home drives still don't 
work.

  $ chromium -v
  cannot create user data directory: /home/test.student2/snap/chromium/1193: 
Stale file handle

  $ tail -f /var/log/syslog
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 
audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 
audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS

  $ apt policy chromium-browser
  chromium-browser:
    Installed: 81.0.4044.129-0ubuntu0.20.04.1
    Candidate: 81.0.4044.129-0ubuntu0.20.04.1
    Version table:
   *** 81.0.4044.129-0ubuntu0.20.04.1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   80.0.3987.163-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

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


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

[Desktop-packages] [Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

2022-05-11 Thread Paul White

** Tags added: bionic focal jammy

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Users with home directories in /home/$USER can run snap application,
  but users in /home/users/$USER can't.

  nate@WorkstationC:~$ snap --version
  snap2.32.8+18.04
  snapd   2.32.8+18.04
  series  16
  ubuntu  18.04
  kernel  4.15.0-22-generic
  nate@WorkstationC:~$ echo $HOME
  /home/users/nate
  nate@WorkstationC:~$ which hello-world
  /snap/bin/hello-world
  nate@WorkstationC:~$ hello-world
  cannot create nate data directory: /home/users/nate/snap/hello-world/27: 
Permission denied

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


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

[Desktop-packages] [Bug 1971532] Re: Fileselector Unable To Paste Into Filename

Upstream report https://gitlab.gnome.org/GNOME/gtk/-/issues/4905

** Changed in: gtk4 (Ubuntu)
   Status: Confirmed => Triaged

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4905
   https://gitlab.gnome.org/GNOME/gtk/-/issues/4905

** Also affects: gtk via
   https://gitlab.gnome.org/GNOME/gtk/-/issues/4905
   Importance: Unknown
   Status: Unknown

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

Title:
  Fileselector Unable To Paste Into Filename

Status in GTK+:
  Unknown
Status in gtk4 package in Ubuntu:
  Triaged

Bug description:
  related to a few other bug reports:

  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970168

  Save File prompt disallows paste to filename. Attached is a screenshot
  of what pops up. Tested in various directories.

  Info:

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04 LTS
  Release:  22.04
  Codename: jammy

  uname -a
  Linux j5awry-sys76 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

  
  snap version
  snap2.55.3+22.04ubuntu1
  snapd   2.55.3+22.04ubuntu1
  series  16
  ubuntu  22.04
  kernel  5.15.0-27-generic

  snap info firefox
  name:  firefox
  summary:   Mozilla Firefox web browser
  publisher: Mozilla✓
  store-url: https://snapcraft.io/firefox
  contact:   
https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla
  license:   unset
  description: |
Firefox is a powerful, extensible web browser with support for modern web
application technologies.
  commands:
- firefox
  snap-id:  3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
  tracking: latest/stable
  refresh-date: 21 days ago, at 14:48 CDT
  ...
  installed:  99.0.1-1   (1232) 163MB -

  (tracking latest/stable)

  Reproduction:

  Download a file to get file prompt
  Cut the name
  attempt to paste the name back in

  Reproducible when targeting ~/Downloads, ~/Documents, and /tmp

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


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

[Desktop-packages] [Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

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

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

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Users with home directories in /home/$USER can run snap application,
  but users in /home/users/$USER can't.

  nate@WorkstationC:~$ snap --version
  snap2.32.8+18.04
  snapd   2.32.8+18.04
  series  16
  ubuntu  18.04
  kernel  4.15.0-22-generic
  nate@WorkstationC:~$ echo $HOME
  /home/users/nate
  nate@WorkstationC:~$ which hello-world
  /snap/bin/hello-world
  nate@WorkstationC:~$ hello-world
  cannot create nate data directory: /home/users/nate/snap/hello-world/27: 
Permission denied

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


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

[Desktop-packages] [Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

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

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

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

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Users with home directories in /home/$USER can run snap application,
  but users in /home/users/$USER can't.

  nate@WorkstationC:~$ snap --version
  snap2.32.8+18.04
  snapd   2.32.8+18.04
  series  16
  ubuntu  18.04
  kernel  4.15.0-22-generic
  nate@WorkstationC:~$ echo $HOME
  /home/users/nate
  nate@WorkstationC:~$ which hello-world
  /snap/bin/hello-world
  nate@WorkstationC:~$ hello-world
  cannot create nate data directory: /home/users/nate/snap/hello-world/27: 
Permission denied

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


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

[Desktop-packages] [Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER

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 firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1776800

Title:
  Unable to start snap applications if user's home directory is not
  /home/$USER

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Users with home directories in /home/$USER can run snap application,
  but users in /home/users/$USER can't.

  nate@WorkstationC:~$ snap --version
  snap2.32.8+18.04
  snapd   2.32.8+18.04
  series  16
  ubuntu  18.04
  kernel  4.15.0-22-generic
  nate@WorkstationC:~$ echo $HOME
  /home/users/nate
  nate@WorkstationC:~$ which hello-world
  /snap/bin/hello-world
  nate@WorkstationC:~$ hello-world
  cannot create nate data directory: /home/users/nate/snap/hello-world/27: 
Permission denied

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


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

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

Public bug reported:

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

This was a contributing factor for LP: #1971415

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

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

It should show the service as "Active: inactive"

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

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

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

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

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

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

What could go wrong
---
The technical fix seems minimal, correct, and targeted to me.

** Affects: gnome-remote-desktop (Ubuntu)
Importance: Low
Status: Fix Committed

** Affects: gnome-remote-desktop (Ubuntu Jammy)
Importance: Low
Status: Triaged

** Tags: jammy

** Also affects: gnome-remote-desktop (Ubuntu Jammy)
Importance: Undecided
Status: New

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Importance: Undecided => Low

** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: New => Triaged

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

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

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

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

This was a contributing factor for LP: #1971415

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

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

It should show the service as "Active: inactive"

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

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

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

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

What could go wrong
---
The technical fix seems minimal, correct, and targeted to me.

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

[Desktop-packages] [Bug 1973014] [NEW] gnome-shell crashes on resume or session change

2022-05-11 Thread julien tous

Public bug reported:

Trying to change session with ctrl-alt f1 or suspend-resume the computer 
systematically leads to a crash on my system :
-First i can see the screen, but mouse an keyboard are not responsive.
-Then many visual artifacts appear on my secondary monitor.
-Then i get a new login prompt.

After that in dmesg i can see errors such as :

[ 6574.079637] gnome-shell[5525]: segfault at 55713299a720 ip 7f7c0af012e7 
sp 7ffc8932bdb8 error 4 in libgbm.so.1.0.0[7f7c0af0+8000]
[ 6574.079660] Code: 18 c3 90 f3 0f 1e fa 48 8b 07 ff a0 c0 00 00 00 0f 1f 00 
f3 0f 1e fa 48 8b 07 ff a0 a8 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07  a0 b0 
00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 b8 00 00 00

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30
Uname: Linux 5.15.0-27-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME-Classic:GNOME
Date: Wed May 11 15:05:07 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-04-23 (1114 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-05-01 (10 days ago)

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


** Tags: amd64 apport-bug jammy third-party-packages wayland-session

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

Title:
  gnome-shell crashes on resume or session change

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Trying to change session with ctrl-alt f1 or suspend-resume the computer 
systematically leads to a crash on my system :
  -First i can see the screen, but mouse an keyboard are not responsive.
  -Then many visual artifacts appear on my secondary monitor.
  -Then i get a new login prompt.

  After that in dmesg i can see errors such as :

  [ 6574.079637] gnome-shell[5525]: segfault at 55713299a720 ip 
7f7c0af012e7 sp 7ffc8932bdb8 error 4 in 
libgbm.so.1.0.0[7f7c0af0+8000]
  [ 6574.079660] Code: 18 c3 90 f3 0f 1e fa 48 8b 07 ff a0 c0 00 00 00 0f 1f 00 
f3 0f 1e fa 48 8b 07 ff a0 a8 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07  a0 b0 
00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 b8 00 00 00

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30
  Uname: Linux 5.15.0-27-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Wed May 11 15:05:07 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-04-23 (1114 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (10 days ago)

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


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

[Desktop-packages] [Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.

2022-05-11 Thread Adam Dyess

Another "side-effect" of this event is that the screen will instantly go
black after 30 idle seconds (it doesn't dim to black or use my normal
screen blank at 3 min inactivity setting).  This "side-effect" goes away
if I log-out of the gnome session and then back in again.

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

Title:
  The operating system does not ask for a password after unlocking the
  screen.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I found a security vulnerability in Ubuntu 22.04 LTS operating system 
(Laptops only) It is reproduced like this (in steps):
  1. I lock the screen Win + L
  2. Close the laptop lid
  3. Then I open the lid of the laptop
  4. I get a vulnerability, the operating system does not ask for a password, 
but immediately shows the desktop without the need to unlock it. that is, 
closing and opening the laptop lid leads to unlocking the screen without asking 
for a password.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:20:28 2022
  InstallationDate: Installed on 2022-04-21 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  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/1972812/+subscriptions


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

[Desktop-packages] [Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.

2022-05-11 Thread Adam Dyess

I have a crash report for gnome-shell as well -- but i can't seem to get
it uploaded to launchpad at the moment

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

Title:
  The operating system does not ask for a password after unlocking the
  screen.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I found a security vulnerability in Ubuntu 22.04 LTS operating system 
(Laptops only) It is reproduced like this (in steps):
  1. I lock the screen Win + L
  2. Close the laptop lid
  3. Then I open the lid of the laptop
  4. I get a vulnerability, the operating system does not ask for a password, 
but immediately shows the desktop without the need to unlock it. that is, 
closing and opening the laptop lid leads to unlocking the screen without asking 
for a password.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:20:28 2022
  InstallationDate: Installed on 2022-04-21 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  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/1972812/+subscriptions


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

[Desktop-packages] [Bug 1972812] Re: The operating system does not ask for a password after unlocking the screen.

2022-05-11 Thread Adam Dyess

This happens to me as well. These are the loaded extensions.


~/.local/share/gnome-shell/extensions
❯ /usr/bin/cat **/metadata.json
{
  "_generated": "Generated by SweetTooth, do not edit",
  "description": "A human-readable clock for the gnome-shell panel",
  "name": "Fuzzy Clock",
  "shell-version": [
"3.34",
"3.36",
"3.38",
"40.0",
"41.0",
"42.0"
  ],
  "url": "https://github.com/dallagi/gnome-shell-fuzzy-clock";,
  "uuid": "Fuzzy_Clock@dallagi",
  "version": 9
}
{
  "_generated": "Generated by SweetTooth, do not edit",
  "description": "The cat tells you the CPU usage by running speed",
  "name": "RunCat",
  "shell-version": [
"3.38",
"40",
"41",
"42"
  ],
  "url": "https://github.com/win0err/gnome-runcat";,
  "uuid": "run...@kolesnikov.se",
  "version": 18
}%

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

Title:
  The operating system does not ask for a password after unlocking the
  screen.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I found a security vulnerability in Ubuntu 22.04 LTS operating system 
(Laptops only) It is reproduced like this (in steps):
  1. I lock the screen Win + L
  2. Close the laptop lid
  3. Then I open the lid of the laptop
  4. I get a vulnerability, the operating system does not ask for a password, 
but immediately shows the desktop without the need to unlock it. that is, 
closing and opening the laptop lid leads to unlocking the screen without asking 
for a password.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:20:28 2022
  InstallationDate: Installed on 2022-04-21 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  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/1972812/+subscriptions


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

[Desktop-packages] [Bug 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29

2022-05-11 Thread Zachary Tahenakos

To reproduce this issue, the following can be done:

1. Create a jammy autopkgtest image via: autopkgtest-buildvm-cloud-ubuntu -r 
jammy
2. Install the 5.15.0-27-29+rfkill2 headers, modules, and unsigned image from 
https://launchpad.net/~ztahenakos/+archive/ubuntu/zt-test-kernels/+build/23733020
 into the image.
3. Run the network-manager autopkgtest

The kernel in step 2 is Jammy linux 5.15.0-27.28 with upstream
54f586a9153201 (rfkill: make new event layout opt-in) added on top.
Based on comments in include/uapi/linux/rfkill.h, userspace changes may
be necessary in order for correct communication with rfkill to work,
otherwise we may start to see more failures in rfkill based tests or
usage.

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

Title:
  network-manager/1.36.4-2ubuntu1 ADT test failure with
  linux/5.15.0-28.29

Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in urfkill package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in network-manager source package in Jammy:
  Invalid
Status in urfkill source package in Jammy:
  New

Bug description:
  This is a scripted bug report about ADT failures while running
  network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is
  caused by the dep8 tests of the tested source or the kernel has yet to
  be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz

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


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

[Desktop-packages] [Bug 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29

2022-05-11 Thread Zachary Tahenakos

** Also affects: urfkill
   Importance: Undecided
   Status: New

** No longer affects: urfkill

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

** Attachment added: "urfkill.log"
   
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1971418/+attachment/5588509/+files/urfkill.log

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

Title:
  network-manager/1.36.4-2ubuntu1 ADT test failure with
  linux/5.15.0-28.29

Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in urfkill package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Committed
Status in network-manager source package in Jammy:
  Invalid
Status in urfkill source package in Jammy:
  New

Bug description:
  This is a scripted bug report about ADT failures while running
  network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is
  caused by the dep8 tests of the tested source or the kernel has yet to
  be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz

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


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

[Desktop-packages] [Bug 1970658] Re: Update zenity to 3.42.1

I installed zenity 3.42.1-0ubuntu1 and verified that the test case works
correctly now (but it didn't work with the older zenity version).

** 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 zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1970658

Title:
  Update zenity to 3.42.1

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

Bug description:
  Impact
  --
  New stable release in the 3.42 series.

  https://gitlab.gnome.org/GNOME/zenity/-/blob/3.42.1/NEWS

  Test Case
  -
  zenity --info --text="1234566789 223456789 323456789 423456789 523456789 
623456789 723456789 823456789 923456789"

  Should wrap the dialog onto 2 lines, instead of one line for each set
  of numbers.

  What Could Go Wrong
  ---
  This is part of core GNOME so it falls under the microrelease exception.
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


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

[Desktop-packages] [Bug 1970788] Re: Update nautilus to 42.1.1

I am using nautilus 1:42.1.1-0ubuntu1 on Ubuntu 22.04 LTS and it works
well.

** 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 nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1970788

Title:
  Update nautilus to 42.1.1

Status in nautilus package in Ubuntu:
  Fix Committed
Status in nautilus source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  This is a new stable release in the GNOME 42 series

  https://gitlab.gnome.org/GNOME/nautilus/-/blob/42.1.1/NEWS

  Easiest change to see is improved theming with the High Contrast
  style.

  Test Case
  -
  Install the update
  Ensure that Nautilus still works well

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for nautilus

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


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

[Desktop-packages] [Bug 1969838] Re: Ubuntu-dock does not work when using Turkish Language

I installed language-pack-gnome-tr. I opened the Settings app and
switched the language to Turkish. I logged out and logged back in. The
Ubuntu Dock was missing.

I installed the gjs updates. I logged out and logged back in. The Ubuntu
Dock works again.

I also verified that the test.js script failed before the update but
works after the update.

** 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 gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1969838

Title:
  Ubuntu-dock does not work when using Turkish Language

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

Bug description:
  [ Impact ]

  Ubuntu dock doesn't work when Turkish language is selected.

  Issue on dash-to-dock's github: 
https://github.com/micheleg/dash-to-dock/issues/1687
  Ubuntu version: Ubuntu 22.04 LTS
  gnome-shell-extension-ubuntu-dock version: 72~ubuntu5

  
  [ Test case ]
  - Run ubuntu session
  - Ubuntu dock should be visible on a screen edge

  Alternatively:

  Save this test case in a file (i.e. /tmp/test.js):

  const { GLib, GObject } = imports.gi;
  const ImplicitProp = GObject.registerClass({
  Properties: {
  "prop-int": GObject.ParamSpec.uint(
  "prop-int", "prop-int", "prop-int",
  GObject.ParamFlags.READWRITE | GObject.ParamFlags.CONSTRUCT_ONLY,
  0, GLib.MAXUINT32, 55),
  },
  }, class DashToDock extends GObject.Object { });
  if (new ImplicitProp().propInt === undefined)
  throw new Error("Missing property")
  print('All good');

  In a terminal run:
   LC_ALL=tr_TR gjs /tmp/test.js

  The script should work without throwing any error.

  [ Regression potential ]

  Implicit properties on GJS may be wrongly computed, and further
  objects could have undefined properties.

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


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

[Desktop-packages] [Bug 1972991] [NEW] 22.04 Totem crashes on launch (segmentation fault)

2022-05-11 Thread Aaron Whitehouse

Public bug reported:

Hello,

Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem
crashing.

I have not been able to pin down when it works and when it doesn't, as
playing the same videos seems to work sometimes and not work others.
After it crashes, trying to open it again normally does not work and
trying to launch totem from the commandline gives a segmentation fault.

Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Segmentation fault (core dumped)

$ totem
Segmentation fault (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: totem 42.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 11 13:10:48 2022
InstallationDate: Installed on 2022-04-24 (16 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


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

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

Title:
  22.04 Totem crashes on launch (segmentation fault)

Status in totem package in Ubuntu:
  New

Bug description:
  Hello,

  Since upgrading (fresh reinstall) to 22.04, I have had issues with
  Totem crashing.

  I have not been able to pin down when it works and when it doesn't, as
  playing the same videos seems to work sometimes and not work others.
  After it crashes, trying to open it again normally does not work and
  trying to launch totem from the commandline gives a segmentation
  fault.

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

[Desktop-packages] [Bug 1969593] Re: rules to prevent non-root users from rebooting not taken into account

2022-05-11 Thread Marc Deslauriers

Great, thanks!

** Changed in: policykit-1 (Ubuntu)
   Status: Incomplete => Invalid

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

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

Title:
  rules to prevent non-root users from rebooting not taken into account

Status in policykit-1 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  On fresh Ubuntu Jammy installation, I add a 
"/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the 
following contents :
  [Disable power-off]
  Identity=unix-user:*
  Action=org.freedesktop.login1.power-off
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable power-off when others are logged in]
  Identity=unix-user:*
  Action=org.freedesktop.login1.power-off-multiple-sessions
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable_reboot]
  Identity=unix-user:*
  Action=org.freedesktop.login1.reboot
  ResultActive=no
  ResultInactive=no
  ResultAny=no

  [Disable_reboot_when_others_are_logged_in]
  Identity=unix-user:*
  Action=org.freedesktop.login1.reboot-multiple-sessions
  ResultActive=no
  ResultInactive=no
  ResultAny=no


  
  It must prevent non-root users from shutdowning and rebooting the system. But 
it only prevent shutdowning. Rebooting is still possible for a non-root user.

  We can see it using pkcheck command (as a non-root user) :
  $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo 
$?
  Not authorized.
  1
  $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $?
  0

  
  As this problem can lead to unexpected reboot on multi-users systems (a 
disponibilty concern), I checked the "This bug is a security vulnerability" box.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: policykit-1 0.105-33
  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: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 10:53:27 2022
  InstallationDate: Installed on 2022-04-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1840473] Re: Don't draw | character on the screen while key is typed. :-)

2022-05-11 Thread Bug Watch Updater

** Bug watch added: Red Hat Bugzilla #2083314
   https://bugzilla.redhat.com/show_bug.cgi?id=2083314

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

Title:
  Don't draw | character on the screen while key is typed.   :-)

Status in xorg-server package in Ubuntu:
  Invalid
Status in xfwm4 package in Fedora:
  Invalid

Bug description:
  Edit:
  more padding.

  Problem:
  don't draw | on the screen, it makes no sense!  :)

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


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

[Desktop-packages] [Bug 1840473]

2022-05-11 Thread xfyzw7

| character is bent!


duplicate of bug:   https://bugzilla.redhat.com/show_bug.cgi?id=2083314 
(bent numbers and capital letters)

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

Title:
  Don't draw | character on the screen while key is typed.   :-)

Status in xorg-server package in Ubuntu:
  Invalid
Status in xfwm4 package in Fedora:
  Invalid

Bug description:
  Edit:
  more padding.

  Problem:
  don't draw | on the screen, it makes no sense!  :)

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


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

[Desktop-packages] [Bug 1840473]

2022-05-11 Thread xfyzw7

Nope, what feels off about animated "|" character I think is
that it needs to be hidden and only appear in animation form
when user hasn't typed around 30 seconds or 15 seconds.   :)

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

Title:
  Don't draw | character on the screen while key is typed.   :-)

Status in xorg-server package in Ubuntu:
  Invalid
Status in xfwm4 package in Fedora:
  Invalid

Bug description:
  Edit:
  more padding.

  Problem:
  don't draw | on the screen, it makes no sense!  :)

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


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

[Desktop-packages] [Bug 1972809] Re: Cant enable ua from GUI, works from CLI

** Package changed: ubuntu-advantage-tools (Ubuntu) => ubuntu-advantage-
desktop-daemon (Ubuntu)

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  Cant enable ua from GUI, works from CLI

Status in ubuntu-advantage-desktop-daemon package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  I have the same UI red message when tryng to enable ua from the GUI on
  a 22.04 LTS fresh install:

  https://askubuntu.com/questions/1403568/can-not-enable-livepatch-
  service-on-22-04

  Step to reproduce:

   1 : open the GUI, a link to get the token is displayed ( 
https://ubuntu.com/advantage )
   2 : I copy past the token into the prompted field
   3 : The GUI says it is successfuly linked, but can't activate livepatch
   4 : Checking on the advantage page, only 1 active device out of a max of 3
   5 : I rebooted (to make sure it wasn't something due with the linux-firmware 
update just received few minutes earlier) and tryed again from the GUI: says 
device is linked, but using the switch on button doesnt enable successfuly 
livepatch
   6 : I use the anwser from the previous askubuntu link ( `sudo ua enable 
livepatch`  )
   7 : it says it was enabled with success, top icon appear, a shield with a 
green check, opening the GUI says it is well enabled, 

  expected result:

  on step 3 it should had work as same it worked from CLI and jump to
  step 7 (success)


  note: note sure I reported it against the right package, sorry if
  that's the case, tryed ubuntu-bug ua, didnt worked, i just picked the
  first package in launchpad talking about advantage

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-advantage-tools 27.8~22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 10:57:23 2022
  InstallationDate: Installed on 2022-04-29 (10 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-advantage-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1972809/+subscriptions


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

[Desktop-packages] [Bug 1972809] [NEW] Cant enable ua from GUI, works from CLI

You have been subscribed to a public bug:

Hi,

I have the same UI red message when tryng to enable ua from the GUI on a
22.04 LTS fresh install:

https://askubuntu.com/questions/1403568/can-not-enable-livepatch-
service-on-22-04

Step to reproduce:

 1 : open the GUI, a link to get the token is displayed ( 
https://ubuntu.com/advantage )
 2 : I copy past the token into the prompted field
 3 : The GUI says it is successfuly linked, but can't activate livepatch
 4 : Checking on the advantage page, only 1 active device out of a max of 3
 5 : I rebooted (to make sure it wasn't something due with the linux-firmware 
update just received few minutes earlier) and tryed again from the GUI: says 
device is linked, but using the switch on button doesnt enable successfuly 
livepatch
 6 : I use the anwser from the previous askubuntu link ( `sudo ua enable 
livepatch`  )
 7 : it says it was enabled with success, top icon appear, a shield with a 
green check, opening the GUI says it is well enabled, 

expected result:

on step 3 it should had work as same it worked from CLI and jump to step
7 (success)


note: note sure I reported it against the right package, sorry if that's
the case, tryed ubuntu-bug ua, didnt worked, i just picked the first
package in launchpad talking about advantage

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-advantage-tools 27.8~22.04.1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue May 10 10:57:23 2022
InstallationDate: Installed on 2022-04-29 (10 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-advantage-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-advantage-desktop-daemon (Ubuntu)
 Importance: High
 Assignee: Sebastien Bacher (seb128)
 Status: In Progress


** Tags: amd64 apport-bug jammy rls-jj-incoming
-- 
Cant enable ua from GUI, works from CLI
https://bugs.launchpad.net/bugs/1972809
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to ubuntu-advantage-desktop-daemon 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 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

The failed n-m autopkgtest worked on retry, netplan seems flacky before
that upload but was retried now

** 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 wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1962541

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  Connecting to some PEAP wifi doesn't work anymore since the openssl3
  transition

  Details on the issue can be found on
  http://lists.infradead.org/pipermail/hostap/2022-May/040511.html

  * Test case

  Try using a PEAP wifi not implementing RFC5746, it should be able to
  connect

  * Regression potential

  The change allows to connect to less secure WiFis the same way that
  wpa allowed before openssl3, lower security enforcement isn't ideal
  but still better than non working hardware.

  

  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2022-02-27T21:07:16.553410

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


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

[Desktop-packages] [Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working

Thanks for testing, I'm marking the SRU as verified!

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

Status in wpa package in Ubuntu:
  Fix Committed
Status in wpa source package in Jammy:
  Fix Committed

Bug description:
  * Impact

  Connecting to some PEAP wifi doesn't work anymore since the openssl3
  transition

  Details on the issue can be found on
  http://lists.infradead.org/pipermail/hostap/2022-May/040511.html

  * Test case

  Try using a PEAP wifi not implementing RFC5746, it should be able to
  connect

  * Regression potential

  The change allows to connect to less secure WiFis the same way that
  wpa allowed before openssl3, lower security enforcement isn't ideal
  but still better than non working hardware.

  

  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2022-02-27T21:07:16.553410

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


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

[Desktop-packages] [Bug 1966091] Re: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic

2022-05-11 Thread Tejesember

5.13.0-41-generic fixed this issue for me too.

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

Title:
  Random noises with 5.13.0-37-generic and later but not with
  5.13.0-35-generic

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a recent update to linux-image-5.13.0-37-generic, I started
  experiencing random noises about every five seconds.  After rebooting
  into linux-image-5.13.0-35-generic, the noises were gone.

  Some details that I've noticed:

  1.  When launching pulseaudio manually, not as a daemon, the problem
  disappears.

  2.  If I set the log-level in /etc/pulse/daemon.conf to debug and
  reload it, the log has a lot of:

  Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!

  Which roughly correspond with the noises.

  3.  The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa
  force-reload" doesn't seem to help.  Only a kernel downgrade does.

  4.  This happens both in Firefox (where I first noticed it) as well as
  in Totem and in system sounds.

  5.  I tried to report the bug using "ubuntu-bug audio", but it showed
  me six inputs of which three looked the same, and for each of them it
  told me that it pulseaudio wasn't configured to use it.  I'm ready to
  collect logs and other info within the next days.


  Additional Info

$ lsb_release -a
  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  Codename: focal

$ apt-cache policy linux-image-generic-hwe-20.04
  linux-image-generic-hwe-20.04:
Installed: 5.13.0.37.42~20.04.22
Candidate: 5.13.0.37.42~20.04.22
Version table:
   *** 5.13.0.37.42~20.04.22 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
  100 /var/lib/dpkg/status
   5.4.0.26.32 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

$ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.13
Candidate: 1:13.99.1-1ubuntu3.13
Version table:
   *** 1:13.99.1-1ubuntu3.13 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.8 500
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
   1:13.99.1-1ubuntu3 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

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


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

[Desktop-packages] [Bug 1972984] [NEW] Cannot paste filename into File Save dialog of Firefox Snap

2022-05-11 Thread vanadium

Public bug reported:

Steps to reproduce the problem:

1. Copy a file name or a file path to the clipboard
2. Open Firefox
3. Hit Ctrl+S to open the File Save dialog.
4. Make sure that the "Name" field has focus (which it may not because of 
another bug) and attempt to paste: Ctrl+V

Expected behavior: the contents of the clipboard is entered into the "Name" 
field.
Observed behaviour: a dialog box appears with error message:

"
The folder contents could not be displayed
Operation not supported 
"
In the same spirit, editing an existing name by e.g. copying/cutting part of 
the name/path and pasting it back elsewhere in the field does not work.

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

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

Title:
  Cannot paste filename into File Save dialog of Firefox Snap

Status in mutter package in Ubuntu:
  New

Bug description:
  Steps to reproduce the problem:

  1. Copy a file name or a file path to the clipboard
  2. Open Firefox
  3. Hit Ctrl+S to open the File Save dialog.
  4. Make sure that the "Name" field has focus (which it may not because of 
another bug) and attempt to paste: Ctrl+V

  Expected behavior: the contents of the clipboard is entered into the "Name" 
field.
  Observed behaviour: a dialog box appears with error message:

  "
  The folder contents could not be displayed
  Operation not supported 
  "
  In the same spirit, editing an existing name by e.g. copying/cutting part of 
the name/path and pasting it back elsewhere in the field does not work.

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


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

[Desktop-packages] [Bug 1972983] [NEW] File dialog in snap firefox does not have keyboard focus

2022-05-11 Thread vanadium

Public bug reported:

Steps to reproduce the issue.

After first log in into Ubuntu Desktop 22.04

1. Launch Firefox and open a website (e.g. www.ubuntu.com)
2. Hit Ctrl+S to open the Save file dialog.
3. Type "Ubuntu" to replace the default file name ("Enterprise Open Source and 
Linux | Ubuntu.html"). Hit Enter. It works the first time round.
4. Hit Ctrl+S to open the Save file dialog again.
5. Type "Ubuntu - 2" to replace the default file name ("Enterprise Open Source 
and Linux | Ubuntu.html"). This time, your typing fails: the file dialog is not 
in focus.

Expected behavior anytime when opening a File dialog: the file dialog
should have keyboard focus.

Observed behavior: the file dialog does not have focus, except the very
first time in the session.

Same observations also for File Open dialogs.

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

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

Title:
  File dialog in snap firefox does not have keyboard focus

Status in mutter package in Ubuntu:
  New

Bug description:
  Steps to reproduce the issue.

  After first log in into Ubuntu Desktop 22.04

  1. Launch Firefox and open a website (e.g. www.ubuntu.com)
  2. Hit Ctrl+S to open the Save file dialog.
  3. Type "Ubuntu" to replace the default file name ("Enterprise Open Source 
and Linux | Ubuntu.html"). Hit Enter. It works the first time round.
  4. Hit Ctrl+S to open the Save file dialog again.
  5. Type "Ubuntu - 2" to replace the default file name ("Enterprise Open 
Source and Linux | Ubuntu.html"). This time, your typing fails: the file dialog 
is not in focus.

  Expected behavior anytime when opening a File dialog: the file dialog
  should have keyboard focus.

  Observed behavior: the file dialog does not have focus, except the
  very first time in the session.

  Same observations also for File Open dialogs.

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


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

[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

2022-05-11 Thread Vitor Martins

Comment #51 fixed all my problems.
unsafe legacy renegotiation disabled & SSL_connect error:0A0C0103:SSL 
routines::internal error

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  Fix Released

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1966091] Re: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic

2022-05-11 Thread Ainar Garipov

Seems to be fixed for me with 5.13.0-41-generic.  Can anyone else
confirm?

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

Title:
  Random noises with 5.13.0-37-generic and later but not with
  5.13.0-35-generic

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a recent update to linux-image-5.13.0-37-generic, I started
  experiencing random noises about every five seconds.  After rebooting
  into linux-image-5.13.0-35-generic, the noises were gone.

  Some details that I've noticed:

  1.  When launching pulseaudio manually, not as a daemon, the problem
  disappears.

  2.  If I set the log-level in /etc/pulse/daemon.conf to debug and
  reload it, the log has a lot of:

  Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!

  Which roughly correspond with the noises.

  3.  The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa
  force-reload" doesn't seem to help.  Only a kernel downgrade does.

  4.  This happens both in Firefox (where I first noticed it) as well as
  in Totem and in system sounds.

  5.  I tried to report the bug using "ubuntu-bug audio", but it showed
  me six inputs of which three looked the same, and for each of them it
  told me that it pulseaudio wasn't configured to use it.  I'm ready to
  collect logs and other info within the next days.


  Additional Info

$ lsb_release -a
  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  Codename: focal

$ apt-cache policy linux-image-generic-hwe-20.04
  linux-image-generic-hwe-20.04:
Installed: 5.13.0.37.42~20.04.22
Candidate: 5.13.0.37.42~20.04.22
Version table:
   *** 5.13.0.37.42~20.04.22 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
  100 /var/lib/dpkg/status
   5.4.0.26.32 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

$ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.13
Candidate: 1:13.99.1-1ubuntu3.13
Version table:
   *** 1:13.99.1-1ubuntu3.13 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.8 500
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
   1:13.99.1-1ubuntu3 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

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


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

[Desktop-packages] [Bug 1689443] Re: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch

** Tags removed: artful wily yakkety zesty
** Tags added: jammy

** Changed in: bluez (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  bluetoothd crashed with SIGSEGV in g_io_channel_unref from
  control_connect_cb from connect_cb from g_main_dispatch from
  g_main_context_dispatch

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
bluez.  This problem was most recently seen with package version 5.43-0ubuntu1, 
the problem page at 
https://errors.ubuntu.com/problem/60e9f362576651ff41d2c58e273c79aa15824ad8 
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 you can request it at 
http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1556324] Re: bluetoothd crashed with SIGSEGV in encrypt_notify from g_main_dispatch from g_main_context_dispatch from g_main_context_iterate from g_main_loop_run

** Tags removed: artful wily yakkety zesty
** Tags added: jammy

** Changed in: bluez (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  bluetoothd crashed with SIGSEGV in encrypt_notify from g_main_dispatch
  from g_main_context_dispatch from g_main_context_iterate from
  g_main_loop_run

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding bluez.  This problem was most recently seen with version
  5.36-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/20c758a42f23b514e8bc98469a414de3ed9b727f
  contains more details.

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


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

[Desktop-packages] [Bug 1972978] Re: /usr/bin/gnome-shell:11:meta_context_terminate:process_ice_messages:process_ice_messages:g_main_dispatch:g_main_context_dispatch

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

** This bug has been marked a duplicate of bug 1959937
   gnome-shell crashed with SIGSEGV in meta_context_terminate(context=0x0) from 
process_ice_messages()

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_context_terminate:process_ice_messages:process_ice_messages:g_main_dispatch:g_main_context_dispatch

Status in gnome-shell package in Ubuntu:
  New

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~beta-1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/fc75ee04fbc965ec925af6675c012cd4e03a770b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


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

[Desktop-packages] [Bug 1972978] [NEW] /usr/bin/gnome-shell:11:meta_context_terminate:process_ice_messages:process_ice_messages:g_main_dispatch:g_main_context_dispatch

2022-05-11 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42~beta-1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/fc75ee04fbc965ec925af6675c012cd4e03a770b 
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/.

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


** Tags: jammy

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

Title:
  /usr/bin/gnome-
  
shell:11:meta_context_terminate:process_ice_messages:process_ice_messages:g_main_dispatch:g_main_context_dispatch

Status in gnome-shell package in Ubuntu:
  New

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~beta-1ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/fc75ee04fbc965ec925af6675c012cd4e03a770b 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


-- 
Mailing list: https://launchpad.net/~desktop-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()

** Summary changed:

- 
/usr/bin/gnome-shell:11:crocus_begin_query:crocus_begin_query:crocus_end_query:crocus_end_query:tc_call_end_query
+ 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()

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

** Tags added: crocus

-- 
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/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 package in Ubuntu:
  New

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/ubuntu/+source/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] [NEW] 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()

2022-05-11 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: crocus jammy

-- 
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/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 package in Ubuntu:
  New

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/ubuntu/+source/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 1972889] Re: Screen reader reads the data while computer is locked

Please run:

  apport-collect 1972889

so we can see if there's anything unusual about your system.


** Tags added: a11y

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

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

Title:
  Screen reader reads the data while computer is locked

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  # lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  # apt-cache policy gnome-shell
  gnome-shell:
Installed: 42.0-2ubuntu1
Candidate: 42.0-2ubuntu1
Version table:
   *** 42.0-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  Ubuntu is installed on a laptop. Within five minutes of inactivity,
  the screen lock activates and locks the system. Computer is secured.
  10 minutes later, my cat (her name is Loaf) comes up to the laptop and
  sits down on the keyboard. This activates a screen reader. (Shortcut
  is Alt + Super + S)

  What I've expected:
  Screen reader would start reading the contents of a lock screen

  What happened:
  Screen reader app started reading contents of a Brave Browser window that was 
opened on my desktop. It read all tabs and proceeded reading the opened web 
page. 

  
  I've reported this bug at secur...@ubuntu.org and got the following answer:

  > Nice find - I am able to reproduce this locally in Ubuntu 22.04 LTS too
  > - I suspect this is a vulnerability in gnome-shell as it is
  > responsible for handling the lock screen in standard Ubuntu.

  As per further directions, I'm posting this bug here and in gnome
  repo.

  
  P.S. I expect Loaf being credited for this find. She really likes treats.

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


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

[Desktop-packages] [Bug 1972889] Re: Screen reader reads the data while computer is locked