date:20220607

Without mirroring, please try reducing the resolution of the external
monitor. Does that stop the flicker?

** Summary changed:

- [ASUS GL552VW] Screen flickering on external monitor
+ [ASUS GL552VW] Loss of signal (black screen) on external monitor

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

Title:
  [ASUS GL552VW] Loss of signal (black screen) on external monitor

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  External screen flickers on and off (image is present and then signal is 
lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh 
installation.
  Details:
  - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. 
The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make 
that HDMI work with NVIDIA GTX 960M in my laptop).
  - Nothing was installed after installing the OS - i connected to the Internet 
while installing the system and marked the option to download the updates.
  - I had that issue on Windows 10 - I fixed it by installing a latest Intel 
GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers 
installed by Windows - they were the latest Intel drivers.
  - Internal screen works fine.
  - If I mirror external and internal monitor, external isn't flickering, but 
internal monitor's resolution is lower that external's one.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 26 22:34:16 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d]
  InstallationDate: Installed on 2022-05-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: GL
  dmi.product.name: GL552VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1976163] Re: Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy) (continuation)

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

** This bug has been marked a duplicate of bug 1975884
   Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)

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

Title:
  Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04
  jammy) (continuation)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See earlier discussion https://bugs.launchpad.net/ubuntu/+bug/1975884

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat May 28 13:01:17 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2021-07-15 (316 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   LC_COLLATE=C
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-02 (26 days ago)

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


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

[Desktop-packages] [Bug 1975410] Re: Maximized window border under status bar in Wayland / Mutter

Thanks for the screenshot. This makes me suspect your issue is caused by
one of the many unsupported extensions that are enabled:

' changetopf...@romano.rgtti.com', 'temperature@xtranophilist', 'anti-
bt-i...@orzechowskid.github.com', 'putwin...@clemens.lab21.org',
'freon@UshakovVasilii_Github.yahoo.com', 'alternate-tab@gnome-shell-
extensions.gcampax.github.com', 'tray...@polof.github.com',
'topic...@phocean.net', 'systemMonitor@gnome-shell-
extensions.gcampax.github.com', 'pulseaudio-equali...@s8dragon.vn',
'dash-to-pa...@jderose9.github.com', 'TaskBar@zpydr',
'task...@ttux.net', 'windowIsReady_Remover@nunofarr...@gmail.com',
'battery-percent...@nohales.org', 'nohotcor...@azuri.free.fr',
'recentit...@bananenfisch.net', 'appmenu-regular-ic...@example.com',
'tinkerer@joebodo', 'battery-percent...@mubaris.github.io', 'desktop-
icons@csoriano', 'coverflowalt...@palatis.blogspot.com', 'compiz-alike-
windows-eff...@hermes83.github.com', 'no-overview@fthx', 'compiz-
windows-eff...@hermes83.github.com', 'trayiconsreloa...@selfmade.pl'

Please uninstall ALL of them. If you're not sure how then just run:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again. Does the bug still occur?

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

Title:
  Maximized window border under status bar in Wayland / Mutter

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Cf. https://gitlab.gnome.org/GNOME/mutter/-/issues/1627

  This is still present in Jammy (as it was in Impish). Were the
  upstream patches included the corresponding builds?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
  Uname: Linux 5.15.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun May 22 12:50:48 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-31 (1724 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073

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


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

[Desktop-packages] [Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace

2022-06-07 Thread Andy Chi

** Description changed:

  [Summary]
  The system will run into freeze if I connect the external monitor through 
DP/HDMI with dongle DA310 or Docking WD19TB
  
  [Steps to reproduce]
  1. Attact DA310 or WD19TB to DUT
  2. Cold Boot into OS
  3. Plug the DP/HDMI cable to DA310 or WD19TB
  4. Check the external monitor has signal
  5. Click keyboard or move mouse to check system can work well
  
  [Expected result]
  System won't be freeze with external monitor.
  
  [Actual result]
- System will be freeze.
+ Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse
+ don't work during the screen freeze.
  It can be recovered after unplug the external monitor sometime.
  
  [gnome-shell stack trace]
-  五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
-  五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
-  五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
-  五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
-  五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]:   ubuntu : TTY=pts/2 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
-  五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
opened for user root(uid=0) by ubuntu(uid=1001)
-  五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
closed for user root
-  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
-  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
-  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
-  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
-  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
-  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
-  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
+  五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
+  五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
+  五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
+  五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
+  五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]:   ubuntu : TTY=pts/2 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
+  五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
opened for user root(uid=0) by ubuntu(uid=1001)
+  五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
closed for user root
+  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
+  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
+  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
+  五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.

[Desktop-packages] [Bug 1973467] Re: [Ubuntu 22.04] [nvidia] [Wayland] Screen Blank: External screen is not turned off in sleep mode

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

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

Title:
  [Ubuntu 22.04] [nvidia] [Wayland] Screen Blank: External screen is not
  turned off in sleep mode

Status in mutter package in Ubuntu:
  New

Bug description:
  In Power -> Power Saving Options -> Screen Blank - the option states
  that the screen will be turned off after some period, which is what
  I'd expect from a sleep mode.

  I have a hybrid system. I have disabled the internal display and I use
  the external connected via HDMI (and I believe it is connected to the
  NVIDIA GPU). When the screen goes blank the external monitor is not
  turned off really. It goes blank but it is still turned on and glows,
  so no power is saved.

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

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


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

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

** Tags added: fixed-in-42.2

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

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

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  In Progress

Bug description:
  Impact
  ==
  GNOME Shell crashes when it's restarted on Xorg. (There is no option to 
restart GNOME Shell on Wayland.)

  Test Case
  =
  Install the update
  On the login screen, select your name.
  Click the gear button in the lower right and choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open the file browser.
  Press Alt-F2.
  In the dialog, enter 'r'
  GNOME Shell should restart without a crash message. Your file browser window 
should remain open.

  What Could Go Wrong
  ===
  See the master bug for this update LP: #1976381

  More Details
  
  gnome-shell crashes with SIGSEGV just after logging:

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

  Examples:

  https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
  https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206
  https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0

  Tracking in:

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

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


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

[Desktop-packages] [Bug 1977917] [NEW] package libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to overw

2022-06-07 Thread Miguel Cortez

Public bug reported:

