[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

[W. J. van der Laan]

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

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in AppArmor:
  New
Status in Wike:
  New
Status in akonadiconsole package in Ubuntu:
  Fix Released
Status in akregator package in Ubuntu:
  Fix Released
Status in angelfish package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Fix Released
Status in devhelp package in Ubuntu:
  Fix Released
Status in digikam package in Ubuntu:
  Fix Released
Status in epiphany-browser package in Ubuntu:
  Fix Released
Status in evolution package in Ubuntu:
  Fix Released
Status in falkon package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in foliate package in Ubuntu:
  Fix Committed
Status in freecad package in Ubuntu:
  Invalid
Status in geary package in Ubuntu:
  Fix Released
Status in ghostwriter package in Ubuntu:
  Fix Released
Status in gnome-packagekit package in Ubuntu:
  Invalid
Status in goldendict-webengine package in Ubuntu:
  Fix Released
Status in guix package in Ubuntu:
  New
Status in kalgebra package in Ubuntu:
  Fix Released
Status in kchmviewer package in Ubuntu:
  Fix Released
Status in kdeplasma-addons package in Ubuntu:
  Fix Released
Status in kgeotag package in Ubuntu:
  Fix Released
Status in kiwix package in Ubuntu:
  Incomplete
Status in kmail package in Ubuntu:
  Fix Released
Status in konqueror package in Ubuntu:
  Fix Released
Status in kontact package in Ubuntu:
  Fix Released
Status in loupe package in Ubuntu:
  Fix Released
Status in marble package in Ubuntu:
  Fix Released
Status in notepadqq package in Ubuntu:
  Fix Released
Status in opam package in Ubuntu:
  Fix Released
Status in pageedit package in Ubuntu:
  Fix Released
Status in plasma-desktop package in Ubuntu:
  Fix Released
Status in plasma-welcome package in Ubuntu:
  Fix Released
Status in privacybrowser package in Ubuntu:
  Invalid
Status in qmapshack package in Ubuntu:
  Fix Released
Status in qutebrowser package in Ubuntu:
  Fix Released
Status in rssguard package in Ubuntu:
  Fix Released
Status in steam package in Ubuntu:
  Fix Released
Status in supercollider package in Ubuntu:
  Fix Released
Status in tellico package in Ubuntu:
  Fix Released
Status in wike package in Ubuntu:
  Fix Committed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2046844/+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 2062950] [NEW] RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[J K]

Public bug reported:

this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504

I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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

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


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

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

Title:
  RE: Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in xorg package in Ubuntu:
  New

Bug description:
  this is a continuation of the bug reported in
  https://bugs.launchpad.net/ubuntu/+bug/2062504

  I reinstalled ubuntu 23, and didn't install anything else. I'm still
  having the flickering when connecting an HDMI to an external monitor.
  please help

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 22:27:21 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
  InstallationDate: Installed on 2024-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
  

[Desktop-packages] [Bug 2062504] [NEW] Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[J K]

Public bug reported:

I just installed ubuntu 23.10 on my thinkpad L13. It works fine on my
laptop monitor. But when I connect an HDMI cable to my other monitor,
then the screen flickers on the laptop and nothing shows on the other
monitor

I know it can't be the problem with the other monitor as I bought it
brand new last week, and the cable works fine on this same laptop when I
run in windows, and it works fine on other laptops with windows/mac

I already installed the driver with `sudo apt install nvidia-driver-535
nvidia-dkms-535` and rebooted, but that didn't help. I then installed
driver 550 and I still have the flickering

This laptop uses an intel Alder Lake-UP3 GT2

I also tried editing `etc/default/grub` by adding 'nomodeset' or
'radeon.modeset=0' within the quotation marks in the line
GRUB_CMDLINE_LINUX_DEFAULT but that didn't help either

can anyone help?

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 18 23:17:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/550.54.14, 6.5.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-13 (6 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=bc80dc13-87d7-4310-bd10-43d45de6d3a7 ro quiet splash radeon.modeset=0 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120+git2404140851.1179ed~oibaf~m
version.libgl1-mesa-dri: libgl1-mesa-dri 24.1~git2404150600.4a1904~oibaf~m
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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

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


** Tags: amd64 apport-bug mantic third-party-packages ubuntu wayland-session

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

Title:
  Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I just installed ubuntu 23.10 on my thinkpad L13. It works fine on my
  laptop monitor. But when I connect an HDMI cable to my other monitor,
  then the screen flickers on the laptop and nothing shows on the other
  monitor

  I know it can't be the problem with the other monitor as I bought it
  brand new last week, and the cable works fine on this same laptop when
  I run in windows, and it works fine on other laptops with windows/mac

  I already installed the driver with `sudo apt install nvidia-
  driver-535 nvidia-dkms-535` and rebooted, but that didn't help. I then
  installed driver 550 and I still have the flickering

  This laptop uses an intel Alder Lake-UP3 GT2

  I also tried editing `etc/default/grub` by adding 'nomodeset' or
  'radeon.modeset=0' within the quotation marks in the line
  GRUB_CMDLINE_LINUX_DEFAULT but that didn't help either

  can anyone help?

  ProblemType: Bug
  DistroRelease: Ubuntu 

[Desktop-packages] [Bug 2033222] Re: Ubuntu Software Center installs Wesnoth with only the tutorial campaign

[P. J. McDermott]

Fixing by moving the wesnoth executable (with its desktop entry and
AppStream component metainfo) from the wesnoth-1.16-core binary package
to wesnoth-1.16 and changing wesnoth-1.16's hard dependencies on
campaign packages into recommendations, as discussed last month on the
debian-devel-games mailing list.

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

** Changed in: wesnoth-1.16 (Ubuntu)
   Status: Triaged => In Progress

** Changed in: wesnoth-1.16 (Ubuntu)
 Assignee: (unassigned) => P. J. McDermott (pehjota)

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

Title:
  Ubuntu Software Center installs Wesnoth with only the tutorial
  campaign

Status in wesnoth-1.16 package in Ubuntu:
  In Progress

Bug description:
  When installed via the Ubuntu Software Center, only the tutorial
  campaign is available rather than all campaigns being available. By
  default, Ubuntu should be installing all the campaigns so that Wesnoth
  does not appear to be a mostly empty, incomplete game.

  I tested this on Ubuntu 23.04, but has also been reported previously
  on Ubuntu 22.04 (https://forums.wesnoth.org/viewtopic.php?t=56927) as
  well as Ubuntu 20.04
  
(https://www.reddit.com/r/wesnoth/comments/kykq6l/error_no_campaigns_available_on_ubuntu/).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wesnoth-1.16/+bug/2033222/+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 1972820] Re: LibreOffice crash when entering data in MySQL database

[J-Paul BERARD]

LO 7.6.2.1 with Ubuntu 23.10 (not a fresh install).
I rename my LO profile.
And the problem is the same.
So, I will continue to use the JDBC connection which works.
Thanks.

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

Title:
  LibreOffice crash when entering data in MySQL database

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

Bug description:
  When I try to enter a new record in a MySQL table in LO Base, the new record 
is accepted but Base close suddenly when I close the table.
  MySQL database is connected by the direct connector (embedded).
  Same kind of problem with LO 6.4

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:29:06 2022
  InstallationDate: Installed on 2020-04-10 (759 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1972820/+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 2045477] [NEW] Canon MF731 will not print

[j gleacher]

Public bug reported:

Printer works fine on other computers and worked on this one until I
reimaged it with new harddrive. Computer reports that printing is
successful, but nothing prints.

ping 192.168.1.19
PING 192.168.1.19 (192.168.1.19) 56(84) bytes of data.
64 bytes from 192.168.1.19: icmp_seq=1 ttl=64 time=100 ms

nmap 192.168.1.19
Starting Nmap 7.80 ( https://nmap.org ) at 2023-12-02 14:56 EST
Nmap scan report for 192.168.1.19
Host is up (0.049s latency).
Not shown: 995 closed ports
PORT STATE SERVICE
80/tcp   open  http
443/tcp  open  https
515/tcp  open  printer
631/tcp  open  ipp
9100/tcp open  jetdirect

/usr/lib/cups/backend/snmp
network socket://192.168.1.19 "Canon MF731C/733C UFR II" "Canon MF731C/733C" 
"MFG:Canon;MDL:MF731C/733C UFR II;CLS:PRINTER;DES:Canon MF731C/733C UFR 
II;CID:CA_XPS_OIP;CMD:LIPSLX,CPCA;PESP:V1;" ""

sudo /usr/lib/cups/backend/dnssd
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Querying "Canon\032MF731C\047733C._ipp._tcp.local"...
DEBUG: Querying "Canon\032MF731C\047733C._pdl-datastream._tcp.local"...
DEBUG: Querying "Canon\032MF731C\047733C._printer._tcp.local"...
DEBUG: sent=0, count=3
DEBUG2: query_callback(browser=0x5559d2370ef0, interfaceIndex=3, protocol=0, 
event=0, fullName="Canon\032MF731C\047733C._ipp._tcp.local", rrclass=1, 
rrtype=16, rdata=0x5559d237175c, rdlen=612, flags=5, context=0x5559d2370430)
DEBUG2: query_callback: "txtvers=1".
DEBUG2: query_callback: "rp=ipp/print".
DEBUG2: query_callback: "note=".
DEBUG2: query_callback: "qtotal=1".
DEBUG2: query_callback: "priority=10".
DEBUG2: query_callback: "ty=Canon MF731C/733C".
DEBUG2: query_callback: "product=(CNMF731C/733C)".
DEBUG2: query_callback: 
"pdl=application/octet-stream,image/urf,image/pwg-raster,image/jpeg,application/pdf".
DEBUG2: query_callback: "adminurl=http://Canone55576.local:80/airprint.html;.
DEBUG2: query_callback: "usb_MFG=Canon".
DEBUG2: query_callback: "usb_MDL=MF731C/733C".
DEBUG2: query_callback: "Transparent=F".
DEBUG2: query_callback: "Binary=F".
DEBUG2: query_callback: "TBCP=F".
DEBUG2: query_callback: "Color=T".
DEBUG2: query_callback: "Copies=T".
DEBUG2: query_callback: "Duplex=T".
DEBUG2: query_callback: "PaperCustom=T".
DEBUG2: query_callback: "Bind=F".
DEBUG2: query_callback: "Collate=F".
DEBUG2: query_callback: "Sort=F".
DEBUG2: query_callback: "Staple=F".
DEBUG2: query_callback: "Punch=0".
DEBUG2: query_callback: "PaperMax=legal-A4".
DEBUG2: query_callback: "UUID=6d4ff0ce-6b11-11d8-8020-f80d60e55576".
DEBUG2: query_callback: "usb_CMD=LIPSLX,CPCA".
DEBUG2: query_callback: "TLS=1.2".
DEBUG2: query_callback: "Scan=T".
DEBUG2: query_callback: "Fax=F".
DEBUG2: query_callback: 
"URF=ADOBERGB24,CP255,DM1,PQ4,RS300,SRGB24,W8-16,FN3,IS1-4,OB10-40,V1.4".
DEBUG2: query_callback: "kind=document,envelope,postcard".
DEBUG2: query_callback: "print_wfds=T".
DEBUG2: query_callback: "mopria-certified=1.2".
DEBUG2: query_callback(browser=0x5559d2370ef0, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF731C\047733C._ipp._tcp.local", rrclass=1, 
rrtype=16, rdata=0x5559d237175c, rdlen=612, flags=5, context=0x5559d2370430)
DEBUG2: query_callback: "txtvers=1".
DEBUG2: query_callback: "rp=ipp/print".
DEBUG2: query_callback: "note=".
DEBUG2: query_callback: "qtotal=1".
DEBUG2: query_callback: "priority=10".
DEBUG2: query_callback: "ty=Canon MF731C/733C".
DEBUG2: query_callback: "product=(CNMF731C/733C)".
DEBUG2: query_callback: 
"pdl=application/octet-stream,image/urf,image/pwg-raster,image/jpeg,application/pdf".
DEBUG2: query_callback: "adminurl=http://Canone55576.local:80/airprint.html;.
DEBUG2: query_callback: "usb_MFG=Canon".
DEBUG2: query_callback: "usb_MDL=MF731C/733C".
DEBUG2: query_callback: "Transparent=F".
DEBUG2: query_callback: "Binary=F".
DEBUG2: query_callback: "TBCP=F".
DEBUG2: query_callback: "Color=T".
DEBUG2: query_callback: "Copies=T".
DEBUG2: query_callback: "Duplex=T".
DEBUG2: query_callback: "PaperCustom=T".
DEBUG2: query_callback: "Bind=F".
DEBUG2: query_callback: "Collate=F".
DEBUG2: query_callback: "Sort=F".
DEBUG2: query_callback: "Staple=F".
DEBUG2: query_callback: "Punch=0".
DEBUG2: query_callback: "PaperMax=legal-A4".
DEBUG2: query_callback: 

[Desktop-packages] [Bug 2043119] Re: screen color calibration : no start button

[J-Paul BERARD]

** Description changed:

  I try to calibrate my screen using the utility of gnome-control-center, color 
section.
  I have a Spyder3 Express probe connected by USB and the Calibrate… button 
become active.
  So I click this button and the process begin with a dialog box giving several 
informations until it ask for the name of the further colour profile.
  
  After that, a small window appears asking to put the probe on this
  window and to press "Start"… but there is no Start button.
  
  I tried the same on Ubuntu 22.04 (on a VM) : the same window occupied
  all the screen and we can see a Start button at the bottom right and a
- Cancel one on the button left.
+ Cancel one on the bottom left.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 15:58:51 2023
  InstallationDate: Installed on 2020-04-10 (1308 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (27 days ago)

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

Title:
  screen color calibration : no start button

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

Bug description:
  I try to calibrate my screen using the utility of gnome-control-center, color 
section.
  I have a Spyder3 Express probe connected by USB and the Calibrate… button 
become active.
  So I click this button and the process begin with a dialog box giving several 
informations until it ask for the name of the further colour profile.

  After that, a small window appears asking to put the probe on this
  window and to press "Start"… but there is no Start button.

  I tried the same on Ubuntu 22.04 (on a VM) : the same window occupied
  all the screen and we can see a Start button at the bottom right and a
  Cancel one on the bottom left.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 15:58:51 2023
  InstallationDate: Installed on 2020-04-10 (1308 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043119/+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 1729433] Re: LibreOffice doesn't remember window size when running under Wayland

[J-Paul BERARD]

With LO 7.6.2.1 and Ubuntu 23.10 (main UI) Wayland :
I create a Writer file with a medium window. I maximize the window and quit LO.
I open again the same file : the window is maximized. When I un-maximize the 
window, it doesn't come back to the medium previous size but to a more 
maximized size ! I mean, the size of the window increases again going behind 
the dock.
If I maximize again and un-maximize a second time, the window comes back to a 
medium size but not the same that the initial one.
But not the very small window we saw before.

Thanks

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

Title:
  LibreOffice doesn't remember window size when running under Wayland

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice package in Fedora:
  Confirmed

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 2043119] [NEW] screen color calibration : no start button

[J-Paul BERARD]

Public bug reported:

I try to calibrate my screen using the utility of gnome-control-center, color 
section.
I have a Spyder3 Express probe connected by USB and the Calibrate… button 
become active.
So I click this button and the process begin with a dialog box giving several 
informations until it ask for the name of the further colour profile.

After that, a small window appears asking to put the probe on this
window and to press "Start"… but there is no Start button.

I tried the same on Ubuntu 22.04 (on a VM) : the same window occupied
all the screen and we can see a Start button at the bottom right and a
Cancel one on the button left.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-control-center 1:45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 15:58:51 2023
InstallationDate: Installed on 2020-04-10 (1308 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to mantic on 2023-10-13 (27 days ago)

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


** Tags: amd64 apport-bug mantic wayland-session

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

Title:
  screen color calibration : no start button

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

Bug description:
  I try to calibrate my screen using the utility of gnome-control-center, color 
section.
  I have a Spyder3 Express probe connected by USB and the Calibrate… button 
become active.
  So I click this button and the process begin with a dialog box giving several 
informations until it ask for the name of the further colour profile.

  After that, a small window appears asking to put the probe on this
  window and to press "Start"… but there is no Start button.

  I tried the same on Ubuntu 22.04 (on a VM) : the same window occupied
  all the screen and we can see a Start button at the bottom right and a
  Cancel one on the button left.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-control-center 1:45.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 15:58:51 2023
  InstallationDate: Installed on 2020-04-10 (1308 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043119/+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 2041008] Re: wayland : no uppercase accented characters with capslock

[J-Paul BERARD]

Additional information:

This issue depends on the application used ! You get it with Gnome-text-
editor or LO Writer but not in Firefox Web browser (snap). Because the
good libraries are embedded with the snap ?

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

Title:
  wayland : no uppercase accented characters with capslock

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  Until Ubuntu 23.04, with the "french alternative" [français (variante)] 
keyboard, capslock gave you directly uppercase accented characters (like É È À) 
from the keys 2, 7 and 0 of the fifth row of the keyboard.
  With 23.10 Mantic, it has disappeared with Wayland (you get é, è, à) BUT it 
works like before if you connect with Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 13:36:26 2023
  DistUpgraded: 2023-10-13 14:46:58,342 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 
6850] [174b:174b]
  InstallationDate: Installed on 2020-04-10 (1294 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=042824eb-95be-471e-bdb4-d7adf594a94a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (13 days ago)
  dmi.bios.date: 08/05/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: 970 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/wayland/+bug/2041008/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode

[Michael J Brancato]

How did you get the FCC Unlock to enable the modem?

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

Title:
  Fibcom FM350-GL not able connect to network with 5G mode

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  Fibcom FM350-GL can support 5G network
  (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu
  22.04, system can only connect to mobile network with 4G mode.


General  | path: /org/freedesktop/ModemManager1/Modem/0
 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e

Hardware | manufacturer: generic
 |model: MBIM [14C3:4D75]
 |firmware revision: 81600..00.29.18.01_GC
 |   C01
 | h/w revision: V1.0.6
 |supported: gsm-umts, lte
 |  current: gsm-umts, lte
 | equipment id: 352750140002001

System   |   device: 
/sys/devices/pci:00/:00:1c.0/:73:00.0
 |  drivers: mtk_t7xx
 |   plugin: generic
 | primary port: wwan0mbim0
 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 
(mbim)

Status   |   unlock retries: sim-pin (3), sim-pin2 (3)
 |state: connected
 |  power state: on
 |  access tech: lte
 |   signal quality: 74% (recent)

Modes|supported: allowed: 3g, 4g; preferred: none
 |  current: allowed: 3g, 4g; preferred: none

IP   |supported: ipv4, ipv6, ipv4v6

3GPP | imei: 352750140002001
 |enabled locks: sim, fixed-dialing
 |  operator id: 46692
 |operator name: Chunghwa Telecom
 | registration: home

3GPP EPS | ue mode of operation: csps-2
 |  initial bearer path: /org/freedesktop/ModemManager1/Bearer/0

SIM  | primary sim path: /org/freedesktop/ModemManager1/SIM/0

Bearer   |paths: /org/freedesktop/ModemManager1/Bearer/1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-06-15 (26 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: modemmanager 1.18.6-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9
  Tags:  jammy
  Uname: Linux 5.17.0-9012-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1981190/+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 2041008] [NEW] wayland : no uppercase accented characters with capslock

[J-Paul BERARD]

Public bug reported:

Until Ubuntu 23.04, with the "french alternative" [français (variante)] 
keyboard, capslock gave you directly uppercase accented characters (like É È À) 
from the keys 2, 7 and 0 of the fifth row of the keyboard.
With 23.10 Mantic, it has disappeared with Wayland (you get é, è, à) BUT it 
works like before if you connect with Xorg.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 13:36:26 2023
DistUpgraded: 2023-10-13 14:46:58,342 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
 virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] 
(prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 
6850] [174b:174b]
InstallationDate: Installed on 2020-04-10 (1294 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=042824eb-95be-471e-bdb4-d7adf594a94a ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (13 days ago)
dmi.bios.date: 08/05/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.80
dmi.board.name: 970 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
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

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


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

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

Title:
  wayland : no uppercase accented characters with capslock

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Until Ubuntu 23.04, with the "french alternative" [français (variante)] 
keyboard, capslock gave you directly uppercase accented characters (like É È À) 
from the keys 2, 7 and 0 of the fifth row of the keyboard.
  With 23.10 Mantic, it has disappeared with Wayland (you get é, è, à) BUT it 
works like before if you connect with Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 13:36:26 2023
  DistUpgraded: 2023-10-13 14:46:58,342 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 
6850] [174b:174b]
  InstallationDate: Installed on 2020-04-10 (1294 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta 

[Desktop-packages] [Bug 2039801] Re: Locate pointer not working when animations are disabled

[J Chapman]

Thanks Daniel, 
Should I start a new thread regarding the 'show pointer' in the screencast 
function that is launched via ctrl+shift+alt+r or prntSc?

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

Title:
  Locate pointer not working when animations are disabled

Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039801] Re: Ubuntu 23.10, locate pointer not working

[J Chapman]

Solved, not sure if a bug still exists but the animation for the 'locate 
pointer' issue is due to the Accessibility->seeing->reduced animation setting 
being turned on. 
The 'show pointer' feature in screencast still does not turn on however I can 
now press the left cntrl key to highlight the whereabouts of the pointer. 
I am not sure if this should be closed as a bug or redirected to reflect the 
continuing issue with the screen capture 'show pointer' 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/2039801

Title:
  Ubuntu 23.10, locate pointer not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039801] monitors.xml.txt

[J Chapman]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/2039801/+attachment/5711674/+files/monitors.xml.txt

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

Title:
  Ubuntu 23.10, locate pointer not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039801] ShellJournal.txt

[J Chapman]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/2039801/+attachment/5711673/+files/ShellJournal.txt

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

Title:
  Ubuntu 23.10, locate pointer not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039801] ProcEnviron.txt

[J Chapman]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2039801/+attachment/5711672/+files/ProcEnviron.txt

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

Title:
  Ubuntu 23.10, locate pointer not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039801] ProcCpuinfoMinimal.txt

[J Chapman]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2039801/+attachment/5711671/+files/ProcCpuinfoMinimal.txt

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

Title:
  Ubuntu 23.10, locate pointer not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039801] GsettingsChanges.txt

