[Touch-packages] [Bug 1960366] Re: skel.bashrc PS1 debian_chroot not dynamic in xterm title
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1960366
Title:
skel.bashrc PS1 debian_chroot not dynamic in xterm title
Status in bash package in Ubuntu:
New
Bug description:
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
Expected:
debian_chroot part of xterm title should update dynamically; with the
following PS1 contents by default
$ set | fgrep PS1 | head -1
PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
Actual result without patch:
debian_chroot part of xterm title got evaluated only during bash
startup, as can be seen in PS1 contents
$ set | fgrep PS1 | head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960366] Re: skel.bashrc PS1 debian_chroot not dynamic in xterm title
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1960366
Title:
skel.bashrc PS1 debian_chroot not dynamic in xterm title
Status in bash package in Ubuntu:
New
Bug description:
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
Expected:
debian_chroot part of xterm title should update dynamically; with the
following PS1 contents by default
$ set | fgrep PS1 | head -1
PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
Actual result without patch:
debian_chroot part of xterm title got evaluated only during bash
startup, as can be seen in PS1 contents
$ set | fgrep PS1 | head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038748] Re: Xorg freeze amdgpu mst powersaving
** 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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038748] [NEW] Xorg freeze amdgpu mst powersaving
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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 2036998] [NEW] Xorg freeze
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 Ubuntu Touch seeded 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:
[Touch-packages] [Bug 1960366] Re: skel.bashrc PS1 debian_chroot not dynamic in xterm title
** Patch added: "0001-Properly-escape-PS1-for-xterm-title.patch"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+attachment/5559792/+files/0001-Properly-escape-PS1-for-xterm-title.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1960366
Title:
skel.bashrc PS1 debian_chroot not dynamic in xterm title
Status in bash package in Ubuntu:
New
Bug description:
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
Expected:
debian_chroot part of xterm title should update dynamically; with the
following PS1 contents by default
$ set | fgrep PS1 | head -1
PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
Actual result without patch:
debian_chroot part of xterm title got evaluated only during bash
startup, as can be seen in PS1 contents
$ set | fgrep PS1 | head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960366] Re: skel.bashrc PS1 debian_chroot not dynamic in xterm title
Added a patch at
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
** Description changed:
- Submitting a patch soon.
+
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
- Without fix:
- $ set|fgrep PS1|head -1
+ Expected:
+
+ debian_chroot part of xterm title should update dynamically; with the
+ following PS1 contents by default
+
+ $ set | fgrep PS1 | head -1
+ PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
+
+ Actual result without patch:
+
+ debian_chroot part of xterm title got evaluated only during bash
+ startup, as can be seen in PS1 contents
+
+ $ set | fgrep PS1 | head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
-
- With quotation fix applied:
- $ set|fgrep PS1|head -1
- PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1960366
Title:
skel.bashrc PS1 debian_chroot not dynamic in xterm title
Status in bash package in Ubuntu:
New
Bug description:
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
Expected:
debian_chroot part of xterm title should update dynamically; with the
following PS1 contents by default
$ set | fgrep PS1 | head -1
PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
Actual result without patch:
debian_chroot part of xterm title got evaluated only during bash
startup, as can be seen in PS1 contents
$ set | fgrep PS1 | head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960366] [NEW] skel.bashrc PS1 debian_chroot not dynamic in xterm title
Public bug reported:
Submitting a patch soon.
Without fix:
$ set|fgrep PS1|head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
With quotation fix applied:
$ set|fgrep PS1|head -1
PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
** Affects: bash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1960366
Title:
skel.bashrc PS1 debian_chroot not dynamic in xterm title
Status in bash package in Ubuntu:
New
Bug description:
Submitting a patch soon.
Without fix:
$ set|fgrep PS1|head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
With quotation fix applied:
$ set|fgrep PS1|head -1
PS1='\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 986779] Re: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis)
Actually https://git.launchpad.net/ubuntu/+source/apport/commit/apport/ui.py?h=ubuntu/quantal=5080c104ebb3a02c4f16a3f6646449db8c72b545 lists a fix (--hanging) for this being available since quantal. ** Tags removed: focal ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/986779 Title: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis) Status in apport package in Ubuntu: Fix Released Bug description: Wishlist: When ubuntu-bug is asked to send a bug on PID, it should check whether the PID shows symptoms of being in an infinite loop and if so, include stack trace of the process to the bug report or ask the user whether he would like to include details needed for retracing in the bug report. In many cases simply sending SEGV signal to the process does indeed manage to generate retraceable coredumps when /proc/sys/kernel/core_pattern points to apport, but such SEGVs can be masked for several reasons. Bug 986774 is an example of a bug report which would benefit from having this kind of feature in apport/ubuntu-bug - in that case pasuspender seems to be masking the apport SEGV handling. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 22 10:01:02 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120112) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en TERM=xterm PATH=(custom, no user) LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/986779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891745] Re: Xorg crashed with SIGSEGV in dixSaveScreens()
*** 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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1891634] Re: $ ubuntu-bug /var/crash/.crash does not work
Also https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie /whoopsie-id) claims "No errors have been reported from this system", which is consistent with no ".uploaded" files appearing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891634 Title: $ ubuntu-bug /var/crash/.crash does not work Status in apport package in Ubuntu: New Bug description: [Impact] 1. When trying to send a report manually, you can not 2. When next possibly unrelated crash of same process happens, .crash gets overwritten even when .crash.upload exists (upload not yet completed) 3. When trying to copy-paste the stacktrace as text, UI does not have such functionality [Test Case] Start Ubuntu Open terminal $ ubuntu-bug /var/crash/.crash # does not appear to send anything to errors.ubuntu.com, when NetworkManager claims missing network connectivity. In multihomed host renderer: networkd in netplan with some of the redundant bridge members lacking physical connectivity and/or offline usb tether backup networks tend to result in perfectly functional state = "routable" network that many ubuntu GUI tools refuse to work with anyway, is apport one of them? Similarly to bug #1825822 I attempted to $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash # but after clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change into ".uploaded". And before the "Send" the UI does not contain any obvious way to copy the report as text somewhere (note: just copy the .crash which is text format with base64 parts anyway, at least for now). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.6 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 CasperMD5CheckResult: skip CrashReports: 664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload 640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:28:31 2020 InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891634] Re: $ ubuntu-bug /var/crash/.crash does not work
** Description changed: [Impact] 1. When trying to send a report manually, you can not - 2. When next possibly unrelated crash of same process happens, .crash gets overwritten even if .crash.upload exists (= upload not yet completed?) - 3. When trying to copy-paste the stacktrace as text, UI does not have such functionality (and does not tell the user that .crash is just a text file) + 2. When next possibly unrelated crash of same process happens, .crash gets overwritten even when .crash.upload exists (upload not yet completed) + 3. When trying to copy-paste the stacktrace as text, UI does not have such functionality [Test Case] Start Ubuntu Open terminal $ ubuntu-bug /var/crash/.crash # does not appear to send anything to errors.ubuntu.com, when NetworkManager claims missing network connectivity. In multihomed host renderer: networkd in netplan with some of the redundant bridge members lacking physical connectivity and/or offline usb tether backup networks tend to result in perfectly functional state = "routable" network that many ubuntu GUI tools refuse to work with anyway, is apport one of them? Similarly to bug #1825822 I attempted to - $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking - "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change - into ".uploaded". And before the "Send" there does not appear to be any - obvious way to copy the report as text somewhere. + $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash # but after + clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not + change into ".uploaded". And before the "Send" the UI does not contain + any obvious way to copy the report as text somewhere (note: just copy + the .crash which is text format with base64 parts anyway, at least for + now). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.6 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 CasperMD5CheckResult: skip CrashReports: 664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload 640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:28:31 2020 InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891634 Title: $ ubuntu-bug /var/crash/.crash does not work Status in apport package in Ubuntu: New Bug description: [Impact] 1. When trying to send a report manually, you can not 2. When next possibly unrelated crash of same process happens, .crash gets overwritten even when .crash.upload exists (upload not yet completed) 3. When trying to copy-paste the stacktrace as text, UI does not have such functionality [Test Case] Start Ubuntu Open terminal $ ubuntu-bug /var/crash/.crash # does not appear to send anything to errors.ubuntu.com, when NetworkManager claims missing network connectivity. In multihomed host renderer: networkd in netplan with some of the redundant bridge members lacking physical connectivity and/or offline usb tether backup networks tend to result in perfectly functional state = "routable" network that many ubuntu GUI tools refuse to work with anyway, is apport one of them? Similarly to bug #1825822 I attempted to $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash # but after clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change into ".uploaded". And before the "Send" the UI does not contain any obvious way to copy the report as text somewhere (note: just copy the .crash which is text format with base64 parts anyway, at least for now). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.6 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 CasperMD5CheckResult: skip CrashReports: 664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload 640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:28:31 2020 InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64
[Touch-packages] [Bug 1891634] Re: $ ubuntu-bug /var/crash/.crash does not work
** Description changed: [Impact] 1. When trying to send a report manually, you can not - 2. When trying to copy-paste the stacktrace as text, you can not + 2. When next possibly unrelated crash of same process happens, .crash gets overwritten even if .crash.upload exists (= upload not yet completed?) + 3. When trying to copy-paste the stacktrace as text, UI does not have such functionality (and does not tell the user that .crash is just a text file) [Test Case] Start Ubuntu Open terminal - $ ubuntu-bug /var/crash/.crash does not appear to send anything to errors.ubuntu.com, when NetworkManager claims missing network connectivity. + $ ubuntu-bug /var/crash/.crash # does not appear to send anything to errors.ubuntu.com, when NetworkManager claims missing network connectivity. In multihomed host renderer: networkd in netplan with some of the redundant bridge members lacking physical connectivity and/or offline usb tether backup networks tend to result in perfectly functional state = "routable" network that many ubuntu GUI tools refuse to work with anyway, is apport one of them? Similarly to bug #1825822 I attempted to $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change into ".uploaded". And before the "Send" there does not appear to be any obvious way to copy the report as text somewhere. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.6 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 CasperMD5CheckResult: skip CrashReports: 664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload 640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:28:31 2020 InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891634 Title: $ ubuntu-bug /var/crash/.crash does not work Status in apport package in Ubuntu: New Bug description: [Impact] 1. When trying to send a report manually, you can not 2. When next possibly unrelated crash of same process happens, .crash gets overwritten even when .crash.upload exists (upload not yet completed) 3. When trying to copy-paste the stacktrace as text, UI does not have such functionality [Test Case] Start Ubuntu Open terminal $ ubuntu-bug /var/crash/.crash # does not appear to send anything to errors.ubuntu.com, when NetworkManager claims missing network connectivity. In multihomed host renderer: networkd in netplan with some of the redundant bridge members lacking physical connectivity and/or offline usb tether backup networks tend to result in perfectly functional state = "routable" network that many ubuntu GUI tools refuse to work with anyway, is apport one of them? Similarly to bug #1825822 I attempted to $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash # but after clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change into ".uploaded". And before the "Send" the UI does not contain any obvious way to copy the report as text somewhere (note: just copy the .crash which is text format with base64 parts anyway, at least for now). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.6 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 CasperMD5CheckResult: skip CrashReports: 664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload 640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:28:31 2020 InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1891745] [NEW] Xorg crashed with SIGSEGV in dixSaveScreens()
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 Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1891745 Title: Xorg crashed with SIGSEGV in
[Touch-packages] [Bug 1891634] [NEW] $ ubuntu-bug /var/crash/.crash does not work
Public bug reported: [Impact] 1. When trying to send a report manually, you can not 2. When trying to copy-paste the stacktrace as text, you can not [Test Case] Start Ubuntu Open terminal $ ubuntu-bug /var/crash/.crash does not appear to send anything to errors.ubuntu.com, when NetworkManager claims missing network connectivity. In multihomed host renderer: networkd in netplan with some of the redundant bridge members lacking physical connectivity and/or offline usb tether backup networks tend to result in perfectly functional state = "routable" network that many ubuntu GUI tools refuse to work with anyway, is apport one of them? Similarly to bug #1825822 I attempted to $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change into ".uploaded". And before the "Send" there does not appear to be any obvious way to copy the report as text somewhere. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.6 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 CasperMD5CheckResult: skip CrashReports: 664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload 640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:28:31 2020 InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: [Impact] 1. When trying to send a report manually, you can not - 2. When trying to copy-paste the stacktrace as text, you can not + 2. When trying to copy-paste the stacktrace as text, you can not [Test Case] Start Ubuntu Open terminal $ ubuntu-bug /var/crash/.crash does not appear to send anything to errors.ubuntu.com, when NetworkManager claims missing network connectivity. In multihomed host renderer: networkd in netplan with some of the redundant bridge members lacking physical connectivity and/or offline usb tether backup networks tend to result in perfectly functional state = "routable" network that many ubuntu GUI tools refuse to work with anyway, is apport one of them? - Similarly to bug#1825822 I attempted to + Similarly to bug #1825822 I attempted to $ ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash but after clicking "Send" the /var/crash/_usr_lib_xorg_Xorg.1000.upload does not change into ".uploaded". And before the "Send" there does not appear to be any obvious way to copy the report as text somewhere. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.6 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 CasperMD5CheckResult: skip CrashReports: - 664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload - 640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash + 664:1000:122:0:2020-08-14 12:54:19.625304351 +0300:2020-08-14 12:54:19.625304351 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.upload + 640:1000:122:26652112:2020-08-14 12:52:50.397685527 +0300:2020-08-14 13:24:21.161265896 +0300:/var/crash/_usr_lib_xorg_Xorg.1000.crash CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:28:31 2020 InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891634 Title: $ ubuntu-bug /var/crash/.crash does not work Status in apport package in Ubuntu: New Bug description: [Impact] 1. When trying to send a report manually, you can not 2. When trying to copy-paste the stacktrace as text, you can not [Test Case] Start Ubuntu Open terminal $ ubuntu-bug /var/crash/.crash does not appear to send anything to errors.ubuntu.com, when NetworkManager claims missing network connectivity. In multihomed host renderer: networkd in netplan with some of the redundant bridge members lacking physical connectivity and/or offline usb tether backup networks tend to result in perfectly functional state =
[Touch-packages] [Bug 986779] Re: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis)
No such feature seen yet on Focal version of ubuntu-bug either. ** Tags added: focal ** Changed in: apport (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/986779 Title: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis) Status in apport package in Ubuntu: Confirmed Bug description: Wishlist: When ubuntu-bug is asked to send a bug on PID, it should check whether the PID shows symptoms of being in an infinite loop and if so, include stack trace of the process to the bug report or ask the user whether he would like to include details needed for retracing in the bug report. In many cases simply sending SEGV signal to the process does indeed manage to generate retraceable coredumps when /proc/sys/kernel/core_pattern points to apport, but such SEGVs can be masked for several reasons. Bug 986774 is an example of a bug report which would benefit from having this kind of feature in apport/ubuntu-bug - in that case pasuspender seems to be masking the apport SEGV handling. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 22 10:01:02 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120112) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en TERM=xterm PATH=(custom, no user) LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/986779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871916] Re: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu
Not reproducible on fresh install on same hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871916] [NEW] Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu
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 Ubuntu Touch seeded 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'
[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites
Semi-worksforme @ OTA-15, as in symptoms disappeared for now. But we shall see whether actual bug(s) were addressed as well after after 10 weeks assuming no OTA-16 before that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1656551 Title: webbrowser only partially loads some https sites Status in Canonical System Image: Fix Committed Status in Oxide: New Status in webbrowser-app package in Ubuntu: Invalid Bug description: The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some https-secured sites correctly, such as https://www.amazon.com or https://www.amazon.de. The browser presents a warning about an invalid ssl certificate, although the certificate appears perfectly valid. It then presents the option to go back to a safe site or continue anyway. If I choose continue anyway, it starts to load the site, but never completes. After some time it stops loading and displays a rather incomplete version of the site. It is clearly composed of only some of the pages' elements and incomplete.The amount of the page that is displayed varies from time to time. It appears that transmission times out while loading the page. Test case: 1) Try loading https://www.amazon.com. Observe that webbrowser-app displays warning about invalid certificate, without any apparent reason. Chose "continue anyway". Observe, that the site is only incompletely loaded and unsable. 2) Try loading the web interface of my router: https://rkupper.no-ip.org/. This site uses a self-signed certificate, which is correctly displayed as a security risk. But self-signed certificates are a common use case on DSL or cable routers' web interfaces. Choose "continue anyway". You should see the login page of a fritz box router. Observe that the site is incompletely loaded and the login button does nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites after accepting self-signed certificate once
Confirming identical symptoms (symantec sites) to the ones mentioned in chromium issue linked above. Please consider removing misleading "self- signed" -part from bug title. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1656551 Title: webbrowser only partially loads some https sites after accepting self- signed certificate once Status in Canonical System Image: New Status in Oxide: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some https-secured sites correctly, such as https://www.amazon.com or https://www.amazon.de. The browser presents a warning about an invalid ssl certificate, although the certificate appears perfectly valid. It then presents the option to go back to a safe site or continue anyway. If I choose continue anyway, it starts to load the site, but never completes. After some time it stops loading and displays a rather incomplete version of the site. It is clearly composed of only some of the pages' elements and incomplete.The amount of the page that is displayed varies from time to time. It appears that transmission times out while loading the page. Test case: 1) Try loading https://www.amazon.com. Observe that webbrowser-app displays warning about invalid certificate, without any apparent reason. Chose "continue anyway". Observe, that the site is only incompletely loaded and unsable. 2) Try loading the web interface of my router: https://rkupper.no-ip.org/. This site uses a self-signed certificate, which is correctly displayed as a security risk. But self-signed certificates are a common use case on DSL or cable routers' web interfaces. Choose "continue anyway". You should see the login page of a fritz box router. Observe that the site is incompletely loaded and the login button does nothing at all. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457405] Re: Unconditional sb-closed cookie incompatible with some sites
Removed reference to one client of mine who happens to prefer security by obscurity over crystal box approaches. Clarified description a little bit as well and changed report to public. Test cases available on request, although shouldn't really be needed unless we want to white/blacklist this cookie per site. ** Description changed: - The sb-closed cookie added by bug #1329799 fix breaks some sites like - https://www.op.fi/op - - Extraneous cookies get classified as potential malware by several SSL - sites, but please keep this part private for now / edit this line out of - summary before disclosing this report. + The sb-closed cookie added by bug #1329799 fix breaks sites using WAFs + that classify extra cookies as malware or cookie poisoning. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1457405 Title: Unconditional sb-closed cookie incompatible with some sites Status in webbrowser-app package in Ubuntu: New Bug description: The sb-closed cookie added by bug #1329799 fix breaks sites using WAFs that classify extra cookies as malware or cookie poisoning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1457405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458704] Re: Cannot use online banking with Bank of Ireland
Is this just useragent-sniffing / them mis-identifying the browser as chrome 35? Or did you get other errors besides them complaining about browser version? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1458704 Title: Cannot use online banking with Bank of Ireland Status in webbrowser-app package in Ubuntu: New Bug description: visiting the below URL gives a compatibility error : I cannot paste URL with BQ device so adding as attachment from terminal instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1458704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431214] [NEW] Unattended-upgrades triggers kernel taint when rebuilding initrd
Public bug reported: Kernel logs from unattended-upgrades doing mkinitrd resemble Bug #1253155 symptoms. Mar 12 06:31:51 network kernel: [213747.796032] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213747.867554] xfs: module verification failed: signature and/or required key missing - tainting kernel Mar 12 06:31:51 network kernel: [213747.958590] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled Mar 12 06:31:51 network kernel: [213748.044351] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.055870] JFS: nTxBlock = 8192, nTxLock = 65536 Mar 12 06:31:51 network kernel: [213748.082768] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.085263] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.090305] NTFS driver 2.1.30 [Flags: R/O MODULE]. Mar 12 06:31:51 network kernel: [213748.092232] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.094614] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.096672] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.118238] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.119378] QNX4 filesystem 0.2.3 registered. Mar 12 06:31:51 network kernel: [213748.120663] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.123118] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.144586] xor: automatically using best checksumming function: Mar 12 06:31:51 network kernel: [213748.184004]avx : 35873.000 MB/sec Mar 12 06:31:51 network kernel: [213748.184139] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.252009] raid6: sse2x1 11454 MB/s Mar 12 06:31:51 network kernel: [213748.320008] raid6: sse2x2 14362 MB/s Mar 12 06:31:51 network kernel: [213748.388007] raid6: sse2x4 16577 MB/s Mar 12 06:31:51 network kernel: [213748.456004] raid6: avx2x1 22081 MB/s Mar 12 06:31:51 network kernel: [213748.524006] raid6: avx2x2 25473 MB/s Mar 12 06:31:51 network kernel: [213748.592005] raid6: avx2x4 29788 MB/s Mar 12 06:31:51 network kernel: [213748.592006] raid6: using algorithm avx2x4 (29788 MB/s) Mar 12 06:31:51 network kernel: [213748.592006] raid6: using avx2x2 recovery algorithm Mar 12 06:31:51 network kernel: [213748.609455] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213748.626343] bio: create slab bio-1 at 1 Mar 12 06:31:51 network kernel: [213748.660695] Btrfs loaded ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.1 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Thu Mar 12 10:32:26 2015 InstallationDate: Installed on 2014-12-20 (81 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: - Kernel logs from unattended-upgrades doing mkinitrd look resemble Bug + Kernel logs from unattended-upgrades doing mkinitrd resemble Bug #1253155 symptoms. Mar 12 06:31:51 network kernel: [213747.796032] Request for unknown module key 'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err -11 Mar 12 06:31:51 network kernel: [213747.867554] xfs: module verification failed: signature and/or required key missing - tainting kernel Mar 12 06:31:51 network kernel: [213747.958590] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled Mar 12 06:31:51 network kernel: [213748.044351] Request for unknown module key 'Magrathea: Glacier signing key:
[Touch-packages] [Bug 1052360] Re: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) for an unknown reason
Got matching issue because of /usr full on an old unattended precise setup that was trying to upgrade firefox. Almost-interesting part of dpkg log just in case: Errors were encountered while processing: /var/cache/apt/archives/firefox_32.0.3+build1-0ubuntu0.12.04.1_amd64.deb /var/cache/apt/archives/thunderbird_1%3a31.1.2+build1-0ubuntu0.12.04.1_amd64.de b Error in function: close failed in file object destructor: IOError: [Errno 9] Bad file descriptor Error in sys.excepthook: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/apport_python_hook.py, line 89, in apport_excepthook pr = apport.report.Report() AttributeError: 'module' object has no attribute 'report' Original exception was: IOError: [Errno 9] Bad file descriptor close failed in file object destructor: IOError: [Errno 9] Bad file descriptor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1052360 Title: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) for an unknown reason Status in “unattended-upgrades” package in Ubuntu: Confirmed Bug description: Happens by itself ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: unattended-upgrades 0.73ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-26.42-generic 3.0.42 Uname: Linux 3.0.0-26-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Tue Sep 18 09:24:15 2012 ExecutablePath: /usr/bin/unattended-upgrade InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/unattended-upgrade ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/sh PythonArgs: ['/usr/bin/unattended-upgrade'] SourcePackage: unattended-upgrades Title: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2012-08-24T13:58:31.952771 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1052360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
