date:20211027

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

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

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

Title:
  Installer inaccessible to Orca screen reader

Status in orca package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Expired

Bug description:
  In Impish (canary), when attempting to use the installer with the Orca
  screen reader for accessibility,  Orca cannot determine the states or
  roles of the form controls, and they all appear as 'grayed'. When I
  select an item, no feedback is given.  To reproduce:  start the Orca
  screen reader, on the live system, and select "install" option.  Move
  among the locale selector. Orca will read the language name and add
  "frame grayed". Select one by hitting the space bar on it. Orca should
  read "selected", but it remains silent.  When you tab among the
  options, you'll eventually hear that you are on the 'next' button,
  yet, it, too, will be described as "grayed".  The behavior described
  here will appear on all pages of the installer wizard.

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


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

[Desktop-packages] [Bug 1941003] Re: Installer inaccessible to Orca screen reader

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

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

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

Title:
  Installer inaccessible to Orca screen reader

Status in orca package in Ubuntu:
  Expired
Status in ubiquity package in Ubuntu:
  Expired

Bug description:
  In Impish (canary), when attempting to use the installer with the Orca
  screen reader for accessibility,  Orca cannot determine the states or
  roles of the form controls, and they all appear as 'grayed'. When I
  select an item, no feedback is given.  To reproduce:  start the Orca
  screen reader, on the live system, and select "install" option.  Move
  among the locale selector. Orca will read the language name and add
  "frame grayed". Select one by hitting the space bar on it. Orca should
  read "selected", but it remains silent.  When you tab among the
  options, you'll eventually hear that you are on the 'next' button,
  yet, it, too, will be described as "grayed".  The behavior described
  here will appear on all pages of the installer wizard.

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


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

[Desktop-packages] [Bug 1948990] Re: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash

It appears BlueZ upstream does not restart on failure, but in Ubuntu we
turned on restart-on-failure in version 5.53-0ubuntu3. I suggest the
best way to get that fix right now is to upgrade to Ubuntu 20.04.

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

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