trying to install wine 7 version

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libxau6 1:1.0.9-0ubuntu1 [modified: 
usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright]
ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Wed Jun  8 00:52:50 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other 
instances of package libxau6:i386
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:0622]
InstallationDate: Installed on 2022-06-07 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Dell Inc. Inspiron 3847
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic 
root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.8
SourcePackage: libxau
Title: package libxau6 1:1.0.9-0ubuntu1 [modified: 
usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other 
instances of package libxau6:i386
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2019
dmi.bios.release: 65.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 088DT1
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/07/2019:br65.10:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr:sku0622:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 3847
dmi.product.sku: 0622
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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

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


** Tags: amd64 apport-package focal ubuntu

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

Title:
  package libxau6 1:1.0.9-0ubuntu1 [modified:
  usr/share/doc/libxau6/changelog.Debian.gz
  usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which
  is different from other instances of package libxau6:i386

Status in libxau package in Ubuntu:
  New

Bug description:
  trying to install wine 7 version

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libxau6 1:1.0.9-0ubuntu1 [modified: 
usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Jun  8 00:52:50 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other 
instances of package libxau6:i386
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:0622]
  InstallationDate: Installed on 2022-06-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. Inspiron 3847
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic 
root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.8
  SourcePackage: libxau
  Title: package libxau6

[Desktop-packages] [Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace

2022-06-07 Thread Kai-Chuan Hsieh

I add commit mentioned in #13 to build mutter packages.
https://launchpad.net/~kchsieh/+archive/ubuntu/verification/

It doesn't help the issue.

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

Title:
  system freeze and gnome-shell reports multiple stack trace

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  [Summary]
  The system will run into freeze if I connect the external monitor through 
DP/HDMI with dongle DA310 or Docking WD19TB

  [Steps to reproduce]
  1. Attact DA310 or WD19TB to DUT
  2. Cold Boot into OS
  3. Plug the DP/HDMI cable to DA310 or WD19TB
  4. Check the external monitor has signal
  5. Click keyboard or move mouse to check system can work well

  [Expected result]
  System won't be freeze with external monitor.

  [Actual result]
  System will be freeze.
  It can be recovered after unplug the external monitor sometime.

  [gnome-shell stack trace]
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]:   ubuntu : TTY=pts/2 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
opened for user root(uid=0) by ubuntu(uid=1001)
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
closed for user root
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.

  This system is using OLED (3456x2160) panel, and I can't reproduce this issue 
on FHD panel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-17 (75 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  Package: gnome-shell 42.1-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1977715] Re: thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from INBOX

Thanks!

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1773140
   Importance: Unknown
   Status: Unknown

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

Title:
  thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from
  INBOX

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

Bug description:
  SUMMARY
  ---

  When moving e-mail from my INBOX to subfolders Thunderbird hangs and
  goes into an unusable state. The '"Thunderbird Mail" is not
  responding' pops up, and there is no option but to 'Force Quit'
  (because 'Wait' isn't helping).

  This does not happen for every move. But yesterday when sorting my
  INBOX, it happened more than 5 times in total.

  
  DESCRIPTION
  ---

  When moving mail,
  - I select one or more from the middle pane;
  - drag it/them to the left (folder pane).
  - There, I hover above the right folder and wait for it to highlight.
  - Upon highlight, I release the mouse.

  Normally this moves the e-mail(s) to that folder, but now I get a
  deadlock in about 1 out of 20 moves.

  On Focal, I used all versions, including
  - 1:91.7.0+build2-0ubuntu0.20.04.1
  - 1:91.8.1+build1-0ubuntu0.20.04.1
  - 1:91.9.1+build1-0ubuntu0.20.04.1

  On Jammy, I'm at:
  - 1:91.9.1+build1-0ubuntu0.22.04.1

  The first time I noticed this issue, was while I'm on Jammy. But, I
  hadn't cleaned my mailbox in a while, so it _might_ be related to the
  Thunderbird version. Although I my money would be on the version in
  conjunction with Jammy (Wayland?).)

  
  OBSERVATIONS
  

  - My INBOX is not big. It contained 2,500 mails or so. (And very few
  large e-mails.) The destination folders aren't particularly big
  either. And I didn't see a pattern related to which destination
  folder.

  - When starting thunderbird from the command line, I get lots of
  these:

  ###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ExpectFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)
  IPDL protocol error: Handler returned error code!
  ###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ForgetFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  IPDL protocol error: Handler returned error code!

(But I have no idea what they mean, or whether those log lines were
  emitted in the Focal version.)

  - Thunderbird runs as a family of three:

  /usr/lib/thunderbird/thunderbird
  \_ /usr/lib/thunderbird/thunderbird -contentproc -childID 1 -isForBrowser 
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021 
-appdir /usr/lib/thunderbird 549186 true tab
  \_ /usr/lib/thunderbird/thunderbird -contentproc -childID 2 -isForBrowser 
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021 
-appdir /usr/lib/thunderbird 549186 true tab

  - Main PID has 248 threads, child 1 has 23, child 2 has 22.

  
  ENVIRONMENT
  ---

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

  $ env | grep ^[GXW] | sort | grep -v GPG
  GDMSESSION=ubuntu
  GNOME_DESKTOP_SESSION_ID=this-is-deprecated
  GNOME_SETUP_DISPLAY=:1
  GNOME_SHELL_SESSION_MODE=ubuntu
  
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/6a49f69b_ac07_4c6d_b681_a0dada8d38d3
  GNOME_TERMINAL_SERVICE=:1.704
  GTK_MODULES=gail:atk-bridge
  WAYLAND_DISPLAY=wayland-0
  XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.0J31M1
  XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
  XDG_CURRENT_DESKTOP=ubuntu:GNOME
  
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
  XDG_MENU_PREFIX=gnome-
  XDG_RUNTIME_DIR=/run/user/1000
  XDG_SESSION_CLASS=user
  XDG_SESSION_DESKTOP=ubuntu
  XDG_SESSION_TYPE=wayland
  XMODIFIERS=@im=ibus

  
  CHILD 1 STRACE
  --

  (the following keeps repeating every 2 or 3 seconds)

  $ sudo strace -tt -fp 549263 -e'!futex,poll,epoll_wait,restart_syscall'
  strace: Process 549263 attached with 23 threads
  [pid 549277] 11:04:12.121020 write(9, "\372", 1) = 1
  [pid 549263] 11:04:12.121709 read(8, "\372", 1) = 1
  [pid 549263] 11:04:12.122327 write(9, "\372", 1) = 1
  [pid 549263] 11:04:12.122635 write(13, "\0", 1) = 1
  [pid 549265] 11:04:12.122921 read(12, "\0", 1) = 1
  [pid 549265] 11:04:12.123142 sendmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\4\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2733\377\377"...,
 iov_len=64}, 
{iov_base="\10\223\2\351\0\230\264f\372\";9E\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 
iov_len=28}], msg_iovlen=2, msg_controllen=0,

