[Bug 1971095] Re: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot)
$ journalctl -g 'Linux version' Apr 27 17:57:21 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) -- Boot 05683256b29947edb0c968d647346b52 -- Apr 28 03:04:05 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) -- Boot ce4c821e541d4983807d163d6651a939 -- May 01 18:48:21 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) -- Boot 8ae1e85dbd854870b942a4bf3a3c8d48 -- May 01 20:16:08 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) -- Boot c4f4000bf3094dceacbe78cd01e97ac6 -- May 01 21:41:27 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic 5.15.30) ... So far this has happened only once, hasn't been reproduced with same nor later kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971095 Title: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971095] Re: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot)
** Attachment added: "previous (successful) boot logs for comparison" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+attachment/5585653/+files/journalctl_b_-1_g_mpt2sas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971095 Title: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971095] [NEW] mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot)
Public bug reported: mpt2sas card driver failed to start properly after normal poweroff + restart. Logs attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-27-generic 5.15.0-27.28 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 2287 F pulseaudio /dev/snd/controlC1: iheino 2287 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 1 20:54:28 2022 InstallationDate: Installed on 2022-04-27 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "journalctl -b 0 -g mpt2sas # failed / latest boot" https://bugs.launchpad.net/bugs/1971095/+attachment/5585633/+files/journalctl_b_0_g_mpt2sas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971095 Title: mpt2sas_cm0: diag reset: FAILED (after shutdown -P and boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898814] Re: Under netplan with "renderer: networkd", Update-manager claims "No network connection detected, you can not download changelog information." even network is connected
As a workaround for this use case may want to try sudo systemctl stop NetworkManager.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898814 Title: Under netplan with "renderer: networkd", Update-manager claims "No network connection detected, you can not download changelog information." even network is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1898814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960366
Title:
skel.bashrc PS1 debian_chroot not dynamic in xterm title
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960366 Title: skel.bashrc PS1 debian_chroot not dynamic in xterm title To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960366
Title:
skel.bashrc PS1 debian_chroot not dynamic in xterm title
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952747] Re: amdgpu PSP load sos failed after hwe 5.11.0-27 -> -41 update
** Description changed: Regression to be analyzed further later. 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5) - Most relevant part of boot logs: + Most relevant part of boot logs (more in attachment): Nov 30 13:08:00 ub3ff kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13 Nov 30 13:08:00 ub3ff kernel: Linux version 5.11.0-41-generic (buildd@lgw01-amd64-005) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 (Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22) Nov 30 13:08:00 ub3ff kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro drm.debug=0x4 splash vt.handoff=7 [...] Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Will use PSP to load VCN firmware Nov 30 13:08:04 ub3ff systemd[1]: Finished Flush Journal to Persistent Storage. Nov 30 13:08:04 ub3ff kernel: snd_hda_intel :03:00.1: refused to change power state from D0 to D3hot Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_start [amdgpu]] *ERROR* PSP load sos failed! Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed Nov 30 13:08:04 ub3ff kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block failed -22 Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Fatal error during GPU init Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu: finishing device. - Nov 30 13:08:04 ub3ff kernel: [ cut here ] - Nov 30 13:08:04 ub3ff kernel: Memory manager not clean during takedown. - Nov 30 13:08:04 ub3ff kernel: WARNING: CPU: 4 PID: 424 at drivers/gpu/drm/drm_mm.c:998 drm_mm_takedown+0x23/0x30 [drm] - Nov 30 13:08:04 ub3ff kernel: Modules linked in: amdgpu(+) snd_hda_codec_realtek intel_rapl_msr 8021q garp mrp snd_hda_codec_generic mei_hdcp ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_common snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hda_core snd_hwdep input_leds coretemp soundwire_bus snd_soc_core iommu_v2 snd_compress ac97_bus kvm_intel gpu_sched joydev snd_pcm_dmaengine drm_ttm_helper ttm snd_pcm kvm snd_seq_midi drm_kms_helper snd_seq_midi_event crct10dif_pclmul ghash_clmulni_intel snd_rawmidi aesni_intel cec rc_core i2c_algo_bit crypto_simd snd_seq fb_sys_fops snd_seq_device cryptd snd_timer bridge glue_helper syscopyarea snd rapl sysfillrect soundcore stp sysimgblt intel_cstate llc wmi_bmof eeepc_wmi mei_me serio_raw efi_pstore at24 mei ie31200_edac mac_hid sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic usbhid hid uas usb_storage mfd_aaeon asus_wmi - Nov 30 13:08:04 ub3ff kernel: sparse_keymap crc32_pclmul psmouse firewire_ohci mpt3sas firewire_core i2c_i801 ahci i2c_smbus crc_itu_t xhci_pci raid_class e1000e lpc_ich libahci xhci_pci_renesas scsi_transport_sas wmi video - Nov 30 13:08:04 ub3ff kernel: CPU: 4 PID: 424 Comm: systemd-udevd Not tainted 5.11.0-41-generic #45~20.04.1-Ubuntu - Nov 30 13:08:04 ub3ff kernel: Hardware name: System manufacturer System Product Name/P8B WS, BIOS 2106 07/16/2012 + [...] Nov 30 13:08:04 ub3ff kernel: RIP: 0010:drm_mm_takedown+0x23/0x30 [drm] - Nov 30 13:08:04 ub3ff kernel: Code: 00 00 00 00 00 66 90 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 f8 75 01 c3 55 48 c7 c7 08 30 45 c0 48 89 e5 e8 13 86 98 e0 <0f> 0b 5d c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 - Nov 30 13:08:04 ub3ff kernel: RSP: :bc5d00da3930 EFLAGS: 00010286 - Nov 30 13:08:04 ub3ff kernel: RAX: RBX: 970a454c60e8 RCX: 0027 - Nov 30 13:08:04 ub3ff kernel: RDX: 0027 RSI: dfff RDI: 97111f518ac8 - Nov 30 13:08:04 ub3ff kernel: RBP: bc5d00da3930 R08: 97111f518ac0 R09: bc5d00da36f0 - Nov 30 13:08:04 ub3ff kernel: R10: 0001 R11: 0001 R12: 970a454c60e8 - Nov 30 13:08:04 ub3ff kernel: R13: 970a454c R14: 970a454c60d0 R15: 970a454c60e8 - Nov 30 13:08:04 ub3ff kernel: FS: 7f147a343880() GS:97111f50() knlGS: - Nov 30 13:08:04 ub3ff kernel: CS: 0010 DS: ES: CR0: 80050033 - Nov 30 13:08:04 ub3ff kernel: CR2: 56070c14 CR3: 000103772006 CR4: 001706e0 - Nov 30 13:08:04 ub3ff kernel: Call Trace: - Nov 30 13:08:04 ub3ff kernel: amdgpu_vram_mgr_fini+0xb3/0x130 [amdgpu] - Nov 30 13:08:04 ub3ff kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] - Nov 30 13:08:04 ub3ff kernel: amdgpu_bo_fini+0x12/0x40 [amdgpu] - Nov 30 13:08:04 ub3ff kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] - Nov 30 13:08:04
[Bug 1952747] Re: amdgpu PSP load sos failed after hwe 5.11.0-27 -> -41 update
Turning off secondary and tertiary monitors for the duration of the initial boot appears to work around this issue. Suspend-to-ram works with all monitors powered (same hardware configuration as in #1926400). ** Attachment added: "journalctl -b -1 -k | egrep -v 'audit|dbus-daemon'" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1952747/+attachment/5544367/+files/jou-b-k.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952747 Title: amdgpu PSP load sos failed after hwe 5.11.0-27 -> -41 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1952747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952747] [NEW] amdgpu PSP load sos failed after hwe 5.11.0-27 -> -41 update
Public bug reported: Regression to be analyzed further later. 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5) Most relevant part of boot logs: Nov 30 13:08:00 ub3ff kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13 Nov 30 13:08:00 ub3ff kernel: Linux version 5.11.0-41-generic (buildd@lgw01-amd64-005) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 (Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22) Nov 30 13:08:00 ub3ff kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro drm.debug=0x4 splash vt.handoff=7 [...] Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Will use PSP to load VCN firmware Nov 30 13:08:04 ub3ff systemd[1]: Finished Flush Journal to Persistent Storage. Nov 30 13:08:04 ub3ff kernel: snd_hda_intel :03:00.1: refused to change power state from D0 to D3hot Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_start [amdgpu]] *ERROR* PSP load sos failed! Nov 30 13:08:04 ub3ff kernel: [drm:psp_hw_init [amdgpu]] *ERROR* PSP firmware loading failed Nov 30 13:08:04 ub3ff kernel: [drm:amdgpu_device_fw_loading [amdgpu]] *ERROR* hw_init of IP block failed -22 Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu_device_ip_init failed Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: Fatal error during GPU init Nov 30 13:08:04 ub3ff kernel: amdgpu :03:00.0: amdgpu: amdgpu: finishing device. Nov 30 13:08:04 ub3ff kernel: [ cut here ] Nov 30 13:08:04 ub3ff kernel: Memory manager not clean during takedown. Nov 30 13:08:04 ub3ff kernel: WARNING: CPU: 4 PID: 424 at drivers/gpu/drm/drm_mm.c:998 drm_mm_takedown+0x23/0x30 [drm] Nov 30 13:08:04 ub3ff kernel: Modules linked in: amdgpu(+) snd_hda_codec_realtek intel_rapl_msr 8021q garp mrp snd_hda_codec_generic mei_hdcp ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_common snd_hda_codec x86_pkg_temp_thermal intel_powerclamp snd_hda_core snd_hwdep input_leds coretemp soundwire_bus snd_soc_core iommu_v2 snd_compress ac97_bus kvm_intel gpu_sched joydev snd_pcm_dmaengine drm_ttm_helper ttm snd_pcm kvm snd_seq_midi drm_kms_helper snd_seq_midi_event crct10dif_pclmul ghash_clmulni_intel snd_rawmidi aesni_intel cec rc_core i2c_algo_bit crypto_simd snd_seq fb_sys_fops snd_seq_device cryptd snd_timer bridge glue_helper syscopyarea snd rapl sysfillrect soundcore stp sysimgblt intel_cstate llc wmi_bmof eeepc_wmi mei_me serio_raw efi_pstore at24 mei ie31200_edac mac_hid sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic usbhid hid uas usb_storage mfd_aaeon asus_wmi Nov 30 13:08:04 ub3ff kernel: sparse_keymap crc32_pclmul psmouse firewire_ohci mpt3sas firewire_core i2c_i801 ahci i2c_smbus crc_itu_t xhci_pci raid_class e1000e lpc_ich libahci xhci_pci_renesas scsi_transport_sas wmi video Nov 30 13:08:04 ub3ff kernel: CPU: 4 PID: 424 Comm: systemd-udevd Not tainted 5.11.0-41-generic #45~20.04.1-Ubuntu Nov 30 13:08:04 ub3ff kernel: Hardware name: System manufacturer System Product Name/P8B WS, BIOS 2106 07/16/2012 Nov 30 13:08:04 ub3ff kernel: RIP: 0010:drm_mm_takedown+0x23/0x30 [drm] Nov 30 13:08:04 ub3ff kernel: Code: 00 00 00 00 00 66 90 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 f8 75 01 c3 55 48 c7 c7 08 30 45 c0 48 89 e5 e8 13 86 98 e0 <0f> 0b 5d c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 Nov 30 13:08:04 ub3ff kernel: RSP: :bc5d00da3930 EFLAGS: 00010286 Nov 30 13:08:04 ub3ff kernel: RAX: RBX: 970a454c60e8 RCX: 0027 Nov 30 13:08:04 ub3ff kernel: RDX: 0027 RSI: dfff RDI: 97111f518ac8 Nov 30 13:08:04 ub3ff kernel: RBP: bc5d00da3930 R08: 97111f518ac0 R09: bc5d00da36f0 Nov 30 13:08:04 ub3ff kernel: R10: 0001 R11: 0001 R12: 970a454c60e8 Nov 30 13:08:04 ub3ff kernel: R13: 970a454c R14: 970a454c60d0 R15: 970a454c60e8 Nov 30 13:08:04 ub3ff kernel: FS: 7f147a343880() GS:97111f50() knlGS: Nov 30 13:08:04 ub3ff kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 30 13:08:04 ub3ff kernel: CR2: 56070c14 CR3: 000103772006 CR4: 001706e0 Nov 30 13:08:04 ub3ff kernel: Call Trace: Nov 30 13:08:04 ub3ff kernel: amdgpu_vram_mgr_fini+0xb3/0x130 [amdgpu] Nov 30 13:08:04 ub3ff kernel: amdgpu_ttm_fini+0xab/0x100 [amdgpu] Nov 30 13:08:04 ub3ff kernel: amdgpu_bo_fini+0x12/0x40 [amdgpu] Nov 30 13:08:04 ub3ff kernel: gmc_v10_0_sw_fini+0x33/0x40 [amdgpu] Nov 30 13:08:04 ub3ff kernel: amdgpu_device_fini+0x2ea/0x52f [amdgpu] Nov 30 13:08:04 ub3ff kernel: amdgpu_driver_unload_kms+0x43/0x70 [amdgpu] Nov 30 13:08:04 ub3ff kernel:
[Bug 1926400] Re: amdgpu with mst WARNING and Kernel Oops on blanking/resume
Similar symptoms to https://gitlab.freedesktop.org/drm/amd/-/issues/1406 and repeats in some form most of the time when unlocking screen after screen blanking. After suspend somewhat more random behaviour (works more often than after blanking). ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1406 https://gitlab.freedesktop.org/drm/amd/-/issues/1406 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926400 Title: amdgpu with mst WARNING and Kernel Oops on blanking/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926400] Re: amdgpu with mst WARNING and Kernel Oops on blanking/resume
** Attachment added: "Possibly related to https://gitlab.freedesktop.org/drm/amd/-/issues/1406; https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5493225/+files/dmesg.20210429.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926400 Title: amdgpu with mst WARNING and Kernel Oops on blanking/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926400] Re: amdgpu with mst WARNING and Kernel Oops on blanking/resume
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5492985/+files/lspci-vvnn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926400 Title: amdgpu with mst WARNING and Kernel Oops on blanking/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926400] Re: amdgpu with mst WARNING and Kernel Oops on blanking/resume
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5492984/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926400 Title: amdgpu with mst WARNING and Kernel Oops on blanking/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926400] Re: amdgpu with mst WARNING and Kernel Oops on blanking/resume
** Description changed: HWE kernel appears to get more amdgpu MST related WARNINGs and Oopses than non-HWE, mostly after resume from blanking or suspend. Kernel logs for most recent one attached. - $ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > /tmp/oops20210428.txt - $ fgrep RIP /tmp/oops20210428.txt - Apr 26 09:06:11 ub3ff kernel: RIP: 0010:dcn20_validate_bandwidth_fp+0x9d/0xf0 [amdgpu] - Apr 26 09:06:11 ub3ff kernel: RIP: 0010:dcn10_get_dig_frontend+0x93/0xc0 [amdgpu] - Apr 28 08:23:04 ub3ff kernel: RIP: 0010:dc_link_allocate_mst_payload+0x1c9/0x1e0 [amdgpu] - Apr 28 08:23:04 ub3ff kernel: RIP: 0033:0x7fe6953a550b - Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dc_link_add_remote_sink+0x65/0x110 [amdgpu] - Apr 28 08:24:02 ub3ff kernel: RIP: 0033:0x7fe6953a550b - Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu] - Apr 28 08:24:02 ub3ff kernel: RIP: 0033:0x7fe6953a550b - Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu] + $ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > oops20210428.txt + $ fgrep RIP oops20210428.txt | cut -c 31- + RIP: 0010:dcn20_validate_bandwidth_fp+0x9d/0xf0 [amdgpu] + RIP: 0010:dcn10_get_dig_frontend+0x93/0xc0 [amdgpu] + RIP: 0010:dc_link_allocate_mst_payload+0x1c9/0x1e0 [amdgpu] + RIP: 0033:0x7fe6953a550b + RIP: 0010:dc_link_add_remote_sink+0x65/0x110 [amdgpu] + RIP: 0033:0x7fe6953a550b + RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu] + RIP: 0033:0x7fe6953a550b + RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 08:43:08 2021 InstallationDate: Installed on 2020-04-10 (382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926400 Title: amdgpu with mst WARNING and Kernel Oops on blanking/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926400] [NEW] amdgpu with mst WARNING and Kernel Oops on blanking/resume
Public bug reported: HWE kernel appears to get more amdgpu MST related WARNINGs and Oopses than non-HWE, mostly after resume from blanking or suspend. Kernel logs for most recent one attached. $ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > /tmp/oops20210428.txt $ fgrep RIP /tmp/oops20210428.txt Apr 26 09:06:11 ub3ff kernel: RIP: 0010:dcn20_validate_bandwidth_fp+0x9d/0xf0 [amdgpu] Apr 26 09:06:11 ub3ff kernel: RIP: 0010:dcn10_get_dig_frontend+0x93/0xc0 [amdgpu] Apr 28 08:23:04 ub3ff kernel: RIP: 0010:dc_link_allocate_mst_payload+0x1c9/0x1e0 [amdgpu] Apr 28 08:23:04 ub3ff kernel: RIP: 0033:0x7fe6953a550b Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dc_link_add_remote_sink+0x65/0x110 [amdgpu] Apr 28 08:24:02 ub3ff kernel: RIP: 0033:0x7fe6953a550b Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu] Apr 28 08:24:02 ub3ff kernel: RIP: 0033:0x7fe6953a550b Apr 28 08:24:02 ub3ff kernel: RIP: 0010:dm_dp_mst_get_modes+0xd9/0x210 [amdgpu] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 28 08:43:08 2021 InstallationDate: Installed on 2020-04-10 (382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal kernel-oops ** Attachment added: "journalctl -b -1 -k | egrep -v 'audit|dbus-daemon'" https://bugs.launchpad.net/bugs/1926400/+attachment/5492972/+files/oops20210428.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926400 Title: amdgpu with mst WARNING and Kernel Oops on blanking/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986779 Title: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/986779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings
*** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891636 Title: After recent updates Xorg crashes whenever entering Display Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1891636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891745 Title: Xorg crashed with SIGSEGV in dixSaveScreens() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1891745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891634 Title: $ ubuntu-bug /var/crash/.crash does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891636 Title: After recent updates Xorg crashes whenever entering Display Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1891636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891636 Title: After recent updates Xorg crashes whenever entering Display Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1891636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891634 Title: $ ubuntu-bug /var/crash/.crash does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891634 Title: $ ubuntu-bug /var/crash/.crash does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891745 Title: Xorg crashed with SIGSEGV in dixSaveScreens() To manage
[Bug 1891636] [NEW] After recent updates Xorg crashes whenever entering Display Settings
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891636 Title: After recent updates Xorg crashes whenever entering Display Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1891636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891634 Title: $ ubuntu-bug /var/crash/.crash does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986779 Title: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/986779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871916 Title: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872020] Re: package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: extra ; ; in postinst script?
** Patch added: "this patch let me dpkg --configure --pending successfully" https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1872020/+attachment/5351085/+files/grubpostinst.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872020 Title: package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: extra ;; in postinst script? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1872020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872020] [NEW] package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: extra ; ; in postinst script?
Public bug reported: (auto)upgrade failed, not analyzed further for now. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu25 AptOrdering: libwacom-bin:amd64: Remove NULL: ConfigurePending Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi Date: Fri Apr 10 07:00:51 2020 DuplicateSignature: package:shim-signed:1.40+15+1533136590.3beb971-0ubuntu1 Setting up grub-efi-amd64-signed (1.139+2.04-1ubuntu24) ... /var/lib/dpkg/info/grub-efi-amd64-signed.postinst: 23: Syntax error: word unexpected (expecting ")") dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 2 EFITables: huhti 09 04:46:02 ub3xx kernel: efi: EFI v2.31 by American Megatrends huhti 09 04:46:02 ub3xx kernel: efi: ACPI=0xdf38f000 ACPI 2.0=0xdf38f000 SMBIOS=0xdec24e98 MPS=0xfc9b0 huhti 09 04:46:02 ub3xx kernel: secureboot: Secure boot disabled huhti 09 04:46:02 ub3xx kernel: secureboot: Secure boot disabled ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-09-25 (1292 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-is-python2, 2.7.17-3 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.1ubuntu1 SourcePackage: shim-signed Title: package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to focal on 2020-04-09 (1 days ago) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal ** Summary changed: - package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: Assumes procfs to contain stuff that isn't there + package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: extra ;; in postinst script? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872020 Title: package shim-signed 1.40+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: extra ;; in postinst script? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1872020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871916 Title: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666650] Re: lpc_ich: Resource conflict(s) found affecting gpio_ich
*** This bug is a duplicate of bug 1486316 *** https://bugs.launchpad.net/bugs/1486316 ** This bug has been marked a duplicate of bug 1486316 lpc_ich: Resource conflict(s) found affecting gpio_ich -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/150 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1486316] Re: lpc_ich: Resource conflict(s) found affecting gpio_ich
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1486316 Title: lpc_ich: Resource conflict(s) found affecting gpio_ich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1486316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752251] Re: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy
@#9, Supposedly rasdaemon could handle MCEs on bionic+. Have not yet witnessed it working though, even on hardware that had dozen reports/year shown with mcelog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752251 Title: Missing mcelog userspace package in bionic - or maybe linux kernel config should disable mcelog_legacy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773004] Re: qemu-system-x86_64 segfaults during guest kernel boot
1. appears to depend on snapshot, given cloud images handle the LUNs fine as additional disks 2. debug symbols part may need more effort than I can spend on this Also appears to require the following PEBCAK configuration snippet, but that alone was not enough to reproduce the crash with stock cloud images: --- vmdef_crashes.xml +++ vmdef_works_ok.xml @@ -67,7 +67,7 @@ - + Apparently some cleanup had already removed the earlier /var/crash contents after May 23rd but since I can both reproduce and workaround this, might attempt reproducing this once I have debugging symbols set up. Whether OVMF is a requirement is unknown for now, but the crashing snapshot does use UEFI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773004 Title: qemu-system-x86_64 segfaults during guest kernel boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1773004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773004] Re: qemu-system-x86_64 segfaults during guest kernel boot
** Attachment added: "i440fx vm definition (same result with q35 too)" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1773004/+attachment/5143449/+files/ovmf_v02c.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773004 Title: qemu-system-x86_64 segfaults during guest kernel boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1773004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773004] [NEW] qemu-system-x86_64 segfaults during guest kernel boot
Public bug reported: Attempting to boot old 14.04 LTS snapshot in a VM with LUN passthrough results in segfaults. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qemu-system-x86 1:2.11+dfsg-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 23 22:12:54 2018 InstallationDate: Installed on 2018-05-20 (3 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: LENOVO ThinkServer TS140 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=88166613-97a3-4912-884e-46bc05b70a85 ro SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT99AUS dmi.board.name: ThinkServer TS140 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKT99AUS:bd09/19/2014:svnLENOVO:pnThinkServerTS140:pvr70A4000PEU:rvnLENOVO:rnThinkServerTS140:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: ThinkServer TS140 dmi.product.version: 70A4000PEU dmi.sys.vendor: LENOVO ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "guest kernel serial console output" https://bugs.launchpad.net/bugs/1773004/+attachment/5143433/+files/ovmf2.ttyS1.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773004 Title: qemu-system-x86_64 segfaults during guest kernel boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1773004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313446] Re: window disappears on toggle shade
As this bug most likely won't ever get fixed (since Unity7 development was scrapped), it might be useful to document the known workarounds here, starting with: 1: Start any window manager with working shade support, for example as follows: $ nohup openbox --replace >/dev/null & # Warning: If you are not familiar with openbox and alike, their default settings are rather minimalistic; no taskbars or app menus included after the replace above (see https://help.ubuntu.com/community/Openbox for more details). 2: Disable any references to shading if you want/need to use Unity $ gsettings list-recursively org.gnome.desktop.wm.keybindings | grep -i shade $ gsettings list-recursively org.gnome.desktop.wm.preferences | grep -i shade $ # ... followed by some form of gsettings set or reset to the ones listed (not tested) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313446 Title: window disappears on toggle shade To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656551 Title: webbrowser only partially loads some https sites To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656551 Title: webbrowser only partially loads some https sites after accepting self- signed certificate once To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1656551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483071] Re: Error creating new VM with OVMF
Reproduced the issue(*) with Xenial / 1.2.21-2ubuntu4. Following Zycorax's line of thinking(**), binary-patched virt-aa-helper to get rid of the error. $ perl -pi -e s/ovmf/OVMF/ virt-aa-helper *: selecting UEFI when creating vm with virt-manager fails to create vm and giving the apparmor profile load error instead. **: as well as further background discussions on the topic like https://www.redhat.com/archives/virt-tools-list/2014-September/msg00141.html referring to unified OVMF.fd as a dead-end solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483071 Title: Error creating new VM with OVMF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1483071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738063] Re: gnome-keyring-daemon assertion failures when changing password remotely
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738063 Title: gnome-keyring-daemon assertion failures when changing password remotely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/738063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1457405 Title: Unconditional sb-closed cookie incompatible with some sites To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1457405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458704 Title: Cannot use online banking with Bank of Ireland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1458704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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:
[Bug 1363519] Re: start-stop-daemon fails debsums check
Spotted this again on a fresh 14.04.1 LTS server (amd64) installation. Applied workaround from https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1363519/comments/11 and added it as another post-inst thing to do on all my installations, along with a verification (dpkg -V/debsums/tripwire/etc). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363519 Title: start-stop-daemon fails debsums check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1363519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426087] [NEW] swift stat container åbject fails when object exists and has non-ascii in name
Public bug reported:
$ swift stat -- container 'åbject'
Traceback (most recent call last):
File /usr/bin/swift, line 1479, in module
globals()['st_%s' % args[0]](parser, argv[1:], thread_manager)
File /usr/bin/swift, line 671, in st_stat
command_helpers.stat_object(conn, options, args, thread_manager)
File /usr/lib/python2.7/dist-packages/swiftclient/command_helpers.py, line
98, in stat_object
), skip_missing=True)
File /usr/lib/python2.7/dist-packages/swiftclient/multithreading.py, line
235, in print_items
self.print_msg('\n'.join(lines))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 58:
ordinal not in range(128)
$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_IE.UTF-8
LC_TIME=en_IE.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=en_IE.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_IE.UTF-8
LC_NAME=en_IE.UTF-8
LC_ADDRESS=en_IE.UTF-8
LC_TELEPHONE=en_IE.UTF-8
LC_MEASUREMENT=en_IE.UTF-8
LC_IDENTIFICATION=en_IE.UTF-8
LC_ALL=
Partial(*) temp fix (real fix is python3):
--- /usr/lib/python2.7/dist-packages/swiftclient/command_helpers.py.orig
2014-03-02 19:59:57.0 +0200
+++ /usr/lib/python2.7/dist-packages/swiftclient/command_helpers.py
2015-02-26 21:05:33.879047630 +0200
@@ -89,7 +89,7 @@
thread_manager.print_items((
('Account', conn.url.rsplit('/', 1)[-1]),
('Container', args[0]),
-('Object', args[1]),
+('Object', unicode(args[1], 'utf8')),
('Content Type', headers.get('content-type')),
('Content Length', content_length),
('Last Modified', headers.get('last-modified')),
*: Most likely similar issue exists for container names as well.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-swiftclient 1:2.0.3-0ubuntu1 [modified:
usr/lib/python2.7/dist-packages/swiftclient/command_helpers.py]
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
Date: Thu Feb 26 21:07:52 2015
InstallationDate: Installed on 2010-12-23 (1525 days ago)
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: python-swiftclient
UpgradeStatus: Upgraded to trusty on 2015-02-19 (7 days ago)
** Affects: python-swiftclient (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug i386 trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-swiftclient in Ubuntu.
https://bugs.launchpad.net/bugs/1426087
Title:
swift stat container åbject fails when object exists and has non-
ascii in name
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-swiftclient/+bug/1426087/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1426087] [NEW] swift stat container åbject fails when object exists and has non-ascii in name
Public bug reported:
$ swift stat -- container 'åbject'
Traceback (most recent call last):
File /usr/bin/swift, line 1479, in module
globals()['st_%s' % args[0]](parser, argv[1:], thread_manager)
File /usr/bin/swift, line 671, in st_stat
command_helpers.stat_object(conn, options, args, thread_manager)
File /usr/lib/python2.7/dist-packages/swiftclient/command_helpers.py, line
98, in stat_object
), skip_missing=True)
File /usr/lib/python2.7/dist-packages/swiftclient/multithreading.py, line
235, in print_items
self.print_msg('\n'.join(lines))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 58:
ordinal not in range(128)
$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_IE.UTF-8
LC_TIME=en_IE.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=en_IE.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_IE.UTF-8
LC_NAME=en_IE.UTF-8
LC_ADDRESS=en_IE.UTF-8
LC_TELEPHONE=en_IE.UTF-8
LC_MEASUREMENT=en_IE.UTF-8
LC_IDENTIFICATION=en_IE.UTF-8
LC_ALL=
Partial(*) temp fix (real fix is python3):
--- /usr/lib/python2.7/dist-packages/swiftclient/command_helpers.py.orig
2014-03-02 19:59:57.0 +0200
+++ /usr/lib/python2.7/dist-packages/swiftclient/command_helpers.py
2015-02-26 21:05:33.879047630 +0200
@@ -89,7 +89,7 @@
thread_manager.print_items((
('Account', conn.url.rsplit('/', 1)[-1]),
('Container', args[0]),
-('Object', args[1]),
+('Object', unicode(args[1], 'utf8')),
('Content Type', headers.get('content-type')),
('Content Length', content_length),
('Last Modified', headers.get('last-modified')),
*: Most likely similar issue exists for container names as well.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: python-swiftclient 1:2.0.3-0ubuntu1 [modified:
usr/lib/python2.7/dist-packages/swiftclient/command_helpers.py]
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic i686
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
Date: Thu Feb 26 21:07:52 2015
InstallationDate: Installed on 2010-12-23 (1525 days ago)
InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: python-swiftclient
UpgradeStatus: Upgraded to trusty on 2015-02-19 (7 days ago)
** Affects: python-swiftclient (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug i386 trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426087
Title:
swift stat container åbject fails when object exists and has non-
ascii in name
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-swiftclient/+bug/1426087/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004792] Re: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor
Fyi, crash reporter claimed two instances of running out of space being DuplicateOf this bug. In case of running out of inodes or disk space, crash reporter's If you notice further problems, try restarting the computer. advice sounds rather harmful. Maybe a topic for another bug report though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004792 Title: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1004792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588993] Re: mcelog does not work due to lack of kernel support
For the record, first ever CE reported by mcelog below on the hardware I have access to. No UCEs nor even repeating CEs seen. Have not tested mce-inject and/or apei/einj.ko kernel module. mcelog: failed to prefill DIMM database from DMI data Hardware event. This is not a software error. MCE 0 CPU 0 BANK 0 TIME 1422983269 Tue Feb 3 19:07:49 2015 MCG status: MCi status: Corrected error Error enabled MCA: Internal parity error STATUS 904f0005 MCGSTATUS 0 MCGCAP c09 APICID 0 SOCKETID 0 CPUID Vendor Intel Family 6 Model 60 Syslog entries for mcelog startup on up-to-date trusty do still mention that page-offlining is unsupported: Feb 19 08:26:04 gx1 mcelog: failed to prefill DIMM database from DMI data Feb 19 08:26:04 gx1 mcelog: Kernel does not support page offline interface ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588993 Title: mcelog does not work due to lack of kernel support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/588993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384943] Re: [SRU] Pinger crashes with segfault in libc
Another similar-looking crash file (3.3.8-1ubuntu6.2 as well) in case it could be useful. ** Attachment added: _usr_lib_squid3_pinger.0.crash https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4306990/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1384943] Re: [SRU] Pinger crashes with segfault in libc
Another similar-looking crash file (3.3.8-1ubuntu6.2 as well) in case it could be useful. ** Attachment added: _usr_lib_squid3_pinger.0.crash https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4306990/+files/_usr_lib_squid3_pinger.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384943 Title: [SRU] Pinger crashes with segfault in libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346828] Re: eth0 (e1000e): transmit queue 0 timed out
** Tags added: amd64 ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346828 Title: eth0 (e1000e): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1346828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346828] Re: eth0 (e1000e): transmit queue 0 timed out
Same symptoms on amd64 (trusty lts installation) Testing mentioned workaround. Vlans in use and vlan offload still on (by default). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346828 Title: eth0 (e1000e): transmit queue 0 timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1346828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405822] Re: Default ups.conf should have maxretry setting above examples section.
** Branch linked: lp:~iheino+ub/+junk/nut-upsconf-docfix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1405822 Title: Default ups.conf should have maxretry setting above examples section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1405822] Re: Default ups.conf should have maxretry setting above examples section.
** Branch linked: lp:~iheino+ub/+junk/nut-upsconf-docfix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405822 Title: Default ups.conf should have maxretry setting above examples section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405822] Re: Default ups.conf should have maxretry setting above examples section.
Merged the changes into 0006-ups-conf-maxretry.patch as requested. ** Patch added: http://bazaar.launchpad.net/~iheino+ub/+junk/nut-upsconf-docfix/diff/4/2; https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+attachment/4295435/+files/4_2.diff ** Changed in: nut (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1405822 Title: Default ups.conf should have maxretry setting above examples section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1405822] Re: Default ups.conf should have maxretry setting above examples section.
Merged the changes into 0006-ups-conf-maxretry.patch as requested. ** Patch added: http://bazaar.launchpad.net/~iheino+ub/+junk/nut-upsconf-docfix/diff/4/2; https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+attachment/4295435/+files/4_2.diff ** Changed in: nut (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405822 Title: Default ups.conf should have maxretry setting above examples section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405822] [NEW] Default ups.conf should have maxretry setting above examples section.
Public bug reported: Default/sample ups.conf has maxretry setting at end. Above that are examples and an empty line. Uncommenting any of the examples or merging with older configs are likely to end up with a broken config file, since the parser will interpret existing maxretries to be inside driver definition. Included patch follows conventions used in other nut config files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nut 2.7.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Fri Dec 26 20:06:50 2014 InstallationDate: Installed on 2014-12-20 (6 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) KernelVersion: Linux lmaas1 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux PackageArchitecture: all SourcePackage: nut UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nut (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty vivid ** Patch added: http://bazaar.launchpad.net/~iheino+ub/+junk/nut-upsconf-docfix/diff/3; https://bugs.launchpad.net/bugs/1405822/+attachment/4287849/+files/3_2.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1405822 Title: Default ups.conf should have maxretry setting above examples section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1405822] [NEW] Default ups.conf should have maxretry setting above examples section.
Public bug reported: Default/sample ups.conf has maxretry setting at end. Above that are examples and an empty line. Uncommenting any of the examples or merging with older configs are likely to end up with a broken config file, since the parser will interpret existing maxretries to be inside driver definition. Included patch follows conventions used in other nut config files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nut 2.7.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Fri Dec 26 20:06:50 2014 InstallationDate: Installed on 2014-12-20 (6 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) KernelVersion: Linux lmaas1 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux PackageArchitecture: all SourcePackage: nut UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nut (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty vivid ** Patch added: http://bazaar.launchpad.net/~iheino+ub/+junk/nut-upsconf-docfix/diff/3; https://bugs.launchpad.net/bugs/1405822/+attachment/4287849/+files/3_2.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405822 Title: Default ups.conf should have maxretry setting above examples section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850672] Re: port = auto does not work with bcmxcp_usb (powerware 5115)
Correction to above: Udevadm-trigger does seem to get fired. Symptoms looked indentical but might be a different issue this time. crw-rw-r-- 1 root nut 189, 258 Dec 26 02:00 /dev/bus/usb/003/003 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/850672 Title: port = auto does not work with bcmxcp_usb (powerware 5115) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/850672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850672] Re: port = auto does not work with bcmxcp_usb (powerware 5115)
Reinstalled nut on 14.04.1 with identical changes in config files, got same issue again. udevadm trigger does not seem to get activated, not even by replugging ups. (command used to start it right after install + editing config files: sudo service nut-server restart) Bus 003 Device 003: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x06da Phoenixtec Power Co., Ltd idProduct 0x0002 UPS bcdDevice1.00 iManufacturer 4 iProduct 24 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 60mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 09 21 00 01 00 01 22 00 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 20 ** Changed in: nut (Ubuntu) Status: Expired = New ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/850672 Title: port = auto does not work with bcmxcp_usb (powerware 5115) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/850672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850672] Re: port = auto does not work with bcmxcp_usb (powerware 5115)
Trusty issue seems to be different from original one, to actually get the error message printed I had to use: $ sudo -g nut -u nut upsdrvctl start ... which revealed an unrelated documentation bug in newer ups.conf. Might file another bug for that unless one is already filed. ** Tags removed: trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/850672 Title: port = auto does not work with bcmxcp_usb (powerware 5115) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/850672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 850672] Re: port = auto does not work with bcmxcp_usb (powerware 5115)
Correction to above: Udevadm-trigger does seem to get fired. Symptoms looked indentical but might be a different issue this time. crw-rw-r-- 1 root nut 189, 258 Dec 26 02:00 /dev/bus/usb/003/003 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850672 Title: port = auto does not work with bcmxcp_usb (powerware 5115) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/850672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850672] Re: port = auto does not work with bcmxcp_usb (powerware 5115)
Reinstalled nut on 14.04.1 with identical changes in config files, got same issue again. udevadm trigger does not seem to get activated, not even by replugging ups. (command used to start it right after install + editing config files: sudo service nut-server restart) Bus 003 Device 003: ID 06da:0002 Phoenixtec Power Co., Ltd UPS Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x06da Phoenixtec Power Co., Ltd idProduct 0x0002 UPS bcdDevice1.00 iManufacturer 4 iProduct 24 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 60mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ** UNRECOGNIZED: 09 21 00 01 00 01 22 00 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 20 ** Changed in: nut (Ubuntu) Status: Expired = New ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850672 Title: port = auto does not work with bcmxcp_usb (powerware 5115) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/850672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850672] Re: port = auto does not work with bcmxcp_usb (powerware 5115)
Trusty issue seems to be different from original one, to actually get the error message printed I had to use: $ sudo -g nut -u nut upsdrvctl start ... which revealed an unrelated documentation bug in newer ups.conf. Might file another bug for that unless one is already filed. ** Tags removed: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850672 Title: port = auto does not work with bcmxcp_usb (powerware 5115) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/850672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300507] Re: Rabbit password is reset on every upgrade which forces lockstep cluster restarts
FYI neel, current version in 14.04.1 LTS (1.5.4+bzr2294-0ubuntu1.1) does not seem include a fix for this. A backport (or SRU?) would be nice to have for this. Or a ReleaseNotes entry at least. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1300507 Title: Rabbit password is reset on every upgrade which forces lockstep cluster restarts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1300507/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1300507] Re: Rabbit password is reset on every upgrade which forces lockstep cluster restarts
FYI neel, current version in 14.04.1 LTS (1.5.4+bzr2294-0ubuntu1.1) does not seem include a fix for this. A backport (or SRU?) would be nice to have for this. Or a ReleaseNotes entry at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300507 Title: Rabbit password is reset on every upgrade which forces lockstep cluster restarts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1300507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360731] Re: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht)
I currently don't have access to the hardware, as that system was decommissioned/repurposed. May have access to it during xmas break. In any case patrick's observations suggest that next step should be https://wiki.ubuntu.com/Kernel/KernelBisection between 3.13.0.32-generic and 3.13.0-34-generic to find which commit introduced the regression. Although older kernel might just as well behave similarly to acpi=off; hard to say whether it does without access to the hw atm. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360731 Title: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002451] Re: Slow reconfiguration during kernel installation or removal
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002451 Title: Slow reconfiguration during kernel installation or removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1002451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1052360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360731] [NEW] Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht)
Public bug reported: Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P. Bios 1.05, newer (undocumented) version 1.11 untested so far. This hang does not occur on Ubuntu 12.04 LTS, but does on 14.04(.1) LTS, unless using acpi=off. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 1777 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 24 04:20:31 2014 HibernationDevice: RESUME=UUID=cd1b13ba-5c85-4c64-bf69-aefe3e92c2dc InstallationDate: Installed on 2014-08-21 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Acer Aspire V3-111P ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5a0c649c-474a-4809-851e-70f69f035055 ro quiet splash acpi=off RelatedPackageVersions: linux-restricted-modules-3.13.0-34-generic N/A linux-backports-modules-3.13.0-34-generic N/A linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd04/11/2014:svnAcer:pnAspireV3-111P:pvrV1.05:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V3-111P dmi.product.version: V1.05 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360731 Title: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1360731] Re: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht)
** Attachment added: dmidecode.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+attachment/4185639/+files/dmidecode.txt ** Description changed: Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P. - Bios 1.05, newer (undocumented) version 1.11 untested so far). + Bios 1.05, newer (undocumented) version 1.11 untested so far. This hang does not occur on Ubuntu 12.04 LTS, but does on 14.04(.1) LTS, unless using acpi=off. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-34-generic 3.13.0-34.60 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: iheino 1777 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: iheino 1777 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 24 04:20:31 2014 HibernationDevice: RESUME=UUID=cd1b13ba-5c85-4c64-bf69-aefe3e92c2dc InstallationDate: Installed on 2014-08-21 (2 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Acer Aspire V3-111P ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5a0c649c-474a-4809-851e-70f69f035055 ro quiet splash acpi=off RelatedPackageVersions: - linux-restricted-modules-3.13.0-34-generic N/A - linux-backports-modules-3.13.0-34-generic N/A - linux-firmware 1.127.5 + linux-restricted-modules-3.13.0-34-generic N/A + linux-backports-modules-3.13.0-34-generic N/A + linux-firmware 1.127.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd04/11/2014:svnAcer:pnAspireV3-111P:pvrV1.05:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire V3-111P dmi.product.version: V1.05 dmi.sys.vendor: Acer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1360731 Title: Acer Aspire V3-111P fails to boot with ACPI on (including acpi=ht) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088081] Re: udev rules make it impossible to deactivate lvm volume group with vgchange -an
** Tags added: quantal raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088081 Title: udev rules make it impossible to deactivate lvm volume group with vgchange -an To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1088081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093541] Re: ACPI Error: Method parse/execution failed
http://blog.le-vert.net/?p=24 reports ACPI 5.0 support as being 3.4 kernel territory. Got same message on P8B WS myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093541 Title: ACPI Error: Method parse/execution failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1093541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890337 Title: gvfs-gdu-volume-monitor high cpu usage during raid-resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/890337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170584] Re: installer unresponsive after attempting grub installation on partitionable raid
Retried after resync'ing to most recent live image. When installer got to the Executing 'grub-install /dev/vda' failed. This is a fatal error. Did not press ok this time, but ran the following: ubuntu@ubuntu:~$ sudo chroot /target apt-get install mdadm ubuntu@ubuntu:~$ sudo chroot /target grub-install --no-floppy /dev/vda /usr/sbin/grub-bios-setup: error: unable to identify a filesystem in hostdisk//dev/vda; safety check can't be performed. ubuntu@ubuntu:~$ sudo chroot /target grub-install --no-floppy /dev/vdb /usr/sbin/grub-bios-setup: error: unable to identify a filesystem in hostdisk//dev/vdb; safety check can't be performed. ubuntu@ubuntu:~$ sudo chroot /target grub-install /dev/vdc /usr/sbin/grub-bios-setup: error: unable to identify a filesystem in hostdisk//dev/vdc; safety check can't be performed. After that, clicked ok on that fatal error message mentioned above. Result is a Bootloader install failed dialog with rather peculiar UI behaviour: 1. mouse icon is a spinner everywhere else except on the text input dialog 2. text input dialog/dropdown does not allow keyboard input, but copy/paste with mouse works as well as opening the dropdown with mouse 3. choosing /dev/md_d2 from list will result in ok button being dimmed without explanation why, even if you choose cancel the installation after that After that, chose /dev/vdb this time and pressed ok. That resulted in rather misleading situation: Installation Complete dialog with continue testing / restart now -buttons was overlaid on top of Unable to install GRUB in /dev/vdb dialog, hiding that error entirely underneath. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170584 Title: installer unresponsive after attempting grub installation on partitionable raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1170584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068137] Re: grub2: Some modules may be missing from core image..
Reproduced during installation of raring as follows, is this same bug or different? 1. boot to livecd (desktop) 2. a) $ sudo apt-get install mdadm # not certain whether this step was needed on raring 2. b) $ sudo mdadm -C /dev/md_d2 -l 1 -n 1 -f -x 2 /dev/vd[abc] 3. run installer, tell it to use entire md_d2 disk for lvm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068137 Title: grub2: Some modules may be missing from core image.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1068137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170584] [NEW] installer unresponsive after attempting grub installation on partitionable raid
Public bug reported: 1. boot to livecd (desktop) 2. a) $ sudo apt-get install mdadm # not certain whether this part was needed 2. b) $ sudo mdadm -C /dev/md_d2 -l 1 -n 1 -f -x 2 /dev/vd[abc] 3. run installer, tell it to use entire md_d2 disk for lvm Results in: Executing 'grub-install /dev/vda' failed. This is a fatal error. Somewhat related to bug #1058129 and bug #1068137. After looking around a bit and possibly mounting things that were not mounted: $ sudo grub-install --root-directory=/target /dev/md_d2 Installation finished. No error reported. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.14.3 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CasperVersion: 1.330 Date: Fri Apr 19 09:28:08 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130418) MarkForUpload: True ProcEnviron: TERM=unknown PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ubiquity-2.14.3 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170584 Title: installer unresponsive after attempting grub installation on partitionable raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1170584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170584] Re: installer unresponsive after attempting grub installation on partitionable raid
** Description changed: 1. boot to livecd (desktop) - 2. a) $ sudo apt-get install mdadm # not certain whether this part was needed + 2. a) $ sudo apt-get install mdadm 2. b) $ sudo mdadm -C /dev/md_d2 -l 1 -n 1 -f -x 2 /dev/vd[abc] 3. run installer, tell it to use entire md_d2 disk for lvm Results in: Executing 'grub-install /dev/vda' failed. This is a fatal error. Somewhat related to bug #1058129 and bug #1068137. After looking around a bit and possibly mounting things that were not mounted: $ sudo grub-install --root-directory=/target /dev/md_d2 Installation finished. No error reported. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.14.3 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CasperVersion: 1.330 Date: Fri Apr 19 09:28:08 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130418) MarkForUpload: True ProcEnviron: TERM=unknown PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: 1. boot to livecd (desktop) - 2. a) $ sudo apt-get install mdadm - 2. b) $ sudo mdadm -C /dev/md_d2 -l 1 -n 1 -f -x 2 /dev/vd[abc] - 3. run installer, tell it to use entire md_d2 disk for lvm + 2. $ sudo apt-get install mdadm + 3. $ sudo mdadm -C /dev/md_d2 -l 1 -n 1 -f -x 2 /dev/vd[abc] + 4. run installer, tell it to use entire md_d2 disk for lvm Results in: Executing 'grub-install /dev/vda' failed. This is a fatal error. Somewhat related to bug #1058129 and bug #1068137. After looking around a bit and possibly mounting things that were not mounted: $ sudo grub-install --root-directory=/target /dev/md_d2 Installation finished. No error reported. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.14.3 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CasperVersion: 1.330 Date: Fri Apr 19 09:28:08 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130418) MarkForUpload: True ProcEnviron: TERM=unknown PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170584 Title: installer unresponsive after attempting grub installation on partitionable raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1170584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170584] Re: installer unresponsive after attempting grub installation on partitionable raid
Error message most likely was a result of mdadm missing from /target. But UI shouldn't hang then. $ sudo mount --bind /run/resolvconf/resolv.conf /target/etc/resolv.conf $ sudo chroot /target apt-get install mdadm $ sudo chroot /target grub-install /dev/md_d2 Installation finished. No error reported. ... that is still missing something to actually boot. Might be trying to boot off one of them virtual disks that have not been synced yet though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170584 Title: installer unresponsive after attempting grub installation on partitionable raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1170584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091032] Re: [ 0.884475] GHES: HEST is not enabled!
Error message also present in Precise. P.S. noticed the message only when attempting to find out whether bad page offlining support exists for Ivy Bridge; inconclusive on that so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091032 Title: [0.884475] GHES: HEST is not enabled! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1091032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968046] Re: unity-2d-shell crashed with SIGSEGV in ref()
libqtbamf1 0.2.4-0ubuntu1 fix works for me. unity-2d-shell 5.12.0-0ubuntu1 has a Depends: ... libqtbamf1 (= 0.1) though, as does unity-2d-panel; libunity-2d-private0 5.12.0-0ubuntu1 has a slightly more recent dependancy [libqtbamf1 (= 0.2.1)], but shouldn't that be updated to = 0.2.4 in whichever packages claim to fix this bug? P.S. https://wiki.ubuntu.com/Testing/EnableProposed should also be updated for Precise. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/968046 Title: unity-2d-shell crashed with SIGSEGV in ref() To manage notifications about this bug go to: https://bugs.launchpad.net/bamf-qt/+bug/968046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986774] [NEW] infinite loop in mumble at/near exit (ran with pasuspender alsa)
Public bug reported: Started mumble yesterday, first with pulseaudio but it didn't seem to work for reason or another, so quit that instance (successfully) and started another with pasuspender mumble . After using the program chose quit from menu, but apparently it got in an infinite loop. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: mumble 1.2.3-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 22 09:45:51 2012 ExecutablePath: /usr/bin/mumble InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120112) ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_IE.UTF-8 LANGUAGE=en_IE:en SourcePackage: mumble UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mumble (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986774 Title: infinite loop in mumble at/near exit (ran with pasuspender alsa) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/986774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986774] Re: infinite loop in mumble at/near exit (ran with pasuspender alsa since through pulseaudio is too buggy to use)
** Summary changed: - infinite loop in mumble at/near exit (ran with pasuspender alsa since through pulseaudio is too buggy to use) + infinite loop in mumble at/near exit (ran with pasuspender alsa) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986774 Title: infinite loop in mumble at/near exit (ran with pasuspender alsa) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/986774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986774] Re: infinite loop in mumble at/near exit (ran with pasuspender alsa)
reason or another above may have been Bug #911783 since symptoms were identical, using alsa helped earlier with sound quality issues; whether it is needed to reproduce this issue is unknown for the time being. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986774 Title: infinite loop in mumble at/near exit (ran with pasuspender alsa) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/986774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986774] Re: infinite loop in mumble at/near exit (ran with pasuspender alsa)
Since pasuspender seems to handle manually sent SEGVs to mumble, there does not seem to be a straightforward way to get apport-retrace of this... Backtrace: /usr/lib/libg15daemon_client.so.1(+0xd59) [0x7f292c3a3d59] Backtrace: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f292aa4ccb0] Backtrace: /lib/x86_64-linux-gnu/libpthread.so.0(pthread_cond_wait+0xc4) [0x7f292aa48d84] Backtrace: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN14QWaitCondition4waitEP6QMutexm+0x1bb) [0x7f2928ef34db] Backtrace: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QThread4waitEm+0xa8) [0x7f2928ef2be8] Backtrace: mumble() [0x5b17f2] Backtrace: mumble() [0x5b1829] Backtrace: mumble() [0x520d75] Backtrace: mumble() [0x43eb19] Backtrace: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f29282cb76d] Backtrace: mumble() [0x442fc9] End of Backtrace. TEST CASE: - configure mumble to use alsa for sound input output, text-to-speech off - run pasuspender mumble and choose quit from the menu Expected result: program quits and you get back to shell prompt. Actual result: mumble gets in an infinite loop Reproduced only with alsa, oss not tested. Does not occur when both input output are set to pulseaudio and mumble is ran without pasuspender. Additional notes: - run killall /usr/bin/speech-dispatcher between repeated test runs to return to pristine state - (another?) infinite loop also occurs if you try to change both input and output at same time back to pulseaudio, doing the change one at time avoids that infinite loop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986774 Title: infinite loop in mumble at/near exit (ran with pasuspender alsa) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/986774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986779] [NEW] ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis)
Public bug reported: 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) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986779 Title: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/986779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986779] Re: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986779 Title: ubuntu-bug lacks an option for collection stack trace of running process (infinite loop analysis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/986779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 985033] Re: noisy sound after starting mumble
I have noticed similar issues with ALC892, please have a look at Bug #975135. For me alsa-only (with pasuspender) seems to keep sound quality ok, but that setup has issues mentioned at Bug #986774. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/985033 Title: noisy sound after starting mumble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/985033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 879324] Re: apt-get dselect-upgrade prefers multiarch over native
Attempted a reinstallation/cloning of precise as follows: $ dpkg --get-selections | fgrep -c :i386 237 $ dpkg --get-selections selections.txt $ sftp clonehost # ... $ sudo dpkg --set-selections selections.txt $ sudo apt-get -y update $ sudo apt-get dselect-upgrade Ended up with bunch of errors and: $ dpkg -l | fgrep -c :i386 507 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879324 Title: apt-get dselect-upgrade prefers multiarch over native To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/879324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980502] Re: update-manager: E:Error, pkgProblemResolver::Resolve generated breaks
Seems related to bug #932581 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980502 Title: update-manager: E:Error, pkgProblemResolver::Resolve generated breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/980502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980502] [NEW] update-manager: E:Error, pkgProblemResolver::Resolve generated breaks
Public bug reported: Seen while attempting to upgrade couple weeks outdated installation of Precise: Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. Please report this bug against the 'update-manager' package and include the following error message: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.10 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Fri Apr 13 08:04:19 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: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980502 Title: update-manager: E:Error, pkgProblemResolver::Resolve generated breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/980502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980502] Re: update-manager: E:Error, pkgProblemResolver::Resolve generated breaks
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980502 Title: update-manager: E:Error, pkgProblemResolver::Resolve generated breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/980502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980502] Re: update-manager: E:Error, pkgProblemResolver::Resolve generated breaks
** Tags added: dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980502 Title: update-manager: E:Error, pkgProblemResolver::Resolve generated breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/980502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980502] Re: update-manager: E:Error, pkgProblemResolver::Resolve generated breaks
The following packages have unmet dependencies: gwibber : Depends: gwibber-service (= 3.4.0-0ubuntu2) but 3.4.0-0ubuntu3 is to be installed gwibber-service : Breaks: gwibber ( 3.4.0-0ubuntu3) but 3.4.0-0ubuntu2 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Might mean just that the mirrors are not yet up to date... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980502 Title: update-manager: E:Error, pkgProblemResolver::Resolve generated breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/980502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 975135] [NEW] [P8B WS, Realtek ALC892, Black Line Out, Rear] fails after a while (distortions after seek of streaming media)
Public bug reported: Some unusual sound usage patterns like seeking streaming media get the driver into a distorted state, where high-frequency chirps are added to all sound played. Seen on natty precise (not tested on others), on natty modprobe-cycled the driver to workaround the issue, on precise pasuspender alsactl init seems to be enough to get the driver play sanely again. Easiest way so far to reproduce this seems to be running speech- dispatcher (started by launching mumble quitting it) and firefox with html5 youtube at same time, playing some video with speech-only content where distortions are easiest to notice and seeking that forward and backward 10-20 times. Might be related to concurrently running applications with different sampling rates and making them interrupt playback at inconvenient times from the driver's point of view. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0-0ubuntu2 Architecture: amd64 Date: Fri Apr 6 15:31:11 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120112) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IE:en TERM=xterm LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Line Out, Rear Symptom_Type: Sound works for a while, then breaks Title: [System Product Name, Realtek ALC892, Black Line Out, Rear] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 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.:bvr0704:bd07/25/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975135 Title: [P8B WS, Realtek ALC892, Black Line Out, Rear] fails after a while (distortions after seek of streaming media) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/975135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 975135] Re: [P8B WS, Realtek ALC892, Black Line Out, Rear] fails after a while (distortions after seek of streaming media)
** Tags added: natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975135 Title: [P8B WS, Realtek ALC892, Black Line Out, Rear] fails after a while (distortions after seek of streaming media) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/975135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969968] [NEW] Kernel BUG - unable to handle kernel NULL pointer dereference; IP is at asus_wmi_rfkill_init+0x188/0x200
Public bug reported: Seen every time when booting Ubuntu 3.2.0-21.34-generic 3.2.13: [4.090752] asus_wmi: Initialization: 0x0 [4.090904] asus_wmi: BIOS WMI version: 0.9 [4.091026] asus_wmi: SFUN value: 0x0 [4.091131] ADDRCONF(NETDEV_UP): br3: link is not ready [4.091390] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input14 [4.093310] BUG: unable to handle kernel NULL pointer dereference at (null) [4.093460] IP: [a0238d08] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi] [4.093574] PGD 4025dc067 PUD 3fe9aa067 PMD 0 [4.093740] Oops: [#1] SMP [4.093869] CPU 0 [4.093908] Modules linked in: eeepc_wmi(+) asus_wmi sparse_keymap nvidia(P) snd_hda_codec_realtek psmouse bridge stp serio_raw snd_hda_intel(+) snd_seq_midi snd_hda_codec snd_hwdep snd_rawmidi snd_pcm snd_seq_midi_event snd_seq snd_timer snd_seq_device snd mei(C) video wmi mac_hid soundcore snd_page_alloc multipath linear raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid10 raid0 usb_storage usbhid hid raid1 firewire_ohci firewire_core crc_itu_t e1000e mpt2sas scsi_transport_sas raid_class [4.094221] [4.094223] Pid: 771, comm: modprobe Tainted: P C O 3.2.0-21-generic #34-Ubuntu System manufacturer System Product Name/P8B WS [4.094225] RIP: 0010:[a0238d08] [a0238d08] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi] [4.094229] RSP: 0018:88040412fc98 EFLAGS: 00010246 [4.094230] RAX: RBX: 880403fbc000 RCX: 1603 [4.094231] RDX: RSI: 000165a0 RDI: 88040e802600 [4.094232] RBP: 88040412fca8 R08: 00010021 R09: a02370bb [4.094234] R10: R11: R12: ffed [4.094235] R13: a0dfe088 R14: R15: 880403fbc400 [4.094237] FS: 7fea32031700() GS:88041f40() knlGS: [4.094238] CS: 0010 DS: ES: CR0: 8005003b [4.094240] CR2: CR3: 0004046a7000 CR4: 000406f0 [4.094241] DR0: DR1: DR2: [4.094242] DR3: DR6: 0ff0 DR7: 0400 [4.094244] Process modprobe (pid: 771, threadinfo 88040412e000, task 88040415ade0) [4.094245] Stack: [4.094246] 880403fbc000 880403fbc400 88040412fcd8 a0238ff7 [4.094248] 880403fbc400 a0dfe088 a0dfe088 [4.094250] 88040412fcf8 a0239194 a0dfe088 880403fbc410 [4.094252] Call Trace: [4.094255] [a0238ff7] asus_wmi_add+0x117/0x260 [asus_wmi] [4.094257] [a0239194] asus_wmi_probe+0x54/0x80 [asus_wmi] [4.094261] [813f6167] platform_drv_probe+0x17/0x20 [4.094263] [813f49c8] really_probe+0x68/0x190 [4.094265] [813f4c55] driver_probe_device+0x45/0x70 [4.094267] [813f4d2b] __driver_attach+0xab/0xb0 [4.094268] [813f4c80] ? driver_probe_device+0x70/0x70 [4.094270] [813f4c80] ? driver_probe_device+0x70/0x70 [4.094273] [813f3abc] bus_for_each_dev+0x5c/0x90 [4.094275] [813f478e] driver_attach+0x1e/0x20 [4.094276] [813f43e0] bus_add_driver+0x1a0/0x270 [4.094278] [813f5296] driver_register+0x76/0x140 [4.094280] [813f6726] platform_driver_register+0x46/0x50 [4.094282] [813f6758] platform_driver_probe+0x28/0xb0 [4.094284] [813f6ef1] platform_create_bundle+0xc1/0xf0 [4.094287] [a0239140] ? asus_wmi_add+0x260/0x260 [asus_wmi] [4.094289] [a0005000] ? 0xa0004fff [4.094291] [a023796a] asus_wmi_register_driver+0x5a/0x70 [asus_wmi] [4.094293] [a0005010] eeepc_wmi_init+0x10/0x1000 [eeepc_wmi] [4.094297] [81002040] do_one_initcall+0x40/0x180 [4.094300] [810a89ce] sys_init_module+0xbe/0x230 [4.094303] [81664602] system_call_fastpath+0x16/0x1b [4.094304] Code: 00 48 c7 c2 06 a7 23 a0 48 89 df e8 33 f3 ff ff 83 f8 ed 41 89 c4 74 08 85 c0 0f 85 f3 fe ff ff 48 8b 83 90 03 00 00 48 8b 40 40 80 38 00 75 18 41 83 fc ed 0f 84 e1 fe ff ff 45 85 e4 0f 84 d8 [4.094318] RIP [a0238d08] asus_wmi_rfkill_init+0x188/0x200 [asus_wmi] [4.094320] RSP 88040412fc98 [4.094321] CR2: [4.094348] ---[ end trace 4784ebf1674346de ]--- ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-21-generic 3.2.0-21.34 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: aplay: device_list:252: no soundcards found... ApportVersion: 2.0-0ubuntu2 Architecture: amd64