Title:
  Bluetooth does not turn on via gnome-control-center after
  bluetooth.service crash

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  I had bluetooth crash (see logs below).  After the crash, I attempted
  to restart bluetooth by pressing the On/Off switch in the top-right of
  the Bluetooth tab of gnome-control-center (it was set to off).  After
  pressing the switch, the switch read "On", but the display of
  Bluetooth devices still appeared as it does when Bluetooth is off (it
  read "Bluetooth Turned Off\nTurn on to connect devices and receive
  file transfers.").

  I was able to remedy the situation by manually executing `sudo
  bluetoothd`.  I did this while the above On/Off switch was "Off" and
  the Bluetooth device list said Bluetooth was off.  After executing,
  the Bluetooth device list listed all my Bluetooth devices as expected.

  This is with bluetoothd 5.48.

  Bluetooth crash logs

  ```
  12:22:15 pulseaudio: (6856.168|   0.576) [pulseaudio] bluez5-util.c: 
Bluetooth daemon disappeared
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, 
status=11/SEGV
  12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
  10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH 
HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  Uname: Linux 5.10.0-051000-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 27 13:00:09 2021
  InstallationDate: Installed on 2021-01-04 (295 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/bluez/+bug/1948990/+subscriptions


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

[Desktop-packages] [Bug 1948990] Re: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash

I don't think the GUI is meant to start bluetoothd at all. It only
toggles the power state of the Bluetooth hardware. It assumes bluetoothd
is always running. So failure to restart after a crash is a problem with
bluez's systemd scripting.

** Package changed: gnome-control-center (Ubuntu) => bluez (Ubuntu)

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

Title:
  Bluetooth does not turn on via gnome-control-center after
  bluetooth.service crash

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  I had bluetooth crash (see logs below).  After the crash, I attempted
  to restart bluetooth by pressing the On/Off switch in the top-right of
  the Bluetooth tab of gnome-control-center (it was set to off).  After
  pressing the switch, the switch read "On", but the display of
  Bluetooth devices still appeared as it does when Bluetooth is off (it
  read "Bluetooth Turned Off\nTurn on to connect devices and receive
  file transfers.").

  I was able to remedy the situation by manually executing `sudo
  bluetoothd`.  I did this while the above On/Off switch was "Off" and
  the Bluetooth device list said Bluetooth was off.  After executing,
  the Bluetooth device list listed all my Bluetooth devices as expected.

  This is with bluetoothd 5.48.

  Bluetooth crash logs

  ```
  12:22:15 pulseaudio: (6856.168|   0.576) [pulseaudio] bluez5-util.c: 
Bluetooth daemon disappeared
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, 
status=11/SEGV
  12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
  10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH 
HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  Uname: Linux 5.10.0-051000-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.26
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 27 13:00:09 2021
  InstallationDate: Installed on 2021-01-04 (295 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/bluez/+bug/1948990/+subscriptions


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

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

The fix in mutter 40.6 could apply to any app. Wait till this fix is
released and if you still have problems with Inkscape after that then a
new bug would need to be opened.

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

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Unknown
Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

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


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

[Desktop-packages] [Bug 1948978] Re: Thunderbird write e-mail window never released in wayland

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

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 1932328, 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 1932328
   Thunderbird under Wayland does not correctly close (or manage) windows

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

Title:
  Thunderbird write e-mail window never released in wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  If I run Thunderbird (latest version), when I write an e-mail or reply
  to an e-mail, a new window opens. When I send the e-mail, it works
  correctly and the e-mail is sent, but the red dot on the Thunderbird
  icon on the task bar never goes out. If I close or pkill Thunderbird,
  only the main Thunderbird window is released by the display manager
  and it is not possible to open Thunderbird again without logging out
  or restarting gdm3. This is with Wayland. There is no Thunderbird
  process left to kill.

  Everything works fine with Xorg, so on this computer running 21.10, I
  will be using Xorg instead of Wayland for now.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 27 14:53:29 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [1179:ff67]
 Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [1179:ff67]
  InstallationDate: Installed on 2020-03-06 (600 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: TOSHIBA Satellite L305
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=baeb07e4-08ee-4d13-be78-7571c5723e1d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd12/09/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-04X02F:skuMontevina_Fab:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Satellite L305
  dmi.product.sku: Montevina_Fab
  dmi.product.version: PSLB8U-04X02F
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Desktop-packages] [Bug 1948589] Re: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimat

Please run:

  gsettings list-recursively org.gnome.shell > settings.txt

and attach the resulting text file here.


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

Title:
  JS ERROR: Error: Expected an object of type ClutterActor for argument
  'sibling' but got type undefined
  _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 development branch with kernel 5.13.0-19-generic @
  24/10/2021 (wayland)

  Testing 4 apps on 4 dynamic workspaces, on switching the apps by clicking 
their icons
  from the dock, im getting a lot of JS ERRORS in the journal logs, the more i 
switch
  between the apps, the more the errors reproduce:

  okt 24 18:54:15 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:15 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:16 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:16 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:29 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:29 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:31 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:32 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 24 18:56:39 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

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


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

[Desktop-packages] [Bug 1948778] Re: Random flashes in gnome-shell

Wayland is only a communication protocol between the app and the server.
The underlying screen updates are implemented by gnome-shell (via
libmutter) using KMS. You can make it log LOTS of information by adding
this to /etc/environment:

  MUTTER_DEBUG=kms

If you do that and then record a separate log each time a flash happens:

  journalctl -b0 > anotherflash.txt

then that might be useful.

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

Title:
  Random flashes in gnome-shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 development branch up to date to latest @ 26/10/2021
  kernel 5.13.0-19-generic

  While working around on the desktop i'm getting short screen flashes like a 
screenshot style
  i cant reproduce them, they seem to come on random like every few minutes
  journal logs dont record anything while they occur

  this only happens on wayland, tested a long session on xorg where they
  dont occur

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 26 11:12:30 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

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


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

[Desktop-packages] [Bug 1948996] [NEW] (gnome-software) Application icons not showing in 200% scaling environment

2021-10-27 Thread Saroumane

Public bug reported:

Ubuntu 21.10 (existing or fresh install, same result)
Package : gnome-software 40.4-1build1
In Gnome Settings / Display : scaling is set to 200%.

Since I upgraded to Gnome 40.4 (with Ubuntu 21.10), gnome-software does
not display anymore most of applications icons when I scale the screen
to 200%.

Steps to reproduce the bug :

1.Boot on a fresh Ubuntu 21.10 USB Live environnement.
2.Install and launch gnome-software (check the "universe" repo first in
software-properties-gtk)
3.Notice that everything is fine, then quit gnome-software.
4. Use gnome settings / display to scale to 200% (or $ gsettings set
org.gnome.settings-daemon.plugins.xsettings overrides
"[{'Gdk/WindowScalingFactor', <2>}]" )
5. Launch again gnome-software. Notice most icons are missing. (see file
attached)

Bug IS NOT reproduced with Fedora 34 / Gnome 40.4
Bug IS NOT reproduced with Fedora 34 / Gnome 40.0
Bug IS NOT reproduced with Ubuntu 21.04

Bug is presumably not upstream, as discussed here
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1516

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

** Attachment added: "Screenshot_from_2021-10-24_15-28-13.png"

https://bugs.launchpad.net/bugs/1948996/+attachment/5536536/+files/Screenshot_from_2021-10-24_15-28-13.png

** Package changed: rhythmbox (Ubuntu) => gnome-software (Ubuntu)

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

Title:
(gnome-software) Application icons not showing in 200% scaling
environment

Status in gnome-software package in Ubuntu:
New

Bug description:
Ubuntu 21.10 (existing or fresh install, same result)
Package : gnome-software 40.4-1build1
In Gnome Settings / Display : scaling is set to 200%.

Since I upgraded to Gnome 40.4 (with Ubuntu 21.10), gnome-software
does not display anymore most of applications icons when I scale the
screen to 200%.

Steps to reproduce the bug :

Bug IS NOT reproduced with Fedora 34 / Gnome 40.4
Bug IS NOT reproduced with Fedora 34 / Gnome 40.0
Bug IS NOT reproduced with Ubuntu 21.04

Bug is presumably not upstream, as discussed here
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1516

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

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

[Desktop-packages] [Bug 1948877] Re: Bluetooth headphones media buttons no longer work

2021-10-27 Thread Roman

Exact package causing the issue is not obvious, but I add bluez.

** Package changed: ubuntu => bluez (Ubuntu)

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

Title:
  Bluetooth headphones media buttons no longer work

Status in bluez package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, most media buttons in my bluetooth headphones
  stopped working. This includes the "play/pause" button, "play next"
  (calls after long press of volume increase), and "play previous" (long
  press of volume decrease). The volume +/- buttons themselves are
  working, but this seemingly is implemented entirely in the headphones
  and does not require any communication over bluetooth.

  In previous ubuntu (20.04) these buttons worked, and I expect them
  working.

  My headset is Qumo Accord 3.

  Here is output of "inxi -Eaz" in terminal:

  Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 
 serial:  
 Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 
 rev: e2f 
 Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept 
 service-classes: rendering, capturing, object transfer, audio, 
telephony

  Some possible workarounds that I found suggest to "modprobe uinput",
  but the uinput module does not get loaded (lsmod does not list it even
  after modprobe'ing).

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


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

[Desktop-packages] [Bug 1948990] Re: Bluetooth does not turn on via gnome-control-center after bluetooth.service crash

2021-10-27 Thread Fletcher Porter

Here's a more complete set of logs around the bluetooth crash


```
12:22:15 gnome-shell: JS ERROR: TypeError: monitor is null
_reposition@resource:///org/gnome/shell/ui/boxpointer.js:508:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_allocate@resource:///org/gnome/shell/ui/boxpointer.js:235:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_init/<@resource:///org/gnome/shell/ui/layout.js:210:17

12:22:15 pulseaudio: (6856.168|   0.000) [pulseaudio] flist.c: 
pulsecore/hashmap.c: entries flist is full (don't worry)
12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
12:22:15 kernel: Code: c0 c3 66 0f 1f 44 00 00 31 c0 48 85 ff 74 59 53 48 8b 4f 
08 48 89 fb 48 85 c9 74 43 48 3b 31 48 8b 79 08 74 4b 48 85 ff 74 5e <48> 39 37 
48 8b 47 08 74 0d 48 89 f9 48 89 c7 eb ea 0f 1f 44 00 00
12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
12:22:15 kernel: show_signal_msg: 5 callbacks suppressed
12:22:15 upowerd: unhandled action 'unbind' on 
/sys/devices/virtual/misc/uhid/0005:046D:B019.0007
12:22:15 gdm-x-session: (II) systemd-logind: releasing fd for 13:87
12:22:15 gnome-shell: g_array_unref: assertion 'array' failed
12:22:15 gdm-x-session: (II) event23 - MX Master 2S Mouse: device removed
12:22:15 gdm-x-session: (II) event23 - MX Master 2S Mouse: device removed
12:22:15 gdm-x-session: (**) Option "fd" "72"
12:22:15 gdm-x-session: (II) config/udev: removing device MX Master 2S Mouse
12:22:15 gnome-shell: g_array_unref: assertion 'array' failed
12:22:15 gdm-x-session: (II) systemd-logind: releasing fd for 13:86
12:22:15 gdm-x-session: (II) systemd-logind: releasing fd for 13:86
12:22:15 gdm-x-session: (II) UnloadModule: "libinput"
12:22:15 gdm-x-session: (II) event22 - MX Master 2S Keyboard: device removed
12:22:15 gdm-x-session: (**) Option "fd" "60"
12:22:15 gdm-x-session: (II) config/udev: removing device MX Master 2S Keyboard
12:22:15 acpid: input device has been disconnected, fd 22
12:22:14 gnome-shell: JS ERROR: TypeError: monitor is null
_reposition@resource:///org/gnome/shell/ui/boxpointer.js:508:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_allocate@resource:///org/gnome/shell/ui/boxpointer.js:235:13
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_init/<@resource:///org/gnome/shell/ui/layout.js:210:17

12:22:14 pulseaudio: (6855.591|  86.788) [pulseaudio] bluez5-util.c: Properties 
changed in device /org/bluez/hci0/dev_E8_F7_90_05_99_E4
```

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

Title:
  Bluetooth does not turn on via gnome-control-center after
  bluetooth.service crash

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

Bug description:
  I had bluetooth crash (see logs below).  After the crash, I attempted
  to restart bluetooth by pressing the On/Off switch in the top-right of
  the Bluetooth tab of gnome-control-center (it was set to off).  After
  pressing the switch, the switch read "On", but the display of
  Bluetooth devices still appeared as it does when Bluetooth is off (it
  read "Bluetooth Turned Off\nTurn on to connect devices and receive
  file transfers.").

  I was able to remedy the situation by manually executing `sudo
  bluetoothd`.  I did this while the above On/Off switch was "Off" and
  the Bluetooth device list said Bluetooth was off.  After executing,
  the Bluetooth device list listed all my Bluetooth devices as expected.

  This is with bluetoothd 5.48.

  Bluetooth crash logs

  ```
  12:22:15 pulseaudio: (6856.168|   0.576) [pulseaudio] bluez5-util.c: 
Bluetooth daemon disappeared
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, 
status=11/SEGV
  12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
  10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH 
HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  Uname: Linux

[Desktop-packages] [Bug 1948877] [NEW] Bluetooth headphones media buttons no longer work

You have been subscribed to a public bug:

In KUbuntu 21.10, most media buttons in my bluetooth headphones stopped
working. This includes the "play/pause" button, "play next" (calls after
long press of volume increase), and "play previous" (long press of
volume decrease). The volume +/- buttons themselves are working, but
this seemingly is implemented entirely in the headphones and does not
require any communication over bluetooth.

In previous ubuntu (20.04) these buttons worked, and I expect them
working.

My headset is Qumo Accord 3.

Here is output of "inxi -Eaz" in terminal:

Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 
   serial:  
   Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 
   rev: e2f 
   Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff 
park link-mode: slave accept 
   service-classes: rendering, capturing, object transfer, audio, 
telephony

Some possible workarounds that I found suggest to "modprobe uinput", but
the uinput module does not get loaded (lsmod does not list it even after
modprobe'ing).

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


** Tags: bot-comment
-- 
Bluetooth headphones media buttons no longer work
https://bugs.launchpad.net/bugs/1948877
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to bluez 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 1948990] [NEW] Bluetooth does not turn on via gnome-control-center after bluetooth.service crash

2021-10-27 Thread Fletcher Porter

Public bug reported:

I had bluetooth crash (see logs below).  After the crash, I attempted to
restart bluetooth by pressing the On/Off switch in the top-right of the
Bluetooth tab of gnome-control-center (it was set to off).  After
pressing the switch, the switch read "On", but the display of Bluetooth
devices still appeared as it does when Bluetooth is off (it read
"Bluetooth Turned Off\nTurn on to connect devices and receive file
transfers.").

I was able to remedy the situation by manually executing `sudo
bluetoothd`.  I did this while the above On/Off switch was "Off" and the
Bluetooth device list said Bluetooth was off.  After executing, the
Bluetooth device list listed all my Bluetooth devices as expected.

This is with bluetoothd 5.48.

Bluetooth crash logs

```
12:22:15 pulseaudio: (6856.168|   0.576) [pulseaudio] bluez5-util.c: Bluetooth 
daemon disappeared
12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, 
status=11/SEGV
12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH HID 
v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
```

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
Uname: Linux 5.10.0-051000-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.26
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 27 13:00:09 2021
InstallationDate: Installed on 2021-01-04 (295 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Bluetooth does not turn on via gnome-control-center after
  bluetooth.service crash

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

Bug description:
  I had bluetooth crash (see logs below).  After the crash, I attempted
  to restart bluetooth by pressing the On/Off switch in the top-right of
  the Bluetooth tab of gnome-control-center (it was set to off).  After
  pressing the switch, the switch read "On", but the display of
  Bluetooth devices still appeared as it does when Bluetooth is off (it
  read "Bluetooth Turned Off\nTurn on to connect devices and receive
  file transfers.").

  I was able to remedy the situation by manually executing `sudo
  bluetoothd`.  I did this while the above On/Off switch was "Off" and
  the Bluetooth device list said Bluetooth was off.  After executing,
  the Bluetooth device list listed all my Bluetooth devices as expected.

  This is with bluetoothd 5.48.

  Bluetooth crash logs

  ```
  12:22:15 pulseaudio: (6856.168|   0.576) [pulseaudio] bluez5-util.c: 
Bluetooth daemon disappeared
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Failed with result 'core-dump'.
  12:22:15 systemd: bluetooth.service: Main process exited, code=dumped, 
status=11/SEGV
  12:22:15 kernel: bluetoothd[816]: segfault at 31 ip 562f7fa9bea2 sp 
7ffd0d54b720 error 4 in bluetoothd[562f7fa0+f3000]
  10:28:31 kernel: hid-generic 0005:046D:B019.0007: input,hidraw6: BLUETOOTH 
HID v0.06 Keyboard [MX Master 2S] on F4:D1:08:9E:7B:85
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  10:28:31 bluetoothd: bt_uhid_send: Invalid argument (22)
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center

[Desktop-packages] [Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken

2021-10-27 Thread Pepijn Bogaard

I committed the solution here:

https://git.launchpad.net/~pbgrd/ubuntu/+source/gnome-shell-extension-
ubuntu-
dock/commit/?h=ubuntu/devel=d64317c4faa07a7c42b478db2027561c7933aa13

How does this 'fix proposing' work exactly?

Thanks in advance.

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

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

Title:
  Click actions "previews" and "minimize-or-previews" are broken

Status in Dash to dock:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Committed

Bug description:
  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  
  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  
  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
Installed: 70~ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

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


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

[Desktop-packages] [Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken

2021-10-27 Thread Pepijn Bogaard

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Assignee: (unassigned) => Pepijn Bogaard (pbgrd)

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

Title:
  Click actions "previews" and "minimize-or-previews" are broken

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

Bug description:
  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  
  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  
  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
Installed: 70~ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

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


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

[Desktop-packages] [Bug 1948978] [NEW] Thunderbird write e-mail window never released in wayland

2021-10-27 Thread Chris Hall

Public bug reported:

If I run Thunderbird (latest version), when I write an e-mail or reply
to an e-mail, a new window opens. When I send the e-mail, it works
correctly and the e-mail is sent, but the red dot on the Thunderbird
icon on the task bar never goes out. If I close or pkill Thunderbird,
only the main Thunderbird window is released by the display manager and
it is not possible to open Thunderbird again without logging out or
restarting gdm3. This is with Wayland. There is no Thunderbird process
left to kill.

Everything works fine with Xorg, so on this computer running 21.10, I
will be using Xorg instead of Wayland for now.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 27 14:53:29 2021
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [1179:ff67]
   Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [1179:ff67]
InstallationDate: Installed on 2020-03-06 (600 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: TOSHIBA Satellite L305
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=baeb07e4-08ee-4d13-be78-7571c5723e1d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.20
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd12/09/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-04X02F:skuMontevina_Fab:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: Satellite L305
dmi.product.sku: Montevina_Fab
dmi.product.version: PSLB8U-04X02F
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug impish ubuntu wayland-session

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

Title:
  Thunderbird write e-mail window never released in wayland

Status in xorg package in Ubuntu:
  New

Bug description:
  If I run Thunderbird (latest version), when I write an e-mail or reply
  to an e-mail, a new window opens. When I send the e-mail, it works
  correctly and the e-mail is sent, but the red dot on the Thunderbird
  icon on the task bar never goes out. If I close or pkill Thunderbird,
  only the main Thunderbird window is released by the display manager
  and it is not possible to open Thunderbird again without logging out
  or restarting gdm3. This is with Wayland. There is no Thunderbird
  process left to kill.

  Everything works fine with Xorg, so on this computer running 21.10, I
  will be using Xorg instead of Wayland for now.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 27 14:53:29 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller

[Desktop-packages] [Bug 1945296] Re: To support goodix fp device [27C6:639C]

This bug was fixed in the package libfprint -
1:1.90.7+git20210222+tod1-0ubuntu4

---
libfprint (1:1.90.7+git20210222+tod1-0ubuntu4) jammy; urgency=medium

  * debian/patches: Add support for new elan, goodix and synaptics drivers.
Most of the drivers only need to list new product IDs to work with new
devices, and including other changes that new devices may require.
(LP: #1945296, #1945298)
  * debian/patches: Fix template struct in goodix drivers (LP: #1945296)

 -- Marco Trevisan (Treviño)   Tue, 26 Oct 2021
21:24:40 +0200

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

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

Title:
  To support goodix fp device [27C6:639C]

Status in OEM Priority Project:
  New
Status in libfprint package in Ubuntu:
  Fix Released
Status in libfprint source package in Focal:
  Incomplete
Status in libfprint source package in Impish:
  Incomplete

Bug description:
  
https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/libfprint/drivers/goodixmoc/goodix.c#L1505

  This ID is included in upstream.

  [Impact]

   * Devices have goodix [27c6:639c] fingerprint component will get 
 supported.

  [Test Plan]

   * Find a machine with this fingerprint device

   * Launch `settings` and enable `Fingerprint Login`

   * Enroll finger and then logout

   * Login system with enrolled finger

  [Where problems could occur]

   * A lot of fingerprint ids is supported in this version, we didn't test 
 all combination.

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


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

[Desktop-packages] [Bug 1945298] Re: To support goodix fp device [27C6:63BC]

This bug was fixed in the package libfprint -
1:1.90.7+git20210222+tod1-0ubuntu4

---
libfprint (1:1.90.7+git20210222+tod1-0ubuntu4) jammy; urgency=medium

  * debian/patches: Add support for new elan, goodix and synaptics drivers.
Most of the drivers only need to list new product IDs to work with new
devices, and including other changes that new devices may require.
(LP: #1945296, #1945298)
  * debian/patches: Fix template struct in goodix drivers (LP: #1945296)

 -- Marco Trevisan (Treviño)   Tue, 26 Oct 2021
21:24:40 +0200

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

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

Title:
  To support goodix fp device [27C6:63BC]

Status in OEM Priority Project:
  New
Status in libfprint package in Ubuntu:
  Fix Released
Status in libfprint source package in Focal:
  New
Status in libfprint source package in Impish:
  New

Bug description:
  
https://gitlab.freedesktop.org/libfprint/libfprint/-/blob/master/libfprint/drivers/goodixmoc/goodix.c#L1507

  This ID is included in upstream.

  [Impact]

   * Devices have goodix [27c6:63bc] fingerprint component will get
 supported.

  [Test Plan]

   * Find a machine with this fingerprint device

   * Launch `settings` and enable `Fingerprint Login`

   * Enroll finger and then logout

   * Login system with enrolled finger

  [Where problems could occur]

   * A lot of fingerprint ids is supported in this version, we didn't test
 all combination.

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


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

[Desktop-packages] [Bug 1948954] Re: snap packaged version of Firefox is inaccessible with Orca screen reader.

2021-10-27 Thread Olivier Tilloy

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

Title:
  snap packaged version of Firefox is inaccessible with Orca screen
  reader.

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I recently updated to Ubuntu mate 21.10, from 21.04.  I am unable to
  browse the web, using the snap version of firefox, provided by default
  in this release. With Orca running, launch firefox, and it will report
  inaccessible. I have another 21.10 machine where I have removed the
  snap version, and it works as expected using the .deb package.

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


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

[Desktop-packages] [Bug 1946599]

2021-10-27 Thread W-jan-k

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

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

Title:
  Firefox break when returning from console with wayland (nvidia) on
  ubuntu 21.10 beta

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

Bug description:
  (again snap firefox) Returning from console break all firefox tabs
  which have to be refreshed

  mv@i56400:~$ firefox
  [GFX1-]: glxtest: libEGL missing
  [GFX1-]: glxtest: EGL test failed
  xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb

  ###!!! [Parent][MessageChannel] Error:
  (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error:
  cannot send/recv

  
  ###!!! [Parent][MessageChannel] Error: 
(msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel 
error: cannot send/recv

  xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
  xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
  xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
  xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
  xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb
  xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb

  ###!!! [Parent][MessageChannel] Error:
  (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error:
  cannot send/recv

  
  ###!!! [Parent][MessageChannel] Error: 
(msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel 
error: cannot send/recv

  
  ###!!! [Parent][MessageChannel] Error: 
(msgtype=0x390144,name=PContent::Msg_AsyncMessage) Channel error: cannot 
send/recv

  
  ###!!! [Parent][MessageChannel] Error: 
(msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot 
send/recv

  
  ###!!! [Parent][MessageChannel] Error: 
(msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel 
error: cannot send/recv

  
  ###!!! [Parent][MessageChannel] Error: 
(msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot 
send/recv

  [Parent 6310, IPC I/O Parent] WARNING: FileDescriptorSet destroyed
  with unconsumed descriptors: file
  
/build/firefox/parts/firefox/build/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19


  After that, I logged under x11 (for test) but wasn't able to launch firefox:
   Error: cannot open display: :0

  I had to reboot and the problem occurs only with wayland.

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


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

[Desktop-packages] [Bug 1948954] Re: snap packaged version of Firefox is inaccessible with Orca screen reader.

** Tags added: snap

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

Title:
  snap packaged version of Firefox is inaccessible with Orca screen
  reader.

Status in firefox package in Ubuntu:
  New

Bug description:
  I recently updated to Ubuntu mate 21.10, from 21.04.  I am unable to
  browse the web, using the snap version of firefox, provided by default
  in this release. With Orca running, launch firefox, and it will report
  inaccessible. I have another 21.10 machine where I have removed the
  snap version, and it works as expected using the .deb package.

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


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

[Desktop-packages] [Bug 1916250] Please test proposed package

Hello Rolf, or anyone else affected,

Accepted libsignon-glib into impish-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/libsignon-
glib/2.1-3ubuntu0.21.10 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libsignon-glib (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-hirsute

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute and Focal2Jammy)

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in libsignon-glib source package in Hirsute:
  Fix Committed
Status in libsignon-glib source package in Impish:
  Fix Committed

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  [Test Case]
  This can be simply tested with a focal schroot:
  1) apt-get install vim libsignon-glib-dev
  2) edit /etc/apt/sources.list replacing focal with hirsute
  3) apt-get update
  4) apt-get install libsignon-glib-dev

  With the version of libsignon-glib-dev from -proposed you'll no longer
  receive the 'dpkg: error' from below.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

  [Regression Potential]
  We are adding a replaces with gir1.2-signon-1.0 so anything that depends on 
that package would be broken but given that that package is no longer available 
after focal that seems fine.

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


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

[Desktop-packages] [Bug 1916250] Please test proposed package

Hello Rolf, or anyone else affected,

Accepted libsignon-glib into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/libsignon-
glib/2.1-3ubuntu0.21.04 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute and Focal2Jammy)

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in libsignon-glib source package in Hirsute:
  Fix Committed
Status in libsignon-glib source package in Impish:
  Fix Committed

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  [Test Case]
  This can be simply tested with a focal schroot:
  1) apt-get install vim libsignon-glib-dev
  2) edit /etc/apt/sources.list replacing focal with hirsute
  3) apt-get update
  4) apt-get install libsignon-glib-dev

  With the version of libsignon-glib-dev from -proposed you'll no longer
  receive the 'dpkg: error' from below.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

  [Regression Potential]
  We are adding a replaces with gir1.2-signon-1.0 so anything that depends on 
that package would be broken but given that that package is no longer available 
after focal that seems fine.

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


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

[Desktop-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)

11:45  vorlon: could you take a look at bug 1916250 for me
please? I'm not sure it's right, but nor am I sure it's wrong.

14:29  rbasak: gir1.2-signon-2.0 exists in hirsute and later;
gir1.2-signon-1.0 exists in focal; we support upgrades from the LTS to
either the next LTS, or to the next supported non-LTS release.  So there
are upgrade paths to hirsute now, and to impish once hirsute EOLs, so
yes it's correct to SRU this fix

17:00  vorlon: I agree it needs SRUing. My question is if a sole
unversioned Replaces is correct.

17:00  rbasak: ah, that should be fine


** Changed in: libsignon-glib (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute and Focal2Jammy)

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in libsignon-glib source package in Hirsute:
  Fix Committed
Status in libsignon-glib source package in Impish:
  Fix Committed

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  [Test Case]
  This can be simply tested with a focal schroot:
  1) apt-get install vim libsignon-glib-dev
  2) edit /etc/apt/sources.list replacing focal with hirsute
  3) apt-get update
  4) apt-get install libsignon-glib-dev

  With the version of libsignon-glib-dev from -proposed you'll no longer
  receive the 'dpkg: error' from below.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

  [Regression Potential]
  We are adding a replaces with gir1.2-signon-1.0 so anything that depends on 
that package would be broken but given that that package is no longer available 
after focal that seems fine.

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


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

[Desktop-packages] [Bug 1948954] [NEW] snap packaged version of Firefox is inaccessible with Orca screen reader.

2021-10-27 Thread Guy Schlosser

Public bug reported:

I recently updated to Ubuntu mate 21.10, from 21.04.  I am unable to
browse the web, using the snap version of firefox, provided by default
in this release. With Orca running, launch firefox, and it will report
inaccessible. I have another 21.10 machine where I have removed the snap
version, and it works as expected using the .deb package.

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


** Tags: firefox orca

** Tags added: firefox orca

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

Title:
  snap packaged version of Firefox is inaccessible with Orca screen
  reader.

Status in firefox package in Ubuntu:
  New

Bug description:
  I recently updated to Ubuntu mate 21.10, from 21.04.  I am unable to
  browse the web, using the snap version of firefox, provided by default
  in this release. With Orca running, launch firefox, and it will report
  inaccessible. I have another 21.10 machine where I have removed the
  snap version, and it works as expected using the .deb package.

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


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

[Desktop-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)

2021-10-27 Thread Rolf Leggewie

** Tags added: focal2jammy

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute and Focal2Jammy)

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in libsignon-glib source package in Hirsute:
  In Progress
Status in libsignon-glib source package in Impish:
  In Progress

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  [Test Case]
  This can be simply tested with a focal schroot:
  1) apt-get install vim libsignon-glib-dev
  2) edit /etc/apt/sources.list replacing focal with hirsute
  3) apt-get update
  4) apt-get install libsignon-glib-dev

  With the version of libsignon-glib-dev from -proposed you'll no longer
  receive the 'dpkg: error' from below.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

  [Regression Potential]
  We are adding a replaces with gir1.2-signon-1.0 so anything that depends on 