[J Chapman]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/2039801/+attachment/5711670/+files/GsettingsChanges.txt

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

Title:
  Ubuntu 23.10, locate pointer not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039801] Re: Ubuntu 23.10, locate pointer not working

[J Chapman]

apport information

** Tags added: apport-collected

** Description changed:

  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.
  
- Expect the mouse pointer to be highlighted instead only the cursor
- position is located.
+ Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2019-10-17 (1464 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 45.0-1ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
+ RelatedPackageVersions: mutter-common 45.0-3ubuntu3
+ Tags: mantic
+ Uname: Linux 6.5.0-9-generic x86_64
+ UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
+ UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2039801/+attachment/5711669/+files/Dependencies.txt

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

Title:
  Ubuntu 23.10, locate pointer not working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039801/+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 2039801] Re: Ubuntu 23.10, locate pointer not working

[J Chapman]

Had to add package, I am not certain but it is most likely to be gnome
shell problem.

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

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

Title:
  Ubuntu 23.10, locate pointer not working

Status in gnome-desktop package in Ubuntu:
  New

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor
  position is located.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2039801/+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 995406] Re: User not added to group sambashare: "You do not have permission to create a usershare."

[J-Paul BERARD]

Hello,
This issue appears again in Mantic (fresh install).
And in Mantic, nautilus-share is not installed by default. So you must add it 
manually.

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

Title:
  User not added to group sambashare:  "You do not have permission to
  create a usershare."

Status in nautilus-share package in Ubuntu:
  Confirmed

Bug description:
  I tried to share a folder and was prompted to install samba, which I 
accepted. I did not install pam-smbpass as I don't need it. I was prompted to 
log out and in again, which I did. Now I get this when creating a share:
  ---
  'net usershare' returned error 255: net usershare: cannot open usershare 
directory /var/lib/samba/usershares. Error Permission denied
  You do not have permission to create a usershare. Ask your administrator to 
grant you permissions to create a share.
  ---
  It looks like the user was not added to the group sambashare at all (which 
script is supposed to do this? Where is the log file?).

  Manually running
  # sudo usermod -a -G sambashare jakob
  fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus-share 0.7.3-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Sun May  6 11:37:08 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
  SourcePackage: nautilus-share
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/995406/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

[Daniel J Blueman]

Thanks for the updates Nathan.

As previously stated, running the unconfined binary
/snap/chromium/current/usr/lib/chromium-browser/chrome or
/snap/firefox/current/usr/lib/firefox/firefox prevents the GPU hang, ie
using the system MESA library. Also disabling GPU acceleration via MESA
environment variables confirms the hang is indeed related to GPU command
queue submission from the MESA library.

The GPU hang still occurs after "snap refresh --candidate gnome-42-2204"
and rebooting to clear possible state, however I see
/snap/chromium/2623/usr/lib/chromium-browser/libGLESv2.so, therefore
surely the chromium snap needs the updated MESA library?

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in Mesa:
  New
Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  When opening a SketchUp model (example:
  
https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_)
  in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes
  for ~4 seconds, and we see a blank page. The logs show the GPU hang
  and browser rendering context failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2035360/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

[Daniel J Blueman]

** Description changed:

- When opening a SketchUp model (example) in Firefox or Chromium, after ~5
- seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank
- page. The logs show the GPU hang and browser rendering context failed to
- initialise.
+ When opening a SketchUp model (example:
+ 
https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_)
+ in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes for
+ ~4 seconds, and we see a blank page. The logs show the GPU hang and
+ browser rendering context failed to initialise.
  
  This has 100% reproducibility on my 12-gen GPU.
  
  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment
  
  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt
  
  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in Mesa:
  Unknown
Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  When opening a SketchUp model (example:
  
https://app.sketchup.com/share/tc/europe/9jWfPS5lgN8?stoken=KYi8KrAR6g3gv6OqLAKNEEMrQHLOA7jd8oV20HmBbHrZqyPRPmG1QlPurYkJnuw_)
  in Firefox or Chromium, after ~5 seconds, the SketchUp logo freezes
  for ~4 seconds, and we see a blank page. The logs show the GPU hang
  and browser rendering context failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2035360/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

[Daniel J Blueman]

My original MESA bug report (now closed) is at:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9695

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When opening a SketchUp model (example) in Firefox or Chromium, after
  ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a
  blank page. The logs show the GPU hang and browser rendering context
  failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035360/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

[Daniel J Blueman]

In order to test if the system MESA has the fix while the Chromium snaps
does not, I unpacked it and ran the Chromium binary against system
libraries.

The GPU hang doesn't reproduce, suggesting the MESA libraries included
in the Snaps is outdated and should be updated to eg
23.0.4-0ubuntu1~23.04.1.

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9695
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/9695

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When opening a SketchUp model (example) in Firefox or Chromium, after
  ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a
  blank page. The logs show the GPU hang and browser rendering context
  failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035360/+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 2035360] Re: GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

[Daniel J Blueman]

System:
  Host: spectre Kernel: 6.2.0-32-generic arch: x86_64 bits: 64
compiler: N/A Desktop: GNOME v: 44.3 tk: GTK v: 3.24.37 wm: gnome-shell
dm: GDM3 Distro: Ubuntu 23.04 (Lunar Lobster)
CPU:
  Info: 9-core model: 12th Gen Intel Core i7-1260P bits: 64 type: MCP
smt: disabled arch: Alder Lake rev: 3 cache: L1: 848 KiB L2: 5.2 MiB
L3: 18 MiB
  Speed (MHz): avg: 2303 high: 2500 min/max: 400/4700:3400 cores: 1: 2500
2: 2500 3: 2500 4: 2500 5: 729 6: 2500 7: 2500 8: 2500 9: 2500
bogomips: 44928
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Alder Lake-P Integrated Graphics vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-12.2 ports: active: eDP-1 empty: DP-1,
DP-2, DP-3, DP-4, DP-5 bus-ID: 00:02.0 chip-ID: 8086:46a6
  Device-2: Intel DG2 [Arc A370M] vendor: Hewlett-Packard driver: vfio-pci
v: N/A arch: Gen-12.7 pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0
chip-ID: 8086:5693
  Display: wayland server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.8
compositor: gnome-shell driver: X: loaded: N/A
unloaded: fbdev,modesetting,vesa gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: Samsung 0x4174 res: 3840x2400 dpi: 284
diag: 406mm (16")
  API: OpenGL v: 4.6 Mesa 23.0.4-0ubuntu1~23.04.1 renderer: Mesa Intel
Graphics (ADL GT2) direct-render: Yes

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When opening a SketchUp model (example) in Firefox or Chromium, after
  ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a
  blank page. The logs show the GPU hang and browser rendering context
  failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035360/+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 2035360] [NEW] GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

[Daniel J Blueman]

Public bug reported:

When opening a SketchUp model (example) in Firefox or Chromium, after ~5
seconds, the SketchUp logo freezes for ~4 seconds, and we see a blank
page. The logs show the GPU hang and browser rendering context failed to
initialise.

This has 100% reproducibility on my 12-gen GPU.

On this system with Ubuntu 23.04, I have always seen a GPU hang with the stock 
Ubuntu kernel or mainline.
Log files as attachment

- the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
- the output of 'dmesg' with kernel boot args 'drm.debug=0x1e log_buf_len=16M' 
is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
- the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

Since I was able to cause failure uncontained to the rendering process
when performing this 5-8 times, there is an argument that this is a
security (DoS) issue, though I'll let someone else make a judgement.

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

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

Title:
  GPU hangs in SketchUp on Intel gen12 due to outdated MESA library

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When opening a SketchUp model (example) in Firefox or Chromium, after
  ~5 seconds, the SketchUp logo freezes for ~4 seconds, and we see a
  blank page. The logs show the GPU hang and browser rendering context
  failed to initialise.

  This has 100% reproducibility on my 12-gen GPU.

  On this system with Ubuntu 23.04, I have always seen a GPU hang with the 
stock Ubuntu kernel or mainline.
  Log files as attachment

  - the output of 'dmesg' is at https://quora.org/OJnlVgn4xZ/dmesg.txt
  - the output of 'dmesg' with kernel boot args 'drm.debug=0x1e 
log_buf_len=16M' is at https://quora.org/OJnlVgn4xZ/dmesg-debug.txt
  - the output of /sys/class/drm/card0/error is at 
https://quora.org/OJnlVgn4xZ/i915-error.txt

  Since I was able to cause failure uncontained to the rendering process
  when performing this 5-8 times, there is an argument that this is a
  security (DoS) issue, though I'll let someone else make a judgement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035360/+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 1972820] Re: LibreOffice crash when entering data in MySQL database

[J-Paul BERARD]

So, this answer is really interesting and not well documented yet.

With my LO version 7.5, when you create a new LO Base file and choose a direct 
connection to MySQL/MariaDB, the next dialog box offer "Using MariaDB C 
Connector" : so already, we understand it's more for MariaDB.
But it's not clearly written anywhere ! Even, in the webpage you report 
https://books.libreoffice.org/en/BG73/BG7302-CreatingADatabase.html#toc9 the 
direct connection to MySQL looks possible !
I will update the french documentation of Ubuntu about this issue. The 
Libreoffice documentation should be updated as well (by a good english writer 
!).
Thanks

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

Title:
  LibreOffice crash when entering data in MySQL database

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

Bug description:
  When I try to enter a new record in a MySQL table in LO Base, the new record 
is accepted but Base close suddenly when I close the table.
  MySQL database is connected by the direct connector (embedded).
  Same kind of problem with LO 6.4

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:29:06 2022
  InstallationDate: Installed on 2020-04-10 (759 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1972820/+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 1943752] Re: cheese does not work with laptop webcam in Ubuntu 21.10+

[Fred J]

Hi,
I have tried much of that... Bios updated too.
There is no /dev/video0 says v4l2
Can you confirm you managed to make camera work on HP Elite Dragonfly 13.5 inch 
G3 Notebook PC (4J044AV) ?
They say here (https://www.linuxnow.com.au) that they can ship it with ubuntu 
installed...

Best,
-Fred

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

Title:
  cheese does not work with laptop webcam in Ubuntu 21.10+

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 from live usb on a HP 840 G3 laptop
  1.Ubuntu Impish Indri (development branch)
  2.cheese version installed: 3.38.0-4, candidate: 3.38.0-4
  version table:***3.38.0-4 500
  3.cheese should display an image from laptop camera after being opened.
  4.The error has reproduced by me on this hardware at least 4 times.
  When opening the cheese app no image is displayed until closing and reopening 
the app at least 3 times. The cheese app works as expected in both Ubuntu 18.04 
and Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-4
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 15 17:10:23 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915)
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.38.0-4
   cheese-common 3.38.0-4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: 2FZ00UP#ABA
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 002: ID 154b:0054 PNY USB 2.0 FD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 5074 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-14-generic N/A
   linux-backports-modules-5.13.0-14-generic  N/A
   linux-firmware 1.199
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  impish
  Uname: Linux 5.13.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP 

[Desktop-packages] [Bug 1943752] Re: cheese does not work with laptop webcam in Ubuntu 21.10+

[Fred J]

Hi,
Didn't work for me, elite dragonfly g3 4J044AV
Tried other distro and cam didn't work either.
Stuck with pc without webcam.
--F

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