[Desktop-packages] [Bug 1977715] Re: thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from INBOX

2022-06-07 Thread Walter

Upstream bug report:
https://bugzilla.mozilla.org/show_bug.cgi?id=1773140

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

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

Title:
  thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from
  INBOX

Status in thunderbird package in Ubuntu:
  New

Bug description:
  SUMMARY
  ---

  When moving e-mail from my INBOX to subfolders Thunderbird hangs and
  goes into an unusable state. The '"Thunderbird Mail" is not
  responding' pops up, and there is no option but to 'Force Quit'
  (because 'Wait' isn't helping).

  This does not happen for every move. But yesterday when sorting my
  INBOX, it happened more than 5 times in total.

  
  DESCRIPTION
  ---

  When moving mail,
  - I select one or more from the middle pane;
  - drag it/them to the left (folder pane).
  - There, I hover above the right folder and wait for it to highlight.
  - Upon highlight, I release the mouse.

  Normally this moves the e-mail(s) to that folder, but now I get a
  deadlock in about 1 out of 20 moves.

  On Focal, I used all versions, including
  - 1:91.7.0+build2-0ubuntu0.20.04.1
  - 1:91.8.1+build1-0ubuntu0.20.04.1
  - 1:91.9.1+build1-0ubuntu0.20.04.1

  On Jammy, I'm at:
  - 1:91.9.1+build1-0ubuntu0.22.04.1

  The first time I noticed this issue, was while I'm on Jammy. But, I
  hadn't cleaned my mailbox in a while, so it _might_ be related to the
  Thunderbird version. Although I my money would be on the version in
  conjunction with Jammy (Wayland?).)

  
  OBSERVATIONS
  

  - My INBOX is not big. It contained 2,500 mails or so. (And very few
  large e-mails.) The destination folders aren't particularly big
  either. And I didn't see a pattern related to which destination
  folder.

  - When starting thunderbird from the command line, I get lots of
  these:

  ###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ExpectFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)
  IPDL protocol error: Handler returned error code!
  ###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ForgetFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  IPDL protocol error: Handler returned error code!

(But I have no idea what they mean, or whether those log lines were
  emitted in the Focal version.)

  - Thunderbird runs as a family of three:

  /usr/lib/thunderbird/thunderbird
  \_ /usr/lib/thunderbird/thunderbird -contentproc -childID 1 -isForBrowser 
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021 
-appdir /usr/lib/thunderbird 549186 true tab
  \_ /usr/lib/thunderbird/thunderbird -contentproc -childID 2 -isForBrowser 
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021 
-appdir /usr/lib/thunderbird 549186 true tab

  - Main PID has 248 threads, child 1 has 23, child 2 has 22.

  
  ENVIRONMENT
  ---

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

  $ env | grep ^[GXW] | sort | grep -v GPG
  GDMSESSION=ubuntu
  GNOME_DESKTOP_SESSION_ID=this-is-deprecated
  GNOME_SETUP_DISPLAY=:1
  GNOME_SHELL_SESSION_MODE=ubuntu
  
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/6a49f69b_ac07_4c6d_b681_a0dada8d38d3
  GNOME_TERMINAL_SERVICE=:1.704
  GTK_MODULES=gail:atk-bridge
  WAYLAND_DISPLAY=wayland-0
  XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.0J31M1
  XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
  XDG_CURRENT_DESKTOP=ubuntu:GNOME
  
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
  XDG_MENU_PREFIX=gnome-
  XDG_RUNTIME_DIR=/run/user/1000
  XDG_SESSION_CLASS=user
  XDG_SESSION_DESKTOP=ubuntu
  XDG_SESSION_TYPE=wayland
  XMODIFIERS=@im=ibus

  
  CHILD 1 STRACE
  --

  (the following keeps repeating every 2 or 3 seconds)

  $ sudo strace -tt -fp 549263 -e'!futex,poll,epoll_wait,restart_syscall'
  strace: Process 549263 attached with 23 threads
  [pid 549277] 11:04:12.121020 write(9, "\372", 1) = 1
  [pid 549263] 11:04:12.121709 read(8, "\372", 1) = 1
  [pid 549263] 11:04:12.122327 write(9, "\372", 1) = 1
  [pid 549263] 11:04:12.122635 write(13, "\0", 1) = 1
  [pid 549265] 11:04:12.122921 read(12, "\0", 1) = 1
  [pid 549265] 11:04:12.123142 sendmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\4\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2733\377\377"...,
 iov_len=64}, 
{iov_base="\10\223\2\351\0\230\264f\372\";9E\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 
iov_len=28}], msg_iovlen=2, msg_controllen=0,

