[Desktop-packages] [Bug 2038748] Re: Xorg freeze amdgpu mst powersaving

2023-10-08 Thread Tuomas Heino
** Package changed: xorg (Ubuntu) => linux-signed-hwe-6.2 (Ubuntu)

** Summary changed:

- Xorg freeze amdgpu mst powersaving
+ amdgpu mst power saving null ptr deref

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

Title:
  amdgpu mst power saving null ptr deref

Status in linux-signed-hwe-6.2 package in Ubuntu:
  New

Bug description:
  Reoccurrence of amdgpu MST power saving related null pointer deref.
  Likely should be against kernel instead, but let's see whether ubuntu-
  bug attached sensible part of logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Sun Oct  8 10:23:57 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2022-04-27 (528 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1
  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-signed-hwe-6.2/+bug/2038748/+subscriptions


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


[Desktop-packages] [Bug 2038748] [NEW] Xorg freeze amdgpu mst powersaving

2023-10-08 Thread Tuomas Heino
Public bug reported:

Reoccurrence of amdgpu MST power saving related null pointer deref.
Likely should be against kernel instead, but let's see whether ubuntu-
bug attached sensible part of logs.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
Date: Sun Oct  8 10:23:57 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Very infrequently
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2022-04-27 (528 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze jammy ubuntu

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

Title:
  Xorg freeze amdgpu mst powersaving

Status in xorg package in Ubuntu:
  New

Bug description:
  Reoccurrence of amdgpu MST power saving related null pointer deref.
  Likely should be against kernel instead, but let's see whether ubuntu-
  bug attached sensible part of logs.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Sun Oct  8 10:23:57 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2022-04-27 (528 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  

[Desktop-packages] [Bug 2036998] [NEW] Xorg freeze

2023-09-21 Thread Tuomas Heino
Public bug reported:

Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in 
random order.
May have reported this earlier myself. Details to be filled later.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
Uname: Linux 6.2.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
Date: Thu Sep 21 20:20:00 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Very infrequently
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2022-04-27 (512 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze jammy ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in 
random order.
  May have reported this earlier myself. Details to be filled later.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15
  Uname: Linux 6.2.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Thu Sep 21 20:20:00 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2022-04-27 (512 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: 

[Desktop-packages] [Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings

2020-08-15 Thread Tuomas Heino
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609

Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to 
errors.ubuntu.com now, marking these two as duplicates for now.

** This bug has been marked a duplicate of bug 1861609
   [focal] Xorg crashed with assertion failure (usually in a VM) at 
[privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and 
call stack comes from DRIMoveBuffersHelper

** Information type changed from Public to Private

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

Title:
  After recent updates Xorg crashes whenever entering Display Settings

Status in xorg-server package in Ubuntu:
  New

Bug description:
  AssertionMessage Xorg: ../../../../../../include/privates.h:121:
  dixGetPrivateAddr: Assertion `key-initialized' failed.

  Also affected by apport bug #1891634 making filling more information
  here somewhat tedious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:08:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1891745] Re: Xorg crashed with SIGSEGV in dixSaveScreens()

2020-08-15 Thread Tuomas Heino
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609

Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to 
errors.ubuntu.com now, marking these two as duplicates for now.

** This bug has been marked a duplicate of bug 1891636
   After recent updates Xorg crashes whenever entering Display Settings

** Information type changed from Public to Private

** This bug is no longer a duplicate of bug 1891636
   After recent updates Xorg crashes whenever entering Display Settings
** This bug has been marked a duplicate of bug 1861609
   [focal] Xorg crashed with assertion failure (usually in a VM) at 
[privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and 
call stack comes from DRIMoveBuffersHelper

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

Title:
  Xorg crashed with SIGSEGV in dixSaveScreens()

Status in xorg package in Ubuntu:
  New

Bug description:
  This instance happened after lockscreen, as such may be suspend-resume
  related. On the other hand at least 0 and 10 parts on backtrace appear
  similar to bug #1891636

  While this appears to be a recent regression, DpkgLog.txt doesn't
  contain xorg references. Could it be related to kernel upgrades then,
  or just happened to slip by undetected after earlier upgrades?

   [ 81555.574] (EE) Backtrace:
   [ 81555.577] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) 
[0x560d53a2ee0c]
   [ 81555.578] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 
(funlockfile+0x60) [0x7fb62037b41f]
   [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
   [ 81555.578] (EE) 2: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb524a0]
   [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
   [ 81555.579] (EE) 3: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb52750]
   [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
   [ 81555.579] (EE) 4: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bb00]
   [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
   [ 81555.579] (EE) 5: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bba0]
   [ 81555.579] (EE) 6: /usr/lib/xorg/Xorg (dixSaveScreens+0x1e6) 
[0x560d538fceb6]
   [ 81555.580] (EE) 7: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x149) 
[0x560d53a0e779]
   [ 81555.580] (EE) 8: /usr/lib/xorg/Xorg (ProcessInputEvents+0x1d) 
[0x560d5390b65d]
   [ 81555.580] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x2c9) 
[0x560d538cdeb9]
   [ 81555.580] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x560d538d1fd4]
   [ 81555.580] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fb6201990b3]
   [ 81555.581] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x560d538bba3e]
   [ 81555.581] (EE) 
   [ 81555.581] (EE) Segmentation fault at address 0x0
   [ 81555.581] (EE) 
   Fatal server error:
   [ 81555.581] (EE) Caught signal 11 (Segmentation fault). Server aborting
   [ 81555.581] (EE) 
   [ 81555.581] (EE) 

  P.S. Don't currently have a remote debugging setup since all the other
  hosts nearby are headless.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 15 13:17:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2020-04-10 (126 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Desktop-packages] [Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings

2020-08-15 Thread Tuomas Heino
** Tags added: regression-update

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

Title:
  After recent updates Xorg crashes whenever entering Display Settings

Status in xorg-server package in Ubuntu:
  New

Bug description:
  AssertionMessage Xorg: ../../../../../../include/privates.h:121:
  dixGetPrivateAddr: Assertion `key-initialized' failed.

  Also affected by apport bug #1891634 making filling more information
  here somewhat tedious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:08:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Desktop-packages] [Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings

2020-08-15 Thread Tuomas Heino
No longer reproducible by visiting display settings after bug #1891745
crash. Possibly a duplicate of bug #1861609.

** Description changed:

- AssertionMessage Xort: ../../../../../../include/privates.h:121:
+ AssertionMessage Xorg: ../../../../../../include/privates.h:121:
  dixGetPrivateAddr: Assertion `key-initialized' failed.
  
  Also affected by apport bug #1891634 making filling more information
  here somewhat tedious.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:08:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
+  Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  After recent updates Xorg crashes whenever entering Display Settings

Status in xorg-server package in Ubuntu:
  New

Bug description:
  AssertionMessage Xorg: ../../../../../../include/privates.h:121:
  dixGetPrivateAddr: Assertion `key-initialized' failed.

  Also affected by apport bug #1891634 making filling more information
  here somewhat tedious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:08:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet 

[Desktop-packages] [Bug 1891745] [NEW] Xorg crashed with SIGSEGV in dixSaveScreens()

2020-08-15 Thread Tuomas Heino
Public bug reported:

This instance happened after lockscreen, as such may be suspend-resume
related. On the other hand at least 0 and 10 parts on backtrace appear
similar to bug #1891636

While this appears to be a recent regression, DpkgLog.txt doesn't
contain xorg references. Could it be related to kernel upgrades then, or
just happened to slip by undetected after earlier upgrades?

 [ 81555.574] (EE) Backtrace:
 [ 81555.577] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x560d53a2ee0c]
 [ 81555.578] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7fb62037b41f]
 [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.578] (EE) 2: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb524a0]
 [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.579] (EE) 3: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb52750]
 [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.579] (EE) 4: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bb00]
 [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10]
 [ 81555.579] (EE) 5: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) 
[0x7fb61fb4bba0]
 [ 81555.579] (EE) 6: /usr/lib/xorg/Xorg (dixSaveScreens+0x1e6) [0x560d538fceb6]
 [ 81555.580] (EE) 7: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x149) 