that package would be broken but given that that package is no longer available 
after focal that seems fine.

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


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

[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-10-27 Thread Alex Deucher

The reverts are in the latest firmware tree:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d7b50e61669dc137924337d03d09b8986eb752a3
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d843e520a4b0d92b986645548d11ade3b9b239a4
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=99d72504bff7ab40c261b8509c0b9d8abf98b296

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

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Desktop-packages] [Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken

2021-10-27 Thread Paul White

Thanks Pepijn, that small deletion does seem to fix the issue.

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

Title:
  Click actions "previews" and "minimize-or-previews" are broken

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

Bug description:
  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  
  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  
  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
Installed: 70~ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

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


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

[Desktop-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)

2021-10-27 Thread Rolf Leggewie

https://packages.ubuntu.com/search?keywords=gir1.2-signon

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute and Focal2Jammy)

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in libsignon-glib source package in Hirsute:
  In Progress
Status in libsignon-glib source package in Impish:
  In Progress

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  [Test Case]
  This can be simply tested with a focal schroot:
  1) apt-get install vim libsignon-glib-dev
  2) edit /etc/apt/sources.list replacing focal with hirsute
  3) apt-get update
  4) apt-get install libsignon-glib-dev

  With the version of libsignon-glib-dev from -proposed you'll no longer
  receive the 'dpkg: error' from below.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

  [Regression Potential]
  We are adding a replaces with gir1.2-signon-1.0 so anything that depends on 