[Desktop-packages] [Bug 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing

I'm assigning this to me for tracking but I won't be able to look into
this more until next week. Sorry.

** Changed in: wireplumber (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: pipewire-media-session (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  wireplumber conflicts with pipewire-media-session & needs fixing

Status in pipewire-media-session package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Triaged
Status in wireplumber package in Ubuntu:
  Triaged
Status in pipewire-media-session package in Debian:
  Confirmed

Bug description:
  This issue was reported on IRC and we should probably fix it before
  installing wireplumber by default so I'm setting the block-proposed
  tag.

  https://i.imgur.com/L5VFZO8.png

  wireplumber is apparently too forceful in how it enables PipeWire.
  Both Arch Linux and Debian had to

  https://archlinux.org/news/undone-replacement-of-pipewire-media-
  session-with-wireplumber/

  Is it necessary for wireplumber to conflict with pipewire-media-
  session?

  Should we add Replaces?

  What files does pipewire-media-session need to clean up when it is
  removed?

  See https://salsa.debian.org/gnome-team/gnome-remote-
  desktop/-/commit/52799cfd for an example of how files that aren't
  technically conffiles can be removed.

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


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

[Desktop-packages] [Bug 1977679] Re: Firefox opens KML file in neverending loop if associated with "System Handler"

2022-06-07 Thread Jaromir Obr

I would expect that Firefox should show the dialog "What to do with file?" 
again if OS is not able to open the file regardless the option "Do this 
automatically from now" is ticked.
I guess Firefox nor OS cannot handle KML file itself. However the state "New 
tab is open again and again  automatically" shouldn't occur because it could 
exhaust memory in worst case and it's also bad use experience to see 
neverending opening of new tabs.

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

Title:
  Firefox opens KML file in neverending loop if associated with "System
  Handler"

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Found when trying open a KML export file from Google Timeline.
  It can be reproduced even with an empty KML file.

  Steps:
  * Create an empty file "test.kml" (run "$ touch test.kml")
  * Open the application "Files"
  * Right click on the test.kml and open it with Firefox
  * Open with "System Handler" and check the option "Do this automatically for 
files like this from now on" (see "Screenshot from 2022-06-05 11-13-23.png")

  Expected result:
  * No infinite opening

  Actual result:
  * Firefox starts opening the file again and again (see "Screenshot from 
2022-06-05 11-04-35.png")

  Used SW:
  * Ubuntu 22.04 LTS
  * Firefox 101.0
  * Files 42.1.1

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


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

[Desktop-packages] [Bug 1975945] Re: Update gnome-control-center to 41.7

I completed all 3 test cases successfully with gnome-control-center
1:41.7-0ubuntu0.22.04.1

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

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

Title:
Update gnome-control-center to 41.7

Status in gnome-control-center package in Ubuntu:
Fix Released
Status in gnome-control-center source package in Jammy:
Fix Committed

Bug description:
Impact
--
There was a new bugfix release in the stable 41 series.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/compare/41.4...41.7
6 of these commits were already in Ubuntu 22.04 LTS.

New changes:
- Translation updates (because of Ubuntu language packs, this has no effect
until the next language pack update, which is a few months away)
- info-overview: Allow changing "Device Name" by pressing "Enter"
- wwan: Remove duplicate line from .desktop
- keyboard: Avoid segfault due to no "data" for `custom_shortcut_add_row`
- network: Fix saving passwords for non-wifi connections
- info-overview: Remove trailing space after CPU name

Test Case 1
---
Install the update.
Make sure that gnome-control-center continues to run well.

Test Case 2
---
Install gnome-session
Log out.
Click your name on the login screen.
Click the gear in the bottom right corner and choose GNOME.
Finish logging in.
Make sure that gnome-control-center continues to run well.

This test case is because some of our Ubuntu customizations only show
in the Ubuntu session, not other sessions like vanilla GNOME.

Test Case 3
---
Open gnome-control-center
Click the last item in the left sidebar named About
Click Device Name.
Type in a different name for your computer.
Press Enter.
The Rename Device dialog should close and your new computer name should take
effect.

What Could Go Wrong
---
gnome-control-center is used by Ubuntu Desktop and Ubuntu Budgie.
It is a critical app for viewing and changing a huge variety of settings for
these desktops.

gnome-control-center is part of GNOME Core and has a microrelease
exception for Ubuntu stable release updates.

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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

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

[Desktop-packages] [Bug 1976120] Re: Update nautilus to 42.2

I successfully completed all 3 test cases with nautilus 1:42.2-0ubuntu1

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

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

Title:
  Update nautilus to 42.2

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

Bug description:
  Impact
  --
  This is a new stable release in the GNOME 42 series

  https://gitlab.gnome.org/GNOME/nautilus/-/blob/42.2/NEWS

  Test Case 1
  ---
  Install the update
  Ensure that Nautilus still works well

  Test Case 2
  ---
  Navigate to a folder.
  In the path bar. Right click on the parent folder and choose Open in New 
Window
  nautilus should open a new window with crashing.
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/2208

  
  Test Case 3 Optional
  
  Click the ☰ menu and choose Preferences.
  Set Performances > Count Number of Files in Folders to "On this computer 
only" (that is the default)
  Connect to a remote server (sshfs, smbfs, Google Drive etc.)
  Nautilus should not be showing you the count of items in those folders.

  
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/2035

  What Could Go Wrong
  ---
  nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop 
flavors use other file browsers.

  As a component of GNOME core, there is a micro-release exception for
  nautilus

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


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

[Desktop-packages] [Bug 1976381] Re: Update mutter to 42.2

** Changed in: mutter (Ubuntu Jammy)
   Status: Triaged => In Progress

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

Title:
  Update mutter to 42.2

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  In Progress

Bug description:
  
  Impact
  --
  There is a new bugfix release in the stable 42 series.
  https://gitlab.gnome.org/GNOME/mutter/-/blob/42.2/NEWS

  Test Case
  -
  sudo apt install budgie-desktop gnome-session gnome-shell-extensions
  Install the update.
  Log out.
  Select your name on the login screen.
  Click the gear button to choose a session to log in to.
  Finish logging in.

  Verify that things continue to work well for all these sessions:
  Budgie
  GNOME
  GNOME Classic
  Ubuntu
  Ubuntu on Xorg

  What Could Go Wrong
  ---
  Mutter is an essential component of the default Ubuntu desktop and for the 
desktop used by Ubuntu Budgie.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  mutter is part of GNOME Core and is included in the GNOME micro
  release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

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


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

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

** Changed in: mutter (Ubuntu Jammy)
   Status: Triaged => In Progress

** Description changed:

+ Impact
+ ==
+ GNOME Shell crashes when it's restarted on Xorg. (There is no option to 
restart GNOME Shell on Wayland.)
+ 
+ Test Case
+ =
+ Install the update
+ On the login screen, select your name.
+ Click the gear button in the lower right and choose Ubuntu on Xorg
+ Enter your password to finish logging in.
+ Open the file browser.
+ Press Alt-F2.
+ In the dialog, enter 'r'
+ GNOME Shell should restart without a crash message. Your file browser window 
should remain open.
+ 
+ What Could Go Wrong
+ ===
+ See the master bug for this update LP: #1976381
+ 
+ More Details
+ 
  gnome-shell crashes with SIGSEGV just after logging:
  
  gnome-shell[3117]: JS ERROR: TypeError: window is null
  _destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
  _initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16
  
  Examples:
  
  https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
  https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206
  https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0
  
  Tracking in:
  
  https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470
  ^^^ this is the second most common gnome-shell crash on errors.ubuntu.com

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

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

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  In Progress

Bug description:
  Impact
  ==
  GNOME Shell crashes when it's restarted on Xorg. (There is no option to 
restart GNOME Shell on Wayland.)

  Test Case
  =
  Install the update
  On the login screen, select your name.
  Click the gear button in the lower right and choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open the file browser.
  Press Alt-F2.
  In the dialog, enter 'r'
  GNOME Shell should restart without a crash message. Your file browser window 
should remain open.

  What Could Go Wrong
  ===
  See the master bug for this update LP: #1976381

  More Details
  
  gnome-shell crashes with SIGSEGV just after logging:

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

  Examples:

  https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
  https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206
  https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0

  Tracking in:

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

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


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

[Desktop-packages] [Bug 1968987] Re: Login hangs after entering password

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

This was fixed in an update for gnome-remote-desktop 42.1.1-0ubuntu1
which should be available to everyone within 2 days. If you install all
updates, you will be able to log in normally. As a workaround, you can
log in to the GNOME on Xorg session so that you can log in for the first
time to install updates.

There will be updated ISOs available when Ubuntu 22.04.1 LTS is released
in a few months.

** This bug has been marked a duplicate of bug 1971195
gnome-remote-desktop leads to a session crash inside qemu with virtio-vga

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

Title:
Login hangs after entering password

Status in gnome-remote-desktop package in Ubuntu:
New

Bug description:
After a recent update Ubuntu 22.04 stalled and screen went black after
entering password. After process of elimination it seems that the
culprit is the update to gnome-remote-desktop.

1. Description: Ubuntu Jammy Jellyfish (development branch)
Release: 22.04

2. gnome-remote-desktop 42.0-2

3. I expected Ubuntu 22.04 to open after entering password at login.

4. Instead the login screen would freeze, then go black. Using a
previous snapshot provided by zsys and synaptic package manager, I
iterated on the "upgradable" updates until I had all the updates
installed except the one. Whenever gnome-remote-desktop is installed,
the login process fails. So, I deleted gnome-remote-desktop and all
seems fine. This ubuntu is installed in a VM using KVM/QEMU

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-remote-desktop (not installed)
ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0
Uname: Linux 5.17.0-1003-oem x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 14 01:52:40 2022
InstallationDate: Installed on 2022-04-14 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-remote-desktop
UpgradeStatus: No upgrade log present (probably fresh install)

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

[Desktop-packages] [Bug 1975642] Re: package firefox 100.0.2+build1-0ubuntu0.21.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess was killed by signal (Killed)

2022-06-07 Thread svenmeier

"Invalid" is wrong, since the upgrade finished without a working Firefox
installation.


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

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

Title:
  package firefox 100.0.2+build1-0ubuntu0.21.10.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess was killed by signal (Killed)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The 'frontend' informing dialog about migration to Firefox snap froze,
  had to kill it to resume upgrade to 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu 5.13.0-44.49-generic 5.13.19
  Uname: Linux 5.13.0-44-generic x86_64
  NonfreeKernelModules: bbswitch
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sven   1645 F pulseaudio
  BuildID: 20220519220738
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Tue May 24 22:26:25 2022
  ErrorMessage: new firefox package pre-installation script subprocess was 
killed by signal (Killed)
  ForcedLayersAccel: False
  InstallationDate: Installed on 2019-10-03 (964 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  IpRoute:
   default via 192.168.178.1 dev wlp60s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.178.0/24 dev wlp60s0 proto kernel scope link src 192.168.178.20 
metric 600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  RunningIncompatibleAddons: False
  Snap: firefox 100.0.2-1 (stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   2Done2022-05-24T22:19:34+02:00  2022-05-24T22:29:56+02:00  Install 
"firefox" snap
  Title: package firefox 100.0.2+build1-0ubuntu0.21.10.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess was 
killed by signal (Killed)
  UpgradeStatus: Upgraded to jammy on 2022-05-24 (0 days ago)
  dmi.bios.date: 03/15/2019
  dmi.bios.release: 1.28
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1A
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:br1.28:efr1.28:svnHUAWEI:pnMACH-WX9:pvrM1A:rvnHUAWEI:rnMACH-WX9-PCB:rvrM1A:cvnHUAWEI:ct10:cvrM1A:skuC100:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C100
  dmi.product.version: M1A
  dmi.sys.vendor: HUAWEI
  modified.conffile..etc.firefox.syspref.js: [deleted]

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


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

[Desktop-packages] [Bug 1975896] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

This looks like a temporary network failure:

error: cannot perform the following tasks:
- Download snap "chromium" (1993) from channel "stable" (Get 
https://canonical-lgw01.cdn.snapcraftcontent.com/download-origin/canonical-lgw01/XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R_1993.snap?interactive=1=1653642000_bd3a40340567d0b61be4048cf8055c93275d7710:
 EOF)

Can you try reinstalling, and let us know whether this succeeds?

sudo apt reinstall chromium-browser

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

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Errors were encountered while processing:
   /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu2_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  AptOrdering:
   chromium-browser:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri May 27 11:02:41 2022
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2022-05-26 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1887195] Re: [snap] "Show in folder" for downloaded files doesn't work

This isn't specific to Unity, but rather to the version of xdg-desktop-
portal available in your distribution. I just verified that it works as
expected in a stock 22.04 VM, but not in 20.04 (which confirms what
you're seeing).

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

Title:
  [snap] "Show in folder" for downloaded files doesn't work

Status in snapd:
  Invalid
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  In the chromium snap (Version 83.0.4103.116 on focal at the moment),
  after downloading files, navigating to the downloaded file doesn't
  work. Clicking on "Show in folder" only opens nautilus, but doesn't
  actually highlight the file. This works as expected on chrome and
  older deb builds in bionic, for example.

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


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

[Desktop-packages] [Bug 1959747]

2022-06-07 Thread Martin Sivak

Same here on Fedora 36, Thunderbird 91.8.0 (64 bit).

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

Title:
  [upstream] Very high CPU and slow responsiveness in Thunderbird 91

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

Bug description:
  Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just
  moving the mouse cursor over a message list results in 365% CPU for
  me.

  I had to set this in the config editor to fix it:

    gfx.webrender.force-disabled = TRUE

  Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423

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


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

[Desktop-packages] [Bug 1975642] Re: package firefox 100.0.2+build1-0ubuntu0.21.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess was killed by signal (Killed)

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

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

Title:
  package firefox 100.0.2+build1-0ubuntu0.21.10.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess was killed by signal (Killed)

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  The 'frontend' informing dialog about migration to Firefox snap froze,
  had to kill it to resume upgrade to 22.04

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  ProcVersionSignature: Ubuntu 5.13.0-44.49-generic 5.13.19
  Uname: Linux 5.13.0-44-generic x86_64
  NonfreeKernelModules: bbswitch
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sven   1645 F pulseaudio
  BuildID: 20220519220738
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Tue May 24 22:26:25 2022
  ErrorMessage: new firefox package pre-installation script subprocess was 
killed by signal (Killed)
  ForcedLayersAccel: False
  InstallationDate: Installed on 2019-10-03 (964 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  IpRoute:
   default via 192.168.178.1 dev wlp60s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.178.0/24 dev wlp60s0 proto kernel scope link src 192.168.178.20 
metric 600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  RunningIncompatibleAddons: False
  Snap: firefox 100.0.2-1 (stable)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   2Done2022-05-24T22:19:34+02:00  2022-05-24T22:29:56+02:00  Install 
"firefox" snap
  Title: package firefox 100.0.2+build1-0ubuntu0.21.10.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess was 
killed by signal (Killed)
  UpgradeStatus: Upgraded to jammy on 2022-05-24 (0 days ago)
  dmi.bios.date: 03/15/2019
  dmi.bios.release: 1.28
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.28
  dmi.board.name: MACH-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1A
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1A
  dmi.ec.firmware.release: 1.28
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:br1.28:efr1.28:svnHUAWEI:pnMACH-WX9:pvrM1A:rvnHUAWEI:rnMACH-WX9-PCB:rvrM1A:cvnHUAWEI:ct10:cvrM1A:skuC100:
  dmi.product.family: MateBook X
  dmi.product.name: MACH-WX9
  dmi.product.sku: C100
  dmi.product.version: M1A
  dmi.sys.vendor: HUAWEI
  modified.conffile..etc.firefox.syspref.js: [deleted]

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


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

[Desktop-packages] [Bug 1977679] Re: Firefox opens KML file in neverending loop if associated with "System Handler"

I can observe the problem in a fully up-to-date Ubuntu 22.04 VM.

I'm not sure what should be the expected behaviour though. Do you expect
firefox to open/render a KML file in any useful way?

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

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

Title:
  Firefox opens KML file in neverending loop if associated with "System
  Handler"

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Found when trying open a KML export file from Google Timeline.
  It can be reproduced even with an empty KML file.

  Steps:
  * Create an empty file "test.kml" (run "$ touch test.kml")
  * Open the application "Files"
  * Right click on the test.kml and open it with Firefox
  * Open with "System Handler" and check the option "Do this automatically for 
files like this from now on" (see "Screenshot from 2022-06-05 11-13-23.png")

  Expected result:
  * No infinite opening

  Actual result:
  * Firefox starts opening the file again and again (see "Screenshot from 
2022-06-05 11-04-35.png")

  Used SW:
  * Ubuntu 22.04 LTS
  * Firefox 101.0
  * Files 42.1.1

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


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

[Desktop-packages] [Bug 1966580] Re: Erroneously huge mouse pointer with snap-packaged firefox in jammy

Thanks for the additional information anyway.

Let's keep the report open in case someone with a similar set up comes
across it and can help understand the problem.

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

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

Title:
  Erroneously huge mouse pointer with snap-packaged firefox in jammy

Status in firefox package in Ubuntu:
  New

Bug description:
  I just upgraded to jammy, and the mouse cursor now becomes comically
  huge whilst it's over a Firefox window.

  I suspect this might be something to do with this being a HiDPI
  laptop.

  
  I'm also fairly upset about the overcomplicated - and apparently broken - 
snaps being enforced on me, so I've fixed this by uninstalling snapd, and 
obtaining Firefox directly from Mozilla instead - which works absolutely fine.

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


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

[Desktop-packages] [Bug 1976330] Re: [upstream] No dropdown menu on bookmarks folder in trunk build under wayland

** Summary changed:

- No dropdown menu on bookmarks folder in trunk build under wayland
+ [upstream] No dropdown menu on bookmarks folder in trunk build under wayland

** Tags added: upstream

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

Title:
  [upstream] No dropdown menu on bookmarks folder in trunk build under
  wayland

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  firefox-trunk: Installed: 103.0~a1~hg20220530r619138-0ubuntu0.22.10.1~umd1
  Ubuntu 22.10 Kinetic Wayland session
  Window Protocol   wayland
  Desktop Environment gnome

  problem with Bookmarks:
  click om Bookmarks - the list of bookmarks is displayed
  right click on a bookmark folder - dropdown menu with 'Open all 
Bookmarks/Edit Folder/Delete Folder...'
  open folder and right click on a second level folder - nothing happens, the 
dropdown menu does not appear.

  corrado@corrado-a4-kk-0513:~$ inxi -SCGx
  System:
Host: corrado-a4-kk-0513 Kernel: 5.15.0-27-generic arch: x86_64 bits: 64
  compiler: gcc v: 11.2.0 Desktop: GNOME v: 42.1
  Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-4130 bits: 64 type: MT MCP
  arch: Haswell rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 798 high: 799 min/max: 800/3400 cores: 1: 798 2: 798
  3: 799 4: 799 bogomips: 27138
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
  vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0
Display: wayland server: X.Org v: 1.22.1.1 with: Xwayland v: 22.1.1
  compositor: gnome-shell driver: gpu: i915 resolution: 1680x1050~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
  v: 4.6 Mesa 22.0.1 direct render: Yes
  corrado@corrado-a4-kk-0513:~$ 

  problem does not occur on same system with FF snap firefox 100.0.2-1 1377 
  Window Protocol   xwayland
  Desktop Environment gnome

  same problem on Ubuntu 22.04 with 
  firefox-trunk Installed: 102.0~a1~hg20220527r619043-0ubuntu0.22.04.1~umd1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: firefox-trunk 103.0~a1~hg20220530r619138-0ubuntu0.22.10.1~umd1 
[origin: LP-PPA-ubuntu-mozilla-daily]
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  corrado1790 F pipewire-media-
   /dev/snd/controlC1:  corrado1790 F pipewire-media-
   /dev/snd/seq:corrado1789 F pipewire
  BuildID: 20220530185055
  CasperMD5CheckResult: pass
  Channel: nightly
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 31 08:37:09 2022
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox-trunk/omni.ja:greprefs.js:306
  DefaultProfilePrefSources:
   /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js
   /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js
  DefaultProfilePrefs: network.manage-offline-status: true 
(/usr/lib/firefox-trunk/defaults/pref/vendor-gre.js)
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-05-14 (16 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220512)
  IpRoute:
   default via 192.168.43.1 dev wlx48ee0c2322b8 proto dhcp src 192.168.43.140 
metric 600 
   169.254.0.0/16 dev wlx48ee0c2322b8 scope link metric 1000 
   192.168.43.0/24 dev wlx48ee0c2322b8 proto kernel scope link src 
192.168.43.140 metric 600
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox-trunk/omni.ja:greprefs.js:306
  Profile0PrefSources:
   /usr/lib/firefox-trunk/defaults/pref/vendor-gre.js
   /usr/lib/firefox-trunk/defaults/pref/channel-prefs.js
   prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=103.0a1/20220530185055 (In use)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade

[Desktop-packages] [Bug 1977715] Re: thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from INBOX

Thanks for this very complete report Walter. It looks like this might be
an upstream bug that affects thunderbird when running natively on
Wayland. Would you mind reporting it in the upstream tracker
(https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird) and
sharing the link to it here?

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

Title:
  thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from
  INBOX

Status in thunderbird package in Ubuntu:
  New

Bug description:
  SUMMARY
  ---

  When moving e-mail from my INBOX to subfolders Thunderbird hangs and
  goes into an unusable state. The '"Thunderbird Mail" is not
  responding' pops up, and there is no option but to 'Force Quit'
  (because 'Wait' isn't helping).

  This does not happen for every move. But yesterday when sorting my
  INBOX, it happened more than 5 times in total.

  
  DESCRIPTION
  ---

  When moving mail,
  - I select one or more from the middle pane;
  - drag it/them to the left (folder pane).
  - There, I hover above the right folder and wait for it to highlight.
  - Upon highlight, I release the mouse.

  Normally this moves the e-mail(s) to that folder, but now I get a
  deadlock in about 1 out of 20 moves.

  On Focal, I used all versions, including
  - 1:91.7.0+build2-0ubuntu0.20.04.1
  - 1:91.8.1+build1-0ubuntu0.20.04.1
  - 1:91.9.1+build1-0ubuntu0.20.04.1

  On Jammy, I'm at:
  - 1:91.9.1+build1-0ubuntu0.22.04.1

  The first time I noticed this issue, was while I'm on Jammy. But, I
  hadn't cleaned my mailbox in a while, so it _might_ be related to the
  Thunderbird version. Although I my money would be on the version in
  conjunction with Jammy (Wayland?).)

  
  OBSERVATIONS
  

  - My INBOX is not big. It contained 2,500 mails or so. (And very few
  large e-mails.) The destination folders aren't particularly big
  either. And I didn't see a pattern related to which destination
  folder.

  - When starting thunderbird from the command line, I get lots of
  these:

  ###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ExpectFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)
  IPDL protocol error: Handler returned error code!
  ###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ForgetFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)
  Unsupported modifier, resource creation failed.
  XXX: resource creation failed
  IPDL protocol error: Handler returned error code!

(But I have no idea what they mean, or whether those log lines were
  emitted in the Focal version.)

  - Thunderbird runs as a family of three:

  /usr/lib/thunderbird/thunderbird
  \_ /usr/lib/thunderbird/thunderbird -contentproc -childID 1 -isForBrowser 
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021 
-appdir /usr/lib/thunderbird 549186 true tab
  \_ /usr/lib/thunderbird/thunderbird -contentproc -childID 2 -isForBrowser 
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021 
-appdir /usr/lib/thunderbird 549186 true tab

  - Main PID has 248 threads, child 1 has 23, child 2 has 22.

  
  ENVIRONMENT
  ---

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

  $ env | grep ^[GXW] | sort | grep -v GPG
  GDMSESSION=ubuntu
  GNOME_DESKTOP_SESSION_ID=this-is-deprecated
  GNOME_SETUP_DISPLAY=:1
  GNOME_SHELL_SESSION_MODE=ubuntu
  
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/6a49f69b_ac07_4c6d_b681_a0dada8d38d3
  GNOME_TERMINAL_SERVICE=:1.704
  GTK_MODULES=gail:atk-bridge
  WAYLAND_DISPLAY=wayland-0
  XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.0J31M1
  XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
  XDG_CURRENT_DESKTOP=ubuntu:GNOME
  
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
  XDG_MENU_PREFIX=gnome-
  XDG_RUNTIME_DIR=/run/user/1000
  XDG_SESSION_CLASS=user
  XDG_SESSION_DESKTOP=ubuntu
  XDG_SESSION_TYPE=wayland
  XMODIFIERS=@im=ibus

  
  CHILD 1 STRACE
  --

  (the following keeps repeating every 2 or 3 seconds)

  $ sudo strace -tt -fp 549263 -e'!futex,poll,epoll_wait,restart_syscall'
  strace: Process 549263 attached with 23 threads
  [pid 549277] 11:04:12.121020 write(9, "\372", 1) = 1
  [pid 549263] 11:04:12.121709 read(8, "\372", 1) = 1
  [pid 549263] 11:04:12.122327 write(9, "\372", 1) = 1
  [pid 549263] 11:04:12.122635 write(13, "\0", 1) = 1
  [pid 549265] 11:04:12.122921 read(12, "\0", 1) = 1
  [pid 549265] 11:04:12.123142 sendmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\4\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2733\377\377"...,
 iov_len=64},

[Desktop-packages] [Bug 1959417] Re: browsers and other apps packaged as snaps can't read files under ~/.local/share/

For reference: https://github.com/snapcore/snapd/commit/561783b88bb.

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

Title:
  browsers and other apps packaged as snaps can't read files under
  ~/.local/share/

Status in snapd:
  Fix Committed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in jupyter-notebook package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 22.04 LTS
  2. Install jupyter-notebook package
  3. Open terminal to launch jupyter-notebook command

  $ jupyter-notebook
  [I 18:53:12.601 NotebookApp] Serving notebooks from local directory: /home/j
  [I 18:53:12.601 NotebookApp] Jupyter Notebook 6.4.5 is running at:
  [I 18:53:12.601 NotebookApp] 
http://localhost:/?token=6df6a314b44a50e058ff27f735d91cbd46bfaf0e403bd2e9
  [I 18:53:12.601 NotebookApp]  or 
http://127.0.0.1:/?token=6df6a314b44a50e058ff27f735d91cbd46bfaf0e403bd2e9
  [I 18:53:12.601 NotebookApp] Use Control-C to stop this server and shut down 
all kernels (twice to skip confirmation).
  [C 18:53:12.635 NotebookApp] 
  
  To access the notebook, open this file in a browser:
  file:///home/j/.local/share/jupyter/runtime/nbserver-45601-open.html
  Or copy and paste one of these URLs:
  
http://localhost:/?token=6df6a314b44a50e058ff27f735d91cbd46bfaf0e403bd2e9
   or 
http://127.0.0.1:/?token=6df6a314b44a50e058ff27f735d91cbd46bfaf0e403bd2e9


  
  Expected results:
  * default web-browser opened and it shows jupyter-notebook interface after 
redirection from local html-file to http://localhost:

  
  Actual results:
  * default web-browser opened with error message

  > Access to the file was denied
  > The file at /home/j/.local/share/jupyter/runtime/nbserver-45601-open.html 
is not readable.
  > It may have been removed, moved, or file permissions may be preventing 
access.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: jupyter-notebook 6.4.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Fri Jan 28 18:49:44 2022
  InstallationDate: Installed on 2022-01-28 (0 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220128)
  PackageArchitecture: all
  SourcePackage: jupyter-notebook
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-01-28T14:45:41.897765

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


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

[Desktop-packages] [Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace

2022-06-07 Thread Treviño

Some updates here:

The shell isn't really hanging... The fact is that the input/output GLib 
Sources that the shell
adds to the main context are starving and never processed because we add 
thousands of timeouts and `Meta.Later` sources as per a `window-removed` signal 
that is triggered thousand times (source is actually `[gnome-shell] 
this._queueCheckWorkspaces`).

This leads to CPU being 100% spending time in processing such sources
(https://usercontent.irccloud-cdn.com/file/v1ZGs5f6/image.png) thousands
of GSources being added: https://i.imgur.com/QUuuZA1.png

And these are added via https://usercontent.irccloud-
cdn.com/file/V4jfRY94/with%20laters%20added%20at that sends the window-
removed signal (https://i.imgur.com/PNBn6Cv.png).

Now, it seems possible that the fixes part of 42.2 in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2413 fix this
case.

But we still need to test that.

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

Title:
  system freeze and gnome-shell reports multiple stack trace

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  [Summary]
  The system will run into freeze if I connect the external monitor through 
DP/HDMI with dongle DA310 or Docking WD19TB

  [Steps to reproduce]
  1. Attact DA310 or WD19TB to DUT
  2. Cold Boot into OS
  3. Plug the DP/HDMI cable to DA310 or WD19TB
  4. Check the external monitor has signal
  5. Click keyboard or move mouse to check system can work well

  [Expected result]
  System won't be freeze with external monitor.

  [Actual result]
  System will be freeze.
  It can be recovered after unplug the external monitor sometime.

  [gnome-shell stack trace]
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]:   ubuntu : TTY=pts/2 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
opened for user root(uid=0) by ubuntu(uid=1001)
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
closed for user root
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.

  This system is using OLED (3456x2160) panel, and I can't reproduce this issue 
on FHD panel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-17 (75 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)

[Desktop-packages] [Bug 1969509] Re: [snap] Unmaximized but not unfullscreened

** Changed in: firefox (Ubuntu)
   Status: Incomplete => 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/1969509

Title:
  [snap] Unmaximized but not unfullscreened

Status in Mozilla Firefox:
  In Progress
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10
  Firefox 99.0.1-1 from snap

  With title bar hidden:
   maximize Firefox window
   set it full-screen
   move cursor to the upper edge of the screen
   double-click the bar

  The window ends up in unexpected state

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


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

[Desktop-packages] [Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace

2022-06-07 Thread Treviño

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

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

Title:
  system freeze and gnome-shell reports multiple stack trace

Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  [Summary]
  The system will run into freeze if I connect the external monitor through 
DP/HDMI with dongle DA310 or Docking WD19TB

  [Steps to reproduce]
  1. Attact DA310 or WD19TB to DUT
  2. Cold Boot into OS
  3. Plug the DP/HDMI cable to DA310 or WD19TB
  4. Check the external monitor has signal
  5. Click keyboard or move mouse to check system can work well

  [Expected result]
  System won't be freeze with external monitor.

  [Actual result]
  System will be freeze.
  It can be recovered after unplug the external monitor sometime.

  [gnome-shell stack trace]
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
   五  27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]:   ubuntu : TTY=pts/2 ; 
PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
opened for user root(uid=0) by ubuntu(uid=1001)
   五  27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session 
closed for user root
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 
0x56156f8f04a0 ==
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was 
window-added on MetaWorkspace 0x56156f916640.
   五  27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back 
into JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.

  This system is using OLED (3456x2160) panel, and I can't reproduce this issue 
on FHD panel.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-03-17 (75 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  Package: gnome-shell 42.1-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  Tags:  jammy wayland-session
  Uname: Linux 5.15.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1958813] Re: [snap] I have on clean install some weird folder /home/user/Downloads/firefox.tmp/

This is now fixed, see the upstream bug report
(https://bugzilla.mozilla.org/show_bug.cgi?id=1733750) for details.

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

** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  [snap] I have on clean install some weird folder
  /home/user/Downloads/firefox.tmp/

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

Bug description:
  I have on clean install some weird folder /home/user/Downloads/firefox.tmp/
  Downloads/
  └── firefox.tmp
  ├── security_state
  ├── Temp-efca5f30-b773-40f3-afd2-fb29f7ca2d30
  │   └── mesa_shader_cache
  │   ├── 5a
  │   │   └── a12b397653d94da952e9174b48042792d0b5b5
  │   ├── 86
  │   │   └── 658cd26a8a5c083a0d01153d2d26eb349759ce
  │   ├── c2
  │   │   └── 6957f33af79c866d74f0dd37b47ef18e57d431
  │   └── index
  └── tmpaddon

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.3
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Mon Jan 24 03:49:13 2022
  InstallationDate: Installed on 2022-01-21 (2 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20220121)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1977782] Re: Unable to open any file:/// URL