[0x560d53a0e779]
 [ 81555.580] (EE) 8: /usr/lib/xorg/Xorg (ProcessInputEvents+0x1d) 
[0x560d5390b65d]
 [ 81555.580] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x2c9) 
[0x560d538cdeb9]
 [ 81555.580] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x560d538d1fd4]
 [ 81555.580] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7fb6201990b3]
 [ 81555.581] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x560d538bba3e]
 [ 81555.581] (EE) 
 [ 81555.581] (EE) Segmentation fault at address 0x0
 [ 81555.581] (EE) 
 Fatal server error:
 [ 81555.581] (EE) Caught signal 11 (Segmentation fault). Server aborting
 [ 81555.581] (EE) 
 [ 81555.581] (EE) 

P.S. Don't currently have a remote debugging setup since all the other
hosts nearby are headless.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 15 13:17:57 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2020-04-10 (126 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Xorg crashed with SIGSEGV in dixSaveScreens()

Status in 

[Desktop-packages] [Bug 1891636] [NEW] After recent updates Xorg crashes whenever entering Display Settings

2020-08-14 Thread Tuomas Heino
Public bug reported:

AssertionMessage Xort: ../../../../../../include/privates.h:121:
dixGetPrivateAddr: Assertion `key-initialized' failed.

Also affected by apport bug #1891634 making filling more information
here somewhat tedious.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 14 13:08:34 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2020-04-10 (125 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  After recent updates Xorg crashes whenever entering Display Settings

Status in xorg-server package in Ubuntu:
  New

Bug description:
  AssertionMessage Xort: ../../../../../../include/privates.h:121:
  dixGetPrivateAddr: Assertion `key-initialized' failed.

  Also affected by apport bug #1891634 making filling more information
  here somewhat tedious.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 14 13:08:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2020-04-10 (125 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  

[Desktop-packages] [Bug 1871916] Re: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu

2020-04-10 Thread Tuomas Heino
Not reproducible on fresh install on same hardware.

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

Title:
  Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu

Status in xorg package in Ubuntu:
  New

Bug description:
  Installed (upgraded 16->18->20 beta) ubuntu appears to utilize
  incorrect x.org drivers for RX 5500 XT. Those drivers appear to be
  missing features like multi-monitor support. On the other hand live-
  usb of 20.04 beta did manage to utilize all 3 connected monitors
  (before crashing), so the issue may also be related to upgrading
  process (used do-release-upgrade since update-managed does not scale
  down to 800x600 fallback which 18.04 used with unsupported hardware).

  Yes, this report is in need of some triaging, unless it happens to be
  a clear duplicate of another bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 22:01:36 2020
  DistUpgraded: 2020-04-09 04:40:21,578 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.132, 5.3.0-46-generic, x86_64: installed
   nvidia, 390.132, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
  InstallationDate: Installed on 2016-09-25 (1292 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=4ae0053b-f333-4800-b242-42a9efca3dde ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago)
  XorgConf:
   Section "Device"
Identifier "AMD"
Driver "amdgpu"
   EndSection
  dmi.bios.date: 07/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B WS
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Thu Apr  9 04:46:16 2020
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.7-2ubuntu2

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

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


[Desktop-packages] [Bug 1871916] [NEW] Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu

2020-04-09 Thread Tuomas Heino
Public bug reported:

Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect
x.org drivers for RX 5500 XT. Those drivers appear to be missing
features like multi-monitor support. On the other hand live-usb of 20.04
beta did manage to utilize all 3 connected monitors (before crashing),
so the issue may also be related to upgrading process (used do-release-
upgrade since update-managed does not scale down to 800x600 fallback
which 18.04 used with unsupported hardware).

Yes, this report is in need of some triaging, unless it happens to be a
clear duplicate of another bug report.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  9 22:01:36 2020
DistUpgraded: 2020-04-09 04:40:21,578 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.132, 5.3.0-46-generic, x86_64: installed
 nvidia, 390.132, 5.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2016-09-25 (1292 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=4ae0053b-f333-4800-b242-42a9efca3dde ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago)
XorgConf:
 Section "Device"
  Identifier "AMD"
  Driver "amdgpu"
 EndSection
dmi.bios.date: 07/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Thu Apr  9 04:46:16 2020
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.7-2ubuntu2

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


** Tags: amd64 apport-bug focal performance ubuntu

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

Title:
  Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu

Status in xorg package in Ubuntu:
  New

Bug description:
  Installed (upgraded 16->18->20 beta) ubuntu appears to utilize
  incorrect x.org drivers for RX 5500 XT. Those drivers appear to be
  missing features like multi-monitor support. On the other hand live-
  usb of 20.04 beta did manage to utilize all 3 connected monitors
  (before crashing), so the issue may also be related to upgrading
  process (used do-release-upgrade since update-managed does not scale
  down to 800x600 fallback which 18.04 used with unsupported hardware).

  Yes, this report is in need of some triaging, unless it happens to be
  a clear duplicate of another bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 22:01:36 2020
  DistUpgraded: 2020-04-09 04:40:21,578 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: 

[Desktop-packages] [Bug 738063] Re: gnome-keyring-daemon assertion failures when changing password remotely

2015-08-22 Thread Tuomas Heino
Reproduced on trusty (using just the test124 part of reproduction
instructions above):

Aug 22 13:08:23 gx1 sshd[11844]: pam_unix(sshd:session): session opened for 
user test124 by (uid=0)
Aug 22 13:08:23 gx1 systemd-logind[1275]: New session 4 of user test124.
Aug 22 13:09:22 gx1 passwd[11988]: pam_unix(passwd:chauthtok): password changed 
for test124
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: Gck: gck_module_new: assertion 
'funcs != NULL' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: module_instances: assertion 
'module' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: egg_error_message: assertion 
'error' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: couldn't find secret store 
module: (unknown)
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: lookup_login_keyring: 
assertion 'GCK_IS_SESSION (session)' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: create_credential: assertion 
'GCK_IS_SESSION (session)' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: egg_error_message: assertion 
'error' failed
Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: couldn't create new login 
credential: (unknown)
Aug 22 13:09:22 gx1 passwd[11988]: gkr-pam: couldn't change password for the 
login keyring: the passwords didn't match.
Aug 22 13:09:22 gx1 passwd[11988]: pam_ecryptfs: Passphrase file wrapped
Aug 22 13:09:23 gx1 passwd[11997]: Error attempting to open 
[/home/test124/.ecryptfs/wrapped-passphrase] for reading
Aug 22 13:09:23 gx1 passwd[11997]: pam_ecryptfs: Error attempting to unwrap 
passphrase; rc = [-5]

Version: 3.10.1-1ubuntu4.2


** Tags added: trusty

** Changed in: gnome-keyring (Ubuntu)
   Status: Invalid = New

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

Title:
  gnome-keyring-daemon assertion failures when changing password
  remotely

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Binary package hint: gnome-keyring

  Changing password remotely results in the following assertion failures
  in auth.log:

  Mar 19 09:49:18 gx1 passwd[17883]: pam_unix(passwd:chauthtok): password 
changed for test123
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: gp11_module_get_slots: 
assertion `data-funcs' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_session: 
assertion `slot' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_keyring: 
assertion `GP11_IS_SESSION (session)' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: create_credential: assertion 
`GP11_IS_SESSION (session)' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: egg_error_message: assertion 
`error' failed
  Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: couldn't create new login 
credential: (unknown)
  Mar 19 09:49:18 gx1 passwd[17883]: gkr-pam: couldn't change password for the 
login keyring: the passwords didn't match.
  Mar 19 09:49:18 gx1 passwd[17883]: Passphrase file wrapped

  Mar 19 09:55:57 gx1 passwd[18305]: pam_unix(passwd:chauthtok): password 
changed for test124
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: gp11_module_get_slots: 
assertion `data-funcs' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_session: 
assertion `slot' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_keyring: 
assertion `GP11_IS_SESSION (session)' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: create_credential: assertion 
`GP11_IS_SESSION (session)' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: egg_error_message: assertion 
`error' failed
  Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: couldn't create new login 
credential: (unknown)
  Mar 19 09:55:57 gx1 passwd[18305]: gkr-pam: couldn't change password for the 
login keyring: the passwords didn't match.
  Mar 19 09:55:57 gx1 passwd[18305]: Passphrase file wrapped

  
  To reproduce:
  sudo adduser --encrypt-home test123
  sudo adduser test124

  ssh in as both users created above, run passwd and change the
  password. Have not tested behaviour without ecryptfs-utils installed,
  but it should be unrelated since both encrypted and unencrypted
  homedirs behaved the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-keyring 2.92.92.is.2.30.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
  Uname: Linux 2.6.32-28-generic i686
  Architecture: i386
  CheckboxSubmission: bc3a49cd6e76f0d54c8965120b490eef
  CheckboxSystem: abf102d6ef41328208f5c1554651535a
  Date: Sat Mar 19 09:51:57 2011
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  SourcePackage: gnome-keyring

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync

2013-05-01 Thread Tuomas Heino
** Tags added: precise

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

Title:
  gvfs-gdu-volume-monitor high cpu usage during raid-resync

Status in “gnome-disk-utility” package in Ubuntu:
  New

Bug description:
  During a raid-resync cpu usage is high - in fact gvfs-gdu-volume-
  monitor was using 100% cpu on one core for the duration of resync.
  Killed it with -SEGV to get something that can be retraced.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gvfs 1.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Nov 13 23:36:38 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_IE:en
   LANG=en_IE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e
   PC (0x7fca9329a3c3) ok
   source 0x7fca9329a32e (0x7fca9329a32e) ok
   SP (0x7fff9b1adac0) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libgdu.so.0
   ?? () from /usr/lib/libgdu.so.0
  Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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

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


[Desktop-packages] [Bug 908358] Re: software-center crashed with SIGSEGV on enabling universe

2011-12-24 Thread Tuomas Heino
** Visibility changed to: Public

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

Title:
  software-center crashed with SIGSEGV on enabling universe

Status in “software-center” package in Ubuntu:
  New

Bug description:
  Tried to enable universe repo, got crash notification. Oddly enough
  sfotware-center window did not disappear, so guess it was just a
  background process it is using.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: software-center 5.1.4
  ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
  Uname: Linux 3.2.0-6-generic x86_64
  ApportVersion: 1.90-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.296
  Date: Sat Dec 24 11:51:56 2011
  ExecutablePath: /usr/share/software-center/software-center
  InterpreterPath: /usr/bin/python2.7
  LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111223)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x4dbe38:  mov0x8(%rbp),%rax
   PC (0x004dbe38) ok
   source 0x8(%rbp) (0x0008) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SoftwareCenterLog:
   2011-12-24 11:51:33,506 - softwarecenter.ui.gtk3.em - INFO - EM's: 17 13 20
   2011-12-24 11:51:33,960 - softwarecenter.backend.reviews - WARNING - Could 
not get usefulness from server, no username in config file
   2011-12-24 11:51:34,117 - softwarecenter.ui.gtk3.utils - INFO - 
Softwarecenter style provider for ambiance Gtk theme: 
/usr/share/software-center/ui/gtk3/css/softwarecenter.css
   2011-12-24 11:51:36,540 - softwarecenter.ui.gtk3.app - INFO - 
software-center-agent finished with status 0
  SourcePackage: software-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: software-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync

2011-11-26 Thread Tuomas Heino
** Attachment added: cpu usage does not drop after several hours of raid 
resync, uses a lot of memory too
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/890337/+attachment/2609183/+files/after_resync_status.txt

** Visibility changed to: Public

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

Title:
  gvfs-gdu-volume-monitor high cpu usage during raid-resync

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  During a raid-resync cpu usage is high - in fact gvfs-gdu-volume-
  monitor was using 100% cpu on one core for the duration of resync.
  Killed it with -SEGV to get something that can be retraced.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gvfs 1.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Nov 13 23:36:38 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_IE:en
   LANG=en_IE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e
   PC (0x7fca9329a3c3) ok
   source 0x7fca9329a32e (0x7fca9329a32e) ok
   SP (0x7fff9b1adac0) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libgdu.so.0
   ?? () from /usr/lib/libgdu.so.0
  Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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

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


[Desktop-packages] [Bug 761478] Re: Enhancement: Prompt to check a busy file system on next reboot

2011-11-26 Thread Tuomas Heino
Simply creating that file would not be entirely enough. As in while that
seems to force the fsck, said file does not get removed automatically.
And maybe even shouldn't be removed, unless it was created by gdu.

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

Title:
  Enhancement: Prompt to check a busy file system on next reboot

Status in “gnome-disk-utility” package in Ubuntu:
  Confirmed
Status in Baltix GNU/Linux:
  New

Bug description:
  Binary package hint: gnome-disk-utility

  When selecting Check File System on a file system which is is use,
  you currently get an error stating the device is busy.

  If a disk was busy, Disk Utility could prompt the user and ask if the
  file system should be scheduled for a check on the next reboot.

  I have just found out about the special file /forcefsck
  (http://www.cyberciti.biz/faq/linux-force-fsck-on-the-next-reboot-or-
  boot-sequence/) which forces the file system to be checked on the next
  reboot, and due to this I think this is a potentially simple
  implementation.  Disk Utility would just have to prompt and create
  that file.

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

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


[Desktop-packages] [Bug 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync

2011-11-26 Thread Tuomas Heino
http://bazaar.launchpad.net/~vcs-imports/gnome-disk-
utility/master/view/head:/src/gdu/gdu-linux-lvm2-volume-
group.c?start_revid=930 has the following comment in find_pvs():

187/* TODO: do incremental list management instead of recomputing on
188 * each add/remove/change event
189 */

So seems it is recomputing all LVM PVS's on every single change event.
Raid resync likely generates a ton of those (resync status %). Do all of
those change events get queued and then processed slowly, consuming
change events at far lower rate than they are being generated?

** Package changed: gvfs (Ubuntu) = gnome-disk-utility (Ubuntu)

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

Title:
  gvfs-gdu-volume-monitor high cpu usage during raid-resync

Status in “gnome-disk-utility” package in Ubuntu:
  New

Bug description:
  During a raid-resync cpu usage is high - in fact gvfs-gdu-volume-
  monitor was using 100% cpu on one core for the duration of resync.
  Killed it with -SEGV to get something that can be retraced.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gvfs 1.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Nov 13 23:36:38 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_IE:en
   LANG=en_IE.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e
   PC (0x7fca9329a3c3) ok
   source 0x7fca9329a32e (0x7fca9329a32e) ok
   SP (0x7fff9b1adac0) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/libgdu.so.0
   ?? () from /usr/lib/libgdu.so.0
  Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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

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


[Desktop-packages] [Bug 889779] [NEW] gvfs-gdu-volume-monitor high cpu usage after palimpsest / during raid-resync

2011-11-13 Thread Tuomas Heino
Public bug reported:

After running palimpsest during a raid-resync cpu usage seemed high - in
fact gvfs-gdu-volume-monitor was using 100% cpu (for more than an hour).

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gvfs 1.8.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
Uname: Linux 2.6.38-12-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Nov 13 12:40:49 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_IE:en
 LANG=en_IE.UTF-8
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug natty

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

Title:
  gvfs-gdu-volume-monitor high cpu usage after palimpsest / during raid-
  resync

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  After running palimpsest during a raid-resync cpu usage seemed high -
  in fact gvfs-gdu-volume-monitor was using 100% cpu (for more than an
  hour).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gvfs 1.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Nov 13 12:40:49 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_IE:en
   LANG=en_IE.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 889779] Re: gvfs-gdu-volume-monitor high cpu usage after palimpsest / during raid-resync

2011-11-13 Thread Tuomas Heino
https://bugzilla.redhat.com/show_bug.cgi?id=575381 may be related.

** Bug watch added: Red Hat Bugzilla #575381
   https://bugzilla.redhat.com/show_bug.cgi?id=575381

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

Title:
  gvfs-gdu-volume-monitor high cpu usage after palimpsest / during raid-
  resync

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  After running palimpsest during a raid-resync cpu usage seemed high -
  in fact gvfs-gdu-volume-monitor was using 100% cpu (for more than an
  hour).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gvfs 1.8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8
  Uname: Linux 2.6.38-12-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Nov 13 12:40:49 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427)
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_IE:en
   LANG=en_IE.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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