that package would be broken but given that that package is no longer available 
after focal that seems fine.

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


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

[Desktop-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)

2021-10-27 Thread Rolf Leggewie

Oh, Robie, come on now.  You already asked that question and an answer
was given in #3 and #4.  Too bad that was so long ago, but it's not my
fault.

"In this case, in essence the package name is already the versioning."
and "IOW, gir1.2-signon-1.0 isn't going to see any further upstream work
and Debian won't reintroduce it either. That line ends with Debian
stable."

You know guys, it's really frustrating to do all the work and then have
to do it over and over again and again.  Sometimes for years without
getting an inch closer to getting a fix uploaded.

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute and Focal2Jammy)

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in libsignon-glib source package in Hirsute:
  In Progress
Status in libsignon-glib source package in Impish:
  In Progress

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  [Test Case]
  This can be simply tested with a focal schroot:
  1) apt-get install vim libsignon-glib-dev
  2) edit /etc/apt/sources.list replacing focal with hirsute
  3) apt-get update
  4) apt-get install libsignon-glib-dev

  With the version of libsignon-glib-dev from -proposed you'll no longer
  receive the 'dpkg: error' from below.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

  [Regression Potential]
  We are adding a replaces with gir1.2-signon-1.0 so anything that depends on 
that package would be broken but given that that package is no longer available 
after focal that seems fine.

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


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

[Desktop-packages] [Bug 1947445] Re: Click actions "previews" and "minimize-or-previews" are broken

2021-10-27 Thread Pepijn Bogaard

Here is the solution ( and the cause of the bug ):

In /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js
at line 472:

change
const singleOrUrgentWindows = windows.length === 1 || !hasUrgentWindows;
to
const singleOrUrgentWindows = windows.length === 1 || hasUrgentWindows;

(basically removing the ! sign before hasUrgentWindows)

Then log-out & log-in again.

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

Title:
  Click actions "previews" and "minimize-or-previews" are broken

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

Bug description:
  Since upgrading to Ubuntu 21.10 the "previews" and "minimize-or-
  previews" options no longer work as expected.

  For "previews":
  No previews are shown when clicking on the app icon.

  For "minimize-or-previews":
  When multiple windows of the same application are open and I click on the app 
icon, no previews are shown anymore.

  
  Schema: org.gnome.shell.extensions.dash-to-dock
  Name: click-action
  Value: "minimize-or-previews"
  Value: "previews"

  
  Description:  Ubuntu 21.10
  Release:  21.10

  gnome-shell-extension-ubuntu-dock:
Installed: 70~ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 16 11:32:51 2021
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-21 (1090 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: Upgraded to impish on 2021-10-14 (1 days ago)

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


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

[Desktop-packages] [Bug 1938223] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-utils-460 460.91

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package
  nvidia-utils-460 460.91.03-0ubuntu0.20.04.1

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  There are some packages that are broken and can't be installed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 (not installed)
  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
  CasperMD5CheckResult: skip
  Date: Wed Jul 28 03:21:03 2021
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-utils-460 460.91.03-0ubuntu0.20.04.1
  InstallationDate: Installed on 2021-07-26 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-utils-460 460.91.03-0ubuntu0.20.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1938223/+subscriptions


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

[Desktop-packages] [Bug 1948939] Re: chromium browser deb to snap switch kills dist-upgrade

2021-10-27 Thread Paul White

** Package changed: ubuntu => chromium-browser (Ubuntu)

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

Title:
  chromium browser deb to snap switch kills dist-upgrade

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  During the 16LTS to 18LTS (GUI) distribution upgrade I received a
  warning that the process couldn't connect to the snap store.   I
  didn't have any snaps installed, so I continued with the distribution
  upgrade and everything worked OK.

  During the 18LTS to 20LTS (GUI) distribution upgrade I received and
  accepted the same warning.   As before I had no snaps installed.
  However, I did have Chromium browser installed, and as part of the
  distribution upgrade this tries to switch from being installed from
  deb to being installed from snap.   At this point the distribution
  upgrade came to a complete halt.   Also the desktop GUI became
  unresponsive, but it was possible to switch to a TTY console with
  (say) CTRL-ALT-F4, login, and execute commands.

  The first time this happened I managed to recover the situation
  somehow, and proceeded to a working 20LTS installation (albeit with a
  few quirks).   The second time it happened I was not, and ended up
  with a mish-mash of 18LTS and 20LTS that wouldn't boot to the desktop.
  Fortunately the second time I had made a disk image of the 18LTS
  system, and was able to go back to that.   I removed Chromium, and
  trying the distribution upgrade again I was not issued with the snap
  store warning, and the process completed uneventfully.

  BTW, I tried to report this problem using ubuntu-bug, but I hit this
  brick wall: https://bugs.launchpad.net/apport/+bug/1160316.   Hence
  the manual report.

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


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

[Desktop-packages] [Bug 1948939] [NEW] chromium browser deb to snap switch kills dist-upgrade

You have been subscribed to a public bug:

During the 16LTS to 18LTS (GUI) distribution upgrade I received a
warning that the process couldn't connect to the snap store.   I didn't
have any snaps installed, so I continued with the distribution upgrade
and everything worked OK.

During the 18LTS to 20LTS (GUI) distribution upgrade I received and
accepted the same warning.   As before I had no snaps installed.
However, I did have Chromium browser installed, and as part of the
distribution upgrade this tries to switch from being installed from deb
to being installed from snap.   At this point the distribution upgrade
came to a complete halt.   Also the desktop GUI became unresponsive, but
it was possible to switch to a TTY console with (say) CTRL-ALT-F4,
login, and execute commands.

The first time this happened I managed to recover the situation somehow,
and proceeded to a working 20LTS installation (albeit with a few
quirks).   The second time it happened I was not, and ended up with a
mish-mash of 18LTS and 20LTS that wouldn't boot to the desktop.
Fortunately the second time I had made a disk image of the 18LTS system,
and was able to go back to that.   I removed Chromium, and trying the
distribution upgrade again I was not issued with the snap store warning,
and the process completed uneventfully.

BTW, I tried to report this problem using ubuntu-bug, but I hit this
brick wall: https://bugs.launchpad.net/apport/+bug/1160316.   Hence the
manual report.

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

-- 
chromium browser deb to snap switch kills dist-upgrade
https://bugs.launchpad.net/bugs/1948939
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to chromium-browser 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 1849478] Re: [snap] (experimental) pipewire support not available

2021-10-27 Thread Olivier Tilloy

Progress: I managed to get screen capture to partially work by rebasing
my test snap on chromium 96.0.4664.18, which contains the following
commit:
https://source.chromium.org/chromium/_/webrtc/src.git/+/593b4d550d5569997c65dc1226238da04d4ea61a.

This works only partially because it allows sharing a selected window,
or a selected browser tab, but not the full screen (in that last case
the capture is entirely black except for the mouse cursor).

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