Title:
  cheese does not work with laptop webcam in Ubuntu 21.10+

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 from live usb on a HP 840 G3 laptop
  1.Ubuntu Impish Indri (development branch)
  2.cheese version installed: 3.38.0-4, candidate: 3.38.0-4
  version table:***3.38.0-4 500
  3.cheese should display an image from laptop camera after being opened.
  4.The error has reproduced by me on this hardware at least 4 times.
  When opening the cheese app no image is displayed until closing and reopening 
the app at least 3 times. The cheese app works as expected in both Ubuntu 18.04 
and Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-4
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 15 17:10:23 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915)
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.38.0-4
   cheese-common 3.38.0-4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: 2FZ00UP#ABA
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 002: ID 154b:0054 PNY USB 2.0 FD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 5074 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-14-generic N/A
   linux-backports-modules-5.13.0-14-generic  N/A
   linux-firmware 1.199
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  impish
  Uname: Linux 5.13.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: 2FZ00UP#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1943752] Re: cheese does not work with laptop webcam in Ubuntu 21.10+

[Fred J]

Dear Warren,
I just bought a HP Elite Dragonfly G3 and I of course ran into this problem 
with cam. I have tried to install webcamoid but it didn't work!
Ubuntu 22.10
Did I miss something? 
Best
--Fred

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

Title:
  cheese does not work with laptop webcam in Ubuntu 21.10+

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10 from live usb on a HP 840 G3 laptop
  1.Ubuntu Impish Indri (development branch)
  2.cheese version installed: 3.38.0-4, candidate: 3.38.0-4
  version table:***3.38.0-4 500
  3.cheese should display an image from laptop camera after being opened.
  4.The error has reproduced by me on this hardware at least 4 times.
  When opening the cheese app no image is displayed until closing and reopening 
the app at least 3 times. The cheese app works as expected in both Ubuntu 18.04 
and Ubuntu 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: cheese 3.38.0-4
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 15 17:10:23 2021
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915)
  MachineType: HP HP EliteBook 840 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.38.0-4
   cheese-common 3.38.0-4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: 2FZ00UP#ABA
  dmi.sys.vendor: HP
  lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 002: ID 154b:0054 PNY USB 2.0 FD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 5074 F pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915)
  Lsusb:
   Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera
   Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint 
Reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-14-generic N/A
   linux-backports-modules-5.13.0-14-generic  N/A
   linux-firmware 1.199
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  impish
  Uname: Linux 5.13.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.52
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.52
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: 2FZ00UP#ABA
  dmi.sys.vendor: 

[Desktop-packages] [Bug 2016183] [NEW] Ubuntu 22.10 nautilus serch sits and spins

[J Chapman]

Public bug reported:

ubuntu 22.10, Nautilus search not working, when opening a directory the files 
and folders display instantaneously as expected, as normal I start typing the 
name of the file/folder I am interested in. 
If I type in only one letter the search seems to work instantly, but if I type 
in the second letter of the search string the search just sits and spins. I 
have experimented with it and if I leave it for some time (multiples of 
minutes) it will eventually find what I have searched for.

I notice several complaints online for this exact problem and it seems
that nobody has a solution for it.

I have a couple of screen recordings to show the problem.

Ubuntu 22.10
About files -> 'Files, The Gnome Project - 43.0' (nautilus)

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

** Attachment added: "Screen recording of the problem."
   
https://bugs.launchpad.net/bugs/2016183/+attachment/5663731/+files/Screencast%20from%202023-04-13%2023-09-41.webm

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

Title:
  Ubuntu 22.10 nautilus serch sits and spins

Status in nautilus package in Ubuntu:
  New

Bug description:
  ubuntu 22.10, Nautilus search not working, when opening a directory the files 
and folders display instantaneously as expected, as normal I start typing the 
name of the file/folder I am interested in. 
  If I type in only one letter the search seems to work instantly, but if I 
type in the second letter of the search string the search just sits and spins. 
I have experimented with it and if I leave it for some time (multiples of 
minutes) it will eventually find what I have searched for.

  I notice several complaints online for this exact problem and it seems
  that nobody has a solution for it.

  I have a couple of screen recordings to show the problem.

  Ubuntu 22.10
  About files -> 'Files, The Gnome Project - 43.0' (nautilus)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2016183/+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 2012534] [NEW] JS ERROR: Error capturing screenshot

[J-P Nurmi]

Public bug reported:

Steps to reproduce:
- run daily-live 20230322
- right click a window title bar and select "take screenshot" or hit 
Alt+PrintScreen
- observe journal

The screenshot does appear on the disk but there's no notification which
might be related.


```
Mar 22 16:34:21 ubuntu gnome-shell[1752]: JS ERROR: Error capturing screenshot: 
Error: Unable to construct struct type BookmarkFile since it has no default 
constructor and cannot be allocated directly
  
saveRecentFile@resource:///org/gnome/shell/ui/screenshot.js:2079:27
  
_storeScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2139:23
  
captureScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2231:21
  
async*_buildMenu/item<@resource:///org/gnome/shell/ui/windowMenu.js:35:34
  
addAction/<@resource:///org/gnome/shell/ui/popupMenu.js:559:21
  
activate@resource:///org/gnome/shell/ui/popupMenu.js:197:14
  
vfunc_button_release_event@resource:///org/gnome/shell/ui/popupMenu.js:141:14
```

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.480
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 22 16:34:42 2023
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'disabled-extensions' b'@as []'
 b'org.gnome.shell' b'enabled-extensions' b"['d...@rastersoft.com']"
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'44.0'"
 b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230322)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug lunar

** Description changed:

  Steps to reproduce:
  - run daily-live 20230322
  - right click a window title bar and select "take screenshot" or hit 
Alt+PrintScreen
- - notice missing notification
  - observe journal
+ 
+ The screenshot does appear on the disk but there's no notification which
+ might be related.
+ 
  
  ```
  Mar 22 16:34:21 ubuntu gnome-shell[1752]: JS ERROR: Error capturing 
screenshot: Error: Unable to construct struct type BookmarkFile since it has no 
default constructor and cannot be allocated directly
-   
saveRecentFile@resource:///org/gnome/shell/ui/screenshot.js:2079:27
-   
_storeScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2139:23
-   
captureScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2231:21
-   
async*_buildMenu/item<@resource:///org/gnome/shell/ui/windowMenu.js:35:34
-   
addAction/<@resource:///org/gnome/shell/ui/popupMenu.js:559:21
-   
activate@resource:///org/gnome/shell/ui/popupMenu.js:197:14
-   
vfunc_button_release_event@resource:///org/gnome/shell/ui/popupMenu.js:141:14
+   
saveRecentFile@resource:///org/gnome/shell/ui/screenshot.js:2079:27
+   
_storeScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2139:23
+   
captureScreenshot@resource:///org/gnome/shell/ui/screenshot.js:2231:21
+   
async*_buildMenu/item<@resource:///org/gnome/shell/ui/windowMenu.js:35:34
+   
addAction/<@resource:///org/gnome/shell/ui/popupMenu.js:559:21
+   
activate@resource:///org/gnome/shell/ui/popupMenu.js:197:14
+   
vfunc_button_release_event@resource:///org/gnome/shell/ui/popupMenu.js:141:14
  ```
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 

[Desktop-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

[J Chapman]

Same here Acer Aspire black edition running 22.10, the search facility in 
nautilus is extremely slow particularly when you enter the second symbol/letter 
of the search string. 
sometime it works as it should but most of the time it just sits and spins for 
a few minutes.
Any ideas what we can do to get it working?

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

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996652/+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 2009726] [NEW] Network Manager sets USB Ethernet to unmanaged in fresh Lunar

[Michał J . Gajda]

Public bug reported:

After installing a recent build of Lunar, the wired connection stopped
working.

It appears that default configuration in 
`/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf` sets all 
wired ethernet to _strictly unmanaged_, whereas USB ethernet should be strictly 
managed:
```
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma
```

Since unmanaged devices are never brought up, it seems that all
`ethernet` devices should be managed anyway.

Detailed description of the problem and solution:
https://jbit.net/NetworkManager_Strictly_Unmanaged/

Related to #279262

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: network-manager 1.40.12-1ubuntu1 [modified: 
usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf]
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  8 17:25:29 2023
InstallationDate: Installed on 2023-03-05 (3 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230301.1)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.40.12  connected  started  full  enabled enabled  
disabled  missing  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug fresh-install lunar wayland-session

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

Title:
  Network Manager sets USB Ethernet to unmanaged in fresh Lunar

Status in network-manager package in Ubuntu:
  New

Bug description:
  After installing a recent build of Lunar, the wired connection stopped
  working.

  It appears that default configuration in 
  `/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf` sets all 
wired ethernet to _strictly unmanaged_, whereas USB ethernet should be strictly 
managed:
  ```
  [keyfile]
  unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma
  ```

  Since unmanaged devices are never brought up, it seems that all
  `ethernet` devices should be managed anyway.

  Detailed description of the problem and solution:
  https://jbit.net/NetworkManager_Strictly_Unmanaged/

  Related to #279262

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: network-manager 1.40.12-1ubuntu1 [modified: 
usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf]
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  8 17:25:29 2023
  InstallationDate: Installed on 2023-03-05 (3 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230301.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.40.12  connected  started  full  enabled enabled  
disabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2009726/+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 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools

[Matthew J. Hill]

This is indeed a defect--marking it "wontfix" is not helpful.

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

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+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 1999083] Re: cannot rename multiple files

[Rebecca J.]

Turns out I wasn't running Nautilus, I was running Nemo. My mistake. I
installed Nautilus. Problem solved.

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

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

Title:
  cannot rename multiple files

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  If I highlight two or more files at once and either press F2 or right-
  click and choose "Rename..." from the popup menu, I expect to be able
  to rename those files in one action. Instead, nothing happens. There
  is absolutely no perceptible response from the system (well the pop-up
  menu does disappear, if I tried the right-click option).

  The bulk rename feature worked in the previous version of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  7 11:50:48 2022
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-24 (2143 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1999083/+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 1999083] [NEW] cannot rename multiple files

[Rebecca J.]

Public bug reported:

If I highlight two or more files at once and either press F2 or right-
click and choose "Rename..." from the popup menu, I expect to be able to
rename those files in one action. Instead, nothing happens. There is
absolutely no perceptible response from the system (well the pop-up menu
does disappear, if I tried the right-click option).

The bulk rename feature worked in the previous version of Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus (not installed)
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  7 11:50:48 2022
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-01-24 (2143 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  cannot rename multiple files

Status in nautilus package in Ubuntu:
  New

Bug description:
  If I highlight two or more files at once and either press F2 or right-
  click and choose "Rename..." from the popup menu, I expect to be able
  to rename those files in one action. Instead, nothing happens. There
  is absolutely no perceptible response from the system (well the pop-up
  menu does disappear, if I tried the right-click option).

  The bulk rename feature worked in the previous version of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: nautilus (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  7 11:50:48 2022
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-24 (2143 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1999083/+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 869516]

[J. Ryan Stinnett]

Switching to an editor in general would not be too hard here, but I've
learned there are many edge cases with view source and extra features I
wasn't originally aware of.  Also, we need to be sure of the perf, as in
comment 4.

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

Title:
  JavaScript & CSS syntax highlighting

Status in Mozilla Firefox:
  Confirmed
Status in SeaMonkey:
  Confirmed
Status in chromium package in Ubuntu:
  Invalid
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in seamonkey package in Ubuntu:
  Confirmed

Bug description:
  Add JavaScript & CSS syntax highlighting to source code viewer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/869516/+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 1989508] Re: hp-plugin unable to load plugin.conf

[Brian J. Murrell]

I finally did discover the workaround, after a while of (wasted time)
searching.

But how many other people are going to continue to have to waste time
researching how to "work-around" this issue when the solution is a
simple matter of just putting the missing file back on the web-server?

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

Title:
  hp-plugin unable to load plugin.conf

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Linux hp-plugin fails on Fedora 35 with the error:

  error: Plugin download failed with error code = 8
  error:  file does not match its checksum. File may have been corrupted or 
altered

  When running "hp-plugin -l debug" the reason turns out to be that
  http://hplip.sourceforge.net/plugin.conf does not exist:

  hp-plugin[540794]: debug: wget returned: 0
  hp-plugin[540794]: debug: --2022-09-13 23:23:02--  
http://hplip.sf.net/plugin.conf
  Resolving hplip.sf.net (hplip.sf.net)... 204.68.111.100
  Connecting to hplip.sf.net (hplip.sf.net)|204.68.111.100|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: http://hplip.sourceforge.net/plugin.conf [following]
  --2022-09-13 23:23:02--  http://hplip.sourceforge.net/plugin.conf
  Resolving hplip.sourceforge.net (hplip.sourceforge.net)... 204.68.111.100
  Reusing existing connection to hplip.sf.net:80.
  HTTP request sent, awaiting response... 404 Not Found
  2022-09-13 23:23:02 ERROR 404: Not Found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1989508/+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 1989508] Re: hp-plugin unable to load plugin.conf

[Brian J. Murrell]

https://bugs.launchpad.net/bugs/1991679 is a duplicate of this ticket.

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

Title:
  hp-plugin unable to load plugin.conf

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Linux hp-plugin fails on Fedora 35 with the error:

  error: Plugin download failed with error code = 8
  error:  file does not match its checksum. File may have been corrupted or 
altered

  When running "hp-plugin -l debug" the reason turns out to be that
  http://hplip.sourceforge.net/plugin.conf does not exist:

  hp-plugin[540794]: debug: wget returned: 0
  hp-plugin[540794]: debug: --2022-09-13 23:23:02--  
http://hplip.sf.net/plugin.conf
  Resolving hplip.sf.net (hplip.sf.net)... 204.68.111.100
  Connecting to hplip.sf.net (hplip.sf.net)|204.68.111.100|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: http://hplip.sourceforge.net/plugin.conf [following]
  --2022-09-13 23:23:02--  http://hplip.sourceforge.net/plugin.conf
  Resolving hplip.sourceforge.net (hplip.sourceforge.net)... 204.68.111.100
  Reusing existing connection to hplip.sf.net:80.
  HTTP request sent, awaiting response... 404 Not Found
  2022-09-13 23:23:02 ERROR 404: Not Found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1989508/+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 1989508] Re: hp-plugin unable to load plugin.conf

[Brian J. Murrell]

What has to happen to get this issue resolved?  Are the hplip
maintainers even paying attention to the bugs filed here for them?

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

Title:
  hp-plugin unable to load plugin.conf

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in hplip package in Fedora:
  Confirmed

Bug description:
  Linux hp-plugin fails on Fedora 35 with the error:

  error: Plugin download failed with error code = 8
  error:  file does not match its checksum. File may have been corrupted or 
altered

  When running "hp-plugin -l debug" the reason turns out to be that
  http://hplip.sourceforge.net/plugin.conf does not exist:

  hp-plugin[540794]: debug: wget returned: 0
  hp-plugin[540794]: debug: --2022-09-13 23:23:02--  
http://hplip.sf.net/plugin.conf
  Resolving hplip.sf.net (hplip.sf.net)... 204.68.111.100
  Connecting to hplip.sf.net (hplip.sf.net)|204.68.111.100|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: http://hplip.sourceforge.net/plugin.conf [following]
  --2022-09-13 23:23:02--  http://hplip.sourceforge.net/plugin.conf
  Resolving hplip.sourceforge.net (hplip.sourceforge.net)... 204.68.111.100
  Reusing existing connection to hplip.sf.net:80.
  HTTP request sent, awaiting response... 404 Not Found
  2022-09-13 23:23:02 ERROR 404: Not Found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1989508/+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 1991587] [NEW] Gnome Keyring SSH agent socket is ignored by Sway session

[Michał J . Gajda]

Public bug reported:

1. `apt-get install -y sway` to install an alternative Wayland window manager.
2. Login to `sway` user session.
3. Gnome Keyring will ask for passphrase to unlock SSH keys.
4. Then `gnome-keyring-daemon` stays in the background.
5. However, no shell terminal will see this ssh.

   Attempting to use `ssh` or `git` remote will ask for the same
passphrase again.

Workaround:

Add `export SSH_AUTH_SOCK=/run/user/${UID}/keyring/ssh` to `.bashrc`.
Then it works.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-keyring 40.0-3ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-48.54-lowlatency 5.15.53
Uname: Linux 5.15.0-48-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Oct  4 00:09:03 2022
InstallationDate: Installed on 2022-09-05 (28 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: gnome-keyring
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Gnome Keyring SSH agent socket is ignored by Sway session

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  1. `apt-get install -y sway` to install an alternative Wayland window manager.
  2. Login to `sway` user session.
  3. Gnome Keyring will ask for passphrase to unlock SSH keys.
  4. Then `gnome-keyring-daemon` stays in the background.
  5. However, no shell terminal will see this ssh.

 Attempting to use `ssh` or `git` remote will ask for the same
  passphrase again.

  Workaround:

  Add `export SSH_AUTH_SOCK=/run/user/${UID}/keyring/ssh` to `.bashrc`.
  Then it works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-keyring 40.0-3ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-48.54-lowlatency 5.15.53
  Uname: Linux 5.15.0-48-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Oct  4 00:09:03 2022
  InstallationDate: Installed on 2022-09-05 (28 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1991587/+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 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication

[J G]

Problem to install/read Belgium e-Id. Is this the problem bug? Is there
a working work-around available?

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

Title:
  [snap] apparmor denied when trying to load pkcs11 module for smart
  card authentication

Status in Mozilla Firefox:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  I use a smart card to access government sites. I have that working in
  firefox and chrome on ubuntu impish, and gave jammy a try, but there
  firefox won't load the library, giving me a generic error.

  dmesg, however, shows this apparmor denied message:

  [sáb abr  2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115):
  apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox"
  name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680
  comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0

  
  Note also the path, that's not what I typed into the firefox dialog box. I 
have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and 
that's what I typed in when prompted for its path by firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  2 17:34:09 2022
  InstallationDate: Installed on 2022-03-20 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  Snap.Changes: no changes found
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1967632/+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 1703377] Re: Gnome online account login prevents paste or autotype

[William J. Vallance]

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

Title:
  Gnome online account login prevents paste or autotype

Status in gnome-online-accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  On entering Login data to an online account such as google.

  Using keepass as password manager I now can not enter my password via
  paste nor via autotype. Trying any of them results in an invalid
  password.

  Ubuntu 16.10 - GNOME Shell 3.20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1703377/+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 1988333] monitors.xml.txt

[Randy J. Ray]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1988333/+attachment/5613357/+files/monitors.xml.txt

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

Title:
  Ubuntu Gnome Dock Randomly Dies

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I
  have at the bottom) will randomly die. When this happens:

  * The dock is reduced to just the "Show Applications" icon
  * One or more open applications will no longer accept events (mouse or 
keyboard)
  * Ctrl-` (and sometimes Ctrl-TAB) cease working

  I can restore it by hitting Alt-F2 and then "r" in the dialog. When
  this happens, icons on my status bar (Slack, Dropbox, etc.) are
  doubled. The extra icons go away after the screensaver kicks in and is
  then unlocked.

  $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] ProcCpuinfoMinimal.txt

[Randy J. Ray]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1988333/+attachment/5613354/+files/ProcCpuinfoMinimal.txt

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

Title:
  Ubuntu Gnome Dock Randomly Dies

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I
  have at the bottom) will randomly die. When this happens:

  * The dock is reduced to just the "Show Applications" icon
  * One or more open applications will no longer accept events (mouse or 
keyboard)
  * Ctrl-` (and sometimes Ctrl-TAB) cease working

  I can restore it by hitting Alt-F2 and then "r" in the dialog. When
  this happens, icons on my status bar (Slack, Dropbox, etc.) are
  doubled. The extra icons go away after the screensaver kicks in and is
  then unlocked.

  $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] ShellJournal.txt

[Randy J. Ray]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1988333/+attachment/5613356/+files/ShellJournal.txt

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

Title:
  Ubuntu Gnome Dock Randomly Dies

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I
  have at the bottom) will randomly die. When this happens:

  * The dock is reduced to just the "Show Applications" icon
  * One or more open applications will no longer accept events (mouse or 
keyboard)
  * Ctrl-` (and sometimes Ctrl-TAB) cease working

  I can restore it by hitting Alt-F2 and then "r" in the dialog. When
  this happens, icons on my status bar (Slack, Dropbox, etc.) are
  doubled. The extra icons go away after the screensaver kicks in and is
  then unlocked.

  $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] ProcEnviron.txt

[Randy J. Ray]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1988333/+attachment/5613355/+files/ProcEnviron.txt

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

Title:
  Ubuntu Gnome Dock Randomly Dies

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I
  have at the bottom) will randomly die. When this happens:

  * The dock is reduced to just the "Show Applications" icon
  * One or more open applications will no longer accept events (mouse or 
keyboard)
  * Ctrl-` (and sometimes Ctrl-TAB) cease working

  I can restore it by hitting Alt-F2 and then "r" in the dialog. When
  this happens, icons on my status bar (Slack, Dropbox, etc.) are
  doubled. The extra icons go away after the screensaver kicks in and is
  then unlocked.

  $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] GsettingsChanges.txt

[Randy J. Ray]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1988333/+attachment/5613353/+files/GsettingsChanges.txt

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

Title:
  Ubuntu Gnome Dock Randomly Dies

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I
  have at the bottom) will randomly die. When this happens:

  * The dock is reduced to just the "Show Applications" icon
  * One or more open applications will no longer accept events (mouse or 
keyboard)
  * Ctrl-` (and sometimes Ctrl-TAB) cease working

  I can restore it by hitting Alt-F2 and then "r" in the dialog. When
  this happens, icons on my status bar (Slack, Dropbox, etc.) are
  doubled. The extra icons go away after the screensaver kicks in and is
  then unlocked.

  $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] Re: Ubuntu Gnome Dock Randomly Dies

[Randy J. Ray]

apport information

** Tags added: apport-collected

** Description changed:

  Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I
  have at the bottom) will randomly die. When this happens:
  
  * The dock is reduced to just the "Show Applications" icon
  * One or more open applications will no longer accept events (mouse or 
keyboard)
  * Ctrl-` (and sometimes Ctrl-TAB) cease working
  
  I can restore it by hitting Alt-F2 and then "r" in the dialog. When this
  happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The
  extra icons go away after the screensaver kicks in and is then unlocked.
  
  $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.04
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 42.4-0ubuntu0.22.04.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
+ RebootRequiredPkgs: Error: path contained symlinks.
+ RelatedPackageVersions: mutter-common 42.2-0ubuntu1
+ Tags:  jammy
+ Uname: Linux 5.15.0-46-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago)
+ UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1988333/+attachment/5613352/+files/Dependencies.txt

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

Title:
  Ubuntu Gnome Dock Randomly Dies

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I
  have at the bottom) will randomly die. When this happens:

  * The dock is reduced to just the "Show Applications" icon
  * One or more open applications will no longer accept events (mouse or 
keyboard)
  * Ctrl-` (and sometimes Ctrl-TAB) cease working

  I can restore it by hitting Alt-F2 and then "r" in the dialog. When
  this happens, icons on my status bar (Slack, Dropbox, etc.) are
  doubled. The extra icons go away after the screensaver kicks in and is
  then unlocked.

  $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-46-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-08-20 (13 days ago)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988333/+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 1988333] [NEW] Ubuntu Gnome Dock Randomly Dies

[Randy J. Ray]

Public bug reported:

Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I
have at the bottom) will randomly die. When this happens:

* The dock is reduced to just the "Show Applications" icon
* One or more open applications will no longer accept events (mouse or keyboard)
* Ctrl-` (and sometimes Ctrl-TAB) cease working

I can restore it by hitting Alt-F2 and then "r" in the dialog. When this
happens, icons on my status bar (Slack, Dropbox, etc.) are doubled. The
extra icons go away after the screensaver kicks in and is then unlocked.

$ apt-cache policy gnome-shell-extension-ubuntu-dock
gnome-shell-extension-ubuntu-dock:
  Installed: 72~ubuntu5.22.04.1
  Candidate: 72~ubuntu5.22.04.1
  Version table:
 *** 72~ubuntu5.22.04.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
100 /var/lib/dpkg/status
 72~ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

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

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

Title:
  Ubuntu Gnome Dock Randomly Dies

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

