date:20220711

** Also affects: xserver-xorg-video-ati (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: xserver-xorg-video-ati (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: xserver-xorg-video-ati (Ubuntu Jammy)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

** Also affects: xserver-xorg-video-ati (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009325
   Importance: Unknown
   Status: Unknown

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

Title:
  [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

Status in xserver-xorg-video-ati package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-ati source package in Jammy:
  Fix Committed
Status in xserver-xorg-video-ati package in Debian:
  Unknown

Bug description:
  * Impact

  The xserver crash, closing the session, when trying to rotate the
  screen when using the ati driver

  * Test case
  - start an xorg based session
  - try to rotate the screen by 90°

  -> the session shouldn't close

  * Regression potential

  if the fix was incorrect it could lead to screen parameters not being
  set correctly. Try changing the resolution and rotation and ensure the
  changes are what is expected

  

  
  When using Settings/Display/Orientation/Portret right and Apply then X 
crashes and login screen is displayed. Tested with 3 different AMD systems 
(older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6005 Pro MT PC
  dmi.product.sku: AT493AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1970473/+subscriptions


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

[Desktop-packages] [Bug 1973143] Re: [impish] Wayland session limited to 1024x768

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

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

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

Title:
  [impish] Wayland session limited to 1024x768

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Even though my monitor support maximum resolution, I can only set it
  to 1024x768.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 12 13:21:28 2022
  DistUpgraded: 2022-05-02 12:21:49,539 DEBUG /openCache(), new cache size 70582
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.12.5, 5.13.0-40-generic, x86_64: installed
   v4l2loopback, 0.12.5, 5.13.0-41-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
     Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c]
  InstallationDate: Installed on 2022-03-02 (70 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20351
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to impish on 2022-05-02 (10 days ago)
  dmi.bios.date: 10/20/2014
  dmi.bios.release: 0.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.ec.firmware.release: 0.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:br0.29:efr0.29:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:skuLENOVO_MT_20351_BU_idea_FM_LenovoG50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20351
  dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Desktop-packages] [Bug 1973143] Re: [impish] Wayland session limited to 1024x768

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

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

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

Title:
  [impish] Wayland session limited to 1024x768

Status in linux package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  Even though my monitor support maximum resolution, I can only set it
  to 1024x768.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
  Uname: Linux 5.13.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 12 13:21:28 2022
  DistUpgraded: 2022-05-02 12:21:49,539 DEBUG /openCache(), new cache size 70582
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback, 0.12.5, 5.13.0-40-generic, x86_64: installed
   v4l2loopback, 0.12.5, 5.13.0-41-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c]
     Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c]
  InstallationDate: Installed on 2022-03-02 (70 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: LENOVO 20351
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to impish on 2022-05-02 (10 days ago)
  dmi.bios.date: 10/20/2014
  dmi.bios.release: 0.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.ec.firmware.release: 0.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:br0.29:efr0.29:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:skuLENOVO_MT_20351_BU_idea_FM_LenovoG50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20351
  dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

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


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

[Desktop-packages] [Bug 1980824] Re: ibus pinyin make crash the system (ubuntumate 22.04)

2022-07-11 Thread Massimo

** Project changed: ubuntu-mate => ubuntu

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

Title:
  ibus pinyin make crash the system (ubuntumate 22.04)

Status in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  When I try to set up ibus pinyin the system (ubuntu mate 22.04) crash.

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


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

[Desktop-packages] [Bug 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU

I suggest your next step should be to reach out to the AMD graphics and
Mesa developers by reporting the issue on one or both of:

  https://gitlab.freedesktop.org/drm/amd/-/issues
  https://gitlab.freedesktop.org/mesa/mesa/-/issues

Assuming you can't find the problem in those lists already.

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

Title:
  UI glitches (coloured squares) in GTK application with AMDGPU

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After updating to (K)ubuntu 22.04, I see user interface glitches in
  GTK application.

  Most obviously affected is Gimp, but Evolution and Eclipse IDE are
  affected, too.

  The glitches don't appear on a notebook with Intel graphics, so maybe
  the problem is caused by a weird interaction between the AMDGPU X.Org
  driver (I use a Radeon RX5600XT) and GTK.

  But as the KDE desktop itself isn't affected and only GTK application
  show these glitches, I think it's not a general problem with AMDGPU.

  I also booted both Kubunutu and Ubuntu live images and installed Gimp:
  The effect shows up there, too. So it's not only a problem of my
  current installation.

  I will upload some Gimp screenshots, so you can see what I mean...

  I'm not sure, but I tried to find the library used by all affected
  application: Maybe it's libcairo2, maybe not...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libcairo2 1.16.0-5ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jun 17 12:36:26 2022
  InstallationDate: Installed on 2022-04-27 (50 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: cairo
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  stieler1622 F pulseaudio
   /dev/snd/pcmC3D0p:   stieler1622 F...m pulseaudio
   /dev/snd/controlC2:  stieler1622 F pulseaudio
   /dev/snd/controlC1:  stieler1622 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller])
 Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 
XT / 5700/5700 XT] [148c:2402]
  InstallationDate: Installed on 2022-04-27 (55 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7B98
  Package: mesa (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  RfKill:
   
  Tags:  jammy ubuntu
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 11/17/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.E1
  dmi.board.asset.tag: Default string
  dmi.board.name: Z390-A PRO (MS-7B98)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7B98
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  vers

[Desktop-packages] [Bug 1981383] [NEW] package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

2022-07-11 Thread Nonokazi Cele

Public bug reported:

Unable to use or turn on bluetooth

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3.6
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jul 12 04:11:50 2022
ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2022-02-06 (155 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540MA_F543MA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=a1980608-1f3e-4705-9432-421aa3851fe6 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: bluez
Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/01/2019
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X540MA.314
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X540MA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540MA.314:bd10/01/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540MA_F543MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: VivoBook
dmi.product.name: VivoBook 15_ASUS Laptop X540MA_F543MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: C0:E4:34:24:68:A6  ACL MTU: 820:8  SCO MTU: 255:12
DOWN 
RX bytes:1154613008 acl:1610113 sco:0 events:493522 errors:0
TX bytes:35384460 acl:492878 sco:0 commands:420 errors:0
rfkill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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


** Tags: amd64 apport-package focal

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

Title:
  package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed
  bluez package post-installation script subprocess returned error exit
  status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  Unable to use or turn on bluetooth

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jul 12 04:11:50 2022
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2022-02-06 (155 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540MA_F543MA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic 
root=UUID=a1980608-1f3e-4705-9432-421aa3851fe6 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: bluez
  Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed 
bluez package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540MA.314
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540MA.314:bd10/01/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540MA_F543MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook 15_ASUS Laptop X540MA_F543MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: C0:E4:34:24:68:A6  ACL MTU

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

2022-07-11 Thread li

The libva 2.6 is not the my native ubunut.  As many users reported: Post
#135, #134, #130, the libva 2.6 is comes from snap package.  It is
default apt install libva version.  In the snap build, there is libva
source build for latest 2.14, but the path is not overridden the default
install path. This is what I understand that there are two libva in the
snap: one is default libva 2.6, anther is libva 2.14 build from path.

In post #131, #110 I point this.  I guess it is the root problem caused
my hardware configure has not been supported by current snap 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/1816497

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the snap with

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if 
possible;
  - Distro version (if in doubt, `grep VERSION= /etc/os_release`);
  - GPU (if in doubt, attach the output of `lscpu`);
  - CPU generation (if in doubt, attach the output of `lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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


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

[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish

2022-07-11 Thread fprietog

Unfortunately I'm still having this problem.
Just tested in Ubuntu 22.04 amd64 and arm64. No updates or phased updates 
pending...

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

Title:
  text in torrent info tabs change after opening it to gibberish

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  on transmission-gtk

  after opening the torrent's properties panel, the text at first it's showing 
ok, buy on mouse hover it changes to random text
  worked fine on 21.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 17 19:28:03 2022
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago)

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


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

[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish

2022-07-11 Thread Daniel

Just tried recreating the issue and I'm no longer getting the bug
either.

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

Title:
  text in torrent info tabs change after opening it to gibberish

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  on transmission-gtk

  after opening the torrent's properties panel, the text at first it's showing 
ok, buy on mouse hover it changes to random text
  worked fine on 21.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 17 19:28:03 2022
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago)

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


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

[Desktop-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

2022-07-11 Thread agoodm

I edited /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
changing wifi.powersave = 3 to wifi.powersave = 2.

This improved the stability of the WiFi and appears to have stopped the
continuous 'roaming'.  I will keep an eye on the dhcp logs at home and
report back if the 'ping during roam' continues.

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

Title:
  Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle
  of WiFi roam events which is causing the IP address to change every
  time it roams on the WiFi network.  This is a huge problem for me
  because I install WiFi networks for a living but in general it causes
  every TCP connection over IPv4 to die every time the laptop roams to a
  new wifi cell.

  00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

  I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18.

  Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate 
with 86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE 
elem, Disable HE
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0110] 
device (wlp0s20f3): supplicant interface state: completed -> authenticating
  Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> 
authenticating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (wlp0s20f3): ip:dhcp4: restarting
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): canceled DHCP transaction
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): state changed no lease
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0113] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to 
associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 
MHz)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0463] 
device (wlp0s20f3): supplicant interface state: authenticating -> associating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0464] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
authenticating -> associating
  Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated
  Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp 
from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 
86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (wlp0s20f3): supplicant interface state: associating -> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associating 
-> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0799] 
device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0800] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associated 
-> 4way_handshake
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key 
negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=]
  Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 
20:11:15.091] [4119] (discord.cpp:551): JS console: 
["%c[GatewaySocket]","Performing an expedited heartbeat reason: network 
detected online."]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0970] 
device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566

[Desktop-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

2022-07-11 Thread agoodm

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

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

Title:
  Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle
  of WiFi roam events which is causing the IP address to change every
  time it roams on the WiFi network.  This is a huge problem for me
  because I install WiFi networks for a living but in general it causes
  every TCP connection over IPv4 to die every time the laptop roams to a
  new wifi cell.

  00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)

  I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18.

  Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate 
with 86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE 
elem, Disable HE
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0110] 
device (wlp0s20f3): supplicant interface state: completed -> authenticating
  Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> 
authenticating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0111] 
device (wlp0s20f3): ip:dhcp4: restarting
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): canceled DHCP transaction
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0112] 
dhcp4 (wlp0s20f3): state changed no lease
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0113] 
dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to 
associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 
MHz)
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0463] 
device (wlp0s20f3): supplicant interface state: authenticating -> associating
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0464] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
authenticating -> associating
  Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated
  Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 
86:2a:a8:8b:05:cb (try 1/3)
  Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp 
from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4)
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 
86:2a:a8:8b:05:cb
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
  Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (wlp0s20f3): supplicant interface state: associating -> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0779] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associating 
-> associated
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0799] 
device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0800] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: associated 
-> 4way_handshake
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key 
negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=]
  Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 
20:11:15.091] [4119] (discord.cpp:551): JS console: 
["%c[GatewaySocket]","Performing an expedited heartbeat reason: network 
detected online."]
  Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: 
CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0970] 
device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed
  Jul 11 20:11:15 littlebrat NetworkManager[1519]:   [1657566675.0975] 
device (p2p-dev-wlp0s20f3): supplicant management interface state: 
4way_handshake -> completed

  Jul 11 20:11:17 gateway-ycs dhcpd: DHCPDISCOVER from 5c:e4:2a:c3:f9:42 
(littlebrat) via br_v251
  Jul 11 20:11:17

[Desktop-packages] [Bug 1981361] Re: xdg-desktop-portal-gtk crashed with SIGSEGV in FcPatternGetString()

2022-07-11 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  xdg-desktop-portal-gtk crashed with SIGSEGV in FcPatternGetString()

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

Bug description:
  Crash occurred after installing ubuntu-desktop on Live server daily
  22.10 and running normal operations.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.10
  Package: xdg-desktop-portal-gtk 1.14.0-1build1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 11 14:37:08 2022
  ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk
  InstallationDate: Installed on 2022-07-10 (1 days ago)
  InstallationMedia: Ubuntu-Server 22.10 "Kinetic Kudu" - Alpha amd64 (20220709)
  JournalErrors: -- No entries --
  ProcCmdline: /usr/libexec/xdg-desktop-portal-gtk
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f960aba37f3:mov(%r8,%rdx,1),%edx
   PC (0x7f960aba37f3) ok
   source "(%r8,%rdx,1)" (0xff2c4435b0b8) not located in a known VMA region 
(needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: xdg-desktop-portal-gtk
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   FcPatternGetString () from /lib/x86_64-linux-gnu/libfontconfig.so.1
   ?? () from /lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libpangoft2-1.0.so.0
  Title: xdg-desktop-portal-gtk crashed with SIGSEGV in FcPatternGetString()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lxd plugdev sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1981361/+subscriptions


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

[Desktop-packages] [Bug 1958019]

2022-07-11 Thread eruyome

(In reply to Philipp Jungkamp from comment #645)
> Created attachment 301327 [details]
> Patch for the ALC287 on the Lenovo Yoga 14IAP7
> 
> I did not include the FIXUP_THINKPAD_ACPI quirk in the fixup chain as I
> don't understand what it does. Could someone explain why it is done on other
> Lenovo Hardware and whether it could be needed on the Yoga9i?

Hi,

I can confirm this patch fixes the issue for 14IAP7 (applied it manually
to 5.18.10 on arch linux). Million thanks!

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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

[Desktop-packages] [Bug 1981351] Re: libreoffice crash, undefined symbol: hb_graphite2_face_get_gr_face

2022-07-11 Thread Yash Patil

Hi @seb128
the output of the command is attached to this post. Let me know if you need 
something else 

Meanwhile I tried reinstalling libreoffice libreoffice-core libreoffice-
common packages with apt but no help, didnt solve the issue

** Attachment added: "ldd-libmergedlo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1981351/+attachment/5602418/+files/ldd-libmergedlo.txt

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

Title:
  libreoffice crash, undefined symbol: hb_graphite2_face_get_gr_face

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Libreoffice doesn't open or work

  launching from terminal errors out with following error:
  /usr/lib/libreoffice/program/soffice.bin: symbol lookup error: 
/usr/lib/libreoffice/program/libmergedlo.so: undefined symbol: 
hb_graphite2_face_get_gr_face

  A quick google search gave solution to remove 
/usr/local/lib/x86_64-linux-gnu/libharfbuzz.so.0, which works although 
temporarily
  the package "libharfbuzz0b" reinstalls this lib and it causes same error again

  Also the package libharfbuzz0b is used by other packages so cant be
  removed from apt directly, leading to no permanent solution to this
  problem

  Info about the libreoffice and libharfbuzz0b packages -

  ```
  apt list libreoffice -a
  Listing... Done
  libreoffice/jammy-updates,now 1:7.3.4-0ubuntu0.22.04.1 amd64 [installed]
  libreoffice/jammy 1:7.3.2-0ubuntu2 amd64
  ```

  ```
  apt list libharfbuzz0b -a
  Listing... Done
  libharfbuzz0b/jammy,now 2.7.4-1ubuntu3 amd64 [installed,automatic]
  libharfbuzz0b/jammy 2.7.4-1ubuntu3 i386
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice 1:7.3.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 11 23:31:01 2022
  InstallationDate: Installed on 2020-08-06 (704 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (78 days ago)

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


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

[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish

2022-07-11 Thread thom

A week ago, after an update, the bug was magically resolved.

I kept on testing but I couldn't recreate the bug anymore.

Also other gtk based applications seemed to run a bit more
reliable/solid (no crashes anymore in caja etc etc).

Could it be that some important library received an update/fix which
also solved this problem ?

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

Title:
  text in torrent info tabs change after opening it to gibberish

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  on transmission-gtk

  after opening the torrent's properties panel, the text at first it's showing 
ok, buy on mouse hover it changes to random text
  worked fine on 21.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 17 19:28:03 2022
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago)

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


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

[Desktop-packages] [Bug 1981333] Re: Firefox icon missing from application list

I think it's fair we debug this one. Do you still have the issue after a
restart?

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

Title:
  Firefox icon missing from application list

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The icon for Firefox in the applications list on Ubuntu 22.04 has gone
  missing, as shown in the attached screenshot. The launcher is still
  there with text only, and clicking on it opens Firefox with no issue.
  This is the default installation of Firefox, not modified or replaced
  by me. To be specific, snap lists Firefox as version 102.0.1-1 and
  revision 1551. I have the Steam and Chrome apt repositories, but my
  list of apt packages has nothing mentioning Firefox.

  Because I use Chrome instead, I'm mostly reporting this because it
  should be fixed for everyone else who may run into this problem, I
  don't need instructions on how to fix it myself.

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


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

[Desktop-packages] [Bug 1981351] Re: libreoffice crash, undefined symbol: hb_graphite2_face_get_gr_face

Thank you for your bug report. What's the output of

$ ldd -r /usr/lib/libreoffice/program/libmergedlo.so

?

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

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

Title:
  libreoffice crash, undefined symbol: hb_graphite2_face_get_gr_face

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Libreoffice doesn't open or work

  launching from terminal errors out with following error:
  /usr/lib/libreoffice/program/soffice.bin: symbol lookup error: 
/usr/lib/libreoffice/program/libmergedlo.so: undefined symbol: 
hb_graphite2_face_get_gr_face

  A quick google search gave solution to remove 
/usr/local/lib/x86_64-linux-gnu/libharfbuzz.so.0, which works although 
temporarily
  the package "libharfbuzz0b" reinstalls this lib and it causes same error again

  Also the package libharfbuzz0b is used by other packages so cant be
  removed from apt directly, leading to no permanent solution to this
  problem

  Info about the libreoffice and libharfbuzz0b packages -

  ```
  apt list libreoffice -a
  Listing... Done
  libreoffice/jammy-updates,now 1:7.3.4-0ubuntu0.22.04.1 amd64 [installed]
  libreoffice/jammy 1:7.3.2-0ubuntu2 amd64
  ```

  ```
  apt list libharfbuzz0b -a
  Listing... Done
  libharfbuzz0b/jammy,now 2.7.4-1ubuntu3 amd64 [installed,automatic]
  libharfbuzz0b/jammy 2.7.4-1ubuntu3 i386
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice 1:7.3.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 11 23:31:01 2022
  InstallationDate: Installed on 2020-08-06 (704 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (78 days ago)

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


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

[Desktop-packages] [Bug 1981333] Re: Firefox icon missing from application list

2022-07-11 Thread Erich Eickmeyer 

Thank you for taking the time to report this bug and help make Ubuntu
better. Firefox is provided by a snap published by Mozilla, and they may
not be aware of this issue. Please contact them via
https://support.mozilla.org/kb/file-bug-report-or-feature-request-
mozilla and link the bug report here so it can be further tracked. Thank
you!

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

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

Title:
  Firefox icon missing from application list

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  The icon for Firefox in the applications list on Ubuntu 22.04 has gone
  missing, as shown in the attached screenshot. The launcher is still
  there with text only, and clicking on it opens Firefox with no issue.
  This is the default installation of Firefox, not modified or replaced
  by me. To be specific, snap lists Firefox as version 102.0.1-1 and
  revision 1551. I have the Steam and Chrome apt repositories, but my
  list of apt packages has nothing mentioning Firefox.

  Because I use Chrome instead, I'm mostly reporting this because it
  should be fixed for everyone else who may run into this problem, I
  don't need instructions on how to fix it myself.

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


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

[Desktop-packages] [Bug 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled

2022-07-11 Thread Treviño

** Also affects: gnome-shell (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Jammy)
   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/1979096

Title:
  gnome-shell search can't launch apps if dock auto-hide is enabled

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

Bug description:
  The problem happens, when I enable the dock to hide automatically.
  With this enabled, it is not possible to run the programs through the
  search. But when disabled, it is possible to search and run the
  programs. Here's the video of the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 17 18:21:45 2022
  DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed
   v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388]
  InstallationDate: Installed on 2021-04-15 (428 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago)
  dmi.bios.date: 03/04/2017
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1201
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M LX/BR
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1981351] [NEW] libreoffice crash, undefined symbol: hb_graphite2_face_get_gr_face

2022-07-11 Thread Yash Patil

Public bug reported:

Libreoffice doesn't open or work

launching from terminal errors out with following error:
/usr/lib/libreoffice/program/soffice.bin: symbol lookup error: 
/usr/lib/libreoffice/program/libmergedlo.so: undefined symbol: 
hb_graphite2_face_get_gr_face

A quick google search gave solution to remove 
/usr/local/lib/x86_64-linux-gnu/libharfbuzz.so.0, which works although 
temporarily
the package "libharfbuzz0b" reinstalls this lib and it causes same error again

Also the package libharfbuzz0b is used by other packages so cant be
removed from apt directly, leading to no permanent solution to this
problem

Info about the libreoffice and libharfbuzz0b packages -

```
apt list libreoffice -a
Listing... Done
libreoffice/jammy-updates,now 1:7.3.4-0ubuntu0.22.04.1 amd64 [installed]
libreoffice/jammy 1:7.3.2-0ubuntu2 amd64
```

```
apt list libharfbuzz0b -a
Listing... Done
libharfbuzz0b/jammy,now 2.7.4-1ubuntu3 amd64 [installed,automatic]
libharfbuzz0b/jammy 2.7.4-1ubuntu3 i386
```

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libreoffice 1:7.3.4-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 11 23:31:01 2022
InstallationDate: Installed on 2020-08-06 (704 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to jammy on 2022-04-24 (78 days ago)

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


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

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

Title:
  libreoffice crash, undefined symbol: hb_graphite2_face_get_gr_face

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Libreoffice doesn't open or work

  launching from terminal errors out with following error:
  /usr/lib/libreoffice/program/soffice.bin: symbol lookup error: 
/usr/lib/libreoffice/program/libmergedlo.so: undefined symbol: 
hb_graphite2_face_get_gr_face

  A quick google search gave solution to remove 
/usr/local/lib/x86_64-linux-gnu/libharfbuzz.so.0, which works although 
temporarily
  the package "libharfbuzz0b" reinstalls this lib and it causes same error again

  Also the package libharfbuzz0b is used by other packages so cant be
  removed from apt directly, leading to no permanent solution to this
  problem

  Info about the libreoffice and libharfbuzz0b packages -

  ```
  apt list libreoffice -a
  Listing... Done
  libreoffice/jammy-updates,now 1:7.3.4-0ubuntu0.22.04.1 amd64 [installed]
  libreoffice/jammy 1:7.3.2-0ubuntu2 amd64
  ```

  ```
  apt list libharfbuzz0b -a
  Listing... Done
  libharfbuzz0b/jammy,now 2.7.4-1ubuntu3 amd64 [installed,automatic]
  libharfbuzz0b/jammy 2.7.4-1ubuntu3 i386
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice 1:7.3.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 11 23:31:01 2022
  InstallationDate: Installed on 2020-08-06 (704 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (78 days ago)

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


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

[Desktop-packages] [Bug 1981349] [NEW] wslu prevents from opening files and folders on some situations

2022-07-11 Thread José Marinho

Public bug reported:

With wslu installed, files and locations can't be opened from Gnome Activities 
View either on a Wayland session or a Xorg one. This affects too when I try to 
open from Places Status Indicator.In fact, I filed a bug some time ago, but 
that bug was expired. Now I found the reason and file a bug against the proper 
package.
The bug is this one: 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181
And I realized when I saw this thread: 
https://answers.launchpad.net/ubuntu/+question/701579

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

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

Title:
  wslu prevents from opening files and folders on some situations

Status in wslu package in Ubuntu:
  New

Bug description:
  With wslu installed, files and locations can't be opened from Gnome 
Activities View either on a Wayland session or a Xorg one. This affects too 
when I try to open from Places Status Indicator.In fact, I filed a bug some 
time ago, but that bug was expired. Now I found the reason and file a bug 
against the proper package.
  The bug is this one: 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/1970181
  And I realized when I saw this thread: 
https://answers.launchpad.net/ubuntu/+question/701579

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


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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

@li, how do you get libva 2.6? that's different from what you posted in
#129, what did you change?

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  To test the snap with VA-API changes,

  1. Install the snap with

     sudo snap install --channel candidate/hwacc chromium

  2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
  --enable-features=VaapiVideoDecoder

  3. Open a video, e.g. one from https://github.com/chthomos/video-
  media-samples

  4. Enter about:media-internals in the address bar and note what the
  page says for kVideoDecoderName.

  Please report

  - The value for kVideoDecoderName from step 4. Success is typically 
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if 
possible;
  - Distro version (if in doubt, `grep VERSION= /etc/os_release`);
  - GPU (if in doubt, attach the output of `lscpu`);
  - CPU generation (if in doubt, attach the output of `lscpu`).

  About the last point, it may be that unfortunately only those with
  newer generations of Intel CPUs will have luck with this, but it's
  still an uncertainty. So reports are highly welcome.

  --Original Bug report -

  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileVC1Simple  :   VAEntrypointVLD
    VAProfileVC1Main:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
    VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileHEVCMain   :   VAEntrypointVLD
    VAProfileHEVCMain10 :   VAEntrypointVLD
    VAProfileJPEGBaseline   :   VAEntrypointVLD
    VAProfileNone   :   VAEntrypointVideoProc`

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


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

[Desktop-packages] [Bug 1975884] Re: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"

2022-07-11 Thread Vivek Gani

Confirming I did not have gsconnect or any non-system extensions
installed for the journalctl's shared in comments #10 (
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1975884/comments/10 ) or #11 (
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1975884/comments/11 ) or #12 (
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1975884/comments/12 ).

I did have Ubuntu Dock disabled but wouldn't expect that to make a
difference.

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

Title:
  Temporary screen freeze when gnome-shell logs "Removing a network
  device that was not added"

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1769981/comments/25 , I've been observing an issue when
  unlocking my computer (usually from a screen lock state, not
  hibernation/sleep) where after entering the first few characters of my
  password the screen freezes for 10-20 seconds before I can do any type
  of input (mouse, touch, keyboard).

  I've also seen it happen when having touch / gesture input switch
  between displaying the user name and the password field - where the
  screen can get stuck in the animation in an interstitial state for a
  number of seconds.

  I've largely been noticing this since upgrading from Ubuntu 21.10 to
  22.04. It doesn't happen all the time, but often enough to file an
  issue for.

  So far I've tried:
  - Disabling the 'blur my shell' extension - still encountered the issue again 
eventually.
  - Looking for anything associated with this in /var/crash - couldn't find 
anything.
  - Looking for anything associated at errors.ubuntu.com for my id.

  What I may eventually try:
  - Seeing if this may depend on having too many browser tabs / apps open. 
Currently not in a position to do this.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 26 19:19:28 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-07-15 (315 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago)

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


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

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

2022-07-11 Thread Jeremy Bicha

** Description changed:

  Impact
  --
  Videos are unplayable in apps like Ubuntu's default video player for people 
using some Intel graphics cards including Ivy Bridge.
  
  Test Case
  -
  On an affected system, install the update.
  Then try playing the video.
  It should display normally.
  
  What Could Go Wrong
  ---
- This is being handled as part of the gstreamer 1.20.3 updates LP: #1980239
- 
- If one of the fixes is bad then it might break video or audio playback,
- or could crash any application that tries to use gstreamer.
+ If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.
  
  Original Bug Report
  ---
  Ubuntu 22.04 freshly installed along with ubuntu-restricted-extra package. 
Default totem player unable to play videos properly. videos looks distorted. 
Forwarding videos does not work. Video get stopped once forwarded.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 23 11:02:49 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2022-04-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 34601F4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.release: 2.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34601F4
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 34601F4
  dmi.product.sku: LENOVO_MT_3460
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Composi

[Desktop-packages] [Bug 1979347] Re: SRU pygobject 3.42.1, including fix for the append function

The failing autopkgtest worked after a retry and were mostly due to
builder issues

The one error remaining is fwupd which fails on
 libudev-dev : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.3 is 
to be installed

which isn't due to pygobject update

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

Title:
  SRU pygobject 3.42.1, including fix for the append function

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

Bug description:
  >> Impact <<

  Applications crash when they call the append function to append data
  to stores.

  >> Test plan <<

  When executing the attached bug.py script,

  - With the fix: A dummy window with a text field is mapped.

  - Without the fix: An error message is raised and no window is mapped.

  >> Regression potential <<

  Since this includes a new upstream release, by looking at the NEWS
  file ,
  regressions could show up:

  - On programs which use ListStore and Treeview. Additionally, those
  changes should not affect GTK2 or GTK3.

  - As leaks, given the replace of g_error by g_critical by
  .

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


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

[Desktop-packages] [Bug 1970473] Re: [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

SRU uploaded to the 22.04 review queue now

** Description changed:

- When using Settings/Display/Orientation/Portret right and Apply then X
- crashes and login screen is displayed. Tested with 3 different AMD
- systems (older). Bug is not present with Intel graphics
+ * Impact
+ 
+ The xserver crash, closing the session, when trying to rotate the screen
+ when using the ati driver
+ 
+ * Test case
+ - start an xorg based session
+ - try to rotate the screen by 90°
+ 
+ -> the session shouldn't close
+ 
+ * Regression potential
+ 
+ if the fix was incorrect it could lead to screen parameters not being
+ set correctly. Try changing the resolution and rotation and ensure the
+ changes are what is expected
+ 
+ 
+ 
+ 
+ When using Settings/Display/Orientation/Portret right and Apply then X 
crashes and login screen is displayed. Tested with 3 different AMD systems 
(older). Bug is not present with Intel graphics
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
+  Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=ro_RO.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=ro_RO.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6005 Pro MT PC
  dmi.product.sku: AT493AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

Title:
  [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

Status in xserver-xorg-video-ati package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  The xserver crash, closing the session, when trying to rotate the
  screen when using the ati driver

  * Test case
  - start an xorg based session
  - try to rotate the screen by 90°

  -> the session shouldn't close

  * Regression potential

  if the fix was incorrect it could lead to screen parameters not being
  set correctly. Try changing the resolution and rotation and ensure the
  changes are what is expected

  

  
  When using Settings/Display/Orientation/Portret right and Apply then X 
crashes and login screen is displayed. Tested with 3 different AMD systems 
(older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  U

[Desktop-packages] [Bug 1981336] [NEW] PCI/internal sound card not detected

2022-07-11 Thread Fernando Marcelino Muniz

Public bug reported:

Ubuntu 22.04 LTS (Kernel updated to version 5.18.10) is unable to
detect/display the sound card of Samsung Galaxy Book S - SAMSUNG
ELECTRONICS CO., LTD. 767XCL

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
Uname: Linux 5.18.10-051810-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 11 11:55:30 2022
InstallationDate: Installed on 2022-07-09 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2020
dmi.bios.release: 5.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P07AJD.053.200820.KS
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP767XCM-K02BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGLA829A06-C01-G001-S0005+10.0.19042
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07AJD.053.200820.KS:bd08/20/2020:br5.15:svnSAMSUNGELECTRONICSCO.,LTD.:pn767XCL:pvrP07AJD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP767XCM-K02BR:rvrSGLA829A06-C01-G001-S0005+10.0.19042:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAJD:
dmi.product.family: Galaxy Book Series
dmi.product.name: 767XCL
dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAJD
dmi.product.version: P07AJD
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 LTS (Kernel updated to version 5.18.10) is unable to
  detect/display the sound card of Samsung Galaxy Book S - SAMSUNG
  ELECTRONICS CO., LTD. 767XCL

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  Uname: Linux 5.18.10-051810-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 11 11:55:30 2022
  InstallationDate: Installed on 2022-07-09 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2020
  dmi.bios.release: 5.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P07AJD.053.200820.KS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP767XCM-K02BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLA829A06-C01-G001-S0005+10.0.19042
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07AJD.053.200820.KS:bd08/20/2020:br5.15:svnSAMSUNGELECTRONICSCO.,LTD.:pn767XCL:pvrP07AJD:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP767XCM-K02BR:rvrSGLA829A06-C01-G001-S0005+10.0.19042:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAJD:
  dmi.product.family: Galaxy Book Series
  dmi.product.name: 767XCL
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAJD
  dmi.product.version: P07AJD
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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

[Desktop-packages] [Bug 1981333] [NEW] Firefox icon missing from application list

2022-07-11 Thread Rachel Hoots

Public bug reported:

The icon for Firefox in the applications list on Ubuntu 22.04 has gone
missing, as shown in the attached screenshot. The launcher is still
there with text only, and clicking on it opens Firefox with no issue.
This is the default installation of Firefox, not modified or replaced by
me. To be specific, snap lists Firefox as version 102.0.1-1 and revision
1551. I have the Steam and Chrome apt repositories, but my list of apt
packages has nothing mentioning Firefox.

Because I use Chrome instead, I'm mostly reporting this because it
should be fixed for everyone else who may run into this problem, I don't
need instructions on how to fix it myself.

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

** Attachment added: "Firefox icon is missing, but clicking on it still works"

https://bugs.launchpad.net/bugs/1981333/+attachment/5602375/+files/Screenshot%20from%202022-07-11%2010-46-35.png

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

Title:
Firefox icon missing from application list

Status in firefox package in Ubuntu:
New

Bug description:
The icon for Firefox in the applications list on Ubuntu 22.04 has gone
missing, as shown in the attached screenshot. The launcher is still
there with text only, and clicking on it opens Firefox with no issue.
This is the default installation of Firefox, not modified or replaced
by me. To be specific, snap lists Firefox as version 102.0.1-1 and
revision 1551. I have the Steam and Chrome apt repositories, but my
list of apt packages has nothing mentioning Firefox.

Because I use Chrome instead, I'm mostly reporting this because it
should be fixed for everyone else who may run into this problem, I
don't need instructions on how to fix it myself.

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

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

[Desktop-packages] [Bug 1981286] Re: Firefox will not start if home folder not in /home

** Package changed: firefox (Ubuntu) => snapd (Ubuntu)

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

Title:
  Firefox will not start if home folder not in /home

Status in snapd package in Ubuntu:
  New

Bug description:
  When a user's home directory is not in /home Firefox will not start.
  If I try to start Firefox from the command line the following message
  is output.

  Sorry, home directories outside of /home are not currently supported. 
  See https://forum.snapcraft.io/t/11209 for details.

  It appears this is a result of the decision to use Snap to install
  Firefox.  If so then this shouldn't have happened until the limitation
  on Snap had been removed.

  Kubuntu 22.04
  Firefox 102.0.1-1

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


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

[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04

Testing 6.4-4ubuntu3

- upgrading from focal gives a rules without the generic ID as expected. 
 -upgrading from jammy without a matching device connected, the rules doesn't 
include the generic IDs as expected and the extra rules isn't installed
- upgrading from jammy with a matching device connected, the user is correctly 
debconf prompted and the rules is installed depending of the answer to the 
question

settings as verified

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

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

Title:
  brltty claiming cp210x devices on 22.04

Status in brltty package in Ubuntu:
  Fix Released
Status in brltty source package in Jammy:
  Fix Committed
Status in brltty package in Debian:
  Confirmed

Bug description:
  * Impact

  The brltty udev rules are claiming generic devices IDs which makes
  some other devices like Arduino cards not able to interact with the
  serial port anymore

  * Test Case

  Try to use an Arduino over a cp210x or FTDI serial port, it should be
  able to talk to the computer

  - upgrades from focal/impish to the SRU version should have no
  question and no /etc/udev/rules.d/86-brltty-usbgeneric.rules generated

  - upgrades from brltty 6.4-4ubuntu2
  1. if a device matching the IDs 0403:6001 / 10C4:EA60 / 10C4:EA80 is 
connectect at the time of the upgrade it should prompt with the debconf question
  1.a if the answer is yes, /etc/udev/rules.d/86-brltty-usbgeneric.rules should 
be generated
  1.b if the answer is no, /etc/udev/rules.d/86-brltty-usbgeneric.rules not 
installed

  2. if no matching device is connected
  there should be no debconf question nor 
/etc/udev/rules.d/86-brltty-usbgeneric.rules generated

  - installing brltty when it was not installed
  no question and no config generated

  * Regression potential

  If the debconf logic is wrong users could be prompted with the
  question when not needed or not prompted when they should. If the udev
  rules was incorrect or wrongly installed it could lead to have brltty
  not starting when it should

  ---

  Distributor ID:   Ubuntu
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04
  Codename: jammy
  brltty:  Installed: 6.4-2ubuntu1

   brltty appears once again to be claiming cp210x devices with the
  vendor/product ID of:

  idVendor=10c4, idProduct=ea60

  Example dmesg output:
    999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, 
bcdDevice= 1.00
  [  999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [  999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge
  [  999.215977] usb 3-6.3: Manufacturer: Silicon Labs
  [  999.215978] usb 3-6.3: SerialNumber: 0005
  [  999.234070] usbcore: registered new interface driver usbserial_generic
  [  999.234081] usbserial: USB Serial support registered for generic
  [  999.235262] usbcore: registered new interface driver cp210x
  [  999.235272] usbserial: USB Serial support registered for cp210x
  [  999.235298] cp210x 3-6.3:1.0: cp210x converter detected
  [  999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0
  [  999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41
  [  999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as 
/devices/virtual/input/input42
  [  999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' 
sets config #1
  [  999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
  [  999.995066] cp210x 3-6.3:1.0: device disconnected

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


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

[Desktop-packages] [Bug 1981163] Re: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince

2022-07-11 Thread Xavier Guillot

Hi, both deb versions - no snap

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

Title:
  In Compose window, if a PDf is joined and clicked to open, Thunderbird
  launches Firefox instead of Evince

Status in thunderbird package in Ubuntu:
  New

Bug description:
  In Thunderbird on Ubuntu Gnome, I set Evince as default program to
  open pdf files from Thunderbird.

  In received messages, and those saved on "Sent" folder, it works
  perfectly.

  But in the "Compose" window: if I add a pdf file to the message, and
  double-click on it to open and verify it, Thunderbird always uses
  Firefox to show it.

  In case Firefox is not installed (has been removed), I have an error
  message telling there is not associated application for pdf files and
  to go to Preferences - where Evince is already and still defined as
  default.

  It happens since many months and bug is still present in Thunderbird
  102 / Ubuntu 22.10 beta.

  It's not the same as bug 234349 as here, it's not an URL file but
  directly a pdf joined in a mail.

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


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

[Desktop-packages] [Bug 1981286] [NEW] Firefox will not start if home folder not in /home

2022-07-11 Thread Tony Middleton

Public bug reported:

When a user's home directory is not in /home Firefox will not start.  If
I try to start Firefox from the command line the following message is
output.

Sorry, home directories outside of /home are not currently supported. 
See https://forum.snapcraft.io/t/11209 for details.

It appears this is a result of the decision to use Snap to install
Firefox.  If so then this shouldn't have happened until the limitation
on Snap had been removed.

Kubuntu 22.04
Firefox 102.0.1-1

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

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

Title:
  Firefox will not start if home folder not in /home

Status in firefox package in Ubuntu:
  New

Bug description:
  When a user's home directory is not in /home Firefox will not start.
  If I try to start Firefox from the command line the following message
  is output.

  Sorry, home directories outside of /home are not currently supported. 
  See https://forum.snapcraft.io/t/11209 for details.

  It appears this is a result of the decision to use Snap to install
  Firefox.  If so then this shouldn't have happened until the limitation
  on Snap had been removed.

  Kubuntu 22.04
  Firefox 102.0.1-1

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


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

[Desktop-packages] [Bug 1980239] Re: Update gstreamer to 1.20.3

2022-07-11 Thread Jeremy Bicha

** Changed in: gst-python1.0 (Ubuntu Jammy)
   Status: Incomplete => Won't Fix

** Changed in: gstreamer-vaapi (Ubuntu Jammy)
   Status: In Progress => Triaged

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

Title:
  Update gstreamer to 1.20.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Jammy:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Jammy:
  Fix Committed
Status in gst-plugins-good1.0 source package in Jammy:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Jammy:
  In Progress
Status in gst-python1.0 source package in Jammy:
  Won't Fix
Status in gst-rtsp-server1.0 source package in Jammy:
  In Progress
Status in gstreamer-editing-services1.0 source package in Jammy:
  Incomplete
Status in gstreamer-vaapi source package in Jammy:
  Triaged
Status in gstreamer1.0 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two 
bugfix stable releases. 

  https://gstreamer.freedesktop.org/releases/1.20/#1.20.2
  https://gstreamer.freedesktop.org/releases/1.20/#1.20.3

  Test Case 1
  ---
  We now run upstream's test suite for most gstreamer components at build time 
and fail the build for errors on our key desktop architectures, amd64 & arm64.

  Ensure the builds succeeed.

  Test Case 2
  ---
  Play a variety of videos in Totem. Play a variety of audio tracks in 
Rhythmbox. Try to stream audio and/or video. Try to install a missing codec.

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

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

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


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

[Desktop-packages] [Bug 1980975] Re: Rubbish Bin Context Menu references wrong name

It's an en_GB translation issue

https://translations.launchpad.net/ubuntu/jammy/+source/nautilus/+pots/nautilus/en_GB/814/+translate

** Package changed: nautilus (Ubuntu) => language-pack-gnome-en (Ubuntu)

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

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

Title:
  Rubbish Bin Context Menu references wrong name

Status in Ubuntu Translations:
  New
Status in language-pack-gnome-en package in Ubuntu:
  Confirmed

Bug description:
  When right clicking the rubbish bin in the file explorer or dock, the
  context menu says "Empty wastebasket". This is an inconsistent
  reference as it is now referred to as Rubbish Bin across the Ubuntu
  OS.

  Even in the File Explorer - Rubbish Bin, the "Empty..." button tooltip
  describes "Delete all items in the Rubbish Bin".

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


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

[Desktop-packages] [Bug 1339832] Re: Apport reported a problem so I forwarded it to you guys. Don't know what the problem may be but I love this OS.

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Apport reported a problem so I forwarded it to you guys. Don't know
  what the problem may be but I love this OS.

Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Just a Apport popup. I'm not having problems otherwise. Great OS!
  Thank you.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.15.1-0ubuntu8
  Uname: Linux 3.16.0-031600rc4-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Wed Jul  9 08:10:16 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:ff67]
 Subsystem: Toshiba America Info Systems Device [1179:ff67]
  InstallationDate: Installed on 2014-07-01 (8 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140619)
  MachineType: TOSHIBA Satellite L305
  ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-031600rc4-generic 
root=UUID=35fc13c4-8ad9-48bb-b4a7-70ab74ba2fa8 ro init=/lib/systemd/systemd
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   ?? ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/09/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd12/09/2009:svnTOSHIBA:pnSatelliteL305:pvrPSLB8U-0JG037:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite L305
  dmi.product.version: PSLB8U-0JG037
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Jul  9 14:03:56 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   14145 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu8

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


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

[Desktop-packages] [Bug 1979289] Re: Network icon in GNOME title bar flickers sporadically with network bridge

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

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

Title:
  Network icon in GNOME title bar flickers sporadically with network
  bridge

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After creating a network bridge (for QEMU), the network connection on the top 
right flickers, which means it sporadically disappears and then appears again 
after a short while.
  The time between the icon disappearing ranges between 5 minutes and 45 
minutes, most of the time it's around 10 minutes.
  The time between the icon re-appearing ranges between 1 seconds and 2 
minutes, most of the time it's gone for around 3 seconds.
  There's no apparent correlation to any user behaviour, it happens independent 
of the network being idle or under load.

  The physical network traffic is not affected, i.e. the network
  connection still works while the icon is gone.

  The network bridge was created with 'nmcli' according to this guide
  and works flawlessly: https://www.answertopia.com/ubuntu/creating-an-
  ubuntu-kvm-networked-bridge-interface/

  
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  package and configuration details: see attachment

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


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

[Desktop-packages] [Bug 1981117] Re: Bluetooth icon appears and disappears after reboot

Three issues here:

1. The log messages you mention are from the kernel, and probably not
important.

2. The flickering GUI is definitely a bug, and is perhaps in libgnome-
bluetooth (?)

3. The bug is currently assigned to 'bluez' which is probably not to
blame.


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

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

Title:
  Bluetooth icon appears and disappears after reboot

Status in gnome-bluetooth package in Ubuntu:
  New

Bug description:
  This morning I tried to use my laptop. I think it was suspended, but
  not deep suspended (screen off, but was attached to AC). When I tried
  resuming it, the screen went on, but instead of the gnome login, I was
  greeted by a black screen with some errors.

  ```
  Bluetooth: hci0: Timed out waiting for suspend events
  Bluetooth: hci0: Suspend timeout bit: 6
  Bluetooth: hci0: Suspend notifier action (3) failed: -110
  ```

  As I could do nothing, I rebooted the laptop (force off with power
  button and turned on).

  As I logged in, the Bluetooth indicator in the top right panel started
  appearing and disappearing continuously. I normally have a Bluetooth
  mouse connected, so I thought it was trying to pair with it. So I went
  into the Bluetooth tab from Settings and I was asked permission to
  pair the device. After allowing that permission appear / disappear
  issue went out.

  I think something is wrong with this flow. I think the service for the
  Bluetooth should handle these issues better, not blinking, but asking
  such permission that it required from the beginning. As it is it looks
  broken and poorly discoverable.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  9 10:31:18 2022
  InstallationDate: Installed on 2020-04-03 (826 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic 
root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 84:C5:A6:94:9C:96  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:233857 acl:2324 sco:0 events:14387 errors:0
TX bytes:892713 acl:1283 sco:0 commands:8484 errors:0

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


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

[Desktop-packages] [Bug 1980975] Re: Rubbish Bin Context Menu references wrong name

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

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

Title:
  Rubbish Bin Context Menu references wrong name

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When right clicking the rubbish bin in the file explorer or dock, the
  context menu says "Empty wastebasket". This is an inconsistent
  reference as it is now referred to as Rubbish Bin across the Ubuntu
  OS.

  Even in the File Explorer - Rubbish Bin, the "Empty..." button tooltip
  describes "Delete all items in the Rubbish Bin".

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


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

[Desktop-packages] [Bug 1980975] Re: Rubbish Bin Context Menu references wrong name

** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) =>
nautilus (Ubuntu)

** Tags added: jammy

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

Title:
  Rubbish Bin Context Menu references wrong name

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When right clicking the rubbish bin in the file explorer or dock, the
  context menu says "Empty wastebasket". This is an inconsistent
  reference as it is now referred to as Rubbish Bin across the Ubuntu
  OS.

  Even in the File Explorer - Rubbish Bin, the "Empty..." button tooltip
  describes "Delete all items in the Rubbish Bin".

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


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

[Desktop-packages] [Bug 1980975] Re: Rubbish Bin Context Menu references wrong name

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

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

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

Title:
  Rubbish Bin Context Menu references wrong name

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When right clicking the rubbish bin in the file explorer or dock, the
  context menu says "Empty wastebasket". This is an inconsistent
  reference as it is now referred to as Rubbish Bin across the Ubuntu
  OS.

  Even in the File Explorer - Rubbish Bin, the "Empty..." button tooltip
  describes "Delete all items in the Rubbish Bin".

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


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

[Desktop-packages] [Bug 1980933] Re: Blanked screen doesn't wake up after put into powersave

Yes, problems in the amdgpu kernel module are a common cause of such
freezes.

We can only suggest you try a newer kernel:

Latest stable:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.18.10/amd64/

Latest development:
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2022-07-08/amd64/


** Tags added: amdgpu

** Summary changed:

- Blanked screen doesn't wake up after put into powersave
+ [amdgpu] Blanked screen doesn't wake up after put into powersave

** Package changed: mutter (Ubuntu) => linux (Ubuntu)

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

Title:
  [amdgpu] Blanked screen doesn't wake up after put into powersave

Status in linux package in Ubuntu:
  New

Bug description:
  This is *similar* to #1968040 but I'm raising it as a separate issue
  as the workarounds there do not work for my system suggesting that
  this is indeed a separate bug.

  When allowing the system to blank the screen, it becomes impossible to
  awaken the screen some unknown length of time after DPMS poweroff is
  triggered. Neither the keyboard nor the mouse can be used to trigger
  the screens to power back on again once powered down by DPMS.

  My system is a custom-build desktop PC with a discrete AMD 6600XT GPU
  and two external 4k monitors.

  I have tried the workarounds in the above bug and neither worked.
  Namely pressing ctrl+alt+f1 (nor any other f-keys in combo with
  ctrl+alt) does not bring the monitors back to life, and adding
  MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment does not change
  the behaviour in any way.

  The system is still responsive to the network and I can SSH into the
  box to investigate when in this scenario.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  7 09:32:16 2022
  InstallationDate: Installed on 2022-05-11 (56 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Thanks for the bug report.

First we need to exclude the most common cause of shell bugs:
unsupported extensions. Please uninstall:

  'sound-output-device-choo...@kgshank.net',
  'clipboard-indica...@tudmotu.com',
  'drive-m...@gnome-shell-extensions.gcampax.github.com',
  'hidetop...@mathieu.bidon.ca',
  'gtktitle...@velitasali.github.io'

and then log in again.

If the bug still occurs then next please check for crashes by following
these steps:

1. Look in /var/crash for crash files and if found run:

ubuntu-bug YOURFILE.crash

   Then tell us the ID of the newly-created bug.

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

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

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

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


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

[Desktop-packages] [Bug 1370953] Re: layout switch is delayed

2022-07-11 Thread Ubuntu Foundations Team Bug Bot

The attachment "keyboard-layout-switching-delay-workaround.patch" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  layout switch is delayed

Status in GNOME Shell:
  New
Status in console-setup package in Ubuntu:
  Incomplete
Status in gconf package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

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


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

[Desktop-packages] [Bug 1370953] Re: layout switch is delayed

2022-07-11 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  layout switch is delayed

Status in GNOME Shell:
  New
Status in console-setup package in Ubuntu:
  Incomplete
Status in gconf package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

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


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

[Desktop-packages] [Bug 1980718] Re: External monitor not working on Wayland

Thanks for the bug report. This sounds like bug 1976204 so please try
disabling the Desktop Icons NG extension in the Extensions app (sudo apt
install gnome-shell-extension-prefs).

** Tags added: multimonitor

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

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

Title:
  External monitor not working on Wayland

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I connect the external monitor the image is shown on the external
  display but it freezes (on both displays); after I unplug the external
  display the following errors are logged (not sure it is related to the
  freeze):

  Jul  5 09:19:39 xps gnome-shell[10252]: 
meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < 
n_logical_monitors' failed
  Jul  5 09:19:39 xps gnome-shell[10252]: 
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) 
number < g_list_length (manager->logical_monitors)' failed
  Jul  5 09:19:39 xps gnome-shell[10252]: 
meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' 
failed

  The external display is connected via a thunderbolt port and an
  adapter to HDMI.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  5 09:21:33 2022
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-08-07 (696 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (68 days ago)

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


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

[Desktop-packages] [Bug 1980586] Re: screen is flickering in Ubuntu 22.04

Sounds like bug 1958191 which for most people is fixed in kernel
5.15.0-40. Please update your system:

  sudo apt update
  sudo apt full-upgrade

Then reboot and tell us if the problem persists.


** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)

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

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

Title:
  screen is flickering in Ubuntu 22.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After I updated to 22.04 sometimes the screen starts glitching and
  flickering. after 4 to 5 second it stops automatically. It's happen in
  both["xorg", "wayland"] display manager.

  Description: Ubuntu 22.04 LTS x86_64
  Release: 22.04
  Xorg, Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xserver-xorg-core 2:21.1.3-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  Uname: Linux 5.15.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  3 11:27:32 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0794]
  InstallationDate: Installed on 2022-05-23 (40 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a05 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=e752f60e-df1c-47ce-a1c9-81d43aa6b975 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 3.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.11.0
  dmi.board.name: 0R2XKN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.11.0:bd12/15/2021:br3.11:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0R2XKN:rvrA00:cvnDellInc.:ct9:cvr:sku0794:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0794
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1980688] Re: Mouse / trackpad buttons sometimes don't work after waking up from suspend

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 1980688

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  Mouse / trackpad buttons sometimes don't work after waking up from
  suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After waking up from suspend, the trackpad (and, if connected mouse)
  buttons sometimes don't work anymore. Only a reboot fixes it.

  Note that I move the mouse pointer and use the keyboard, just the
  trackpad / mouse buttons stop working.

  I have observed this bug both with Wayland and with X11.

  1. Release: Ubuntu 22.04
  2. Version: gnome-shell 42.2-0ubuntu0.2
  3. What I expect to happen: the trackpad and mouse buttons work always after 
waking up from suspend.
  4. What happened instead: the trackpad and mouse buttons do not work about 
every third time after waking up from suspend.

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


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

[Desktop-packages] [Bug 1735986] Re: Unable to set different scale correctly on different monitors

"Fix Released" since the issue in the title "Unable to set different
scale correctly on different monitors" really has been working for a few
years at least.

Please open new bugs about any remaining issues you have.


** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gnome-control-center (Ubuntu)
   Status: Invalid => Fix Released

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

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

Title:
  Unable to set different scale correctly on different monitors

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gnome-control-
  center/issues/17

  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.

  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).

  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.

  When I logged into graphical session (selected the default Ubuntu
  session), I confirmed wayland is running by checking loginctl:

  loginctl show-session 2 -p Type
  Type=wayland

  With external display connected, display settings show that the high
  DPI laptop screen got scaling set automatically to 200%, and the
  external low DPI display got scaling set to 100%. So far, looks good -
  automatic detection of hi dpi screens did the right thing.

  The built-in Ubuntu applications like terminal, file browser or
  setting window work fine. When I start e.g. the terminal, it appears
  first on the laptop screen - it is scaled properly, then I drag it to
  the external screen and once I release the mouse button, the window
  shrinks to 2x smaller, so it adapts to lower DPI of that screen.
  Everything is sharp and crispy and the sizes are ok.

  Problems:

  * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly
  on the external screen. Everything is twice too big. When started,
  they appear first on the built-in hiDPI screen with the correct size,
  but after dragging to the external screen, they remain scaled by 200%.

  * When I enabled dock to be displayed on all screens, the dock icons
  are twice too big on the external screen. So, 200% scaling seems to be
  applied to the dock on both screens.

  * Sometimes the mouse pointer is twice as large. Sometimes it is twice
  too small. I didn't figure out yet when it happens. Sometimes it is
  only twice too large when over the desktop background, but ok when
  over an application window. This is a very minor issue, but looks
  funny.

  -
  What I tried so far:

  Resetting dconf to factory settings with:
  dconf reset -f /org/gnome/
  did not help.

  Then I tried enabling experimental fractional scaling, with 200% /
  100% scales set (I do not really need fractional scaling, but I hoped
  it changes how things are rendered and where scaling is applied). This
  actually helped for both scaling issues - including the dock scaling
  problem. Windows get even properly scaled in the *middle of dragging*
  between displays. Everything is the right size with this setting on.
  Really cool.

  Unfortunately now the image on the builtin display for the non-native
  applications like Firefox, Chrome or Idea is severely blurred. And it
  is blurred even if I disconnect the external display. It looks as if
  it rendered these apps at half the resolution (I noticed xrandr shows
  1920x1080 for that screen, but ubuntu display settings window shows
  3840x2160) and then upscaled twice the bitmap to reach higher 4k real
  screen resolution. The blur does not happen for native Ubuntu apps
  like terminal.

  Unfortunately the blurring effect is much stronger than if I just
  manually force the builtin screen to 1920x1080. In this case
  everything is a bit lower resolution, but still sharp enough.

  Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for 
me at all, despite some rumours it should have. I still have to switch to lower 
resolution on the builtin display to get everything crisp and the right size.
  ---
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-04-12 (234 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Package:

[Desktop-packages] [Bug 1760849] Re: Login screen appears on only one monitor and it's not the one I want

We could add a button to gnome-control-center that does the above. Label
the button "Apply on login screen".

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => Opinion

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

Title:
  Login screen appears on only one monitor and it's not the one I want

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

Bug description:
  Upstream bugs:
  https://gitlab.gnome.org/GNOME/gdm/issues/168
  https://gitlab.gnome.org/GNOME/gdm/issues/183
  https://gitlab.gnome.org/GNOME/gdm/issues/195
  https://gitlab.gnome.org/GNOME/gdm/issues/319
  https://gitlab.gnome.org/GNOME/gdm/issues/372
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3867

  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1760849] Re: Login screen appears on only one monitor and it's not the one I want

WORKAROUND/FIX:

1. Log in and configure your multi-monitor desktop the way you want.

2. sudo cp ~/.config/monitors.xml ~gdm/.config/

3. Edit ~gdm/.config/monitors.xml to make sure the monitor you want as
primary is set as yes

4. Log out.

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

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Login screen appears on only one monitor and it's not the one I want

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

Bug description:
  Upstream bugs:
  https://gitlab.gnome.org/GNOME/gdm/issues/168
  https://gitlab.gnome.org/GNOME/gdm/issues/183
  https://gitlab.gnome.org/GNOME/gdm/issues/195
  https://gitlab.gnome.org/GNOME/gdm/issues/319
  https://gitlab.gnome.org/GNOME/gdm/issues/372
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3867

  The Ubuntu login screen is tiled on all displays, not mirrored, making
  it nearly impossible to login when using an external monitor if the
  laptop screen is not visible.

  There appears to be no available control to alter the display settings
  of the login screen. Prior to bionic, the controls followed the mouse
  onto different displays so you could login by giving the mouse a swipe
  to the right to get the controls to appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 22:13:53 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1980556] Re: Focus on hover causes problems with software features that open the file explorer

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

** Tags added: focus

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

Title:
  Focus on hover causes problems with software features that open the
  file explorer

Status in mutter package in Ubuntu:
  New

Bug description:
  I enabled focus on hover in ubuntu. Whenever I follow a path like
  file->open in a piece of software (eg, VSCode) there is a very small
  delay while the "open" button disappears and the file explorer opens.
  During this delay my cursor is over the main program window, so this
  gets granted focus and the file explorer window opens behind it, which
  is very irritating.

  Many programs will freeze while you are selecting a file to open, and
  it can give the impression something has crashed when the file
  explorer window is hidden behind the main window.

  I would propose an optional delay in focus switching if a window has
  just been opened in order to allow a new sub-window to appear beneath
  the cursor, before focus switches to the original window again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-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.129.06  Thu May 12 
22:52:02 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  2 08:40:45 2022
  DistUpgraded: 2022-05-08 10:05:05,106 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/470.129.06, 5.15.0-39-generic, x86_64: installed
   nvidia/470.129.06, 5.15.0-40-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-39-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
 Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [103c:8601]
  InstallationDate: Installed on 2020-06-05 (756 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. XPS 15 7590
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-40-generic 
root=UUID=c961107c-b500-4680-9b42-5b932e13da50 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-05-08 (54 days ago)
  dmi.bios.date: 12/14/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 0VYV0G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd12/14/2020:br1.9:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another

No bug reports since 2020 so I assume this is fixed for GNOME. At least
in Ubuntu 22.04.

Anyone still experiencing problems, please open a NEW bug by running:

  ubuntu-bug gnome-shell

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Fix Released

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

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Confirmed
Status in Mutter:
  Expired
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

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


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

[Desktop-packages] [Bug 1975884] Re: Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"

I guess just confirm you don't have "gsconnect" loaded when the bug
occurs?

** Summary changed:

- Temporary screen freeze on gnome screen lock (wayland, ubuntu 22.04 jammy)
+ Temporary screen freeze when gnome-shell logs "Removing a network device that 
was not added"

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

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

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

Title:
  Temporary screen freeze when gnome-shell logs "Removing a network
  device that was not added"

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1769981/comments/25 , I've been observing an issue when
  unlocking my computer (usually from a screen lock state, not
  hibernation/sleep) where after entering the first few characters of my
  password the screen freezes for 10-20 seconds before I can do any type
  of input (mouse, touch, keyboard).

  I've also seen it happen when having touch / gesture input switch
  between displaying the user name and the password field - where the
  screen can get stuck in the animation in an interstitial state for a
  number of seconds.

  I've largely been noticing this since upgrading from Ubuntu 21.10 to
  22.04. It doesn't happen all the time, but often enough to file an
  issue for.

  So far I've tried:
  - Disabling the 'blur my shell' extension - still encountered the issue again 
eventually.
  - Looking for anything associated with this in /var/crash - couldn't find 
anything.
  - Looking for anything associated at errors.ubuntu.com for my id.

  What I may eventually try:
  - Seeing if this may depend on having too many browser tabs / apps open. 
Currently not in a position to do this.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 26 19:19:28 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-07-15 (315 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago)

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


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

[Desktop-packages] [Bug 1975884] [NEW] Temporary screen freeze when gnome-shell logs "Removing a network device that was not added"

You have been subscribed to a public bug:

As first mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1769981/comments/25 , I've been observing an issue when
unlocking my computer (usually from a screen lock state, not
hibernation/sleep) where after entering the first few characters of my
password the screen freezes for 10-20 seconds before I can do any type
of input (mouse, touch, keyboard).

I've also seen it happen when having touch / gesture input switch
between displaying the user name and the password field - where the
screen can get stuck in the animation in an interstitial state for a
number of seconds.

I've largely been noticing this since upgrading from Ubuntu 21.10 to
22.04. It doesn't happen all the time, but often enough to file an issue
for.

So far I've tried:
- Disabling the 'blur my shell' extension - still encountered the issue again 
eventually.
- Looking for anything associated with this in /var/crash - couldn't find 
anything.
- Looking for anything associated at errors.ubuntu.com for my id.

What I may eventually try:
- Seeing if this may depend on having too many browser tabs / apps open. 
Currently not in a position to do this.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 26 19:19:28 2022
DisplayManager: gdm3
InstallationDate: Installed on 2021-07-15 (315 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-05-02 (24 days ago)

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


** Tags: amd64 apport-bug jammy third-party-packages wayland-session
-- 
Temporary screen freeze when gnome-shell logs "Removing a network device that 
was not added"
https://bugs.launchpad.net/bugs/1975884
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions

** Also affects: nvidia-graphics-drivers-515 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Status: New => Triaged

** Changed in: nvidia-graphics-drivers-515 (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [nvidia] Secondary monitor performance is slow on an Nvidia hybrid
  system in Wayland sessions

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Triaged

Bug description:
  In session with Wayland the Nvidia driver settings do not load. And
  there is a sluggishness when opening apps, show applications menu,
  maximize, changing workspace, resize, changing monitor windows etc.
  When in an Xorg session the Nvidia settings load correctly and the
  performance is satisfactory.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 21:18:08 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 
[8086:2086]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] 
[8086:2086]
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  MachineType: Avell High Performance A60 MUV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: QCCFL357.0122.2020.0911.1520
  dmi.board.name: Avell High Performance
  dmi.board.vendor: Avell High Performance
  dmi.chassis.type: 10
  dmi.chassis.vendor: Avell High Performance
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV:
  dmi.product.family: A60 MUV
  dmi.product.name: A60 MUV
  dmi.product.sku: A60 MUV
  dmi.sys.vendor: Avell High Performance
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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

[Desktop-packages] [Bug 1965809] Re: 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with SIGSEGV in magazine_chain_pop_head()

Tracking in
https://errors.ubuntu.com/problem/ae6854a0c695a678f443c0456198327d8dd2a50e

** Description changed:

+ https://errors.ubuntu.com/problem/ae6854a0c695a678f443c0456198327d8dd2a50e
+ 
+ ---
+ 
  Attempting to open videos in multiple formats (tried .webm and .mp4 so
  far) results in ‘specified movie could not be found’ errors in Videos.
  
  I’ve moved them into multiple folders with the same result. If I hit the
  upper left button ’ < ’ I can see the file just fine
  
  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer1.0-0 1.20.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 14:20:08 2022
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2022-02-17 (32 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
  SegvAnalysis:
-  Segfault happened at: 0x7f023771dd0c :mov
0x8(%r12),%rax
-  PC (0x7f023771dd0c) ok
-  source "0x8(%r12)" (0x55e51814962008) not located in a known VMA region 
(needed readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7f023771dd0c :mov
0x8(%r12),%rax
+  PC (0x7f023771dd0c) ok
+  source "0x8(%r12)" (0x55e51814962008) not located in a known VMA region 
(needed readable region)!
+  destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
-  g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
+  g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: totem crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  separator:

** Summary changed:

- 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with 
SIGSEGV in magazine_chain_pop_head()
+ totem crashed with SIGSEGV in magazine_chain_pop_head() from 
thread_memory_magazine1_alloc() from g_slice_alloc() from 
g_object_notify_queue_freeze()

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

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

** Changed in: totem (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  totem crashed with SIGSEGV in magazine_chain_pop_head() from
  thread_memory_magazine1_alloc() from g_slice_alloc() from
  g_object_notify_queue_freeze()

Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/ae6854a0c695a678f443c0456198327d8dd2a50e

  ---

  Attempting to open videos in multiple formats (tried .webm and .mp4 so
  far) results in ‘specified movie could not be found’ errors in Videos.

  I’ve moved them into multiple folders with the same result. If I hit
  the upper left button ’ < ’ I can see the file just fine

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer1.0-0 1.20.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 14:20:08 2022
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2022-02-17 (32 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f023771dd0c :mov
0x8(%r12),%rax
   PC (0x7f023771dd0c) ok
   source "0x8(%r12)" (0x55e51814962008) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:

[Desktop-packages] [Bug 1981191] Re: /usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_object_notify_queue_freeze:g_object_unref

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

** This bug has been marked a duplicate of bug 1965809
   22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed 
with SIGSEGV in magazine_chain_pop_head()

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

Title:
  
/usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_object_notify_queue_freeze:g_object_unref

Status in totem package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 1981192] [NEW] /usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_object_notify_queue_freeze:g_object_init

2022-07-11 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: jammy

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

Title:
  
/usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_object_notify_queue_freeze:g_object_init

Status in totem package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 1981192] Re: /usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_object_notify_queue_freeze:g_object_init

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

** This bug has been marked a duplicate of bug 1965809
   totem crashed with SIGSEGV in magazine_chain_pop_head() from 
thread_memory_magazine1_alloc() from g_slice_alloc() from 
g_object_notify_queue_freeze()

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

Title:
  
/usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_object_notify_queue_freeze:g_object_init

Status in totem package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 1981191] [NEW] /usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_object_notify_queue_freeze:g_object_unref

2022-07-11 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: jammy

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

Title:
  
/usr/bin/totem:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_object_notify_queue_freeze:g_object_unref

Status in totem package in Ubuntu:
  New

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

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


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

[Desktop-packages] [Bug 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing

** Summary changed:

- gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
+ gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing

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

Title:
  gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have set gnome to "focus on hover", i.e. focus follows mouse. If I
  alt-tab to bring a window to the front but the mouse is over another
  window, then the hovered-over window will reclaim focus and the window
  I raised will typically get covered up again.

  In previous gnome versions, if I explicitly focussed a window via
  keyboard shortcuts, it remained focussed and I think this is the
  preferred behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 20 11:35:20 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-03-17 (33 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

apport information

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

-- 
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 modemmanager package in Ubuntu:
  New

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/modemmanager/+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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode

apport information

** Tags added: apport-collected

** Description changed:

  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

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

-- 
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 modemmanager package in Ubuntu:
  New

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)

[Desktop-packages] [Bug 1981190] ProcEnviron.txt

apport information

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

-- 
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 modemmanager package in Ubuntu:
  New

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/modemmanager/+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 1981163] Re: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince

Thank you for your bug report. Do you use the deb or the snap for
thunderbird and evince?

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

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

Title:
  In Compose window, if a PDf is joined and clicked to open, Thunderbird
  launches Firefox instead of Evince

Status in thunderbird package in Ubuntu:
  New

Bug description:
  In Thunderbird on Ubuntu Gnome, I set Evince as default program to
  open pdf files from Thunderbird.

  In received messages, and those saved on "Sent" folder, it works
  perfectly.

  But in the "Compose" window: if I add a pdf file to the message, and
  double-click on it to open and verify it, Thunderbird always uses
  Firefox to show it.

  In case Firefox is not installed (has been removed), I have an error
  message telling there is not associated application for pdf files and
  to go to Preferences - where Evince is already and still defined as
  default.

  It happens since many months and bug is still present in Thunderbird
  102 / Ubuntu 22.10 beta.

  It's not the same as bug 234349 as here, it's not an URL file but
  directly a pdf joined in a mail.

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


-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] Fibcom FM350-GL not able connect to network with 5G mode

Public bug reported:

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

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


** Tags: apport-collected jammy wwan

** Tags added: jammy wwan

-- 
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 modemmanager package in Ubuntu:
  New

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

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