Title:
  [snap] (experimental) pipewire support not available

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's
  not possible to enable experimental support for pipewire, as the
  toggle doesn't show up in chrome://flags.

  It would be nice to have chromium compiled with pipewire support, to
  enable screensharing in Hangouts and similar apps.

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


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

[Desktop-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

2021-10-27 Thread Jerry Lee

By investigating the mentioned patches directly, the existing behavior
should not be changed:

* The patch for Quectel EM160 4G
There is only one patch, all changes are for the Quectel modems.

* Patches for Foxconn T99W175
There are 5 patches,
(patch#1): Modify the command line tool to get additional scan report for
WWAN subsystem
(patch#2): Move methods between 2 files
(patch#3): Add more 15 seconds wait for the firmware upgrading
(patch#4): Rename an existed carrier mapping configuration file for Foxconn
modem
(patch#5): Add a new carrier mapping configuration file for Foxconn modem

From the code review, it's clear that changes only affect Foxconn and Quectel
modems.

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

Title:
Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
In Progress
Status in modemmanager package in Ubuntu:
New

Bug description:
[Impact]

The modem certification requires that different modem firmware is used for
different network carrier.
This needs the firmware upgrading capability during the modem certification
process.

The modem manufacture vendors (Foxconn and Quectel) provided utilities to do
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
These utilities are verified to be working when the recent versions(> v
1.18.2) of ModemManager are used with.

To support manual firmware upgrading on the current Focal release which is
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
The requested upstream patches are listed as below:
* for Quectel EM160 4G
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
* for Foxconn T99W175
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

The firmware upgrading was verified using the patched ModemManager v 1.16.6
with the following 2 modems:
* Foxconn SDX55 T99W175 5G sub6 PCIE Modem
* Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

[Test Plan]

1. Install the Ubuntu image.
2. Boot and login the system.
3. Prepare the modem’s firmware and install the firmware upgrading
application provided by Foxconn and Quectel
4. Using the firmware upgrading application to upgrade the modem’s firmware
5. Verify if the modem’s firmware upgrading is successful
6. Reboot
7. Verify if the upgraded modem firmware is still working

[Where problems could occur]

The requested upstream patches are for these 2 specific modems.
This should not affect existing generic functions and other modems.

[Other Info]

The firmware and the upgrading utilities can be downloaded from the following
link:
* LP#1943774 for Quectel modems
* LP#1943780 for Foxconn modems

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

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

2021-10-27 Thread Stefano Maffulli

I just noticed that the same issue appears while using Inkscape: open
the export dialog, export the image and close the dialog. Then you will
still see two dots in the dock near the inkscape icon. And if you quit
Inkscape, on dot remains and ALT-TAB doesn't work anymore.

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

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Unknown
Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

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


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

[Desktop-packages] [Bug 1846188] Re: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only)

2021-10-27 Thread Chris Guiver

** Tags added: impish

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

Title:
  Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland
  sessions only)

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  
  In Nautilus, tooltips appear far to the left in the app menu.

  (Kazam and Peek were unable to record Nautilus)

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


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

[Desktop-packages] [Bug 1948933] [NEW] [SRU] libreoffice 7.1.7 for hirsute

2021-10-27 Thread Rico Tzschichholz

Public bug reported:

[Impact]

 * LibreOffice 7.1.7 is in its sixth bugfix release of the 7.1 line:
 https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release

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

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

[Testing]

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

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

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

 * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
* [amd64] ...
* [arm64] ...
* [armhf] ...
* [ppc64el] ...
* [s390x] ...

 * General smoke testing of all the applications in the office suite
were carried out by going through the manual testplan as documented by:
https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice

[Regression Potential]

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

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

** Affects: libreoffice (Ubuntu)
 Importance: High
 Assignee: Rico Tzschichholz (ricotz)
 Status: Triaged

** Affects: libreoffice (Ubuntu Hirsute)
 Importance: High
 Assignee: Rico Tzschichholz (ricotz)
 Status: Triaged

** Also affects: libreoffice (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: libreoffice (Ubuntu Hirsute)
   Status: New => Triaged

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

** Changed in: libreoffice (Ubuntu Hirsute)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

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

Title:
   [SRU] libreoffice 7.1.7 for hirsute

Status in libreoffice package in Ubuntu:
  Triaged
Status in libreoffice source package in Hirsute:
  Triaged

Bug description:
  [Impact]

   * LibreOffice 7.1.7 is in its sixth bugfix release of the 7.1 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release

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

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

  [Testing]

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

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

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

   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] ...
  * [arm64] ...
  * [armhf] ...
  * [ppc64el] ...
  * [s390x] ...

   * General smoke testing of all the applications in the office suite
  were

[Desktop-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

How do you intend to verify that (3) has worked correctly?

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

Title:
Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
In Progress
Status in modemmanager package in Ubuntu:
New

Bug description:
[Impact]

The modem certification requires that different modem firmware is used for
different network carrier.
This needs the firmware upgrading capability during the modem certification
process.

The firmware upgrading was verified using the patched ModemManager v 1.16.6
with the following 2 modems:
* Foxconn SDX55 T99W175 5G sub6 PCIE Modem
* Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

[Test Plan]

[Where problems could occur]

The requested upstream patches are for these 2 specific modems.
This should not affect existing generic functions and other modems.

[Other Info]

The firmware and the upgrading utilities can be downloaded from the following
link:
* LP#1943774 for Quectel modems
* LP#1943780 for Foxconn modems

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

[Desktop-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

> 3) Add a bunch of mappings from SIM->Carrier

> Assuming (3) is not expected to change existing behaviour this looks
like it would be acceptable under the hardware-enablement SRU policy.

Agreed, but I would expect SRU information against every change being
made, that would then receive separate SRU verification. This helps us
mitigate risk by 1) actually considering each change in the first place,
rather than it "slipping past" review; and 2) reducing the potential
number of SRUs, and therefore user time, bandwidth and regression risk,
by actually verifying that things are being changed as expected so we
don't have to do it twice.

I'm disappointed that this has now gone through two SRU review rounds,
and it is Chris who has extracted the actual nature of the changes that
you are looking to land here. This detail should have been laid out in
the bug (or multiple bugs) and in the SRU information in the first
place.

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

Title:
Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
In Progress
Status in modemmanager package in Ubuntu:
New

Bug description:
[Impact]

The modem certification requires that different modem firmware is used for
different network carrier.
This needs the firmware upgrading capability during the modem certification
process.

The firmware upgrading was verified using the patched ModemManager v 1.16.6
with the following 2 modems:
* Foxconn SDX55 T99W175 5G sub6 PCIE Modem
* Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

[Test Plan]

[Where problems could occur]

The requested upstream patches are for these 2 specific modems.
This should not affect existing generic functions and other modems.

[Other Info]

The firmware and the upgrading utilities can be downloaded from the following
link:
* LP#1943774 for Quectel modems
* LP#1943780 for Foxconn modems

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

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

I've reported the lack of symbols to Debian on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997932 with a patch
now

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

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

[Desktop-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)

I'm surprised to see Replaces without a Breaks, and further for the
Replaces to be unversioned. This doesn't match one of the cases listed
at https://wiki.debian.org/PackageTransition, and
https://www.debian.org/doc/debian-policy/ch-relationships.html#id11
explains why usually a Breaks is also required.

Since I'm not sure this is correct, I'm reluctant to accept it on
review. I'm not sure it's necessarily wrong, either. I'll ping Steve for
an opinion.

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute and Focal2Jammy)

Status in libsignon-glib package in Ubuntu:
  Fix Released
Status in libsignon-glib source package in Hirsute:
  In Progress
Status in libsignon-glib source package in Impish:
  In Progress

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  [Test Case]
  This can be simply tested with a focal schroot:
  1) apt-get install vim libsignon-glib-dev
  2) edit /etc/apt/sources.list replacing focal with hirsute
  3) apt-get update
  4) apt-get install libsignon-glib-dev

  With the version of libsignon-glib-dev from -proposed you'll no longer
  receive the 'dpkg: error' from below.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

  [Regression Potential]
  We are adding a replaces with gir1.2-signon-1.0 so anything that depends on 
that package would be broken but given that that package is no longer available 
after focal that seems fine.

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


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

[Desktop-packages] [Bug 1947677] Re: Colemak keyboard layout's left-hand backspace is also acting as Caps Lock

2021-10-27 Thread Tialae

I have since found that executing in Terminal, the command
  횡횖횘획횖횊횙 -횎 "회횕횎횊횛 홻횘회횔"  
is a temporary workaround to fix this behaviour; however, I would definitely 
think this issue should be fixed so it works out-of-the-box for new users.
It's a very problematic behaviour for one's primary backspace to be also 
toggling caps lock, affecting daily typing.

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

Title:
  Colemak keyboard layout's left-hand backspace is also acting as Caps
  Lock

Status in xorg package in Ubuntu:
  New