Bug description:
  Since upgrading to Ubuntu 22.04, I have noticed that the dock (which I
  have at the bottom) will randomly die. When this happens:

  * The dock is reduced to just the "Show Applications" icon
  * One or more open applications will no longer accept events (mouse or 
keyboard)
  * Ctrl-` (and sometimes Ctrl-TAB) cease working

  I can restore it by hitting Alt-F2 and then "r" in the dialog. When
  this happens, icons on my status bar (Slack, Dropbox, etc.) are
  doubled. The extra icons go away after the screensaver kicks in and is
  then unlocked.

  $ apt-cache policy gnome-shell-extension-ubuntu-dock
  gnome-shell-extension-ubuntu-dock:
Installed: 72~ubuntu5.22.04.1
Candidate: 72~ubuntu5.22.04.1
Version table:
   *** 72~ubuntu5.22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   72~ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

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


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

Re: [Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

[Robert P. J. Day]

Thanks, I'll check it out.

On Mon, Aug 22, 2022 at 9:50 AM Olivier Tilloy <1987...@bugs.launchpad.net>
wrote:

> This upstream bug seems relevant:
> https://bugs.chromium.org/p/chromium/issues/detail?id=1340181
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987137
>
> Title:
>   Migrating chromium-browser to core22 has libwayland-client0 issues
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   Following on an earlier bug report that related to simple core22
>   migration for chromium-browser, here is a blocker that I don't know
>   how to deal with.
>
>   After checking out the core22 branch from
>   git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
>   (which already contains the early, easy migration commits), doing a
>   build eventually generates (snippet here):
>
>   2022-08-19 20:15:05.809 :: In file included from
> ../../third_party/wayland/src/src/wayland-client.h:40:
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.809 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.809 ::^
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.810 ::^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>   2022-08-19 20:15:05.810 ::  ^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>   and lots more of the same; it seems pretty clear that the relevant
>   wayland library is simply not new enough, and I don't know what to
>   add/modify to add core22 support to the mix, so I am open to
>   suggestions.
>
>   I do notice the file
>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
>   which contains package version manifests for various distros, but not
>   Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
>   that's just a guess.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions
>
>

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  2022-08-19 20:15:05.810 ::  ^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor,

  and lots more of the same; it seems pretty clear that the relevant
  wayland library is simply not new enough, and I don't know what to
  add/modify to add core22 support to the mix, so I am open to
  suggestions.

  I do notice the file
  

Re: [Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

[Robert P. J. Day]

OK, I'll take a look at that when time permits.

On Mon, Aug 22, 2022 at 8:36 AM Nathan Teodosio <1987...@bugs.launchpad.net>
wrote:

> > Can I adjust snapcraft.yaml to override 1.20.0 and specifically
> request 1.18.0?
>
> We used override-build to get newer versions of Libva:
> https://git.launchpad.net/~nteodosio/chromium-
> browser/tree/snapcraft.yaml?h=hwacc#n362
>
> I wonder if you could do the same for libwayland-client0, but this could
> be more difficult if it is in a dependency tree...
>
> > Or maybe I can check if there is a development version of chromium
> that has already moved up to 1.20.0.
>
> According to that README file, I would try the "To import a new snapshot
> of wayland:" instructions with git checkout 1.20.0.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987137
>
> Title:
>   Migrating chromium-browser to core22 has libwayland-client0 issues
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   Following on an earlier bug report that related to simple core22
>   migration for chromium-browser, here is a blocker that I don't know
>   how to deal with.
>
>   After checking out the core22 branch from
>   git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
>   (which already contains the early, easy migration commits), doing a
>   build eventually generates (snippet here):
>
>   2022-08-19 20:15:05.809 :: In file included from
> ../../third_party/wayland/src/src/wayland-client.h:40:
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.809 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.809 ::^
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.810 ::^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>   2022-08-19 20:15:05.810 ::  ^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>   and lots more of the same; it seems pretty clear that the relevant
>   wayland library is simply not new enough, and I don't know what to
>   add/modify to add core22 support to the mix, so I am open to
>   suggestions.
>
>   I do notice the file
>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
>   which contains package version manifests for various distros, but not
>   Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
>   that's just a guess.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions
>
>

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  2022-08-19 

Re: [Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

[Robert P. J. Day]

Well, yes, that would be the problem. What would be the for-the-moment
hacky workaround (if any)? Can I adjust snapcraft.yaml to override 1.20.0
and specifically request 1.18.0? Or maybe I can check if there is a
development version of chromium that has already moved up to 1.20.0. This
is not a high priority, it would just be nice to have.

On Mon, Aug 22, 2022 at 5:46 AM Olivier Tilloy <1987...@bugs.launchpad.net>
wrote:

>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
> isn't used by the snap build process, so that's not the right thing to
> look at.
>
> There appears to be an incompatibility between the version of libwayland
> in Ubuntu 22.04 (1.20.0) and the version vendored into the chromium
> source tree (1.18.0 according to
>
> https://source.chromium.org/chromium/chromium/src/+/main:third_party/wayland/README.chromium
> ).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987137
>
> Title:
>   Migrating chromium-browser to core22 has libwayland-client0 issues
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   Following on an earlier bug report that related to simple core22
>   migration for chromium-browser, here is a blocker that I don't know
>   how to deal with.
>
>   After checking out the core22 branch from
>   git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
>   (which already contains the early, easy migration commits), doing a
>   build eventually generates (snippet here):
>
>   2022-08-19 20:15:05.809 :: In file included from
> ../../third_party/wayland/src/src/wayland-client.h:40:
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.809 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.809 ::^
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.810 ::^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>   2022-08-19 20:15:05.810 ::  ^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>   and lots more of the same; it seems pretty clear that the relevant
>   wayland library is simply not new enough, and I don't know what to
>   add/modify to add core22 support to the mix, so I am open to
>   suggestions.
>
>   I do notice the file
>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
>   which contains package version manifests for various distros, but not
>   Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
>   that's just a guess.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions
>
>

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 

[Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

[Robert P. J. Day]

** Description changed:

  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know how
  to deal with.
  
  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (which
  already contains the early, easy migration commits), doing a build
  eventually generates (snippet here):
  
+ 2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
+ 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
+ 2022-08-19 20:15:05.809 ::^
+ 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
+ 2022-08-19 20:15:05.810 ::^
+ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
+ 2022-08-19 20:15:05.810 ::  ^
+ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor,
  
- 2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

- 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
- 2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

- 2022-08-19 20:15:05.809 ::^   

   
- 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
- 2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

- 2022-08-19 20:15:05.810 ::^   

   
- 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
- 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  
- 2022-08-19 20:15:05.810 ::  ^ 

   
- 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
- 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor, 
+ and lots more of the same; it seems pretty clear that the relevant
+ wayland library is simply not new enough, and I don't know what to
+ add/modify to add core22 support to the mix, so I am open to
+ suggestions.
  
- 
- and lots more of the same; it seems pretty clear that the relevant wayland 
library is simply not new enough, and I don't know what to add/modify to add 
core22 support to the mix, so I am open to suggestions.
+ I do notice the file
+ parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
+ which contains package version manifests for various distros, but not
+ Ubuntu 22.04, so I'm *guessing* that might need enhancement. But that's
+ just a guess.

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch 

[Desktop-packages] [Bug 1987137] [NEW] Migrating chromium-browser to core22 has libwayland-client0 issues

[Robert P. J. Day]

Public bug reported:

Following on an earlier bug report that related to simple core22
migration for chromium-browser, here is a blocker that I don't know how
to deal with.

After checking out the core22 branch from
git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (which
already contains the early, easy migration commits), doing a build
eventually generates (snippet here):


2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

2022-08-19 20:15:05.809 ::^ 

 
2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

2022-08-19 20:15:05.810 ::^ 

 
2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy 
*) wl_registry, 
 
2022-08-19 20:15:05.810 ::  ^   

 
2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy 
*) wl_compositor, 


and lots more of the same; it seems pretty clear that the relevant wayland 
library is simply not new enough, and I don't know what to add/modify to add 
core22 support to the mix, so I am open to suggestions.

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

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  
  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

  2022-08-19 20:15:05.809 ::^   

   
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

  2022-08-19 20:15:05.810 ::^   

   
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
  2022-08-19 

[Desktop-packages] [Bug 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done

[Robert P. J. Day]

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

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

Title:
  snapcraft build fails on second run as "ln -s libdrm.pc libdrm-
  uninstalled.pc" already done

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I'm trying to migrate the chromium browser snapcraft.yaml file to
  core22 and Snapcraft 7 and, after a build error on the first test
  (more on that later), I cleaned and re-ran the build to make sure the
  build error was reproducible, and got:

  ... big snip ...
  2022-08-18 08:50:45.224 :: + OUT=out/Release  
 
  2022-08-18 08:50:45.224 :: + mkdir -p out/Release 
 
  2022-08-18 08:50:45.243 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc
 
  2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 
'libdrm-uninstalled.pc': File exists 
  2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 
1.
  Review the scriptlet and make sure it's correct. 

  Naturally, since that symlink had been created during the first run
  (in a persistent 22.04 LXD container), it was still there for the
  second run. Operations like that should be idempotent so one can run
  multiple builds.

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


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

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

Ok, thanks.

On Fri, Aug 19, 2022 at 8:10 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> > Perhaps one should create a core 22 branch where I can submit my
> changes.
>
> I think that is only possible with a team. See if you can push to
> https://code.launchpad.net/~chromium-core22/+git/chromium-core22. If
> yes, just force push your current work to it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

My interest in this is that I'm stress testing migrating snaps to core
22/snapcraft 7 as part of the update for the Snapcraft 101 course, and when
I asked my team for an example of a snap that would be challenging to
migrate, one of them immediately suggested chromium, so that's why I'm
working on this. So far, the necessary changes were fairly minimal, until
this issue, which I don't know what to do with.

Perhaps one should create a core 22 branch where I can submit my
changes.

In terms of getting more output, with Snapcraft 7, I'm running "snapcraft
--verbosity=trace" for tons of output.

Anyway, this wl_proxy* stuff is the current bottleneck.

On Fri, Aug 19, 2022 at 7:25 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> For a matter of fact, wl_proxy_marshal_flags is declared in wayland-
> client-core.h, provided by libwayland-dev, which is specified in the
> build-packages of chromium in snapcraft.yaml. As long as it is version
> >=1.20, I'd think it should work, but reality shows otherwise.
>
> I'm trying to build the snap too so I can see full logs, but weirdly
> they are much less verbose than what I'm used to (e.g.
>
> https://launchpadlibrarian.net/618908242/buildlog_snap_ubuntu_jammy_amd64_chromium-
> browser-core22_BUILDING.txt.gz
> ),
> and I don't want to believe that would
> be caused by a mere switch to core22.
>
> > P.S. Thanks for your patience with all of this.
>
> No such thing, it's a pleasure :). This is both useful and a great
> chance to better understand snaps.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying 

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

Last comment for the day ... from what little I've seen, it seems like it
might require defining a lengthy list of packages relative to 22.04 to
migrate this snap to 22.04. Or maybe I'm misreading it. In any event, I'd
still like to make this happen.

On Thu, Aug 18, 2022 at 3:56 PM Robert Day 
wrote:

> Actually, another part of my grep search produced the following, which
> seems to suggest that an older version of libwayland-client0 is being used:
>
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mips64el.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm64:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_arm64.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.i386:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_i386.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.armel:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armel.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mipsel:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mipsel.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armhf.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.amd64:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_amd64.deb
>
> At least that's the way I read it.
>
> rday
>
> On Thu, Aug 18, 2022 at 3:43 PM Robert Day 
> wrote:
>
>> A comprehensive grep includes the lines:
>>
>> parts/launcher/state/build:  - libwayland-client0=1.20.0-1
>> parts/va-drivers/state/build:  - libwayland-client0=1.20.0-1
>> parts/pipewire/state/build:  - libwayland-client0=1.20.0-1
>> parts/chromium-build/state/build:  - libwayland-client0=1.20.0-1
>> parts/manpage/state/build:  - libwayland-client0=1.20.0-1
>>
>> Oh, wait, there we
>> go: 
>> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
>> appears to be a version manifest that does not include anything for 22.04.
>> Does that sound like the problem?
>>
>> P.S. Thanks for your patience with all of this.
>>
>> On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <
>> 1986...@bugs.launchpad.net> wrote:
>>
>>> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>>>
>>> wayland-1.21.0/debian/libwayland-client0.symbols:
>>> wl_proxy_marshal_flags@Base 1.20.0
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1986925
>>>
>>> Title:
>>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>>
>>> Status in chromium-browser package in Ubuntu:
>>>   New
>>>
>>> Bug description:
>>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>>   did what seemed necessary to update snapcraft.yaml to build with
>>>   snapcraft 7 for core22. The only change of any significance was to
>>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>>   extension. I started the build and it ran for quite some time (in a
>>>   persistent 22.04 LXD container) until:
>>>
>>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>>
>>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>>
>>>   2022-08-18 09:11:00.888 :: + cp
>>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>>
>>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>>
>>>   2022-08-18 09:11:00.935 :: + cd -
>>>
>>>   2022-08-18 09:11:00.935 ::
>>> /root/snaps/snap-from-source/parts/chromium/build
>>>
>>>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>>
>>>   2022-08-18 09:11:07.112 :: ERROR at
>>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
>>> code.
>>>
>>>   2022-08-18 09:11:07.112 :: pkgresult =
>>> exec_script(pkg_config_script, args, "value")
>>>   2022-08-18 09:11:07.113 :: ^--
>>>
>>>   2022-08-18 09:11:07.113 :: Current dir:
>>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>>>   2022-08-18 09:11:07.113 :: Command: python3
>>> 

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

Actually, another part of my grep search produced the following, which
seems to suggest that an older version of libwayland-client0 is being used:

parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mips64el.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm64:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_arm64.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.i386:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_i386.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.armel:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armel.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mipsel:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mipsel.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armhf.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.amd64:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_amd64.deb

At least that's the way I read it.

rday

On Thu, Aug 18, 2022 at 3:43 PM Robert Day 
wrote:

> A comprehensive grep includes the lines:
>
> parts/launcher/state/build:  - libwayland-client0=1.20.0-1
> parts/va-drivers/state/build:  - libwayland-client0=1.20.0-1
> parts/pipewire/state/build:  - libwayland-client0=1.20.0-1
> parts/chromium-build/state/build:  - libwayland-client0=1.20.0-1
> parts/manpage/state/build:  - libwayland-client0=1.20.0-1
>
> Oh, wait, there we
> go: 
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
> appears to be a version manifest that does not include anything for 22.04.
> Does that sound like the problem?
>
> P.S. Thanks for your patience with all of this.
>
> On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <
> 1986...@bugs.launchpad.net> wrote:
>
>> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>>
>> wayland-1.21.0/debian/libwayland-client0.symbols:
>> wl_proxy_marshal_flags@Base 1.20.0
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1986925
>>
>> Title:
>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>
>> Status in chromium-browser package in Ubuntu:
>>   New
>>
>> Bug description:
>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>   did what seemed necessary to update snapcraft.yaml to build with
>>   snapcraft 7 for core22. The only change of any significance was to
>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>   extension. I started the build and it ran for quite some time (in a
>>   persistent 22.04 LXD container) until:
>>
>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>
>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>
>>   2022-08-18 09:11:00.888 :: + cp
>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>
>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>
>>   2022-08-18 09:11:00.935 :: + cd -
>>
>>   2022-08-18 09:11:00.935 ::
>> /root/snaps/snap-from-source/parts/chromium/build
>>
>>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>
>>   2022-08-18 09:11:07.112 :: ERROR at
>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
>> code.
>>
>>   2022-08-18 09:11:07.112 :: pkgresult =
>> exec_script(pkg_config_script, args, "value")
>>   2022-08-18 09:11:07.113 :: ^--
>>
>>   2022-08-18 09:11:07.113 :: Current dir:
>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>>   2022-08-18 09:11:07.113 :: Command: python3
>> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
>> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>>
>>   2022-08-18 09:11:07.113 :: Returned 1.
>>
>>   2022-08-18 09:11:07.113 :: stderr:
>>
>>   2022-08-18 09:11:07.113 ::
>>
>>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>>
>>   2022-08-18 09:11:07.113 ::
>>
>>   2022-08-18 09:11:07.113 :: See
>> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>>   2022-08-18 

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

A comprehensive grep includes the lines:

parts/launcher/state/build:  - libwayland-client0=1.20.0-1
parts/va-drivers/state/build:  - libwayland-client0=1.20.0-1
parts/pipewire/state/build:  - libwayland-client0=1.20.0-1
parts/chromium-build/state/build:  - libwayland-client0=1.20.0-1
parts/manpage/state/build:  - libwayland-client0=1.20.0-1

Oh, wait, there we
go: 
parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
appears to be a version manifest that does not include anything for 22.04.
Does that sound like the problem?

P.S. Thanks for your patience with all of this.

On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>
> wayland-1.21.0/debian/libwayland-client0.symbols:
> wl_proxy_marshal_flags@Base 1.20.0
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

This appears to describe precisely this issue:

https://github.com/libsdl-org/SDL/pull/5092

On Thu, Aug 18, 2022 at 1:06 PM Robert Day 
wrote:

> Yup, same errors ... lots of "wl "and "marshal" undefined references.
> Here's just a small sample:
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1038:13:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>
>
> 2022-08-18 17:03:57.646 ::^
>
>
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1062:13:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>
>
> 2022-08-18 17:03:57.646 ::^
>
>
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1175:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>
>
> 2022-08-18 17:03:57.646 ::  ^
>
>
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1291:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>
> 2022-08-18 17:03:57.647 ::  ^
>
>
>
> 2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1307:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>
> 2022-08-18 17:03:57.647 ::  ^
>
>
>
> 2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1371:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_shm_pool,
>
>
> 2022-08-18 17:03:57.647 ::  ^
>
>
> On Thu, Aug 18, 2022 at 1:04 PM Robert Day 
> wrote:
>
>> That's what I did, but that's also when I got the errors I included in my
>> previous comment. I'm rebuilding just to make sure those errors are
>> reproducible.
>>
>> On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <
>> 1986...@bugs.launchpad.net> wrote:
>>
>>> > but that appears to be because this newer gnome does not supply such
>>> an executable; there is no "pkg-config" under
>>> /snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
>>> under gnome-3-38.
>>>
>>> Oh, so this time pkg-config in build-packages could solve it? Probably
>>> you will have to remove the pkg_config line from args.gn, though.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1986925
>>>
>>> Title:
>>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>>
>>> Status in chromium-browser package in Ubuntu:
>>>   New
>>>
>>> Bug description:
>>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>>   did what seemed necessary to update snapcraft.yaml to build with
>>>   snapcraft 7 for core22. The only change of any significance was to
>>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>>   extension. I started the build and it ran for quite some time (in a
>>>   persistent 22.04 LXD container) until:
>>>
>>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>>
>>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>>
>>>   2022-08-18 09:11:00.888 :: + cp
>>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>>
>>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>>
>>>   2022-08-18 09:11:00.935 :: + cd -
>>>
>>>   2022-08-18 09:11:00.935 ::
>>> /root/snaps/snap-from-source/parts/chromium/build
>>>
>>>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>>
>>>   2022-08-18 09:11:07.112 :: ERROR at
>>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
>>> code.
>>>
>>>   2022-08-18 09:11:07.112 :: pkgresult =
>>> exec_script(pkg_config_script, args, "value")
>>>   2022-08-18 09:11:07.113 :: ^--
>>>
>>>   2022-08-18 09:11:07.113 :: Current dir:
>>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>>>   2022-08-18 09:11:07.113 :: Command: python3
>>> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
>>> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>>>
>>>   2022-08-18 09:11:07.113 :: Returned 1.
>>>
>>>   2022-08-18 09:11:07.113 :: stderr:
>>>
>>>   2022-08-18 09:11:07.113 ::
>>>
>>>   2022-08-18 09:11:07.113 :: Could not run pkg-config.

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

Yup, same errors ... lots of "wl "and "marshal" undefined references.
Here's just a small sample:

2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1038:13:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.646 :: callback =
wl_proxy_marshal_flags((struct wl_proxy *) wl_display,


2022-08-18 17:03:57.646 ::^


2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1062:13:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.646 :: registry =
wl_proxy_marshal_flags((struct wl_proxy *) wl_display,


2022-08-18 17:03:57.646 ::^


2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1175:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_registry,


2022-08-18 17:03:57.646 ::  ^


2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1291:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_compositor,


2022-08-18 17:03:57.647 ::  ^


2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1307:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_compositor,


2022-08-18 17:03:57.647 ::  ^


2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1371:7:
error: use of undeclared identifier 'wl_proxy_marshal_flags'


2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
wl_proxy *) wl_shm_pool,


2022-08-18 17:03:57.647 ::  ^


On Thu, Aug 18, 2022 at 1:04 PM Robert Day  wrote:

> That's what I did, but that's also when I got the errors I included in my
> previous comment. I'm rebuilding just to make sure those errors are
> reproducible.
>
> On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <
> 1986...@bugs.launchpad.net> wrote:
>
>> > but that appears to be because this newer gnome does not supply such
>> an executable; there is no "pkg-config" under
>> /snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
>> under gnome-3-38.
>>
>> Oh, so this time pkg-config in build-packages could solve it? Probably
>> you will have to remove the pkg_config line from args.gn, though.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1986925
>>
>> Title:
>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>
>> Status in chromium-browser package in Ubuntu:
>>   New
>>
>> Bug description:
>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>   did what seemed necessary to update snapcraft.yaml to build with
>>   snapcraft 7 for core22. The only change of any significance was to
>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>   extension. I started the build and it ran for quite some time (in a
>>   persistent 22.04 LXD container) until:
>>
>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>
>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>
>>   2022-08-18 09:11:00.888 :: + cp
>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>
>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>
>>   2022-08-18 09:11:00.935 :: + cd -
>>
>>   2022-08-18 09:11:00.935 ::
>> /root/snaps/snap-from-source/parts/chromium/build
>>
>>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>
>>   2022-08-18 09:11:07.112 :: ERROR at
>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
>> code.
>>
>>   2022-08-18 09:11:07.112 :: pkgresult =
>> exec_script(pkg_config_script, args, "value")
>>   2022-08-18 09:11:07.113 :: ^--
>>
>>   2022-08-18 09:11:07.113 :: Current dir:
>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>>   2022-08-18 09:11:07.113 :: Command: python3
>> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
>> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>>
>>   2022-08-18 09:11:07.113 :: Returned 1.
>>
>>   2022-08-18 09:11:07.113 :: stderr:
>>
>>   2022-08-18 09:11:07.113 ::
>>
>>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>>
>>   2022-08-18 09:11:07.113 ::
>>
>>   2022-08-18 09:11:07.113 :: See
>> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>>
>>   2022-08-18 09:11:07.113 :: ^--
>>
>>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which 

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

That's what I did, but that's also when I got the errors I included in my
previous comment. I'm rebuilding just to make sure those errors are
reproducible.

On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> > but that appears to be because this newer gnome does not supply such
> an executable; there is no "pkg-config" under
> /snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
> under gnome-3-38.
>
> Oh, so this time pkg-config in build-packages could solve it? Probably
> you will have to remove the pkg_config line from args.gn, though.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'  

[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

Just deleting that line seemed to allow the build to progress further,
but now I have a slew of errors; I'll post a snippet here, then must run
off but will be back in a bit:

2022-08-18 14:42:14.617 :: In file included from 
../../third_party/angle/src/gpu_info_util/SystemInfo_vulkan.cpp:10: 

   
2022-08-18 14:42:14.617 :: In file included from 
../../third_party/angle/src/gpu_info_util/SystemInfo_vulkan.h:12:   

   
2022-08-18 14:42:14.617 :: In file included from 
../../third_party/angle/src/common/vulkan/vulkan_icd.h:15:  

   
2022-08-18 14:42:14.617 :: In file included from 
../../third_party/angle/src/common/vulkan/vk_headers.h:14:  

   
2022-08-18 14:42:14.617 :: In file included from 
../../third_party/angle/src/third_party/volk/volk.h:50: 

   
2022-08-18 14:42:14.617 :: In file included from 
../../third_party/vulkan-deps/vulkan-headers/src/include/vulkan/vulkan.h:41:

   
2022-08-18 14:42:14.617 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

   
2022-08-18 14:42:14.617 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
 
2022-08-18 14:42:14.618 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 
   
2022-08-18 14:42:14.618 ::^ 


2022-08-18 14:42:14.618 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
 
2022-08-18 14:42:14.618 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 
   
2022-08-18 14:42:14.618 ::^ 


2022-08-18 14:42:14.618 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
2022-08-18 14:42:14.618 :: id = wl_proxy_marshal_flags((struct wl_proxy 
*) wl_registry, 

2022-08-18 14:42:14.618 ::  ^   


2022-08-18 14:42:14.618 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
2022-08-18 14:42:14.618 :: id = wl_proxy_marshal_flags((struct wl_proxy 
*) wl_compositor,   

2022-08-18 14:42:14.618 ::  ^   


2022-08-18 14:42:14.618 :: /usr/include/wayland-client-protocol.h:1307:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
2022-08-18 14:42:14.618 :: id = wl_proxy_marshal_flags((struct wl_proxy 
*) wl_compositor,   
  

[Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

I made that change, it still failed:

2022-08-18 14:31:54.099 :: Current dir: 
/root/snaps/snap-from-source/parts/chromium/build/out/Release/  


2022-08-18 14:31:54.099 :: Command: python3 
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
 -p /snap/gnome-42-2204/current/usr/bin/pkg-config x11-xcb  
  
2022-08-18 14:31:54.099 :: Returned 1.  


2022-08-18 14:31:54.099 :: stderr:  


2022-08-18 14:31:54.099 ::  


2022-08-18 14:31:54.099 :: Could not run pkg-config.

but that appears to be because this newer gnome does not supply such an
executable; there is no "pkg-config" under
/snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
under gnome-3-38. What about just deleting that line from build/args.gn,
and assuming pkg-config is run from the standard package?

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
 
  2022-08-18 09:11:00.935 :: + cd - 
 
  2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build  
 
  2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release   
 
  2022-08-18 09:11:07.112 :: ERROR at 
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code. 

   
  2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script, 
args, "value")   
  2022-08-18 09:11:07.113 :: ^--
 
  2022-08-18 09:11:07.113 :: Current dir: 
/root/snaps/snap-from-source/parts/chromium/build/out/Release/ 
  2022-08-18 09:11:07.113 :: Command: python3 
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
 -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
 
  2022-08-18 09:11:07.113 :: Returned 1.
 
  2022-08-18 09:11:07.113 :: stderr:
 
  2022-08-18 09:11:07.113 ::
 
  2022-08-18 09:11:07.113 :: Could not run pkg-config.  
 
  2022-08-18 09:11:07.113 ::
 
  2022-08-18 09:11:07.113 :: See 
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.   
  2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
 
  2022-08-18 09:11:07.113 :: 

[Desktop-packages] [Bug 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done

[Robert P. J. Day]

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

Title:
  snapcraft build fails on second run as "ln -s libdrm.pc libdrm-
  uninstalled.pc" already done

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I'm trying to migrate the chromium browser snapcraft.yaml file to
  core22 and Snapcraft 7 and, after a build error on the first test
  (more on that later), I cleaned and re-ran the build to make sure the
  build error was reproducible, and got:

  ... big snip ...
  2022-08-18 08:50:45.224 :: + OUT=out/Release  
 
  2022-08-18 08:50:45.224 :: + mkdir -p out/Release 
 
  2022-08-18 08:50:45.243 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc
 
  2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 
'libdrm-uninstalled.pc': File exists 
  2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 
1.
  Review the scriptlet and make sure it's correct. 

  Naturally, since that symlink had been created during the first run
  (in a persistent 22.04 LXD container), it was still there for the
  second run. Operations like that should be idempotent so one can run
  multiple builds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986922/+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 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done

[Robert P. J. Day]

Ah:

build/args.gn:pkg_config = "/snap/gnome-3-38-2004/current/usr/bin/pkg-
config"

In my container, it's now /snap/gnome-42-2204; I'll change that and see
what happens.

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

Title:
  snapcraft build fails on second run as "ln -s libdrm.pc libdrm-
  uninstalled.pc" already done

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I'm trying to migrate the chromium browser snapcraft.yaml file to
  core22 and Snapcraft 7 and, after a build error on the first test
  (more on that later), I cleaned and re-ran the build to make sure the
  build error was reproducible, and got:

  ... big snip ...
  2022-08-18 08:50:45.224 :: + OUT=out/Release  
 
  2022-08-18 08:50:45.224 :: + mkdir -p out/Release 
 
  2022-08-18 08:50:45.243 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc
 
  2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 
'libdrm-uninstalled.pc': File exists 
  2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 
1.
  Review the scriptlet and make sure it's correct. 

  Naturally, since that symlink had been created during the first run
  (in a persistent 22.04 LXD container), it was still there for the
  second run. Operations like that should be idempotent so one can run
  multiple builds.

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


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

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

OK, I'm trying that now, but I would be astonished if that was the solution
as pkg-config is already installed, either because I installed it manually
at some point, or maybe it was installed by an earlier snap, who knows? But
it's definitely there so adding it to "build-packages" should make no
difference.

On Thu, Aug 18, 2022 at 9:30 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> Thanks for the bug report, Robert.
>
> My first attempt would be adding a pkg-config line to the build-packages
> of chromium. Does it make sense to you? If yes, could you please try
> that?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

Hang on, look at that hard-coded directory name: "/snap/gnome-3-38-2004".
Since the gnome extension under core 22 is named just "gnome", any
hardcoded names to the old extension should fail.

On Thu, Aug 18, 2022 at 10:15 AM Robert Day 
wrote:

> Same result:
>
> 2022-08-18 14:13:31.315 :: + OUT=out/Release
>
> 2022-08-18 14:13:31.316 :: + mkdir -p out/Release
>
> 2022-08-18 14:13:31.335 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
> 2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'
>
> 2022-08-18 14:13:31.368 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
> 2022-08-18 14:13:31.368 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
> 2022-08-18 14:13:31.389 :: + cd -
>
> 2022-08-18 14:13:31.389 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
> 2022-08-18 14:13:31.389 :: + out/Release/gn gen out/Release
>
> 2022-08-18 14:13:37.548 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
> 2022-08-18 14:13:37.549 :: pkgresult = exec_script(pkg_config_script,
> args, "value")
> 2022-08-18 14:13:37.549 :: ^--
>
> 2022-08-18 14:13:37.549 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
> 2022-08-18 14:13:37.549 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
> 2022-08-18 14:13:37.549 :: Returned 1.
>
> 2022-08-18 14:13:37.549 :: stderr:
>
> 2022-08-18 14:13:37.549 ::
>
> 2022-08-18 14:13:37.550 :: Could not run pkg-config.
>
> 2022-08-18 14:13:37.550 ::
>
> 2022-08-18 14:13:37.550 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
> 2022-08-18 14:13:37.550 :: pkg_config("x11-xcb") {
>
> 2022-08-18 14:13:37.550 :: ^--
>
> 2022-08-18 14:13:37.550 :: See //BUILD.gn:529:7: which caused the file to
> be included.
> 2022-08-18 14:13:37.550 ::
> "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
> 2022-08-18 14:13:37.550 ::
> ^---
> 2022-08-18 14:13:37.782 'override-build' in part 'chromium' failed with
> code 1.
> Review the scriptlet and make sure it's correct.
>
> 2022-08-18 14:13:37.867 Traceback (most recent call last):
>
> 2022-08-18 14:13:37.867   File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/snapcraft/parts/parts.py",
> line 170, in run
>
> 2022-08-18 14:13:37.867 aex.execute(action, stdout=stream,
> stderr=stream)
> 2022-08-18 14:13:37.867   File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
> line 301, in execute
>
> 2022-08-18 14:13:37.867 self._executor.execute(actions, stdout=stdout,
> stderr=stderr)
> 2022-08-18 14:13:37.867   File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
> line 126, in execute
>
> 2022-08-18 14:13:37.867 self._run_action(act, stdout=stdout,
> stderr=stderr)
> 2022-08-18 14:13:37.868   File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
> line 189, in _run_action
>
> 2022-08-18 14:13:37.868 handler.run_action(action, stdout=stdout,
> stderr=stderr)
> 2022-08-18 14:13:37.868   File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
> line 161, in run_action
>
> 2022-08-18 14:13:37.868 state = handler(step_info, stdout=stdout,
> stderr=stderr)
> 2022-08-18 14:13:37.868   File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
> line 297, in _run_build
>
> 2022-08-18 14:13:37.868 self._run_step(
>
> 2022-08-18 14:13:37.868   File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
> line 469, in _run_step
>
> 2022-08-18 14:13:37.868 step_handler.run_scriptlet(
>
> 2022-08-18 14:13:37.868   File
> "/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/step_handler.py",
> line 265, in run_scriptlet
>
> 2022-08-18 14:13:37.868 raise errors.ScriptletRunError(
>
> 2022-08-18 14:13:37.868 craft_parts.errors.ScriptletRunError:
> 'override-build' in part 'chromium' failed with code 1.
>
>
> 2022-08-18 14:13:37.869 Review the scriptlet and make sure it's correct.
>
> 2022-08-18 14:13:37.869 Full execution log:
> '/root/.cache/snapcraft/log/snapcraft-20220818-140941.486880.log'
>
>
> I think pkg-config is being invoked, it's just failing based on what it's
> being asked to do.
>
> On Thu, Aug 18, 2022 at 10:11 AM Robert Day 
> wrote:
>
>> OK, I'm trying that now, but I would be astonished if that was the
>> solution as pkg-config is already installed, either because I installed it
>> manually at some point, or maybe it was installed by an earlier snap, who
>> knows? But it's definitely there so adding it to "build-packages" should
>> make no difference.
>>
>> On Thu, Aug 

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

Same result:

2022-08-18 14:13:31.315 :: + OUT=out/Release

2022-08-18 14:13:31.316 :: + mkdir -p out/Release

2022-08-18 14:13:31.335 :: + cp /root/snaps/snap-from-source/stage/build/
args.gn out/Release/
2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'

2022-08-18 14:13:31.367 :: + '[' amd64 = armhf ']'

2022-08-18 14:13:31.368 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig

2022-08-18 14:13:31.368 :: + ln -s libdrm.pc libdrm-uninstalled.pc

2022-08-18 14:13:31.389 :: + cd -

2022-08-18 14:13:31.389 ::
/root/snaps/snap-from-source/parts/chromium/build

2022-08-18 14:13:31.389 :: + out/Release/gn gen out/Release

2022-08-18 14:13:37.548 :: ERROR at
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
code.

2022-08-18 14:13:37.549 :: pkgresult = exec_script(pkg_config_script,
args, "value")
2022-08-18 14:13:37.549 :: ^--

2022-08-18 14:13:37.549 :: Current dir:
/root/snaps/snap-from-source/parts/chromium/build/out/Release/
2022-08-18 14:13:37.549 :: Command: python3
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
-p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb

2022-08-18 14:13:37.549 :: Returned 1.

2022-08-18 14:13:37.549 :: stderr:

2022-08-18 14:13:37.549 ::

2022-08-18 14:13:37.550 :: Could not run pkg-config.

2022-08-18 14:13:37.550 ::

2022-08-18 14:13:37.550 :: See
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
2022-08-18 14:13:37.550 :: pkg_config("x11-xcb") {

2022-08-18 14:13:37.550 :: ^--

2022-08-18 14:13:37.550 :: See //BUILD.gn:529:7: which caused the file to
be included.
2022-08-18 14:13:37.550 ::
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
2022-08-18 14:13:37.550 ::
^---
2022-08-18 14:13:37.782 'override-build' in part 'chromium' failed with
code 1.
Review the scriptlet and make sure it's correct.

2022-08-18 14:13:37.867 Traceback (most recent call last):

2022-08-18 14:13:37.867   File
"/snap/snapcraft/8122/lib/python3.8/site-packages/snapcraft/parts/parts.py",
line 170, in run

2022-08-18 14:13:37.867 aex.execute(action, stdout=stream,
stderr=stream)
2022-08-18 14:13:37.867   File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
line 301, in execute

2022-08-18 14:13:37.867 self._executor.execute(actions, stdout=stdout,
stderr=stderr)
2022-08-18 14:13:37.867   File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
line 126, in execute

2022-08-18 14:13:37.867 self._run_action(act, stdout=stdout,
stderr=stderr)
2022-08-18 14:13:37.868   File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/executor.py",
line 189, in _run_action

2022-08-18 14:13:37.868 handler.run_action(action, stdout=stdout,
stderr=stderr)
2022-08-18 14:13:37.868   File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
line 161, in run_action

2022-08-18 14:13:37.868 state = handler(step_info, stdout=stdout,
stderr=stderr)
2022-08-18 14:13:37.868   File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
line 297, in _run_build

2022-08-18 14:13:37.868 self._run_step(

2022-08-18 14:13:37.868   File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/part_handler.py",
line 469, in _run_step

2022-08-18 14:13:37.868 step_handler.run_scriptlet(

2022-08-18 14:13:37.868   File
"/snap/snapcraft/8122/lib/python3.8/site-packages/craft_parts/executor/step_handler.py",
line 265, in run_scriptlet

2022-08-18 14:13:37.868 raise errors.ScriptletRunError(

2022-08-18 14:13:37.868 craft_parts.errors.ScriptletRunError:
'override-build' in part 'chromium' failed with code 1.


2022-08-18 14:13:37.869 Review the scriptlet and make sure it's correct.

2022-08-18 14:13:37.869 Full execution log:
'/root/.cache/snapcraft/log/snapcraft-20220818-140941.486880.log'


I think pkg-config is being invoked, it's just failing based on what it's
being asked to do.

On Thu, Aug 18, 2022 at 10:11 AM Robert Day 
wrote:

> OK, I'm trying that now, but I would be astonished if that was the
> solution as pkg-config is already installed, either because I installed it
> manually at some point, or maybe it was installed by an earlier snap, who
> knows? But it's definitely there so adding it to "build-packages" should
> make no difference.
>
> On Thu, Aug 18, 2022 at 9:30 AM Nathan Teodosio <
> 1986...@bugs.launchpad.net> wrote:
>
>> Thanks for the bug report, Robert.
>>
>> My first attempt would be adding a pkg-config line to the build-packages
>> of chromium. Does it make sense to you? If yes, could you please try
>> that?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1986925
>>
>> Title:
>>   [snap] Trying to build chromium snap for 

[Desktop-packages] [Bug 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done

[Robert P. J. Day]

I know I don't need to suggest this, but the seeming solution is to just
replace "ln -s" with "ln -sf", unless there's something more subtle
going on.

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

Title:
  snapcraft build fails on second run as "ln -s libdrm.pc libdrm-
  uninstalled.pc" already done

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I'm trying to migrate the chromium browser snapcraft.yaml file to
  core22 and Snapcraft 7 and, after a build error on the first test
  (more on that later), I cleaned and re-ran the build to make sure the
  build error was reproducible, and got:

  ... big snip ...
  2022-08-18 08:50:45.224 :: + OUT=out/Release  
 
  2022-08-18 08:50:45.224 :: + mkdir -p out/Release 
 
  2022-08-18 08:50:45.243 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc
 
  2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 
'libdrm-uninstalled.pc': File exists 
  2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 
1.
  Review the scriptlet and make sure it's correct. 

  Naturally, since that symlink had been created during the first run
  (in a persistent 22.04 LXD container), it was still there for the
  second run. Operations like that should be idempotent so one can run
  multiple builds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986922/+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 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

Let me know if there's anything you want me to test; I have the
container sitting here, ready for further experimentation.

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
 
  2022-08-18 09:11:00.935 :: + cd - 
 
  2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build  
 
  2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release   
 
  2022-08-18 09:11:07.112 :: ERROR at 
//build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code. 

   
  2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script, 
args, "value")   
  2022-08-18 09:11:07.113 :: ^--
 
  2022-08-18 09:11:07.113 :: Current dir: 
/root/snaps/snap-from-source/parts/chromium/build/out/Release/ 
  2022-08-18 09:11:07.113 :: Command: python3 
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
 -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
 
  2022-08-18 09:11:07.113 :: Returned 1.
 
  2022-08-18 09:11:07.113 :: stderr:
 
  2022-08-18 09:11:07.113 ::
 
  2022-08-18 09:11:07.113 :: Could not run pkg-config.  
 
  2022-08-18 09:11:07.113 ::
 
  2022-08-18 09:11:07.113 :: See 
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.   
  2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
 
  2022-08-18 09:11:07.113 :: ^--
 
  2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be 
included. 
  2022-08-18 09:11:07.114 ::   
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan", 
  2022-08-18 09:11:07.114 ::   
^---  
  2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code 
1.
  Review the scriptlet and make sure it's correct.

  I verified that the pkg-config utility is installed in the container;
  I can only suspect that this error is related to switching to the
  core22 gnome extension. I am open to suggestions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+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 1986925] [NEW] Trying to build chromium snap for core22: pkg-config fails.

[Robert P. J. Day]

Public bug reported:

I checked out the "dev" branch of chromium-browser from launchpad and
did what seemed necessary to update snapcraft.yaml to build with
snapcraft 7 for core22. The only change of any significance was to
change the extension from "gnome-3-38" to the core22-specific "gnome"
extension. I started the build and it ran for quite some time (in a
persistent 22.04 LXD container) until:

2022-08-18 09:11:00.869 :: + OUT=out/Release
   
2022-08-18 09:11:00.869 :: + mkdir -p out/Release   
   
2022-08-18 09:11:00.888 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'  
   
2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'  
   
2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 
   
2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc  
   
2022-08-18 09:11:00.935 :: + cd -   
   
2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build
   
2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release 
   
2022-08-18 09:11:07.112 :: ERROR at //build/config/linux/pkg_config.gni:104:17: 
Script returned non-zero exit code. 
   
2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script, args, 
"value")   
2022-08-18 09:11:07.113 :: ^--  
   
2022-08-18 09:11:07.113 :: Current dir: 
/root/snaps/snap-from-source/parts/chromium/build/out/Release/ 
2022-08-18 09:11:07.113 :: Command: python3 
/root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
 -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
 
2022-08-18 09:11:07.113 :: Returned 1.  
   
2022-08-18 09:11:07.113 :: stderr:  
   
2022-08-18 09:11:07.113 ::  
   
2022-08-18 09:11:07.113 :: Could not run pkg-config.
   
2022-08-18 09:11:07.113 ::  
   
2022-08-18 09:11:07.113 :: See 
//third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.   
2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {  
   
2022-08-18 09:11:07.113 :: ^--  
   
2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be 
included. 
2022-08-18 09:11:07.114 ::   
"//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan", 
2022-08-18 09:11:07.114 ::   
^---  
2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code 1.
Review the scriptlet and make sure it's correct.

I verified that the pkg-config utility is installed in the container; I
can only suspect that this error is related to switching to the core22
gnome extension. I am open to suggestions.

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

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

Title:
  Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 

[Desktop-packages] [Bug 1986922] [NEW] snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done

[Robert P. J. Day]

Public bug reported:

I'm trying to migrate the chromium browser snapcraft.yaml file to core22
and Snapcraft 7 and, after a build error on the first test (more on that
later), I cleaned and re-ran the build to make sure the build error was
reproducible, and got:

... big snip ...
2022-08-18 08:50:45.224 :: + OUT=out/Release
   
2022-08-18 08:50:45.224 :: + mkdir -p out/Release   
   
2022-08-18 08:50:45.243 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']'  
   
2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']'  
   
2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 
   
2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc  
   
2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 
'libdrm-uninstalled.pc': File exists 
2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 1.
Review the scriptlet and make sure it's correct. 

Naturally, since that symlink had been created during the first run (in
a persistent 22.04 LXD container), it was still there for the second
run. Operations like that should be idempotent so one can run multiple
builds.

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

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

Title:
  snapcraft build fails on second run as "ln -s libdrm.pc libdrm-
  uninstalled.pc" already done

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I'm trying to migrate the chromium browser snapcraft.yaml file to
  core22 and Snapcraft 7 and, after a build error on the first test
  (more on that later), I cleaned and re-ran the build to make sure the
  build error was reproducible, and got:

  ... big snip ...
  2022-08-18 08:50:45.224 :: + OUT=out/Release  
 
  2022-08-18 08:50:45.224 :: + mkdir -p out/Release 
 
  2022-08-18 08:50:45.243 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc
 
  2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 
'libdrm-uninstalled.pc': File exists 
  2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 
1.
  Review the scriptlet and make sure it's correct. 

  Naturally, since that symlink had been created during the first run
  (in a persistent 22.04 LXD container), it was still there for the
  second run. Operations like that should be idempotent so one can run
  multiple builds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986922/+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 1972820] [NEW] LibreOffice crash when entering data in MySQL database

[J-Paul BERARD]

Public bug reported:

When I try to enter a new record in a MySQL table in LO Base, the new record is 
accepted but Base close suddenly when I close the table.
MySQL database is connected by the direct connector (embedded).
Same kind of problem with LO 6.4

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libreoffice 1:7.3.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May 10 12:29:06 2022
InstallationDate: Installed on 2020-04-10 (759 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to jammy on 2022-04-09 (30 days ago)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  LibreOffice crash when entering data in MySQL database

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When I try to enter a new record in a MySQL table in LO Base, the new record 
is accepted but Base close suddenly when I close the table.
  MySQL database is connected by the direct connector (embedded).
  Same kind of problem with LO 6.4

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 12:29:06 2022
  InstallationDate: Installed on 2020-04-10 (759 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1972820/+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 1968679] [NEW] Unable to connect to online account

[J-Paul BERARD]

Public bug reported:

When I try to create a new connection to an online service like Google, the 
process start but the connection window stay blank and the process seems to be 
blocked.
Screenshot added

Ubuntu 22.04, Wayland, AMD64

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-online-accounts 3.44.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 08:39:27 2022
InstallationDate: Installed on 2020-04-10 (731 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)

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


** Tags: amd64 apport-bug jammy wayland-session

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1968679/+attachment/5579750/+files/Screenshot%20from%202022-04-12%2008-47-59.png

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

Title:
  Unable to connect to online account

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  When I try to create a new connection to an online service like Google, the 
process start but the connection window stay blank and the process seems to be 
blocked.
  Screenshot added

  Ubuntu 22.04, Wayland, AMD64

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:39:27 2022
  InstallationDate: Installed on 2020-04-10 (731 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1968679/+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 1956888] Re: can't manually sort bookmarks anymore

[Allan J Kelly]

I have this problem.
Chromium Version 97.0.4692.71 (Official Build) snap (64-bit)
Ubuntu 20.04.3 LTS

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

Title:
  can't manually sort bookmarks anymore

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 21.10
  Chromium is installed via snap.
  chromium97.0.4692.711864   latest/stable

  Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the 
bookmarks view (control + shift + O) nor directly in the bookmarks bar. 
  Bookmarks folders have the same problem.

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


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

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

[J-Paul BERARD]

For Ubuntu 21.10, an update of mutter was delivered yesterday (40.5-1).
It seems to have solved the problem.

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

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

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

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

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


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

[Desktop-packages] [Bug 1948010] [NEW] photo comment changed in "binary comment"

[J-Paul BERARD]

Public bug reported:

I add a comment in several photo (F3 key) (image 1) and this comment is
changed in the following string : binary comment (image 2) !

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: shotwell 0.30.11-0ubuntu3
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 21 14:06:06 2021
InstallationDate: Installed on 2020-04-10 (558 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
SourcePackage: shotwell
UpgradeStatus: Upgraded to impish on 2021-10-16 (5 days ago)

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


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

** Attachment added: "Comment I write"
   
https://bugs.launchpad.net/bugs/1948010/+attachment/5534891/+files/Capture%201.png

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

Title:
  photo comment changed in "binary comment"

Status in shotwell package in Ubuntu:
  New

Bug description:
  I add a comment in several photo (F3 key) (image 1) and this comment
  is changed in the following string : binary comment (image 2) !

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: shotwell 0.30.11-0ubuntu3
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 21 14:06:06 2021
  InstallationDate: Installed on 2020-04-10 (558 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: shotwell
  UpgradeStatus: Upgraded to impish on 2021-10-16 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1948010/+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 1630176] Re: Ubuntu version reported wrong in system settings

[Knut J Bjuland]

This affects me to

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

Title:
  Ubuntu version reported wrong in system settings

Status in unity-control-center package in Ubuntu:
  Expired

Bug description:
  https://help.ubuntu.com/community/CheckingYourUbuntuVersion describes
  two ways of getting your current Ubuntu version: via system settings,
  and via terminal. For me, those two methods give me a different
  version (14.04 vs 16.04, see attached screenshot). I upgraded my pre-
  installed trusty to xenial, so the version printed on terminal is
  correct. That means that the system settings displays the wrong
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1630176/+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 1945367] [NEW] Xorg crash with Nvidia drivers after installation

[j l h]

Public bug reported:

i open a second bug report because i have already freeze problem after the 
installation of nvidia drivers and reboot.
Freeze become generally when i am using firefox and visioning a video with 
youtube.
I specify that since the last bug report, i re install ubuntu with official 
.iso without other package non official.
To create the report, i have to connect to the PC from another one with ssh.
When i use ubuntu-bug, it is not possible to join nvidia-bug-report because the 
application dont give me the hand to finish the report.
When i try to execute nvidia-bug-report, i have the same thing.

To use the PC, i have to use nouveau drivers and intel Xe GPU with poor
performances ...

Thanks for help.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-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  470.63.01  Tue Aug  3 20:44:16 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
Date: Tue Sep 28 21:13:05 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed
 virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed
 virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2090]
 NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Intel Corporation Device [8086:2090]
InstallationDate: Installed on 2021-09-26 (1 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Intel(R) Client Systems NUC11PHi7
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic 
root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2021
dmi.bios.release: 5.19
dmi.bios.vendor: Intel Corp.
dmi.bios.version: PHTGL579.0063.2021.0707.1057
dmi.board.name: NUC11PHBi7
dmi.board.vendor: Intel Corporation
dmi.board.version: M26151-402
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 12.19
dmi.modalias: 
dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0:
dmi.product.family: PH
dmi.product.name: NUC11PHi7
dmi.product.sku: SWNUC11PHKi7C00
dmi.product.version: M26149-403
dmi.sys.vendor: Intel(R) Client Systems
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2
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:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash focal ubuntu

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

Title:
  Xorg crash with Nvidia drivers after installation

Status in xorg package in Ubuntu:
  New

Bug description:
  i open a second bug report because i have already freeze problem after the 
installation of nvidia drivers and reboot.
  Freeze become generally when i am using firefox and visioning a video with 
youtube.
  I specify that since the last bug report, i re install ubuntu with official 
.iso without other package non official.
  To create the report, i have to connect to the PC from another one with ssh.
  When i use ubuntu-bug, it is 

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

[J-Paul BERARD]

Like it was said before, this issue is probably not specific to
Thunderbird. I get the same problem with ImageMagick !

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

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

Status in Mozilla Thunderbird:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

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

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


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

[Desktop-packages] [Bug 1940925] Re: [FFe] Do not activate spread view on first boot

[J-P Nurmi]

+1 from me too.

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

Title:
  [FFe] Do not activate spread view on first boot

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

Bug description:
  On first boot the spread view shows the first boot wizard and it looks
  really weird. Moreover if you click on the right workspace the wizard
  is not displayed.

  The spread view should be disabled and the wizard should be displayed
  full screen immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 24 12:41:16 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-31 (450 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1940925/+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 1936393] Re: thunderbird window hided and abnormal context menu

[J-Paul BERARD]

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

Thanks !
Yes, I think so : probably same issue.

** This bug has been marked a duplicate of bug 1932328
   Thunderbird under Wayland does not correctly close (or manage) windows

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

Title:
  thunderbird window hided and abnormal context menu

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Many times, when I minimize the main Thunderbird window to the dock, later, 
it's impossible to maximise it again (impossible to see it) and the contextual 
menu of the Thunderbird icon in the dock, appears on the top left of the screen 
like frozen : you can do nothing with it and you cannot hide it until you close 
the session.
  I join a screenshot

  Ubuntu 21.04 WAYLAND (64 bits)
  Thunderbird 78.11

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BuildID: 20210528153351
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 15 15:42:15 2021
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   Français Language Pack - langpack...@thunderbird.mozilla.org
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-04-10 (461 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=78.11.0/20210528153351 (In use)
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to hirsute on 2021-04-26 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1936393/+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 1936393] [NEW] thunderbird window hided and abnormal context menu

[J-Paul BERARD]

Public bug reported:

Many times, when I minimize the main Thunderbird window to the dock, later, 
it's impossible to maximise it again (impossible to see it) and the contextual 
menu of the Thunderbird icon in the dock, appears on the top left of the screen 
like frozen : you can do nothing with it and you cannot hide it until you close 
the session.
I join a screenshot

Ubuntu 21.04 WAYLAND (64 bits)
Thunderbird 78.11

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BuildID: 20210528153351
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul 15 15:42:15 2021
IncompatibleExtensions:
 Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
 Français Language Pack - langpack...@thunderbird.mozilla.org
 English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
 Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-04-10 (461 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=78.11.0/20210528153351 (In use)
SourcePackage: thunderbird
UpgradeStatus: Upgraded to hirsute on 2021-04-26 (79 days ago)

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


** Tags: amd64 apport-bug hirsute wayland-session

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1936393/+attachment/5511199/+files/Capture%20ecran%20du%202021-07-15.jpg

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

Title:
  thunderbird window hided and abnormal context menu

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Many times, when I minimize the main Thunderbird window to the dock, later, 
it's impossible to maximise it again (impossible to see it) and the contextual 
menu of the Thunderbird icon in the dock, appears on the top left of the screen 
like frozen : you can do nothing with it and you cannot hide it until you close 
the session.
  I join a screenshot

  Ubuntu 21.04 WAYLAND (64 bits)
  Thunderbird 78.11

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BuildID: 20210528153351
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 15 15:42:15 2021
  IncompatibleExtensions:
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   Français Language Pack - langpack...@thunderbird.mozilla.org
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2020-04-10 (461 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=78.11.0/20210528153351 (In use)
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to hirsute on 2021-04-26 (79 days ago)

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


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

Re: [Desktop-packages] [Bug 1926325] Re: After upgrade to 21.04, WiFi unable to connect on channel 13

[J-Paul BERARD]

Thanks. Done.

-- 
Jean-Paul

Le 30/04/2021 à 11:10, Sebastien Bacher a écrit :
> Thank you for your bug report, you might have a better chance to get a
> reply if you report it upstream on
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues
>
> ** Changed in: network-manager (Ubuntu)
> Importance: Undecided => Low
>

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

Title:
  After upgrade to 21.04, WiFi unable to connect on channel 13

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have upgraded a desktop system from 20.10 to 21.04
  Then, the computer didn't connect to my WiFi network anymore ! When I opened 
Network manager, I could see the WiFi networks of my neighbours but not mine !

  My Wifi network is provided by a Freebox (french provider Free) and choose 
automatically the channel for the Wifi network (n type). At home, it was 
channel n° 13. The neighbours were on channel 6.
  So I changed the setup of my box manually to channel 11 and the computer can 
see again my network and connect without problem ! Of course, this problem 
didn't happen with the 20.10 version : it was connected on channel 13 before 
the upgrade !

  So it seems that Ubuntu 21.04 is unable to connect to a network on
  channel 13 !

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 27 19:01:54 2021
  InstallationDate: Installed on 2020-04-10 (382 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IpRoute:
   default via 192.168.0.254 dev wlp4s6 proto dhcp metric 600 
   default via 172.20.10.1 dev bnep0 proto dhcp metric 750 
   169.254.0.0/16 dev bnep0 scope link metric 1000 
   172.20.10.0/28 dev bnep0 proto kernel scope link src 172.20.10.6 metric 750 
   192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to hirsute on 2021-04-26 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1926325/+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 1926325] [NEW] After upgrade to 21.04, WiFi unable to connect on channel 13

[J-Paul BERARD]

Public bug reported:

I have upgraded a desktop system from 20.10 to 21.04
Then, the computer didn't connect to my WiFi network anymore ! When I opened 
Network manager, I could see the WiFi networks of my neighbours but not mine !

My Wifi network is provided by a Freebox (french provider Free) and choose 
automatically the channel for the Wifi network (n type). At home, it was 
channel n° 13. The neighbours were on channel 6.
So I changed the setup of my box manually to channel 11 and the computer can 
see again my network and connect without problem ! Of course, this problem 
didn't happen with the 20.10 version : it was connected on channel 13 before 
the upgrade !

So it seems that Ubuntu 21.04 is unable to connect to a network on
channel 13 !

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: network-manager 1.30.0-1ubuntu3
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 27 19:01:54 2021
InstallationDate: Installed on 2020-04-10 (382 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
IpRoute:
 default via 192.168.0.254 dev wlp4s6 proto dhcp metric 600 
 default via 172.20.10.1 dev bnep0 proto dhcp metric 750 
 169.254.0.0/16 dev bnep0 scope link metric 1000 
 172.20.10.0/28 dev bnep0 proto kernel scope link src 172.20.10.6 metric 750 
 192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600
SourcePackage: network-manager
UpgradeStatus: Upgraded to hirsute on 2021-04-26 (0 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute wayland-session

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

Title:
  After upgrade to 21.04, WiFi unable to connect on channel 13

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have upgraded a desktop system from 20.10 to 21.04
  Then, the computer didn't connect to my WiFi network anymore ! When I opened 
Network manager, I could see the WiFi networks of my neighbours but not mine !

  My Wifi network is provided by a Freebox (french provider Free) and choose 
automatically the channel for the Wifi network (n type). At home, it was 
channel n° 13. The neighbours were on channel 6.
  So I changed the setup of my box manually to channel 11 and the computer can 
see again my network and connect without problem ! Of course, this problem 
didn't happen with the 20.10 version : it was connected on channel 13 before 
the upgrade !

  So it seems that Ubuntu 21.04 is unable to connect to a network on
  channel 13 !

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 27 19:01:54 2021
  InstallationDate: Installed on 2020-04-10 (382 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IpRoute:
   default via 192.168.0.254 dev wlp4s6 proto dhcp metric 600 
   default via 172.20.10.1 dev bnep0 proto dhcp metric 750 
   169.254.0.0/16 dev bnep0 scope link metric 1000 
   172.20.10.0/28 dev bnep0 proto kernel scope link src 172.20.10.6 metric 750 
   192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to hirsute on 2021-04-26 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

Re: [Desktop-packages] [Bug 1917300] Re: updated firefox 86.0 (64 bit)

[J. Cherubini]

Hey Olivier,

with the new version of Firefox Browser 88.0 (64-Bit) Mozilla Firefox 
for Ubuntu is the browser now working again! So you can close my ticket.

Thank you very much for your support!

Joe

Am 29.03.21 um 18:19 schrieb Olivier Tilloy:
> The fact that the problem doesn't happen in safe mode suggests that it's
> hardware-accelerated rendering/compositing that is to blame.
>
> After restarting firefox in normal mode, you might want to try
> instructions at https://support.mozilla.org/en-US/kb/upgrade-graphics-
> drivers-use-hardware-acceleration#w_i-still-have-problems-with-my-
> graphics-card-in-firefox.
>

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

Title:
  updated firefox 86.0 (64 bit)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  updated firefox 86.0 (64 bit) starts and colored pixels blinking all around 
the screen; cannot use it any more.
  Using a ThinkPad SL 510, 4 GB RAM
  Ubuntu 20.04 LTS
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe 878 F pulseaudio
   /dev/snd/controlC1:  joe 878 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-08 (137 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.178.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.178.0/24 dev enp8s0 proto kernel scope link src 192.168.178.35 
metric 100
  Package: firefox 87.0+build3-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  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/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2011
  dmi.bios.release: 1.73
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JET91WW (1.49 )
  dmi.board.name: 28476NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.48
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JET91WW(1.49):bd12/12/2011:br1.73:efr1.48:svnLENOVO:pn28476NG:pvrThinkPadSL510:rvnLENOVO:rn28476NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad SL510
  dmi.product.name: 28476NG
  dmi.product.version: ThinkPad SL510
  dmi.sys.vendor: LENOVO

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

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

Re: [Desktop-packages] [Bug 1917300] Re: updated firefox 86.0 (64 bit)

[J. Cherubini]

Hallo Oliveier,

thank you!

The link you send give the message

> Mozilla Support Logo 
>
>   * Get Help 
>   * Volunteer 
>
>   * Sign In/Up 
>
>
>   Page Not Found
>
> Sorry, we couldn't find the page you were looking for. Please, try 
> searching our site using the form below.
>
> Enter your terms in the form below and click*Search*
>
have you another one?

greetings

Joe

Am 29.03.21 um 18:19 schrieb Olivier Tilloy:
> The fact that the problem doesn't happen in safe mode suggests that it's
> hardware-accelerated rendering/compositing that is to blame.
>
> After restarting firefox in normal mode, you might want to try
> instructions at https://support.mozilla.org/en-US/kb/upgrade-graphics-
> drivers-use-hardware-acceleration#w_i-still-have-problems-with-my-
> graphics-card-in-firefox.
>

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

Title:
  updated firefox 86.0 (64 bit)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  updated firefox 86.0 (64 bit) starts and colored pixels blinking all around 
the screen; cannot use it any more.
  Using a ThinkPad SL 510, 4 GB RAM
  Ubuntu 20.04 LTS
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe 878 F pulseaudio
   /dev/snd/controlC1:  joe 878 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-08 (137 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.178.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.178.0/24 dev enp8s0 proto kernel scope link src 192.168.178.35 
metric 100
  Package: firefox 87.0+build3-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  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/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2011
  dmi.bios.release: 1.73
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JET91WW (1.49 )
  dmi.board.name: 28476NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.48
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JET91WW(1.49):bd12/12/2011:br1.73:efr1.48:svnLENOVO:pn28476NG:pvrThinkPadSL510:rvnLENOVO:rn28476NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad SL510
  dmi.product.name: 28476NG
  dmi.product.version: ThinkPad SL510
  dmi.sys.vendor: LENOVO

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

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

Re: [Desktop-packages] [Bug 1917300] Re: updated firefox 86.0 (64 bit)

[J. Cherubini]

Good Morning Oliver,

Firefox is running in save mode!

here the information from about:support


Application Basics

NameFirefox
Version 87.0
Build ID20210318103112
Distribution ID canonical
User Agent  Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:87.0) 
Gecko/20100101 Firefox/87.0
OS  Linux 5.8.0-48-generic #54~20.04.1-Ubuntu SMP Sat Mar 20 13:40:25 
UTC 2021
Multiprocess Windows1/1
Fission Windows 0/1 Disabled by safe mode
Remote Processes4 <#remote-processes>
Enterprise Policies Inactive
Google Location Service Key Found
Google Safebrowsing Key Found
Mozilla Location Service KeyMissing
Safe Mode   true


Crash Reports for the Last 3 Days

Report ID   Submitted


Firefox Features

NameVersion ID
DoH Roll-Out2.0.0   doh-roll...@mozilla.org
Firefox Screenshots 39.0.0  screensh...@mozilla.org
Form Autofill   1.0 formautof...@mozilla.org
Web Compatibility Interventions 20.1.0  webcom...@mozilla.org
WebCompat Reporter  1.4.0   webcompat-repor...@mozilla.org


Remote Features


Remote Processes

TypeCount
Web Content 1 / 8
Privileged About1
Extension   1
Preallocated1


Add-ons

NameTypeVersion Enabled ID
Amazon.com  extension   1.3 trueamazondot...@search.mozilla.org
Amazon.de   extension   1.4 trueama...@search.mozilla.org
Bingextension   1.3 trueb...@search.mozilla.org
DuckDuckGo  extension   1.1 trued...@search.mozilla.org
eBayextension   1.3 truee...@search.mozilla.org
Ecosia  extension   1.0 trueeco...@search.mozilla.org
Google  extension   1.1 truegoo...@search.mozilla.org
LEO Eng-Deu extension   1.0 trueleo_ende...@search.mozilla.org
Wikipedia (de)  extension   1.1 truewikipe...@search.mozilla.org
Adblock Plus - kostenloser Adblockerextension   3.10.2  false 
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
AdBlocker for YouTube™  extension   0.3.3   false 
jid1-q4sG8pYhq8KGHs@jetpack
AdGuard Werbeblockerextension   3.5.34  false 
adguardadbloc...@adguard.com
anonymoXextension   4.4.2   false   cli...@anonymox.net
Auto Pause|Stop for YouTube™extension   0.1.4   false 
jid1-s2tSKqH4h0BHUw@jetpack
Auto-Sort Bookmarks extension   3.4.1   false   sortbookmarks@bouanto
Binnen-I be goneextension   2.8 false 
{b65d7d9a-4ec0-4974-b07f-83e30f6e973f}
Bitwarden - Kostenloser Passwortmanager extension   1.49.1  false 
{446900e4-71c2-419f-a6a7-df9c091e268b}
Citavi Picker   extension   2020.12.11.4false 
{8AA36F4F-6DC7-4c06-77AF-5035170634FE}
Dark Reader extension   4.9.29  false   ad...@darkreader.org
DontBugMe   extension   1.12false   
{a504b604-10c6-4475-a554-ce0878783f10}
EmbedUpdaterextension   1.3.0   false 
{eb8240fc-eee9-4cc7-ab15-12ac64614064}
Enhancer for YouTube™   extension   2.0.103.3   false 
enhancerforyout...@maximerf.addons.mozilla.org
Flash Playerextension   1.1.9   false 
{87e997f4-ae0e-42e6-a780-ff73977188c5}
FoxyProxy Standard  extension   7.5.1   false   foxypr...@eric.h.jung
Gesturefy   extension   3.1.1   false   
{506e023c-7f2b-40a3-8066-bc5deb40aebe}
Ghostery – Datenschutzorientierter Werbeblocker extension   8.5.5   
false 
fire...@ghostery.com
HTTPS Everywhereextension   2021.1.27   false   
https-everywh...@eff.org
LastPass: Free Password Manager extension   4.67.1.4false 
supp...@lastpass.com
LEO Dictionariesextension   3.4.1   false   
contextmenuextens...@leo.org
Librefox HTTP Watcher - Red flagextension   2.8 false 
librefox.http.watc...@intika.be
Nimbus Screen Capture: Screenshots, Annotateextension   15.6.9  false 
nimbusscreencaptur...@everhelper.me
Notes by Firefoxextension   4.3.7   false   no...@mozilla.com
Privacy Badger  extension   2021.2.2false   
jid1-MnnxcxisBPnSXQ@jetpack
ProxTubeextension   7.0.1   false   i...@maltegoetz.de
Qwant Lite  extension   1.0.5   false   
{7965226e-78d5-45c1-a1e9-2c9e6b80fff4}
Qwant Sidebar   extension   1.6 false   @Qwant.Sidebar
SortTabsextension   1.1.0   false   jid1-ybZYGXHcBi9FHA@jetpack
Startpage.com — Datenschutz-Suchmaschineextension   1.3.0   false 
{20fc2e06-e3e4-4b2b-812b-ab431220cada}
Stop AutoPlay Next for YouTube™ extension   0.2.2   false 
jid1-nbzaq9ol2hyY64gGe@jetpack
Suche auf YouTube   extension   2.0.1   false 
{be8f6f90-2079-4e84-ac5c-13e6af2b48d1}
TabSearch   extension   0.4.8   false   
{11a68c03-baa3-41fb-869c-5172c4c4dd2e}
Telegram Webextension   3.0 false   
{ed387cfb-e57a-49e0-9bf3-017a1f7f2378}
Tree Style Tab  extension   3.7.3   false   

Re: [Desktop-packages] [Bug 1917300] Re: updated firefox 86.0 (64 bit)

[J. Cherubini]

I add the message from the terminal:

> joe@joe-ThinkPad-SL510:~$ apport-collect 1917300
> The authorization page:
>  
> (https://launchpad.net/+authorize-token?oauth_token=n8Wctwb2SrpjgsfNRQtk_permission=DESKTOP_INTEGRATION)
> should be opening in your browser. Use your browser to authorize
> this program to access Launchpad on your behalf.
> Waiting to hear from Launchpad about your decision...
> joc[2787:2787:0326/090546.981484:ERROR:sandbox_linux.cc(374)] 
> InitializeSandbox() called with multiple threads in process gpu-process.
> h[2760:2760:0326/090548.511411:ERROR:CONSOLE(1)] "[Shields]: Can't 
> request shields panel data. Error: No tab url specified", source: 
> chrome-extension://mnojpmjdmbbfmejpflffifhffcmidifd/out/brave_extension_background.bundle.js
>  
> (1)
> Failed to parse JSON adblock resources: EOF while parsing a value at 
> line 1 column 0

Am 23.03.21 um 21:20 schrieb Olivier Tilloy:
> apport-collect 1917300

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

Title:
  updated firefox 86.0 (64 bit)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  updated firefox 86.0 (64 bit) starts and colored pixels blinking all around 
the screen; cannot use it any more.
  Using a ThinkPad SL 510, 4 GB RAM
  Ubuntu 20.04 LTS
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe 878 F pulseaudio
   /dev/snd/controlC1:  joe 878 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-08 (137 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.178.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.178.0/24 dev enp8s0 proto kernel scope link src 192.168.178.35 
metric 100
  Package: firefox 87.0+build3-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  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/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2011
  dmi.bios.release: 1.73
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JET91WW (1.49 )
  dmi.board.name: 28476NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.48
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JET91WW(1.49):bd12/12/2011:br1.73:efr1.48:svnLENOVO:pn28476NG:pvrThinkPadSL510:rvnLENOVO:rn28476NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad SL510
  dmi.product.name: 28476NG
  dmi.product.version: ThinkPad SL510
  dmi.sys.vendor: LENOVO

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

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

Re: [Desktop-packages] [Bug 1917300] Re: updated firefox 86.0 (64 bit)

[J. Cherubini]

Hi Olivier,

thank you; I did it agin - Authorized application to access Launchpad

greetings from k'town, germany

Joe


Am 23.03.21 um 21:20 schrieb Olivier Tilloy:
> apport-collect 1917300

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

Title:
  updated firefox 86.0 (64 bit)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  updated firefox 86.0 (64 bit) starts and colored pixels blinking all around 
the screen; cannot use it any more.
  Using a ThinkPad SL 510, 4 GB RAM
  Ubuntu 20.04 LTS
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe 878 F pulseaudio
   /dev/snd/controlC1:  joe 878 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-08 (137 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.178.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.178.0/24 dev enp8s0 proto kernel scope link src 192.168.178.35 
metric 100
  Package: firefox 87.0+build3-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  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/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2011
  dmi.bios.release: 1.73
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JET91WW (1.49 )
  dmi.board.name: 28476NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.48
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JET91WW(1.49):bd12/12/2011:br1.73:efr1.48:svnLENOVO:pn28476NG:pvrThinkPadSL510:rvnLENOVO:rn28476NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad SL510
  dmi.product.name: 28476NG
  dmi.product.version: ThinkPad SL510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917300/+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 1917300] PulseList.txt

[J. Cherubini]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1917300/+attachment/5481079/+files/PulseList.txt

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

Title:
  updated firefox 86.0 (64 bit)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  updated firefox 86.0 (64 bit) starts and colored pixels blinking all around 
the screen; cannot use it any more.
  Using a ThinkPad SL 510, 4 GB RAM
  Ubuntu 20.04 LTS
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe 878 F pulseaudio
   /dev/snd/controlC1:  joe 878 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-08 (137 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.178.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.178.0/24 dev enp8s0 proto kernel scope link src 192.168.178.35 
metric 100
  Package: firefox 87.0+build3-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  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/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2011
  dmi.bios.release: 1.73
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JET91WW (1.49 )
  dmi.board.name: 28476NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.48
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JET91WW(1.49):bd12/12/2011:br1.73:efr1.48:svnLENOVO:pn28476NG:pvrThinkPadSL510:rvnLENOVO:rn28476NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad SL510
  dmi.product.name: 28476NG
  dmi.product.version: ThinkPad SL510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917300/+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 1917300] PciNetwork.txt

[J. Cherubini]

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1917300/+attachment/5481076/+files/PciNetwork.txt

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

Title:
  updated firefox 86.0 (64 bit)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  updated firefox 86.0 (64 bit) starts and colored pixels blinking all around 
the screen; cannot use it any more.
  Using a ThinkPad SL 510, 4 GB RAM
  Ubuntu 20.04 LTS
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe 878 F pulseaudio
   /dev/snd/controlC1:  joe 878 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-08 (137 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.178.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.178.0/24 dev enp8s0 proto kernel scope link src 192.168.178.35 
metric 100
  Package: firefox 87.0+build3-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  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/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2011
  dmi.bios.release: 1.73
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JET91WW (1.49 )
  dmi.board.name: 28476NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.48
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JET91WW(1.49):bd12/12/2011:br1.73:efr1.48:svnLENOVO:pn28476NG:pvrThinkPadSL510:rvnLENOVO:rn28476NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad SL510
  dmi.product.name: 28476NG
  dmi.product.version: ThinkPad SL510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917300/+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 1917300] Lspci.txt

[J. Cherubini]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1917300/+attachment/5481075/+files/Lspci.txt

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

Title:
  updated firefox 86.0 (64 bit)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  updated firefox 86.0 (64 bit) starts and colored pixels blinking all around 
the screen; cannot use it any more.
  Using a ThinkPad SL 510, 4 GB RAM
  Ubuntu 20.04 LTS
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe 878 F pulseaudio
   /dev/snd/controlC1:  joe 878 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-08 (137 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.178.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.178.0/24 dev enp8s0 proto kernel scope link src 192.168.178.35 
metric 100
  Package: firefox 87.0+build3-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  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/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2011
  dmi.bios.release: 1.73
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JET91WW (1.49 )
  dmi.board.name: 28476NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.48
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JET91WW(1.49):bd12/12/2011:br1.73:efr1.48:svnLENOVO:pn28476NG:pvrThinkPadSL510:rvnLENOVO:rn28476NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad SL510
  dmi.product.name: 28476NG
  dmi.product.version: ThinkPad SL510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917300/+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 1917300] Profile0Prefs.txt

[J. Cherubini]

apport information

** Attachment added: "Profile0Prefs.txt"
   
https://bugs.launchpad.net/bugs/1917300/+attachment/5481078/+files/Profile0Prefs.txt

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

Title:
  updated firefox 86.0 (64 bit)

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  updated firefox 86.0 (64 bit) starts and colored pixels blinking all around 
the screen; cannot use it any more.
  Using a ThinkPad SL 510, 4 GB RAM
  Ubuntu 20.04 LTS
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe 878 F pulseaudio
   /dev/snd/controlC1:  joe 878 F pulseaudio
  BuildID: 20210318103112
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  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/omni.ja:greprefs.js:352
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-11-08 (137 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.178.1 dev enp8s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp8s0 scope link metric 1000 
   192.168.178.0/24 dev enp8s0 proto kernel scope link src 192.168.178.35 
metric 100
  Package: firefox 87.0+build3-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  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/omni.ja:greprefs.js:352
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=87.0/20210318103112
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.8.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2011
  dmi.bios.release: 1.73
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JET91WW (1.49 )
  dmi.board.name: 28476NG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.48
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JET91WW(1.49):bd12/12/2011:br1.73:efr1.48:svnLENOVO:pn28476NG:pvrThinkPadSL510:rvnLENOVO:rn28476NG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad SL510
  dmi.product.name: 28476NG
  dmi.product.version: ThinkPad SL510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917300/+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