Bug description:
  I have installed Ubuntu with the default English (US) Qwerty keyboard
  layout and I added the English (Australia) Colemak keyboard layout
  through the Settings app (as per the screenshot attached). This is for
  the in-built laptop keyboard on the Lenovo ThinkPad X1 Yoga Touch.

  The bug is that the CapsLock key, which is meant to be remapped to a
  Backspace key on the Colemak keyboard layout, acts as both the
  CapsLock AND the Backspace, when the Colemak keyboard layout is
  active. This means that backspacing a single time deletes a single
  character AND also toggles Caps Lock.

  The expected behaviour is that the key acts only as Backspace when the
  Colemak keyboard layout is active.

  The output of  횡횙횛횘횙 -횛횘횘횝 | 횐횛횎횙 횇홺홱  is

   _횇홺홱_횁횄홻홴횂_홽홰홼홴횂(횂횃횁홸홽홶) = "횎횟획횎횟", "횙회ퟷퟶퟻ", "횞횜,횞횜,횞횜", ",회횘횕횎횖횊횔,",
  ""

  I hope a fix can be found soon :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 19 17:34:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224e]
  InstallationDate: Installed on 2021-10-09 (9 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 20JDA00CAU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-38-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2021
  dmi.bios.release: 1.41
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1NET54W (1.41 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20JDA00CAU
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.19
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1NET54W(1.41):bd08/17/2021:br1.41:efr1.19:svnLENOVO:pn20JDA00CAU:pvrThinkPadX1Yoga2nd:skuLENOVO_MT_20JD_BU_Think_FM_ThinkPad:rvnLENOVO:rn20JDA00CAU:rvrSDK0K17763WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad
  dmi.product.name: 20JDA00CAU
  dmi.product.sku: LENOVO_MT_20JD_BU_Think_FM_ThinkPad
  dmi.product.version: ThinkPad X1 Yoga 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1948778] Re: Random flashes in gnome-shell

2021-10-27 Thread lotuspsychje

@Daniel i tested both fixes for several hours individualy
but the flashes seem to keep happening

is there some sort of wayland realtime debug command i could try
to see if i can trace on the time its happening, as in journal logs nothing 
shows?

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

Title:
  Random flashes in gnome-shell

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04 development branch up to date to latest @ 26/10/2021
  kernel 5.13.0-19-generic

  While working around on the desktop i'm getting short screen flashes like a 
screenshot style
  i cant reproduce them, they seem to come on random like every few minutes
  journal logs dont record anything while they occur

  this only happens on wayland, tested a long session on xorg where they
  dont occur

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 26 11:12:30 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

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


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

[Desktop-packages] [Bug 1891338] Re: apparmor misconfigured for evince

** Changed in: evince (Ubuntu)
   Importance: Undecided => Low

** Changed in: evince (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  apparmor misconfigured for evince

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Committed

Bug description:
  On a fully up to date xubuntu 20-04 system, when i run evince and
  click on a link, it fails to follow that link in my browser. This kind
  of thing happens when you are reading a technical paper and want to
  follow one of the references and click on the doi or url.

  When i click on the link i get a box that i cannot copy from that says:
  Failed to launch preferred application for category "WebBrowser".

  Failed to execute child process "/usr/lib/x86_64-linux-
  gnu/xfce4/exo-2/exo-helper-2"(Permission denied).

  Did I say that it is annoying that i could not copy the text in this
  box!!

  The output of the ldd command you asked for is attached.

  I should also point out that this worked fine under xubuntu 18.04.

  I had originally posted this as an additional comment on
  https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159?comments=all
  but https://launchpad.net/~seb128 said that I should submit this as a
  separate bug because this is likely an apparmor configuration problem
  that is similar to the ancient bug
  https://bugs.launchpad.net/bugs/987578.

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


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

[Desktop-packages] [Bug 1948566] Re: Sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable (main)

2021-10-27 Thread Simon Quigley

This bug was fixed in the package java-atk-wrapper - 0.38.0-5
Sponsored for Hans Joachim Desserud (hjd)

---
java-atk-wrapper (0.38.0-5) unstable; urgency=medium

  [ Debian Janitor ]
  * Bump debhelper from old 12 to 13.
  * Update standards version to 4.5.1, no changes needed.
  * Remove constraints unnecessary since buster:
+ Build-Depends: Drop versioned constraint on java-common.

  [ Samuel Thibault ]
  * libatk-wrapper-java.lintian-overrides: Drop lintian warning for jar name.

 -- Samuel Thibault   Sat, 18 Sep 2021 18:34:13
+0200

java-atk-wrapper (0.38.0-4) unstable; urgency=medium

  * patches/dbus: Also detect at-spi through dbus.

 -- Samuel Thibault   Thu, 26 Aug 2021 02:50:17
+0200

java-atk-wrapper (0.38.0-3) unstable; urgency=medium

  * patches/werror: Only enable -Werror in upstream development
(Closes: Bug#984069).
  * control: Set Rules-Requires-Root to no.
  * rules: Drop ddeb-migration rules, now useless

 -- Samuel Thibault   Sun, 15 Aug 2021 22:56:34
+0200

** Changed in: java-atk-wrapper (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable (main)

Status in java-atk-wrapper package in Ubuntu:
  Fix Released

Bug description:
  Please sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable
  (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* No-change rebuild to build packages with zstd compression.
* No-change rebuild to build packages with zstd compression.
* Import an unreleased debian patch to better address the s390x FTBFS
  - debian/patches/werror
* Import an unreleased debian patch to better address the s390x FTBFS
  - debian/patches/werror

  Werror patch has been included in Debian package.

  Changelog entries since current jammy version 0.38.0-2ubuntu3:

  java-atk-wrapper (0.38.0-5) unstable; urgency=medium

[ Debian Janitor ]
* Bump debhelper from old 12 to 13.
* Update standards version to 4.5.1, no changes needed.
* Remove constraints unnecessary since buster:
  + Build-Depends: Drop versioned constraint on java-common.

[ Samuel Thibault ]
* libatk-wrapper-java.lintian-overrides: Drop lintian warning for jar name.

   -- Samuel Thibault   Sat, 18 Sep 2021 18:34:13
  +0200

  java-atk-wrapper (0.38.0-4) unstable; urgency=medium

* patches/dbus: Also detect at-spi through dbus.

   -- Samuel Thibault   Thu, 26 Aug 2021 02:50:17
  +0200

  java-atk-wrapper (0.38.0-3) unstable; urgency=medium

* patches/werror: Only enable -Werror in upstream development
  (Closes: Bug#984069).
* control: Set Rules-Requires-Root to no.
* rules: Drop ddeb-migration rules, now useless

   -- Samuel Thibault   Sun, 15 Aug 2021 22:56:34
  +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1948566/+subscriptions


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

[Desktop-packages] [Bug 1945368]

2021-10-27 Thread Rimersburgboro

I am afraid that if I enter manually all of my tasks, I will have issues going 
forward if I use the original installation of TB that has been gradually 
updated.
*How can I get my email folders and address book into the clean install of TB 
91.2.0, please? My home/ main calendar and tasks are showing in this one and, 
most importantly, it has never had any addons installed within it.

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

Title:
  Thunderbird 91 forgets default calendar

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Upon upgrading from Thunderbird 78 to 91, the default calendar for new
  events that I selected has been forgotten. I has Google set as the
  default, but Thunderbird 91 has changed the default to a local
  calendar that I rarely use.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.1.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2076 F pulseaudio
  BuildID: 20210916142849
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Sep 28 22:11:42 2021
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-07-14 (441 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   169.254.0.0/16 dev wg0 scope link metric 1000 
   172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric 
600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-09-24 (4 days ago)
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET29W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1945100]

2021-10-27 Thread Ryanvm

https://hg.mozilla.org/releases/mozilla-esr91/rev/f6e36e1fb791

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

Title:
  Widevine violates the sandbox and crashes

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

Bug description:
  I just updated for Impish Indri beta release but Firefox's  Widevine
  is always crashing. When I disable the GMP sandbox (setting the
  environment variable  MOZ_DISABLE_GMP_SANDBOX to 1) it works fine. I'm
  using Firefox 92.0.1 installed via .deb package.

  Here is some console logs showing the violations:

  ➜ firefox --ProfileManager
  Gtk-Message: 09:58:02.539: Failed to load module "appmenu-gtk-module"

  ###!!! [Child][RunMessage] Error: Channel closing: too late to
  send/recv, messages will be lost

  Gtk-Message: 09:58:10.435: Failed to load module "appmenu-gtk-module"
  Sandbox: attempt to open unexpected file /usr/lib/firefox/librt.so.1
  Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/librt.so.1
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v2/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/tls/haswell/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/tls/haswell/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/tls/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/tls/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/haswell/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/haswell/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v2/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/tls/haswell/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/tls/haswell/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/tls/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/tls/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120

[Desktop-packages] [Bug 1945368]

2021-10-27 Thread Conft

This issue is closed for me. I uninstalled 91.2.0, deleted the
Roaming>Thunderbird directory, and re-installed 91.2.0. I was then able
to import my 78.14.0 Home.ics file into the default Home calendar. Then
I just had to re-add my few tasks. And also import my address book .csv
files. And copy in all my years of saved Local Folders.

Rather a pain to re-create my email accounts and set all the preferences
like I wanted them, but now I have all that documented. Thanks to
Richard for the hint on deleting the VTODO entries. That .ics file did
not import; it just completed this time with no entries in the Home
calendar. My lesson learned was to back up my calendar and address books
before an update (or a new install), empty my inbox to a Local Folder,
and to stop overwriting the preference files, etc. Back on the normal
update path now, and happy to be using Thunderbird.

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

Title:
  Thunderbird 91 forgets default calendar

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Upon upgrading from Thunderbird 78 to 91, the default calendar for new
  events that I selected has been forgotten. I has Google set as the
  default, but Thunderbird 91 has changed the default to a local
  calendar that I rarely use.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.1.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2076 F pulseaudio
  BuildID: 20210916142849
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Sep 28 22:11:42 2021
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-07-14 (441 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   169.254.0.0/16 dev wg0 scope link metric 1000 
   172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric 
600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-09-24 (4 days ago)
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET29W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1945368]

2021-10-27 Thread Anjeyelf

(In reply to rimersburgb...@comcast.net from comment #96)
> *How can I get my email folders and address book into the clean install of TB 
> 91.2.0, please? My home/ main calendar and tasks are showing in this one and, 
> most importantly, it has never had any addons installed within it.

This forum is specifically for reporting bugs and providing information 
regarding that bug. It is not a Support Forum.
Please create a question regarding this request for Support in the Thunderbird 
Support forum and then post a link to it in this forum.
https://support.mozilla.org/en-US/questions/new/thunderbird/form

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

Title:
  Thunderbird 91 forgets default calendar

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Upon upgrading from Thunderbird 78 to 91, the default calendar for new
  events that I selected has been forgotten. I has Google set as the
  default, but Thunderbird 91 has changed the default to a local
  calendar that I rarely use.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.1.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2076 F pulseaudio
  BuildID: 20210916142849
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Sep 28 22:11:42 2021
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-07-14 (441 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   169.254.0.0/16 dev wg0 scope link metric 1000 
   172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric 
600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-09-24 (4 days ago)
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET29W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1945100]

2021-10-27 Thread Ryanvm

Comment on attachment 9237836
Bug 1725828 - Preload dependencies for the Widevine CDM when sandboxing it on 
Linux.

Approved for 91.3esr.

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

Title:
  Widevine violates the sandbox and crashes

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

Bug description:
  I just updated for Impish Indri beta release but Firefox's  Widevine
  is always crashing. When I disable the GMP sandbox (setting the
  environment variable  MOZ_DISABLE_GMP_SANDBOX to 1) it works fine. I'm
  using Firefox 92.0.1 installed via .deb package.

  Here is some console logs showing the violations:

  ➜ firefox --ProfileManager
  Gtk-Message: 09:58:02.539: Failed to load module "appmenu-gtk-module"

  ###!!! [Child][RunMessage] Error: Channel closing: too late to
  send/recv, messages will be lost

  Gtk-Message: 09:58:10.435: Failed to load module "appmenu-gtk-module"
  Sandbox: attempt to open unexpected file /usr/lib/firefox/librt.so.1
  Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/librt.so.1
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v2/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/tls/haswell/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/tls/haswell/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/tls/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/tls/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/haswell/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/haswell/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/lib/x86_64-linux-gnu/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file /lib/x86_64-linux-gnu/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v3/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/glibc-hwcaps/x86-64-v2/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/tls/haswell/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/tls/haswell/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/tls/x86_64/librt.so.1
  Sandbox: seccomp sandbox violation: pid 24799, tid 24799, syscall 262, args 
4294967196 140721817045120 140721817045312 0 4294967295 140721817045120.
  Sandbox: attempt to open unexpected file 
/usr/lib/x86_64-linux-gnu/tls/librt.so.1
  Sandbox: seccomp sandbox violation: pid

[Desktop-packages] [Bug 1945368]

2021-10-27 Thread Conft

I got my calendar entries to re-appear after upgrading from 78.14.0
(64-bit) to 91.2.0 (64-bit). Win 10 21H1. On 78.14, I deleted the few
tasks I had as per the above remark, and exported the calendar to
Home.ics. After the 91.2 upgrade, my Home calendar was empty. I then
added a new local calendar Junk1, and then successfully imported the
Home.ics file to Junk1. I have only ever used one local calendar (Home)
for years now. And yes, I am one of those errant profile file replace
folks as I replicate my email from machine to machine (and from Linux to
Windows a while back).

I am also now able to add calendar entries to Junk1, and they do not
disappear on a Thunderbird exit / reload (as they did before when my
Home local calendar had no entries after the 91 upgrade). And add new
tasks. Events and tasks added to the Home calendar (when Junk1 is
hidden) still disappear on a reload.

If I try to import the same Home.ics file to the empty local Home
calendar, the import dialog shows no progress what so ever (stalls)
after selecting 'Import All'; and selecting an 'Import Event' also
stalls. By stalling, I mean the 'Import All' button becomes washed out,
and the progress bar shows no activity. Importing into the Junk1
calendar happened in like 3 seconds. So I don't think it's a performance
thing. Also based on watching the memory and CPU activity of Thunderbird
in the Task Manager over like 20 min, just in case.

So how do I move all the Junk1 calendar entries back to my local Home
calendar please?

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

Title:
  Thunderbird 91 forgets default calendar

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Upon upgrading from Thunderbird 78 to 91, the default calendar for new
  events that I selected has been forgotten. I has Google set as the
  default, but Thunderbird 91 has changed the default to a local
  calendar that I rarely use.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: thunderbird 1:91.1.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   2076 F pulseaudio
  BuildID: 20210916142849
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Sep 28 22:11:42 2021
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-07-14 (441 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  IpRoute:
   default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600 
   10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2 
   169.254.0.0/16 dev wg0 scope link metric 1000 
   172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric 
600
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:359
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to impish on 2021-09-24 (4 days ago)
  dmi.bios.date: 06/21/2021
  dmi.bios.release: 1.19
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET29W (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20U9CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 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.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon Gen 8
  dmi.product.name: 20U9CTO1WW
  dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
  dmi.product.version: ThinkPad X1 Carbon Gen 8
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 1948539] Re: System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB. Current OS - Ubuntu 20.10

2021-10-27 Thread Paul White

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

** Tags removed: bug in monitor system
** Tags added: impish

** Summary changed:

- System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB.  
Current OS - Ubuntu 20.10
+ System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB.

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

Title:
  System Monitor is showing wrong Memory info. Actual is 8 GB showing
  8.2GB.

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  System Monitor is showing wrong Memory info. Actual is 8(7.6) GB showing 8.2 
GB.
  Current OS version - Ubuntu 21.10.

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


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

[Desktop-packages] [Bug 1948539] [NEW] System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB. Current OS - Ubuntu 20.10

You have been subscribed to a public bug:

System Monitor is showing wrong Memory info. Actual is 8(7.6) GB showing 8.2 GB.
Current OS version - Ubuntu 21.10.

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


** Tags: bug in monitor system
-- 
System Monitor is showing wrong Memory info. Actual is 8 GB showing 8.2GB.  
Current OS - Ubuntu 20.10
https://bugs.launchpad.net/bugs/1948539
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-system-monitor 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 1948829] Re: AppIndicator icon looks squashed in Ubuntu focal

2021-10-27 Thread Penny Chiu

Add my example in below, and attach svg file for this example. I used python3 
to run this example.
--

import os
import gi

gi.require_version("Gtk", "3.0")
gi.require_version('AppIndicator3', '0.1')

from gi.repository import Gtk as gtk
from gi.repository import AppIndicator3 as appindicator

APPINDICATOR_ID = 'myappindicator'
ICON_PATH = os.path.abspath('/home/x/linux-laptop.svg')

def main():
indicator = appindicator.Indicator.new(APPINDICATOR_ID, ICON_PATH, 
appindicator.IndicatorCategory.SYSTEM_SERVICES)
indicator.set_status(appindicator.IndicatorStatus.ACTIVE)
indicator.set_menu(gtk.Menu())
indicator.set_label('TEST APP', '')
gtk.main()

if __name__ == "__main__":
main()


** Attachment added: "linux-laptop.svg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1948829/+attachment/5536433/+files/linux-laptop.svg

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

Title:
  AppIndicator icon looks squashed in Ubuntu focal

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

Bug description:
  Release of Ubuntu: Ubuntu 20.04 (focal)
  Version of gnome-shell: 3.36.9-0ubuntu0.20.04.2
  Version of gnome-shell-extension-appindicator: 33.1-0ubuntu0.20.04.2

  I implemented a simple AppIndicator app using python which contains an
  icon and a label. The icon image is SVG file and image size is 300 x
  200 in px. When running the AppIndicator app, the icon should be
  scaled based on AppIndicator bar height and keeps aspect ratio, but
  only image height is scaled and image width still keeps 300px so the
  icon looks squashed on AppIndicator bar.

  This issue was only happened if the icon image weight and height are
  different (eg. 300 x 200). I tried the icon image weight and height
  are the same (300 x 300), the issue was not reproduced.

  The same AppIndicator app works fine in Ubuntu 18.04 (bionic, gnome-
  shell version: 3.28.4-0ubuntu18.04.7), and both weight and height are
  scaled and keeps aspect ratio even if the icon image weight and height
  are different. So this issue is only happened in gnome-shell 3.36.

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


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

[Desktop-packages] [Bug 1875671] Re: wayland: desktop folder missing in sidebar

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

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

Title:
  wayland: desktop folder missing in sidebar

Status in GNOME Shell:
  Unknown
Status in GTK+:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Using Wayland session nautilus home window does not show Desktop folder in 
sidebar while is dispayed using X11 session.
  see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  Uname: Linux 5.7.0-050700rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:24:45 2020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 
852)'
  InstallationDate: Installed on 2020-04-23 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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

[Desktop-packages] [Bug 1846188] Re: Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland sessions only)

** Tags added: desktop-lts-wishlist

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

Title:
  Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland
  sessions only)

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  
  In Nautilus, tooltips appear far to the left in the app menu.

  (Kazam and Peek were unable to record Nautilus)

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


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

[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-10-27 Thread Juerg Haefliger

Hi. I'm picking up this ticket from Seth. Reading through the history it
seems it's still an open issue? My understanding is that upstream
'fixed' this by reverting fw blobs in version 20210818. I can produce a
linux-firmware test package for hirsute 20.04 with these reverts if
necessary. Just let me know.


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

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

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Desktop-packages] [Bug 1948874] Re: Some Nautilus tooltips open somewhere else than near the hovered button

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

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

** This bug has been marked a duplicate of bug 1846188
   Tooltips in Nautilus 3.34's burger menu are out of place (in Wayland 
sessions only)

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

Title:
  Some Nautilus tooltips open somewhere else than near the hovered
  button

Status in nautilus package in Ubuntu:
  New

Bug description:
  I can only include a single image
  This also happens with the other five buttons in the same submenu, and the 
other three buttons in the submenu right next to the one opened in the image

  This does not occur when running Ubuntu CD images

  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nautilus 1:40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 26 22:10:40 2021
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2021-10-10 (16 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince40.4-2
   file-roller   3.40.0-2
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu2
   nautilus-share0.7.3-2ubuntu4

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


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

[Desktop-packages] [Bug 1948647] Re: Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange circle persists

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Medium => Low

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

Title:
  Screeen recording via Ctrl+Alt+Shift+R creates empty webm file, orange
  circle persists

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Running 21.10 and Gnome 40.4 the screen recording no longer works with
  the Ctrl+Alt+Shift+R keystroke. A .webm file does appear in the Videos
  folder but it is empty. The orange circle does appear in the upper
  corner, but it will not go away.

  Further Ctrl+Alt+Shift+R strokes do not make a new .webm file or
  remove the orange circle.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.15.0-rc4-soffixes x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 25 11:11:13 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-12 (12 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-14 (10 days ago)

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


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

[Desktop-packages] [Bug 1948829] Re: AppIndicator icon looks squashed in Ubuntu focal

thank you for your bug report, could you perhaps add your example to the
report to make easier for others to try?

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Importance: Undecided => Low

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

Title:
  AppIndicator icon looks squashed in Ubuntu focal

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

Bug description:
  Release of Ubuntu: Ubuntu 20.04 (focal)
  Version of gnome-shell: 3.36.9-0ubuntu0.20.04.2
  Version of gnome-shell-extension-appindicator: 33.1-0ubuntu0.20.04.2

  I implemented a simple AppIndicator app using python which contains an
  icon and a label. The icon image is SVG file and image size is 300 x
  200 in px. When running the AppIndicator app, the icon should be
  scaled based on AppIndicator bar height and keeps aspect ratio, but
  only image height is scaled and image width still keeps 300px so the
  icon looks squashed on AppIndicator bar.

  This issue was only happened if the icon image weight and height are
  different (eg. 300 x 200). I tried the icon image weight and height
  are the same (300 x 300), the issue was not reproduced.

  The same AppIndicator app works fine in Ubuntu 18.04 (bionic, gnome-
  shell version: 3.28.4-0ubuntu18.04.7), and both weight and height are
  scaled and keeps aspect ratio even if the icon image weight and height
  are different. So this issue is only happened in gnome-shell 3.36.

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


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

[Desktop-packages] [Bug 1875671] Re: wayland: desktop folder missing in sidebar

2021-10-27 Thread Santiago Fernández Núñez

This also affects the recently launched Ubuntu 21.10.

Reported a bug to GNOME Shell: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4730

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4730
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4730

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

Title:
  wayland: desktop folder missing in sidebar

Status in GTK+:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Using Wayland session nautilus home window does not show Desktop folder in 
sidebar while is dispayed using X11 session.
  see attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  Uname: Linux 5.7.0-050700rc3-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 17:24:45 2020
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 
852)'
  InstallationDate: Installed on 2020-04-23 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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

[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.

Expect it to still fail in 40.5-1ubuntu2 as the expected fix (mutter!77)
is only in version 41.0.

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

Title:
  Xwayland crash in gdm as screen off and touchscreen detach.

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in X.Org X server:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter package in Fedora:
  Unknown

Bug description:
  This is a reproducible issue. Step to reproduce
  1. cold boot into gdm login screen.
  2. wait for 5 mins, and the screen will be turned off.

  Expected result:
  The screen just turns black.

  Actual result:
  Saw Vendor boot logo on the monitor (previous draw by plymouth during booting)

  Analysis as it happens:
  1. Saw "LGDisplay Incell Touch" drop off the USB bus.
 Kernel message like: "usb 1-9: USB disconnect, device number 6"
 as the screen turned black.
  2. There is no switch on virtual tty.
  3. journal log from Xwayland "wl_display@1: error 0: invalid object 24"
  4. Xwayland and gnome-shell process both die as this happens.
  5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and
 gnome-shell stop there for 30 more seconds.
  6. backtrace as Xwayland crashed:

  ```
  #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351
  #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872
  #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at 
../../../../os/log.c:1010
  #5 0x56437429c8b0 in xwl_log_handler (format=, 
args=) at ../../../../../hw/xwayland/xwayland.c:1312
  #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error 
%d: %s\n") at ../src/wayland-util.c:404
  #7 0x7f447c3cb78b in display_handle_error (data=, 
display=0x56437639f000, object=0x56437639f000, code=0, message=)
  at ../src/wayland-client.c:911
  #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #10 0x7f447c3cf3a8 in wl_closure_invoke 
(closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=,
  target@entry=0x56437639f000, opcode=opcode@entry=0, data=) 
at ../src/connection.c:1018
  #11 0x7f447c3cbc48 in dispatch_event 
(display=display@entry=0x56437639f000, queue=) at 
../src/wayland-client.c:1445
  #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, 
display=0x56437639f000) at ../src/wayland-client.c:1584
  #13 wl_display_dispatch_queue_pending (display=0x56437639f000, 
queue=0x56437639f0d0) at ../src/wayland-client.c:1833
  #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896
  #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at 
../../../../../hw/xwayland/xwayland.c:957
  #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, 
timeout=) at ../../../../os/ospoll.c:657
  #17 0x5643743faa23 in WaitForSomething (are_ready=0) at 
../../../../os/WaitFor.c:208
  #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220
  #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, 
envp=) at ../../../../dix/main.c:276
  #20 0x7f447b8c90b3 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
  #21 0x56437429c60e in _start ()```

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


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

[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.

2021-10-27 Thread Yuan-Chen Cheng

Currently we are doing a little bit more test to make sure we this patch
does work.

For now, the versions of mutter:
 jammy: 40.5-1ubuntu2
 impish: 40.5-1ubuntu2
Debian:
 sid: 41.0-5

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

Title:
  Xwayland crash in gdm as screen off and touchscreen detach.

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in X.Org X server:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter package in Fedora:
  Unknown

Bug description:
  This is a reproducible issue. Step to reproduce
  1. cold boot into gdm login screen.
  2. wait for 5 mins, and the screen will be turned off.

  Expected result:
  The screen just turns black.

  Actual result:
  Saw Vendor boot logo on the monitor (previous draw by plymouth during booting)

  Analysis as it happens:
  1. Saw "LGDisplay Incell Touch" drop off the USB bus.
 Kernel message like: "usb 1-9: USB disconnect, device number 6"
 as the screen turned black.
  2. There is no switch on virtual tty.
  3. journal log from Xwayland "wl_display@1: error 0: invalid object 24"
  4. Xwayland and gnome-shell process both die as this happens.
  5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and
 gnome-shell stop there for 30 more seconds.
  6. backtrace as Xwayland crashed:

  ```
  #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351
  #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872
  #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at 
../../../../os/log.c:1010
  #5 0x56437429c8b0 in xwl_log_handler (format=, 
args=) at ../../../../../hw/xwayland/xwayland.c:1312
  #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error 
%d: %s\n") at ../src/wayland-util.c:404
  #7 0x7f447c3cb78b in display_handle_error (data=, 
display=0x56437639f000, object=0x56437639f000, code=0, message=)
  at ../src/wayland-client.c:911
  #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #10 0x7f447c3cf3a8 in wl_closure_invoke 
(closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=,
  target@entry=0x56437639f000, opcode=opcode@entry=0, data=) 
at ../src/connection.c:1018
  #11 0x7f447c3cbc48 in dispatch_event 
(display=display@entry=0x56437639f000, queue=) at 
../src/wayland-client.c:1445
  #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, 
display=0x56437639f000) at ../src/wayland-client.c:1584
  #13 wl_display_dispatch_queue_pending (display=0x56437639f000, 
queue=0x56437639f0d0) at ../src/wayland-client.c:1833
  #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896
  #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at 
../../../../../hw/xwayland/xwayland.c:957
  #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, 
timeout=) at ../../../../os/ospoll.c:657
  #17 0x5643743faa23 in WaitForSomething (are_ready=0) at 
../../../../os/WaitFor.c:208
  #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220
  #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, 
envp=) at ../../../../dix/main.c:276
  #20 0x7f447b8c90b3 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
  #21 0x56437429c60e in _start ()```

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


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

[Desktop-packages] [Bug 1948893] Re: Application grid fails to appear or disappear

Sounds like a bug in dash-to-panel only. There might be some hints as to
what needs fixing in bug 1922353 or bug 1918874.

** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-dash-
to-panel (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/1948893

Title:
  Application grid fails to appear or disappear

Status in gnome-shell-extension-dash-to-panel package in Ubuntu:
  New

Bug description:
  3.38.4

  What you expected to happen:
  gnome-shell application grid to behave normally

  What actually happened:
  Upon clicking the show applications button once and reopening overview, 
applications do not show up. When clicking the button twice to open/close the 
application view, the grid will briefly flash on second click, and after 
closing and reopening overview the grid will persist in the main overview 
behind open windows.

  This bug seems to be triggered by extensions such as dash-to-panel
  when configuring settings to use the default gnome-dash/applications
  button and disabling the button on the panel. Because this bug is very
  similar to https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1922353 which was also triggered by the same extension for
  many users, it seems appropriate to report here.

  I've recreated this bug on ubuntu 21.04 with vanilla gnome as well as
  pop_os 21.04 and ubuntu 21.04 with default extensions disabled.

  Error log:
  value "nan" of type 'gfloat' is invalid or out of range for property 
'translation-x' of type 'gfloat'
  value "nan" of type 'gfloat' is invalid or out of range for property 
'translation-y' of type 'gfloat'
  value "-nan" of type 'gdouble' is invalid or out of range for property 
'value' of type 'gdouble'

  Steps to recreate:
  1) Disable any built-in extensions that modify gnome-shell
  2) Install and enable dash-to-panel, toggle 'show applications button' off 
and 'activities button' on and enable 'keep original gnome-shell dash'
  3) Restart shell and click show applications button on the dash

  screenshot of log:
  
https://user-images.githubusercontent.com/89889704/134977896-7a4a2457-e4c4-4d30-9eb7-8eac60e4d524.png

  video of bug:
  
https://user-images.githubusercontent.com/89889704/134979056-653976d3-ec83-44c5-948a-4ee8baac2fa7.mp4

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22
  Uname: Linux 5.11.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Oct 26 19:10:25 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-10-26 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  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-dash-to-panel/+bug/1948893/+subscriptions


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

[Desktop-packages] [Bug 1940836] Re: Libreoffice Calc rendering very slow on GTK3

2021-10-27 Thread laurent

Experiencing similar slowdowns running the LibreOffice 7.2.1.2 snap on
Ubuntu 20.04.3

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

Title:
  Libreoffice Calc rendering very slow on GTK3

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  I'm on a MATE 20.04 machine, with Nvidia proprietary drivers (for
  reference, can't use Nouveau, since my machine doesn't boot with it).

  Libreoffice Calc renders slow. The delay is very noticeable, even when
  just typing characters.

  If I remove the GTK3 styling (`libreoffice-gtk3` package), then the
  rendering speed is fine (but of course, the program is unstyled, with
  some workflow consequences).

  I've tried to run on GTK2 (`libreoffice-gtk2` package installed), but
  I see Calc as unstyled, so it seems it's not actually running on GTK2.

  I've also tried to disable HW acceleration, but there is no
  improvement.

  I don't experience this slowness on any other program on my
  installation.

  I've noticed that when there's a delay, the Xorg process CPU
  occupation skyrockets (depending on how fast I type, it may go even to
  100% (single thread)).

  I've reproduced the same problem on all the LO versions, from the
  default (6.4.7) to the latest (7.2).

  The kernel version doesn't affect the problem as well (experienced on
  different 5.x versions).

  I've tried a packaged LO (from https://libreoffice.soluzioniopen.com),
  and it has the same behavior.

  I'd be perfectly happy to run on GTK2 as workaround, if that allowed
  persistent copy/paste :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-calc 1:6.4.7-0ubuntu0.20.04.1
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Aug 23 15:21:08 2021
  InstallationDate: Installed on 2020-07-01 (418 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1948641] Re: can not change dock bar position