[Bug 2060534]
Best I've got is to check a candidate file doesn't match the `filePath` or `summaryFile` of any `nsIMsgFolder`. If we're only looking for things starting with `nstmp` speed shouldn't be any more of an issue compared to iterating through the files. This wouldn't prevent accidentally deleting files in accounts that have been removed from Thunderbird but not from the file system. I guess we could look only in the files of active accounts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060534 Title: Thunderbird doesn't always clean nstmp cache files To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/2060534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945585] Re: Cannot burn Kubuntu ISO to DVD
Thank you, Thomas. Most interesting & helpful. As you suggested, I used Xfburn & that has worked OK. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945585 Title: Cannot burn Kubuntu ISO to DVD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1945585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945585] Re: Cannot burn Kubuntu ISO to DVD
** Description changed: Downloaded Kubuntu 21.04 ISO & checked SHA256, perfect match. Tried burning with K3B to a 4GB DVD. Stopped at 98% with a message "Fatal error during recording: Invalid argument." & ejected the DVD. I tried it on another machine, SAME problem. I then ran a simulated burn on both machines, to check it wasn't a HW problem, the same problem again. I'd already burned Kubuntu 20.04.3 to a DVD a couple of days before without any trouble at all! So I downloaded Kubuntu 21.10 (Beta), with the same results, the burn failed at 98%. - System + System Debian KDE 10.10 --- K3b Version: 18.8.1 KDE Version: 5.49.0 Qt Version: 5.11.3 Kernel: 5.10.0-0.bpo.8-amd64 Used versions --- growisofs: 7.1 growisofs --- Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0' /dev/sr0: engaging DVD-R DAO upon user request... /dev/sr0: reserving 1436098 blocks /dev/sr0: "Current Write Speed" is 16.4x1352KBps. - 98304/2941128704 ( 0.0%) @0.0x, remaining 2493:08 RBU 100.0% UBU 0.0% + 98304/2941128704 ( 0.0%) @0.0x, remaining 2493:08 RBU 100.0% UBU 0.0% + 98304/2941128704 ( 0.0%) @0.0x, remaining 4487:39 RBU 100.0% UBU 100.0% + 98304/2941128704 ( 0.0%) @0.0x, remaining 5983:32 RBU 100.0% UBU 100.0% + 98304/2941128704 ( 0.0%) @0.0x, remaining 7479:25 RBU 100.0% UBU 100.0% + 98304/2941128704 ( 0.0%) @0.0x, remaining 9473:56 RBU 100.0% UBU 100.0% + 98304/2941128704 ( 0.0%) @0.0x, remaining 10969:49 RBU 100.0% UBU 100.0% + 26574848/2941128704 ( 0.9%) @5.7x, remaining 45:41 RBU 100.0% UBU 98.6% + 56164352/2941128704 ( 1.9%) @6.4x, remaining 24:49 RBU 100.0% UBU 97.6% + [== ==] + 2474016768/2941128704 (84.1%) @12.7x, remaining 0:39 RBU 99.9% UBU 97.1% + 2532999168/2941128704 (86.1%) @12.8x, remaining 0:34 RBU 100.0% UBU 97.1% + 2589655040/2941128704 (88.0%) @12.3x, remaining 0:29 RBU 99.9% UBU 97.1% + 2649620480/2941128704 (90.1%) @13.0x, remaining 0:24 RBU 100.0% UBU 97.1% + 2710110208/2941128704 (92.1%) @13.1x, remaining 0:18 RBU 100.0% UBU 97.1% + 2768240640/2941128704 (94.1%) @12.6x, remaining 0:14 RBU 100.0% UBU 97.1% + 2829713408/2941128704 (96.2%) @13.3x, remaining 0:09 RBU 100.0% UBU 97.1% + 2891677696/2941128704 (98.3%) @13.4x, remaining 0:03 RBU 100.0% UBU 97.1% + + Second Machine + + + System Kubuntu 20.04.3 + --- + K3b Version: 19.12.3 + KDE Version: 5.67.0 + Qt Version: 5.12.8 + Kernel: 5.11.0-37-generic + + Used versions + --- + growisofs: 7.1 + + growisofs + --- + Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0' + /dev/sr0: engaging DVD-R DAO upon user request... + /dev/sr0: reserving 1436098 blocks + /dev/sr0: "Current Write Speed" is 16.4x1352KBps. + 98304/2941128704 ( 0.0%) @0.0x, remaining 2991:46 RBU 100.0% UBU 0.0% 98304/2941128704 ( 0.0%) @0.0x, remaining 4487:39 RBU 100.0% UBU 100.0% - 98304/2941128704 ( 0.0%) @0.0x, remaining 5983:32 RBU 100.0% UBU 100.0% - 98304/2941128704 ( 0.0%) @0.0x, remaining 7479:25 RBU 100.0% UBU 100.0% + 98304/2941128704 ( 0.0%) @0.0x, remaining 6482:10 RBU 100.0% UBU 100.0% + 98304/2941128704 ( 0.0%) @0.0x, remaining 7978:03 RBU 100.0% UBU 100.0% 98304/2941128704 ( 0.0%) @0.0x, remaining 9473:56 RBU 100.0% UBU 100.0% - 98304/2941128704 ( 0.0%) @0.0x, remaining 10969:49 RBU 100.0% UBU 100.0% -26574848/2941128704 ( 0.9%) @5.7x, remaining 45:41 RBU 100.0% UBU 98.6% -56164352/2941128704 ( 1.9%) @6.4x, remaining 24:49 RBU 100.0% UBU 97.6% + 98304/2941128704 ( 0.0%) @0.0x, remaining 11468:27 RBU 100.0% UBU 100.0% + 6422528/2941128704 ( 0.2%) @1.4x, remaining 198:00 RBU 100.0% UBU 99.5% +25657344/2941128704 ( 0.9%) @4.2x, remaining 54:55 RBU 100.0% UBU 99.5% +44892160/2941128704 ( 1.5%) @4.2x, remaining 35:29 RBU 100.0% UBU 99.5% +64126976/2941128704 ( 2.2%) @4.2x, remaining 26:55 RBU 100.0% UBU 99.5% + [== ==] + 2849112064/2941128704 (96.9%) @4.2x, remaining 0:17 RBU 100.0% UBU 99.5% + 2868346880/2941128704 (97.5%) @4.2x, remaining 0:13 RBU 100.0% UBU 99.0% + 2887581696/2941128704 (98.2%) @4.2x, remaining 0:10 RBU 100.0% UBU 99.5% + 2906816512/2941128704 (98.8%) @4.2x, remaining 0:06 RBU 100.0% UBU 99.5% + :-[ WRITE@LBA=15e9c0h failed with SK=5h/ASC=21h/ACQ=04h]: Invalid argument + :-( write failed: Invalid argument + /dev/sr0: flushing cache -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945585 Title: Cannot burn Kubuntu ISO to DVD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1945585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945585] [NEW] Cannot burn Kubuntu ISO to DVD
Public bug reported: Downloaded Kubuntu 21.04 ISO & checked SHA256, perfect match. Tried burning with K3B to a 4GB DVD. Stopped at 98% with a message "Fatal error during recording: Invalid argument." & ejected the DVD. I tried it on another machine, SAME problem. I then ran a simulated burn on both machines, to check it wasn't a HW problem, the same problem again. I'd already burned Kubuntu 20.04.3 to a DVD a couple of days before without any trouble at all! So I downloaded Kubuntu 21.10 (Beta), with the same results, the burn failed at 98%. System --- K3b Version: 18.8.1 KDE Version: 5.49.0 Qt Version: 5.11.3 Kernel: 5.10.0-0.bpo.8-amd64 Used versions --- growisofs: 7.1 growisofs --- Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0' /dev/sr0: engaging DVD-R DAO upon user request... /dev/sr0: reserving 1436098 blocks /dev/sr0: "Current Write Speed" is 16.4x1352KBps. 98304/2941128704 ( 0.0%) @0.0x, remaining 2493:08 RBU 100.0% UBU 0.0% 98304/2941128704 ( 0.0%) @0.0x, remaining 4487:39 RBU 100.0% UBU 100.0% 98304/2941128704 ( 0.0%) @0.0x, remaining 5983:32 RBU 100.0% UBU 100.0% 98304/2941128704 ( 0.0%) @0.0x, remaining 7479:25 RBU 100.0% UBU 100.0% 98304/2941128704 ( 0.0%) @0.0x, remaining 9473:56 RBU 100.0% UBU 100.0% 98304/2941128704 ( 0.0%) @0.0x, remaining 10969:49 RBU 100.0% UBU 100.0% 26574848/2941128704 ( 0.9%) @5.7x, remaining 45:41 RBU 100.0% UBU 98.6% 56164352/2941128704 ( 1.9%) @6.4x, remaining 24:49 RBU 100.0% UBU 97.6% ** Affects: 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/1945585 Title: Cannot burn Kubuntu ISO to DVD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1945585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846423]
I think you'll find the error message was added to events before the fix and is still there because there's no mechanism to remove it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938100] [NEW] Unable to print to usb connected HP Deskjet 2621
Public bug reported: I can print over wifi to the HP Deskjet 2621 1. However, Unable to print to usb connected HP Deskjet 2621 As soon as an attempt is made to reference the printer on the usb port or print over usb, the usb port is crashed/locked The problem seems to be with usblp, ippusbxd and apparmor If usblp is blacklisted, removed and apt remove ippusbxd is performed, the printer on the usb port can be referenced or printed to successfully. However, ippusbxd is required: a. to enable modification of network settings (Advanced Network Configuration) b. when a ghost printer is selected, causes message 'Getting printer information' in application print dialog window (more accurately - fails to communicate with usb connected printer in print dialog window) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Jul 27 09:05:23 2021 InstallCmdLine: file=/cdrom/preseed/xubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2021-07-24 (2 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ** Attachment added: "This screenshot shows the ghost printer in the application printer dialog window compared to actual queues displayed in 'Printers - localhost'" https://bugs.launchpad.net/bugs/1938100/+attachment/5513908/+files/Screenshot_2021-07-27_09-26-47.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938100 Title: Unable to print to usb connected HP Deskjet 2621 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1938100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
same issue with alienware i7-6700HQ CPU and GTX 965M running clean install of 20.04.2 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I'm seeing the same symptoms, screen scaling 125% gives 200%, when accessing a Ubuntu 20.04 VMware system via xdrp from Windows 10. My graphics driver is root@geoff-ubuntu-2004:~# lshw -c video *-display description: VGA compatible controller product: SVGA II Adapter vendor: VMware physical id: f bus info: pci@:00:0f.0 version: 00 width: 32 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=vmwgfx latency=64 resources: irq:16 ioport:1070(size=16) memory:e800-efff memory:fe00-fe7f memory:c-d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846423]
Comment on attachment 9227653 1560151-trigger-duration.diff [Approval Request Comment] Regression caused by (bug #): Bug 1555646 User impact if declined: Calendar item parsing fails to read a property, adds an error message to the item, other clients complain about it Testing completed (on c-c, etc.): Just landed Risk to taking this patch (and alternatives if risky): I don't see any risk, it's a correctness patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846423]
That's for your patch OpenJD, I've approved it and will have it checked in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846423]
Created attachment 9227653 1560151-trigger-duration.diff I sure would. I hate this error message too, but I've never had the time to figure it out. FWIW, `X-` properties are [allowed in the specification](https://datatracker.ietf.org/doc/html/rfc5545#section-3.8.8.2) and should be ignored by implementations that don't understand them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846423 Title: Lightning: Cannot dismiss reminders. Got a VALUE parameter with an illegal type for property: VALUE=DURATION To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1846423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923277] [NEW] package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st
Public bug reported: Error came up after doing a fresh install of ubuntu 20.10 from disk. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 19:56:28 2021 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-10 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923277 Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1923277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917748] [NEW] datehook functions missing in Secure Boot mode
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 Package: grub-efi-amd64-signed 1.142.11+2.04-1ubuntu26.9 datehook.mod provides variables such as $HOUR, $DAY - we use these to control the boot options on a large number of classroom PCs. This module is not included in the signed grub binary, so when Secure Boot is enabled on the PC, our custom grub config no longer works. Can you include datehook.mod in future releases please? ** Affects: grub2 (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/1917748 Title: datehook functions missing in Secure Boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1917748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909117] Re: Repeated kernel OOPS in dentry_unlink_inode
Since moving to 5.4.0-65.73 I've twice experienced a crash in raw_spin_lock(). Is this related or a different issue? This happened at 5:11pm yesterday. [274680.293259] BUG: unable to handle page fault for address: c0561000 [274680.293276] #PF: supervisor write access in kernel mode [274680.293286] #PF: error_code(0x0003) - permissions violation [274680.293296] PGD 231a0e067 P4D 231a0e067 PUD 231a10067 PMD 888c98067 PTE 897308161 [274680.293310] Oops: 0003 [#1] SMP NOPTI [274680.293318] CPU: 0 PID: 130 Comm: kswapd0 Not tainted 5.4.0-65-generic #73-Ubuntu [274680.293331] Hardware name: Gigabyte Technology Co., Ltd. Z390 GAMING X/Z390 GAMING X-CF, BIOS F6 12/04/2018 [274680.293349] RIP: 0010:_raw_spin_lock+0xc/0x30 [274680.293357] Code: 0f c1 07 a9 ff 01 00 00 75 07 4c 89 e0 41 5c 5d c3 e8 98 98 62 ff 4c 89 e0 41 5c 5d c3 90 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 01 c3 55 89 c6 48 89 e5 e8 62 80 62 ff 66 90 5d c3 [274680.293386] RSP: 0018:afd740337a88 EFLAGS: 00010246 [274680.293396] RAX: RBX: 9d9753264650 RCX: [274680.293408] RDX: 0001 RSI: 9d96d3264650 RDI: c0561000 [274680.293420] RBP: afd740337ac0 R08: R09: afd740337cb0 [274680.293432] R10: R11: 0010 R12: 9d9b557208e8 [274680.293444] R13: 9d96d3264650 R14: c0561000 R15: [274680.293457] FS: () GS:9d9b5e20() knlGS: [274680.293470] CS: 0010 DS: ES: CR0: 80050033 [274680.293480] CR2: c0561000 CR3: 000231a0a002 CR4: 003606f0 [274680.293492] DR0: DR1: DR2: [274680.293505] DR3: DR6: fffe0ff0 DR7: 0400 [274680.293517] Call Trace: [274680.293524] ? list_lru_add+0x6c/0x1c0 [274680.293534] inode_lru_list_add+0x24/0x50 [274680.293542] iput+0x1e8/0x210 [274680.293549] dentry_unlink_inode+0xc6/0x110 [274680.293557] __dentry_kill+0xdf/0x180 [274680.293565] shrink_dentry_list+0x4e/0xc0 [274680.293573] prune_dcache_sb+0x5c/0x80 [274680.293582] super_cache_scan+0xfe/0x1b0 [274680.293591] do_shrink_slab+0x150/0x2a0 [274680.293599] shrink_slab+0x20c/0x2a0 [274680.293606] shrink_node+0xd3/0x410 [274680.293614] balance_pgdat+0x319/0x590 [274680.293622] kswapd+0x1f8/0x3c0 [274680.293629] ? wait_woken+0x80/0x80 [274680.293637] kthread+0x104/0x140 [274680.293644] ? balance_pgdat+0x590/0x590 [274680.293652] ? kthread_park+0x90/0x90 [274680.294130] ret_from_fork+0x35/0x40 [274680.294593] Modules linked in: ipt_REJECT nf_reject_ipv4 xt_multiport xt_MASQUERADE xt_nat xt_dscp xt_DSCP xt_hashlimit xt_length xt_tcpudp xt_state xt_conntrack nf_log_ipv4 nf_log_common xt_LOG iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_filter bpfilter binfmt_misc nls_iso8859_1 si2157 lgdt3306a dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua cx231xx_dvb dvb_core cx231xx_alsa cx25840 cx231xx videobuf_vmalloc tveeprom cx2341x videobuf_core i2c_mux videodev mc intel_rapl_msr mei_hdcp snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt intel_rapl_common snd_sof_intel_ipc x86_pkg_temp_thermal intel_powerclamp snd_sof kvm_intel snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi kvm snd_soc_core snd_hda_codec_realtek snd_compress snd_hda_codec_generic ledtrig_audio ac97_bus rapl ir_rc5_decoder intel_cstate snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_hda_codec [274680.294608] snd_hda_core input_leds snd_hwdep serio_raw snd_pcm snd_timer snd intel_wmi_thunderbolt wmi_bmof rc_hauppauge soundcore mei_me mceusb rc_core mei intel_pch_thermal mac_hid acpi_pad sch_fq_codel coretemp parport_pc ppdev lp parport ip_tables x_tables autofs4 xfs btrfs zstd_compress raid10 raid0 multipath linear raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel crypto_simd cryptd glue_helper i2c_algo_bit drm_kms_helper mpt3sas syscopyarea sysfillrect i2c_i801 sysimgblt raid_class fb_sys_fops scsi_transport_sas drm e1000e ahci libahci wmi video pinctrl_cannonlake pinctrl_intel [274680.301352] CR2: c0561000 [274680.301976] ---[ end trace 40ffc2777ae81e7c ]--- [274680.302600] RIP: 0010:_raw_spin_lock+0xc/0x30 [274680.303227] Code: 0f c1 07 a9 ff 01 00 00 75 07 4c 89 e0 41 5c 5d c3 e8 98 98 62 ff 4c 89 e0 41 5c 5d c3 90 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 01 c3 55 89 c6 48 89 e5 e8 62 80 62 ff 66 90 5d c3 [274680.304540] RSP: 0018:afd740337a88 EFLAGS: 00010246 [274680.305200] RAX: RBX: 9d9753264650 RCX: [274680.305864] RDX: 0001 RSI: 9d96d3264650 RDI: c0561000 [274680.306530] RBP: afd740337ac0 R08: R0
[Bug 1909117] Re: Repeated kernel OOPS in dentry_unlink_inode
Done. We'll see if this occurs again. FYI my system got a lot more stable once I moves /tmp off my M.2 drive around the end of Dec. The drive was showing clean and not logging any SMART errors, and I hadn't seen another dentry_unlink_inode fault until last week (though that one was due to some minor XFS corruption on a different drive). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909117 Title: Repeated kernel OOPS in dentry_unlink_inode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909117] Re: Repeated kernel OOPS in dentry_unlink_inode
Another triggered at 12:04am last night. Here's what's running: find / -ls 2>/dev/null | gzip -c > /backupvol/rootfs/MANIFEST.gz Top confirms: top - 00:04:17 up 1 day, 13:05, 1 user, load average: 3.26, 2.38, 1.71 Tasks: 290 total, 3 running, 287 sleeping, 0 stopped, 0 zombie %Cpu(s): 8.8 us, 5.6 sy, 0.0 ni, 83.0 id, 0.0 wa, 0.0 hi, 2.7 si, 0.0 st MiB Mem : 31977.6 total,235.1 free, 6346.5 used, 25396.0 buff/cache MiB Swap: 8192.0 total, 8184.5 free, 7.5 used. 25146.1 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 266530 root 20 0 17956 12780 3288 R 90.0 0.0 1:04.16 find / -ls 266531 root 20 03252 1736 1184 R 30.5 0.0 0:21.79 gzip -c Kernel logs attached: root@nas:/var/log# grep "Dec 24 00:04:" kern.log Dec 24 00:04:18 nas kernel: [133551.460463] general protection fault: [#4] SMP NOPTI Dec 24 00:04:18 nas kernel: [133551.461133] CPU: 3 PID: 266530 Comm: find Tainted: G D 5.4.0-58-generic #64-Ubuntu Dec 24 00:04:18 nas kernel: [133551.461806] Hardware name: Gigabyte Technology Co., Ltd. Z390 GAMING X/Z390 GAMING X-CF, BIOS F6 12/04/2018 Dec 24 00:04:18 nas kernel: [133551.462492] RIP: 0010:_raw_spin_lock+0xc/0x30 Dec 24 00:04:18 nas kernel: [133551.463224] Code: 0f c1 07 a9 ff 01 00 00 75 07 4c 89 e0 41 5c 5d c3 e8 38 aa 62 ff 4c 89 e0 41 5c 5d c3 90 0f 1f 44 00 00 31 c0 ba 01 00 00 00 0f b1 17 75 01 c3 55 89 c6 48 89 e5 e8 02 92 62 ff 66 90 5d c3 Dec 24 00:04:18 nas kernel: [133551.464658] RSP: 0018:b70541343d80 EFLAGS: 00010246 Dec 24 00:04:18 nas kernel: [133551.465382] RAX: RBX: 913354783980 RCX: 0001 Dec 24 00:04:18 nas kernel: [133551.466112] RDX: 0001 RSI: 9132d4783980 RDI: ff913952b13ec0ff Dec 24 00:04:18 nas kernel: [133551.466844] RBP: b70541343db8 R08: 0001 R09: 0064 Dec 24 00:04:18 nas kernel: [133551.467613] R10: 0900 R11: R12: 9139471f84c7 Dec 24 00:04:18 nas kernel: [133551.468353] R13: 9132d4783980 R14: ff913952b13ec0ff R15: Dec 24 00:04:18 nas kernel: [133551.469096] FS: 7f395597f800() GS:91395e2c() knlGS: Dec 24 00:04:18 nas kernel: [133551.469846] CS: 0010 DS: ES: CR0: 80050033 Dec 24 00:04:18 nas kernel: [133551.470599] CR2: 7f7798646dd0 CR3: 0973c005 CR4: 003606e0 Dec 24 00:04:18 nas kernel: [133551.471357] DR0: DR1: DR2: Dec 24 00:04:18 nas kernel: [133551.472117] DR3: DR6: fffe0ff0 DR7: 0400 Dec 24 00:04:18 nas kernel: [133551.472874] Call Trace: Dec 24 00:04:18 nas kernel: [133551.473634] ? list_lru_add+0x6c/0x1c0 Dec 24 00:04:18 nas kernel: [133551.474394] d_lru_add+0x48/0x60 Dec 24 00:04:18 nas kernel: [133551.475153] dput+0x187/0x2f0 Dec 24 00:04:18 nas kernel: [133551.475894] path_put+0x16/0x30 Dec 24 00:04:18 nas kernel: [133551.476616] vfs_statx+0x9f/0xe0 Dec 24 00:04:18 nas kernel: [133551.477332] __do_sys_newfstatat+0x36/0x70 Dec 24 00:04:18 nas kernel: [133551.478045] __x64_sys_newfstatat+0x1e/0x20 Dec 24 00:04:18 nas kernel: [133551.478755] do_syscall_64+0x57/0x190 Dec 24 00:04:18 nas kernel: [133551.479479] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 24 00:04:18 nas kernel: [133551.480192] RIP: 0033:0x7f3955b4db2f Dec 24 00:04:18 nas kernel: [133551.480903] Code: 00 b8 ff ff ff ff c3 0f 1f 40 00 f3 0f 1e fa 41 89 f9 45 89 c2 89 f7 48 89 d6 48 89 ca 41 83 f9 01 77 30 b8 06 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 09 c3 0f 1f 84 00 00 00 00 00 48 8b 15 29 a3 Dec 24 00:04:18 nas kernel: [133551.482350] RSP: 002b:7fffcffd3838 EFLAGS: 0246 ORIG_RAX: 0106 Dec 24 00:04:18 nas kernel: [133551.483066] RAX: ffda RBX: 7fffcffd3900 RCX: 7f3955b4db2f Dec 24 00:04:18 nas kernel: [133551.483826] RDX: 7fffcffd3900 RSI: 55a302ed3c88 RDI: 000a Dec 24 00:04:18 nas kernel: [133551.484517] RBP: 7fffcffd3900 R08: 0100 R09: 0001 Dec 24 00:04:18 nas kernel: [133551.485194] R10: 0100 R11: 0246 R12: 55a302ed3c88 Dec 24 00:04:18 nas kernel: [133551.485858] R13: 55a302e94d40 R14: 000b R15: 55a302ed3b80 Dec 24 00:04:18 nas kernel: [133551.486507] Modules linked in: cfg80211 ipt_REJECT nf_reject_ipv4 xt_multiport xt_MASQUERADE xt_nat xt_dscp xt_DSCP xt_hashlimit xt_length xt_tcpudp xt_state xt_conntrack nf_log_ipv4 nf_log_common xt_LOG iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_filter bpfilter binfmt_misc nls_iso8859_1 dm_multipath si2157 scsi_dh_rdac scsi_dh_emc scsi_dh_alua lgdt3306a cx231xx_dvb dvb_core cx231xx_alsa cx25840 cx231xx videobuf_vmalloc tveeprom cx2341x videobuf_core i2c_mux videodev mc intel_rapl_ms
[Bug 1909117] [NEW] Repeated kernel OOPS in dentry_unlink_inode
Public bug reported: Happened twice last night, precisely one hour apart root@nas:/var/log# grep "Dec 23 0[23]:13:" /var/log/syslog* /var/log/syslog:Dec 23 02:13:01 nas CRON[156065]: (root) CMD (date >> /var/log/sensors.log; /usr/bin/sensors -f >> /var/log/sensors.log) /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404588] BUG: kernel NULL pointer dereference, address: 0408 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404607] #PF: supervisor write access in kernel mode /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404616] #PF: error_code(0x0002) - not-present page /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404626] PGD 0 P4D 0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404632] Oops: 0002 [#1] SMP NOPTI /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404640] CPU: 6 PID: 130 Comm: kswapd0 Not tainted 5.4.0-58-generic #64-Ubuntu /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404652] Hardware name: Gigabyte Technology Co., Ltd. Z390 GAMING X/Z390 GAMING X-CF, BIOS F6 12/04/2018 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404671] RIP: 0010:dentry_unlink_inode+0x56/0x110 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404680] Code: 00 08 00 74 08 65 48 ff 05 6f ee 32 6f 49 8b 84 24 b8 00 00 00 48 85 c0 74 2c 49 8b 94 24 b0 00 00 00 48 89 10 48 85 d2 74 04 <48> 89 42 08 49 c7 84 24 b0 00 00 00 00 00 00 00 49 c7 84 24 b8 00 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404708] RSP: 0018:b70540327b18 EFLAGS: 00010206 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404718] RAX: 9131de578680 RBX: 9134d3266c00 RCX: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404732] RDX: 0400 RSI: 91395d9c9fa8 RDI: 9134d32666c0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404746] RBP: b70540327b28 R08: 02ad R09: b70540327cb0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404760] R10: R11: 0010 R12: 9134d32666c0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404772] R13: 9131de578548 R14: 9134d32666c0 R15: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404786] FS: () GS:91395e38() knlGS: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404800] CS: 0010 DS: ES: CR0: 80050033 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404810] CR2: 0408 CR3: 000117e0a006 CR4: 003606e0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404822] DR0: DR1: DR2: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404837] DR3: DR6: fffe0ff0 DR7: 0400 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404851] Call Trace: /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404858] __dentry_kill+0xdf/0x180 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404866] shrink_dentry_list+0x4e/0xc0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404874] prune_dcache_sb+0x5c/0x80 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404882] super_cache_scan+0xfe/0x1b0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404891] do_shrink_slab+0x150/0x2a0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404900] shrink_slab+0x20c/0x2a0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404908] shrink_node+0xd3/0x410 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404916] balance_pgdat+0x319/0x590 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404924] kswapd+0x1f8/0x3c0 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404932] ? wait_woken+0x80/0x80 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404940] kthread+0x104/0x140 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404946] ? balance_pgdat+0x590/0x590 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404954] ? kthread_park+0x90/0x90 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.404963] ret_from_fork+0x35/0x40 /var/log/syslog:Dec 23 02:13:10 nas kernel: [54882.405418] Modules linked in: ipt_REJECT nf_reject_ipv4 xt_multiport xt_MASQUERADE xt_nat xt_dscp xt_DSCP xt_hashlimit xt_length xt_tcpudp xt_state xt_conntrack nf_log_ipv4 nf_log_common xt_LOG iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_filter bpfilter binfmt_misc nls_iso8859_1 dm_multipath si2157 scsi_dh_rdac scsi_dh_emc scsi_dh_alua lgdt3306a cx231xx_dvb dvb_core cx231xx_alsa cx25840 cx231xx videobuf_vmalloc tveeprom cx2341x videobuf_core i2c_mux videodev mc intel_rapl_msr mei_hdcp intel_rapl_common x86_pkg_temp_thermal intel_powerclamp kvm_intel snd_hda_codec_hdmi kvm rapl intel_cstate snd_sof_pci snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_acpi_intel_match snd_hda_codec_generic snd_soc_acpi ledtrig_audio ir_rc5_decode
[Bug 1801814] Re: Environment overwrites XDG_DATA_DIRS
I've just run into this on 20.04 also. Installing flatpak broke all the snaps in my Wayland session because of the way flatpak overwrites the XDG_DATA_DIRS envar. It doesn't break snaps in xorg sessions. Removing flatpak to try to make Wayland sessions usable again breaks gnome-session on both xorg and Wayland. It crashes on login with this error: Jul 07 02:48:51 serenity gnome-session[3205]: gnome-session-binary[3205]: GLib-GIO-ERROR: No GSettings schemas are installed on the system Jul 07 02:48:51 serenity gnome-session[3205]: aborting... Jul 07 02:48:51 serenity gnome-session-binary[3205]: GLib-GIO-ERROR: No GSettings schemas are installed on the system aborting... I've tried various things to try to get flatpak off the system, but no luck. Wayland is still broken. The upstream bugs here are all closed, but the bugfixes aren't effective on Wayland sessions, and the uninstall problems appear to be new. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801814 Title: Environment overwrites XDG_DATA_DIRS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1801814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869963] Re: Unable to install chromium-browser in docker
We use chromium-browser in an 18.04 container for several thousand interactive kiosks. This bug prevents us from fully updating to the latest LTS version of Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869963 Title: Unable to install chromium-browser in docker To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878465] Re: Lubuntu 20.04/LibreOffice Lacks Spellchecker
I appear to have fixed the problem with this: sudo apt-get update && sudo apt-get upgrade sudo apt-get install hunspell-en-gb Featherpad is still telling me that I need to install a Hunspell dictionary when I try to spell check. It gives instructions that I expect are for KDE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878465 Title: Lubuntu 20.04/LibreOffice Lacks Spellchecker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1878465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 376715]
None at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/376715 Title: Thunderbird - feature request - nest in toolbar To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/376715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 397574]
68.4: https://hg.mozilla.org/releases/comm-esr68/rev/3f45fb298e6800a27449ca2acb4909d42108dc5d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/397574 Title: Encoding problems after switching the layout To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/397574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 397574]
72.0b3: https://hg.mozilla.org/releases/comm-beta/rev/b4316a22736be13136f583faa6c83a563136550e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/397574 Title: Encoding problems after switching the layout To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/397574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842951] Re: adcli join fails
Having the same issue on 19.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842951 Title: adcli join fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1842951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852116] [NEW] zfs send / recv properties failing
Public bug reported: Running Ubuntu 19.10 on both the send and recv systems. I can't send properties. If I don't include the -p switch, all is good. If I include the -p switch it looks like it is going to work, but it hangs like this: sudo /usr/sbin/zfs send -vp -I tank/vm@2019-11-02_22-41-35__daily__batch1 tank/vm@2019-11-05_18-26-01__daily__batch1 | /bin/ssh back1 sudo /usr/sbin/zfs recv -vu backup/vm send from @2019-11-02_22-41-35__daily__batch1 to tank/vm@2019-11-05_18-24-41__daily__batch1 estimated size is 4.12G send from @2019-11-05_18-24-41__daily__batch1 to tank/vm@2019-11-05_18-26-01__daily__batch1 estimated size is 2.50M total estimated size is 4.13G TIME SENT SNAPSHOT tank/vm@2019-11-05_18-24-41__daily__batch1 receiving incremental stream of tank/vm@2019-11-05_18-24-41__daily__batch1 into backup/vm@2019-11-05_18-24-41__daily__batch1 20:03:24 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1 20:03:25 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1 20:03:26 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1 20:03:27 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1 20:03:28 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1 20:03:29 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1 20:03:30 2.06M tank/vm@2019-11-05_18-24-41__daily__batch1 Then I have to kill it. Any thoughts? thanks, Geoff ** Affects: zfs-linux (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/1852116 Title: zfs send / recv properties failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109943]
There's only a few which are indeterminate and they're important for providing feedback to the user that something is happening. I think the best solution, if any, is to chase the toolkit people to fix their widget. FWIW I've not had a problem with this thing for years but it probably does use more CPU than necessary, about 6% of a CPU for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/109943 Title: Thunderbird: high CPU usage from progress bars To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827142] [NEW] package linux-image-4.4.0-146-generic 4.4.0-146.172~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1
Public bug reported: automatic update 14.04 LTS ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-146-generic 4.4.0-146.172~14.04.1 ProcVersionSignature: Ubuntu 4.4.0-144.170~14.04.1-generic 4.4.176 Uname: Linux 4.4.0-144-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Tue Apr 30 15:01:31 2019 DuplicateSignature: package:linux-image-4.4.0-146-generic:4.4.0-146.172~14.04.1:run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 InstallationDate: Installed on 2019-03-27 (34 days ago) InstallationMedia: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: grub Title: package linux-image-4.4.0-146-generic 4.4.0-146.172~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827142 Title: package linux-image-4.4.0-146-generic 4.4.0-146.172~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1827142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798938] [NEW] Installing Lubuntu 18.04.1 from USB on MSI Cubi - Fails to install GRUB Bootloader
Public bug reported: Fails to install grub bootloader on both Direct Install and through trial Lubuntu Install options. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Sat Oct 20 18:08:40 2018 InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic lubuntu ubiquity-18.04.14.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798938 Title: Installing Lubuntu 18.04.1 from USB on MSI Cubi - Fails to install GRUB Bootloader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1798938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759860] Re: Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS P8H67-M PRO
Radu, take a look at this bug - https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297 As you suggested, adding the resume entry to grub worked around my inability to resume from hibernate, but the fix noted in bug #1769297 looks to be the real fix. I tested it successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759860 Title: Ubuntu MATE Bionic Beaver alpha - Hibernate/Resume Failure - ASUS P8H67-M PRO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758427] Re: Juniper VPN connection fails after authentication
Thanks Mike. I appreciate the reply. The local version of openconnect (which I had forgotten about) was causing the problem. ** Changed in: network-manager-openconnect (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758427 Title: Juniper VPN connection fails after authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1758427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758427] Re: Juniper VPN connection fails after authentication
I should mention that I am running a fully updated version of vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758427 Title: Juniper VPN connection fails after authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1758427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758427] [NEW] Juniper VPN connection fails after authentication
Public bug reported: I'm having trouble establishing a connection with a Juniper vpn. Using NetworkManager, after entering a correct username and password as well as a multifactor authentication code, the connection fails. I've attached a debug log from Network Manager showing the attempted connection. The only error I see is: [1521836200.4261] vpn-connection[0x55c588000170,194c1d3d-042b- 494a-8f02-d29e98262a6e,"WCU",0]: VPN plugin: failed: connect-failed (1) Connecting to this same server using the CLI for openconnect (e.g. sudo openconnect --juniper server.name) works fine. ** Affects: network-manager-openconnect (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Network Manager Trace Log" https://bugs.launchpad.net/bugs/1758427/+attachment/5088553/+files/thing.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758427 Title: Juniper VPN connection fails after authentication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openconnect/+bug/1758427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1696651] Re: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Dear Dino99, I'm not sure what this means. My system tells me it is running Ubuntu 17.10 (See attached screenshot.) I checked for any updates and none was recommended. Do I need to do something else? Regards ... Geoff Kyle. Original Message On January 27, 2018 9:45 PM, dino99 <1696...@bugs.launchpad.net> wrote: >That version is now dead >http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Invalid > > >You received this bug notification because you are subscribed to the bug > report. >https://bugs.launchpad.net/bugs/1696651 > > Title: > package linux-image-4.10.0-22-generic (not installed) failed to > install/upgrade: subprocess new pre-installation script returned error > exit status 128 > > Status in linux package in Ubuntu: > Invalid > > Bug description: > I downloaded OS updates and shut down. Next boot I got this error > message. > > ProblemType: Package > DistroRelease: Ubuntu 17.04 > Package: linux-image-4.10.0-22-generic (not installed) > ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 > Uname: Linux 4.10.0-21-generic x86_64 > ApportVersion: 2.20.4-0ubuntu4.1 > Architecture: amd64 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC0: doctorwu 1693 F pulseaudio > Date: Wed Jun 7 22:01:41 2017 > ErrorMessage: subprocess new pre-installation script returned error exit > status 128 > InstallationDate: Installed on 2017-05-19 (19 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > Lsusb: > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd > Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. E402SA > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed > root=UUID=29feef4a-96ae-4680-bdca-76622ff6a7ac ro quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: grub-pc N/A > RfKill: > 0: phy0: Wireless LAN > Soft blocked: no > Hard blocked: no > SourcePackage: linux > Title: package linux-image-4.10.0-22-generic (not installed) failed to > install/upgrade: subprocess new pre-installation script returned error exit > status 128 > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 02/22/2016 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: E402SA.209 > dmi.board.asset.tag: ATN12345678901234567 >dmi.board.name: E402SA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: ATN12345678901234567 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrE402SA.209:bd02/22/2016:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: >dmi.product.name: E402SA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696651/+subscriptions > ** Attachment added: "ubuntu 17.10.jpg" https://bugs.launchpad.net/bugs/1696651/+attachment/5044264/+files/ubuntu%2017.10.jpg ** Attachment added: "ubuntu 17.10.jpg" https://bugs.launchpad.net/bugs/1696651/+attachment/5044265/+files/ubuntu%2017.10.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696651 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)
Tested 4.4.0-108.131~lp1741934 in a Ubuntu Xenial install on the following: Asus CS-B - booted OK Asus Q170M-C - booted OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741934 Title: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)
Tested 4.4.0-108.131~lp1741934 in a Ubuntu Xenial install on the following: Intel DQ77MK - booted OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741934 Title: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)
Tested 4.4.0-108.131 on PCs with the following motherboards: Asus CS-B - failed to boot Intel DQ77MK - failed to boot Asus Q170M-C - booted OK I'll retry with the kernel from #24 now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741934 Title: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739056] Re: Subsequent launches forks from the same process which causes grouping to stretch across all instances
Perhaps there's some way that could be the default action, or at least some sort of notification could be given upon install? People used to terminator on ubuntu could run into some bad issues with this. I was using terminator for hours after upgrading to 17.10 not realizing I was editing and saving files on dozens of servers that were open in other workspaces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739056 Title: Subsequent launches forks from the same process which causes grouping to stretch across all instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1739056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739056] [NEW] Subsequent launches forks from the same process which causes grouping to stretch across all instances
Public bug reported: On previous ubuntu versions, every launch of a terminator instance creates a new process. 17.10 appears to not do so. As a result, if I attempt to "group"the internal terminals within a terminator window, it instead groups every instance of every terminator window that has been opened. This not only makes the grouping functionality in terminator completely useless, it is extremely hazardous as users will be unknowingly typing commands in other unintended terminals. Description:Ubuntu 17.10 Release:17.10 terminator: Installed: 1.91-1 Candidate: 1.91-1 Version table: *** 1.91-1 500 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status ** Affects: terminator (Ubuntu) Importance: Undecided Status: New ** Description changed: On previous ubuntu versions, every launch of a terminator instance creates a new process. 17.10 appears to not do so. As a result, if I attempt to "group"the internal terminals within a terminator window, it instead groups every instance of every terminator window that has been opened. This not only makes the grouping functionality in terminator completely useless, it is extremely hazardous as users will be - unknowingly typing commands in other terminals. + unknowingly typing commands in other unintended terminals. Description: Ubuntu 17.10 Release: 17.10 terminator: - Installed: 1.91-1 - Candidate: 1.91-1 - Version table: - *** 1.91-1 500 - 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu artful/universe i386 Packages - 100 /var/lib/dpkg/status + Installed: 1.91-1 + Candidate: 1.91-1 + Version table: + *** 1.91-1 500 + 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu artful/universe i386 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739056 Title: Subsequent launches forks from the same process which causes grouping to stretch across all instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1739056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725609] Re: no wifi after upgrading to 17.10
Brian, good question. I assumed it was the upgrade but it wansn't. I've done some digging and found this: geoff@monster:~$ aptitude why linux-image-4.13.0-16-lowlatency i docker-engineRecommends aufs-tools i A aufs-tools Recommends aufs-dkms i A linux-image-4.13.0-16-lowlatency Provides aufs-dkms I'd installed the docker-engine package *ages* ago and forgotten about it. This is what dragged in the lowlatency kernel. I'm pretty sure my fix will fail on the next kernel update too since the longterm fix would be: sudo apt-get install linux-headers-lowlatency As you mentioned -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725609 Title: no wifi after upgrading to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1725609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725609] [NEW] no wifi after upgrading to 17.10
Public bug reported: Overview After upgrading Xubuntu 17.04 to 17.10, wifi stopped working completely Expected behaviour == Wifi should continue to work after an OS upgrade Actual behaviour Wifi not available, no driver loaded Analysis System reports wifi as Broadcom Limited BCM4352 802.11ac Wireless Network Adapter (rev 03), in Additional Drivers, Linux STA driver from bcmwl-kernel-source is shown as selected Attempting to reconfigure bcmwl-kernel-source gives an error: geoff@monster:~$ sudo dpkg-reconfigure bcmwl-kernel-source Removing all DKMS Modules Done. Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 4.13.0-16-lowlatency Building for architecture x86_64 Module build for kernel 4.13.0-16-lowlatency was skipped since the kernel headers for this kernel does not seem to be installed. modprobe: FATAL: Module wl not found in directory /lib/modules/4.13.0-16-lowlatency update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.125ubuntu12) ... update-initramfs: Generating /boot/initrd.img-4.13.0-16-lowlatency cryptsetup: WARNING: target cryptswap1 has a random key, skipped Processing triggers for shim-signed (1.32+0.9+1474479173.6c180c6-1ubuntu1) ... Secure Boot not enabled on this system. Looks like the upgrade didn't install the kernel headers which meant no WIFI on reboot Workaround == Installing the appropriate kernel headers and reconfiguring bcmwl-kernel-source fixed my system immediately Connect wired Ethernet then: sudo apt-get install linux-headers-$(uname -r) sudo dpkg-reconfigure bcmwl-kernel-source ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-release-upgrader-core 1:17.10.7 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Sat Oct 21 19:53:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-23 (1123 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful 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/1725609 Title: no wifi after upgrading to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1725609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713842] [NEW] rkt fetch broken on arm64
Public bug reported: ProblemType: Bug ApportVersion: 2.20.4-0ubuntu4.5 Architecture: arm64 Date: Tue Aug 29 15:03:36 2017 Package: rkt 1.21.0+dfsg-1 PackageArchitecture: arm64 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 SourcePackage: rkt Tags: zesty Uname: Linux 4.10.0-32-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True The rkt version packaged in zesty has a known bug that does not allow it to use docker images on arm64 systems. The upstream fix: https://github.com/rkt/rkt/pull/3534 Fixed in rkt release: rkt-1.23.0 To reproduce: $ sudo rkt --debug --insecure-options=image fetch docker://aarch64/ubuntu:latest fetch: └─error converting docker image to ACI └─error generating ACI: bad arch "arm64" for linux (must be one of: [amd64 i386 aarch64 aarch64_be armv6l armv7l armv7b ppc64 ppc64le s390x]) ** Affects: rkt (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/1713842 Title: rkt fetch broken on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rkt/+bug/1713842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
FYI, 4.12 was released as stable yesterday, so I'm hoping the maintainers of Ubuntu/Fedora/etc have the patches ready for update in the next week or so and this problem will be a thing of the past! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696651] [NEW] package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: I downloaded OS updates and shut down. Next boot I got this error message. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-22-generic (not installed) ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: doctorwu 1693 F pulseaudio Date: Wed Jun 7 22:01:41 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-19 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E402SA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=29feef4a-96ae-4680-bdca-76622ff6a7ac ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402SA.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402SA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402SA.209:bd02/22/2016:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E402SA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696651 Title: package linux-image-4.10.0-22-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692215] Re: package grub-pc 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 1692175 *** https://bugs.launchpad.net/bugs/1692175 To be clear on my previous comment, the fix recommended is adding a semicolon on line 699 of /var/lib/dpkg/info/grub-pc.postinst (use sudo with your favourite text editor) Changing: if dpkg --compare-versions "$2" lt-nl 2.02~beta2-36ubuntu3.10 then into if dpkg --compare-versions "$2" lt-nl 2.02~beta2-36ubuntu3.10 ; then …and then instructing pdkg to complete the configuration with: sudo dpkg --configure grub-pc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692215 Title: package grub-pc 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1692215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692215] Re: package grub-pc 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Correction suggested for efi version in LP: #1692175 comment #8 appears to also be a fix for this package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692215 Title: package grub-pc 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1692215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692215] [NEW] package grub-pc 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: On Ubuntu 16.04LTS. Automatic package updater indicated grub2 needed updating. When it finished it said there was a problem and asked if I wanted to report it. After clicking 'Report it' no further action was taken at that time. I have just rebooted, and the 'there was a problem' dialog box reappear, this time clicking 'Report it' elicited a password prompt and eventual display of this page. My system appears, on the surface, to be working correctly at the moment, but I have not done much since the reboot. Bug report #1692175 sounds similar but is for the efi version of grub. Additional details: $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 $ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02~beta2-36ubuntu3.10 Version table: 2.02~beta2-36ubuntu3.10 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-proposed/universe amd64 Packages 2.02~beta2-36ubuntu3.9 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 2.02~beta2-36ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grub-pc 2.02~beta2-36ubuntu3.10 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sat May 20 12:10:23 2017 DuplicateSignature: package:grub-pc:2.02~beta2-36ubuntu3.10 Setting up grub-pc (2.02~beta2-36ubuntu3.10) ... /var/lib/dpkg/info/grub-pc.postinst: line 703: syntax error near unexpected token `fi' dpkg: error processing package grub-pc (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=8d5fb140-93f5-40ce-9e58-1d9abb865022 ro net.ifnames=0 biosdevname=0 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.21 SourcePackage: grub2 Title: package grub-pc 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-08-03 (290 days ago) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-from-proposed third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692215 Title: package grub-pc 2.02~beta2-36ubuntu3.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1692215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250
In my experience it was only after I added the Intel-specific drivers for my video card (in the Dell XPS 15 9560) that the crashing happened on 4.10.x. So, I'm just running 4.8.x until 4.12 comes out or someone magical advises here that the fix has gone into a minor release of 4.10 (which I read somewhere else wasn't going to happen because while the upstream folks have fixed the bug, the stream it is being merged into is 4.12) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Follow-up to #34, on a system where unattended-upgrades happens to be running when shutdown is called, the shutdown does not wait, therefore any running dpkg is killed and the package left in an inconsistent state. - Xenial with single partition, InstallOnShutdown not defined. This may be a separate issue, but I'll investigate further before raising it as such. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
The Unit file in #33 works for me, ie stops the 10 minute hang, when unattended-upgrades is not running. - Xenial with /var as a separate FS, InstallOnShutdown="false" I will try to create a test case where unattended-upgrades is running when shutdown is called. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982316] Re: Deja Dup is unable to detect network connection
I'm on 16.04.1 LTS and had the following error after configuring the settings in the System Settings Backup: "Backup location not available Waiting for a network connection..." For me, the issue was with NetworkManager. After getting the above error, I went to look at the Connection Information in the systray only to get another error: "Error displaying connection information:No valid active connections found!" Following: https://bugs.launchpad.net/ubuntu/+source/network-manager- applet/+bug/305606 I found that my /etc/NetworkManager/NetworkManager.conf had: [ifupdown] managed=false so I changed it to: [ifupdown] managed=true rebooted and now the backup works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982316 Title: Deja Dup is unable to detect network connection To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/982316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652019] [NEW] udev does not read LINK files dynamically
Public bug reported: Hello all, To comply to SystemD's way of thinking, NIC names can be changed assuming my MAC addresses. I have then changed /etc/systemd/10-net.link assuming the nomenclature in https://www.freedesktop.org/software/systemd/man/systemd.link.html. Expected behavior: When restart, changes can be taken into account and NIC names changed, just like udev udev raw rules in /etc/udev/rules.d. Got: NIC names not changed. However: whane re-updating initramfs ( # update-initramfs -u ), it works. Question: why is udev not reading SystemD link files directly in the root FS, but is able to read udev rules.d files ? Distro : Ubuntu 16.04.4 Thanks, ** Affects: 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/1652019 Title: udev does not read LINK files dynamically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1652019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625822] Re: tcplay hangs at the device mapper stage. This happens in 16.04 LTS version of xubuntu (32 bit and 64 bit) and ubuntu (64bit). This makes tcplay containers not accessible.
I should make it clear that it is the device mapper that is at fault. After first installing the 32-bit xubuntu system, I found that tcplay was unable to open an existing container that I had been using successfully for many months using xubuntu 14.04: it hung at the device mapper stage on 16.04. The test sequence described here is so that you can reproduce the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625822 Title: tcplay hangs at the device mapper stage. This happens in 16.04 LTS version of xubuntu (32 bit and 64 bit) and ubuntu (64bit). This makes tcplay containers not accessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcplay/+bug/1625822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625822] [NEW] tcplay hangs at the device mapper stage. This happens in 16.04 LTS version of xubuntu (32 bit and 64 bit) and ubuntu (64bit). This makes tcplay containers not accessible.
Public bug reported: Is there anything changed in xubuntu 16.04 LTS that causes tcplay device mapper to hang ? The following command sequence works fine in xubuntu 14.04 but in 16.04 it hangs at the device mapper stage (5 below) when the valid passphrase is entered. The passphrase I use here is ‘testpw’. I know it has accepted the correct passphrase because it gives a message if I enter an invalid passphrase. This is a fresh install using the xubuntu-16.04.1-desktop-i386.iso on the same 32-bit processor laptop as the 14.04 system (multi-boot). I prefer using tcplay because of the container portability. There are no dmesg messages during the process on 16.04. This is the command sequence: 1) fallocate -l 20M foo.tc 2) sudo losetup -f (response is /dev/loop0) 3) sudo losetup /dev/loop0 foo.tc 4) sudo tcplay -c -d /dev/loop0 -a whirlpool -b AES-256-XTS (response is Passphrase: Repeat passphrase: Summary of actions: - Completely erase *EVERYTHING* on /dev/loop0 - Create volume on /dev/loop0 Are you sure you want to proceed? (y/n) y Securely erasing the volume... This process may take some time depending on the size of the volume Creating volume headers... Depending on your system, this process may take a few minutes as it uses true random data which might take a while to refill and after about 10 minutes Writing volume headers to disk... All done! ) 5) sudo tcplay -m foo.tc -d /dev/loop0 (response is Passphrase: and it then hangs – I have given it up to one hour. ) On xubuntu 14.04 step (5) takes less than one second, and I can then do the following 6) sudo mkfs.ext4 /dev/mapper/foo.tc 7) sudo mount /dev/mapper/foo.tc /mnt/FOO_DRIVE/ 8) df -h which shows the normal stuff plus /dev/mapper/foo.tc 19M 170K 17M 1% /mnt/FOO_DRIVE On xubuntu 16.04, after killing step 5, the would be step 6 gets the message ‘The file /dev/mapper/foo.tc does not exist and no size was specified.’ The above was the bug experience on a 32-bit laptop. On a test 64-bit base unit, I was able to show that the bug also applies to 16.04 LTS 64-bit versions of xubuntu and ubuntu ** Affects: 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/1625822 Title: tcplay hangs at the device mapper stage. This happens in 16.04 LTS version of xubuntu (32 bit and 64 bit) and ubuntu (64bit). This makes tcplay containers not accessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1625822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620358] [NEW] System-wide monitors.xml is ignored
Public bug reported: Using gnome-settings-daemon 3.18.2-0ubuntu3.1 on Ubuntu 16.04.1 LTS Logging in with a new user account, my two monitors are the wrong way round. I can fix for this user by right-click; run "Display Settings" and manually reconfiguring. This creates ~/.config/monitors.xml I now copy that file to /etc/gnome-settings-daemon/xrandr/monitors.xml - I expect this to apply to all other users on this PC: $ gsettings get org.gnome.settings-daemon.plugins.xrandr default-configuration-file '/etc/gnome-settings-daemon/xrandr/monitors.xml' When other users log in, they still get the incorrect display setup. It looks like /etc/gnome-settings-daemon/xrandr/monitors.xml is having no effect. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: "monitors.xml" https://bugs.launchpad.net/bugs/1620358/+attachment/4734979/+files/monitors.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620358 Title: System-wide monitors.xml is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1620358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612934] Re: upgrade uncalcuable due to mixxx PPA
Thanks for the reply your info pointed me in the right direction to fix my problem. Uplgraded ok now Geoff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612934 Title: upgrade uncalcuable due to mixxx PPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1612934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612934] [NEW] error on upgrade to 16.04
Public bug reported: Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade. This can be caused by: * Upgrading to a pre-release version of Ubuntu * Running the current pre-release version of Ubuntu * Unofficial software packages not provided by Ubuntu If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.8 ProcVersionSignature: Ubuntu 3.13.0-88.135-lowlatency 3.13.11-ckt39 Uname: Linux 3.13.0-88-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Sat Aug 13 11:14:07 2016 InstallationDate: Installed on 2013-02-26 (1263 days ago) InstallationMedia: Ubuntu-Studio 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2016-08-13 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612934 Title: error on upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1612934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611350] Re: d-push: Array to string conversion (8) failures
** Attachment added: "d-push.log.txt" https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+attachment/4717490/+files/d-push.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611350 Title: d-push: Array to string conversion (8) failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611350] Re: d-push: Array to string conversion (8) failures
** Attachment added: "config.php.txt" https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+attachment/4717492/+files/config.php.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611350 Title: d-push: Array to string conversion (8) failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611350] Re: d-push: Array to string conversion (8) failures
** Attachment added: "d-push-error.log.txt" https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+attachment/4717491/+files/d-push-error.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611350 Title: d-push: Array to string conversion (8) failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611350] [NEW] d-push: Array to string conversion (8) failures
Public bug reported: Upgraded to 16.04.1 LTS. d-push was removed during the upgrade. I did an 'apt-get install d-push' to reinstall, though it was generating a lot of "array to string conversion" errors and my iPhone wasn't seeing any new mail. I then attempted to purge and reinstall with a clean image by running 'apt-get remove d-push; dpkg -P d-push; rm -rf /etc/d-push /var/lib/d-push /var/log/d-push; apt-get install d-push'. That did force a resync but I still cannot see any mail d-push.log shows "/usr/share/d-push/lib/syncobjects/syncobject.php:302 Array to string conversion (8)" and "/usr/share/d-push/lib/core/streamer.php:237 Array to string conversion (8)" dozens of times for each message. d-push-error.log shows "Ignored broken message (SyncFolder). Reason: '4' FolderId: '' message id ''" for every folder. Repeats for SyncMail as well for every message. ** Affects: d-push (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/1611350 Title: d-push: Array to string conversion (8) failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-push/+bug/1611350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1549711] Re: Old version gives defined(@array) is deprecated warnings
This bug should be upgraded to important. Xenial uses Perl 5.22 and the deprecation warnings have turned to fatal errors. Try perl -MMail::Sender -e 1; to see them. Upgrading to the latest version of Mail::Sender using cpan fixes the issue (for those who need it). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549711 Title: Old version gives defined(@array) is deprecated warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-sender-perl/+bug/1549711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563109] [NEW] package at 3.1.16-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: Trying to install the printer drivers for openprinting-gutenprint. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: at 3.1.16-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Mon Mar 28 16:18:28 2016 DuplicateSignature: package:at:3.1.16-1ubuntu1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-03-23 (371 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: at Title: package at 3.1.16-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-27 (153 days ago) ** Affects: at (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563109 Title: package at 3.1.16-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1563109/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554848] Re: Please randomise automatic updates over a longer period
My apologies - this delay is already configurable using APT::Periodic::RandomSleep ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554848] Re: Please randomise automatic updates over a longer period
It would be good to have the delay length as a configuration option, I would like to reduce the random delay for some of my PCs which are not turned on very often. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494225] Re: Call audio is not routed to headset with HFP
sorry not been able to set my phone up for logging at the moment - although reasonably technical and used to using the cli for out of the normal occasions, I don't go for the cli normally and prefer a gui, so just need to get my head around setting up. Not sure if it helps, but I did notice though that for normal operation as long as you are slow in connecting everything then it does all seem to hang together. Here's what I do (to get it to work); - have bluetooth switched on on the phone (with the pairing already completed) - switch on the headset and wait for the bluetooth icon to go from a black background, to white and then back to black. - wait 20-30 seconds (till I think it will have sorted itself out) - press the button on the headset (the one that initiates a connection and is also used for answering and ending calls) - wait till the bluetooth icon goes white and the bluetooth volume 'overlay' is shown - this can take 30-40 seconds I can now make or receive calls and the sound/mic are passed to/from the headset correctly. If I try to 'rush' this cycle or answer a call then switch on the headset, that's when the problem shows and I get connection to the headset to no sound to or from the headset or speakers/phone mic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494225 Title: Call audio is not routed to headset with HFP To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1494225] Re: Call audio is not routed to headset with HFP
Think this affects me too on my MX4 using HTC BH M200 headset. If there's anything I can send from the phone that'll help, let me know. Looks by the packages that are affected that it could also be loosely related to https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1544477 This started with me with OTA-9 and continues after OTA-9.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1494225 Title: Call audio is not routed to headset with HFP To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
here's a zip of the media hub files before and after it going wrong (I'm assuming that this is what the .gz files are). I don't recall changing the volume or silent status until after it went wrong yesterday apart from on Friday evening when it was on silent for around 1-2 hours. Media-hub-7.gz should show when it was in silent mode (Friday evening). Hope this info is useful - if not and you need something else please holla. ** Attachment added: "mx4 media hub.zip" https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1544477/+attachment/4578374/+files/mx4%20media%20hub.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
I did change the sounds from the default to positive the other week as I thought I was missing text messages due to not hearing them - then I did the tests and found it was due to only the vibration working - before it was left on the Amsterdam default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
I believe that it is inconsistent (more than just putting into silent and back out). I had my MX4 in silent on Friday evening then back to normal Saturday seemed OK Sunday morning I thought the SMS sound notification wasn't working (vibration still good) - I had to hard reset my phone 2-3 times to get bluetooth working again to my headset and phone app crashed as locked up the screen (bluetooth kept connecting but no voice transferred, then after 2-3 hard resets (power button for 10 secs) all came good again). Sunday evening SMS notifications all ok for multiple texts from multiple people, sent various SMS's and a single MMS, again OK received SMS after this, sound still good Something happened (unknown what though) now sound failed again on SMS... Would you like a copy of the ubuntu-phablet-stream-volumes.tdb file again or anything else I can provide to assist? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
OK, thx, I also raised a question https://answers.launchpad.net/ubuntu/+source/ubuntu- settings/+question/285197 (but may have posted into the wrong place) asking if there's any apps or methods of changing the volumes independently as on Android as I hadn't found anything when searching the web, however there were no suggestions given. Wonder if you could share some light - at present if this happens again is the only way forwards to delete the file again. As with any issue, it isn't a solution but a usable workaround currently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
ah, just deleted the ubuntu-phablet-stream-volumes.tdb file and rebooted the mx4 - sound is back - great, thanks for the suggestion. Volume (in System Settings | Sound) never made a difference when I tried to adjust before. thx again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1544477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
and also the media-hub.log file (again from my mx4) as requested. Many thanks for your help so far. ** Attachment added: "media-hub.log" https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1544477/+attachment/4569610/+files/media-hub.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1544477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
here's the ubuntu-phablet-stream-volumes.tdb file from my mx4 ** Attachment added: "ubuntu-phablet-stream-volumes.tdb" https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1544477/+attachment/4569609/+files/ubuntu-phablet-stream-volumes.tdb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1544477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
On my MX4, then this is a permanent issue, that is, a reboot or forced- reboot (power button held for 10 seconds) does not clear it - opening Music and playing tracks, incoming calls and going into System Settings | Sound and selecting different sounds (Amsterdam, Positive, etc) all cause playing of the tune (with the stop icon at the bottom of the screen when in the System Settings | Sound screen). It's just that when you leave the phone and an SMS comes in, it just vibrates and doesn't give any sound - it gives sound and vibration when a call comes in still. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1544477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
On Meizu MX4 with OTA-9 installed, I have the green envelope OK, the vibration notification also works but there is no sound. Tried the following sounds; Amsterdam (Default), Mallet and Positive - all have the same outcome - no sound produced on a new SMS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544477 Title: No sound notification for new SMS (Ubuntu Touch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1544477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1029209] Re: tidy doesn't support html5 syntax
> it's about the deb-package tidy Absolutely! That is what it is all about, for sure... not 'conflicts' or 'forks' ;=)) On Dec 4 I sent a direct email to Jason asking about an update. No reply yet. Even re-tested the first few of the bugs listed at - https://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=jason%40debian.org suggesting they can be CLOSED... and offered help dealing with the rest... Is there anything else I can do, as a tidy maintainer, to get an Ubuntu tidy deb-package updated? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1029209 Title: tidy doesn't support html5 syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tidy/+bug/1029209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1029209] Re: tidy doesn't support html5 syntax
As explained in that issue, and in an Ubuntu question https://answers.launchpad.net/ubuntu/+source/tidy/+question/276623 the https://github.com/htacg/tidy-html5 is not a fork. It is canonical for HTML Tidy as of 2015-January-15... first release: https://github.com/htacg/tidy-html5/releases/tag/5.0.0 last release: https://github.com/htacg/tidy-html5/releases/tag/5.1.25 There is no conflicting version numbers. This Samantic type versioning was adopted in the first release, and will continue. And the package name will remain tidy... I am trying to get in touch with Jason Thomas to try to do something about debian and ubuntu outdated tidy packages. Hopefully soon... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1029209 Title: tidy doesn't support html5 syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tidy/+bug/1029209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1486456] Re: Please set back libvpx1 into Wily archive
That does fix it, wily wasn't an option before On Nov 25, 2015 2:35 PM, "Marcos William Ferretti" wrote: > sudo sed -i 's/vivid/wily/' /etc/apt/sources.list > sudo apt-get update > sudo apt-get install virtualbox-5.0 > > from: > > https://askubuntu.com/questions/696870/dependency-errors-when-trying-to-install-virtualbox-5-0-on-15-10 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1486456 > > Title: > Please set back libvpx1 into Wily archive > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1486456/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1486456 Title: Please set back libvpx1 into Wily archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1486456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1486456] Re: Please set back libvpx1 into Wily archive
I did a work around, I went and downloaded the older version at http://packages.ubuntu.com/trusty/libvpx1 and installed it with dpkg. This seemed to make everything happy for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1486456 Title: Please set back libvpx1 into Wily archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1486456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518448] [NEW] NameError: name 'RULES_BINARY_ALL_TARGET' is not defined
Public bug reported: Running this command: $ sudo python3 setup.py --command-packages=stdeb.command sdist_dsc --debian-version ppa1 Produces this output: running sdist_dsc running egg_info writing entry points to ravenc.egg-info/entry_points.txt writing top-level names to ravenc.egg-info/top_level.txt writing dependency_links to ravenc.egg-info/dependency_links.txt writing requirements to ravenc.egg-info/requires.txt writing ravenc.egg-info/PKG-INFO reading manifest file 'ravenc.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching '*.xml' under directory 'ravenc' writing manifest file 'ravenc.egg-info/SOURCES.txt' Traceback (most recent call last): File "setup.py", line 34, in entry_points = {'gui_scripts': ['ravenc = ravenc.ravenc:run']} File "/usr/lib/python3.4/distutils/core.py", line 148, in setup dist.run_commands() File "/usr/lib/python3.4/distutils/dist.py", line 955, in run_commands self.run_command(cmd) File "/usr/lib/python3.4/distutils/dist.py", line 974, in run_command cmd_obj.run() File "/usr/lib/python3/dist-packages/stdeb/command/sdist_dsc.py", line 27, in run debinfo = self.get_debinfo() File "/usr/lib/python3/dist-packages/stdeb/command/common.py", line 226, in get_debinfo allow_virtualenv_install_location=self.allow_virtualenv_install_location, File "/usr/lib/python3/dist-packages/stdeb/util.py", line 1102, in __init__ RULES_BINARY_ALL_TARGET%self.__dict__ + \ NameError: name 'RULES_BINARY_ALL_TARGET' is not defined A quick look into utils.py shows that RULES_BINARY_ALL_TARGET is not defined BUT looking at the package source in launchpad AND looking at the github version shows that it IS defined. Something odd has gone on in the Ubuntu packaging. For reference: The end of utils.py on github looks like this: RULES_OVERRIDE_INSTALL_TARGET = """ override_dh_auto_install: %(rules_override_install_target_pythons)s %(scripts_cleanup)s """ RULES_OVERRIDE_PYTHON3 = """ override_dh_python3: dh_python3 %(scripts)s """ RULES_BINARY_TARGET = """ binary: binary-arch binary-indep """ RULES_BINARY_ALL_TARGET = """ binary: binary-indep """ RULES_BINARY_ARCH_TARGET = """ binary-arch: build %(dh_binary_arch_lines)s """ RULES_BINARY_INDEP_TARGET = """ binary-indep: build %(dh_binary_indep_lines)s %(dh_installmime_indep_line)s %(dh_desktop_indep_line)s """ and installed on my system like this: CONTROL_PY2_STANZA = """ Package: %(package)s Architecture: %(architecture)s Depends: %(depends)s %(package_stanza_extras)sDescription: %(description)s %(long_description)s """ CONTROL_PY3_STANZA = """ Package: %(package3)s Architecture: %(architecture3)s Depends: %(depends3)s %(package_stanza_extras3)sDescription: %(description)s %(long_description)s """ RULES_MAIN = """\ #!/usr/bin/make -f # This file was automatically generated by stdeb %(stdeb_version)s at # %(date822)s %(exports)s %(percent_symbol)s: dh $@ %(sequencer_options)s %(override_dh_auto_install)s %(binary_target_lines)s """ RULES_OVERRIDE_INSTALL_TARGET = """ override_dh_auto_install: dh_auto_install %(scripts_cleanup)s """ RULES_BINARY_ARCH_TARGET = """ binary-arch: build %(dh_binary_arch_lines)s """ RULES_BINARY_INDEP_TARGET = """ binary-indep: build %(dh_binary_indep_lines)s %(dh_installmime_indep_line)s %(dh_desktop_indep_line)s """ ** Affects: stdeb (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/1518448 Title: NameError: name 'RULES_BINARY_ALL_TARGET' is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stdeb/+bug/1518448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1512066] Re: Desktop screen and icon corruption
If I may take the opportunity to show examples of corruption taken as screenshots prior to reverting to 15.04. At present I am trialing mint as a second resort. I will attempt the recommendations. Like hundreds if not thousands who dislike windows in any format, I changed to Ubuntu 10.4 many years ago, and progressed through upgrades as they became available. It is only since moving from 14.10 that these corruptions began. Best Regards. and thank you for the response Geoff On 7 November 2015 at 14:11, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Geoff, thank you for reporting this and helping make Ubuntu better. > > As per > > http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=3785043&swLangOid=8&swEnvOid=4060 > an update to your computer's buggy and outdated BIOS is available > (1.26). If you update to this following > https://help.ubuntu.com/community/BIOSUpdate does it change anything? > > If it doesn't, could you please both specify what happened, and provide > the output of the following terminal command: > sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date > > For more on BIOS updates and linux, please see > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > . > > Please note your current BIOS is already in the Bug Description, so > posting this on the old BIOS would not be helpful. As well, you don't > have to create a new bug report. > > Once the BIOS is updated, if the problem is still reproducible, and the > information above is provided, then please mark this report Status New. > Otherwise, please mark this as Invalid. > > Thank you for your understanding. > > ** Tags added: bios-outdated-1.32 > > ** Tags removed: bios-outdated-1.32 > ** Tags added: bios-outdated-1.26 > > ** Changed in: xorg (Ubuntu) >Importance: Undecided => Low > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1512066 > > Title: > Desktop screen and icon corruption > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > This is now the 3 rd time to reinstall 15.10. Previously the 15.04 > version has been re-installed. > Under 15.04 the problem (bug) was restricted to the desktop background > image in that after a few days and new updates loaded the screen became > corrupted with the appearance of a view like looking through opaque reed > glass. The blame was put on 'Variety' which was in use. Peter Levi terms > this problem a 'low key bug'? It makes no difference whether 'Variety' is > in use or not > As the problem (bug) only affected the desktop background then it was > workable. > The new release of 15.10 was hoped to iron out the problem, but once > again after receiving updates corruption began, and is much more severe in > that icons become distorted when the mouse passes over them sections of > text work become a. invisible or b. distorted to be unreadable. > To date I have re-installed 15.10 four times. Everything is stable until > I begin to accept updates. and the corruption begins. > I have brought up this problem before since 23 rd October. > I cannot be the only individual suffering from this problem. I have two > machines and the results are the same on both. I have changed monitors to > no avail. > The programme was re-installed yesterday and is stable without any > updates. > I run also windows 10 on this machine but have experienced no problems > with display or documents text/ icons > > ProblemType: Bug > DistroRelease: Ubuntu 15.04 > Package: xorg 1:7.7+7ubuntu4 > ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 > Uname: Linux 3.19.0-15-generic x86_64 > .tmp.unity.support.test.0: > > ApportVersion: 2.17.2-0ubuntu1 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Sun Nov 1 08:34:28 2015 > DistUpgraded: Fresh install > DistroCodename: vivid > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 4 Series Chipset Integrated Graphics Controller > [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company Device [103c:3034] > Subsystem: Hewlett-Packard Company Device [103c:3034] > InstallationDat
[Bug 1438708] Re: frequent lockups asus g705js/GeForce GTX 870M
Update: Not sure if anyone other then me was affected by this - in the end I was able resolve things and get a 100% usable system by removing the nouveau driver - cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438708 Title: frequent lockups asus g705js/GeForce GTX 870M To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1438708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1513446] [NEW] ruby error when running vim-addon-manager in a non-login shell
Public bug reported: Overview === When running /usr/bin/vim-addon-manager in a non-login shell, users receive a ruby error and are unable to use the program Expected Result = vim-addon-manager should be able to run normally within a non-login shell and perform requested alterations Actual Result === Users receive the following error message from ruby: /usr/bin/vim-addon-manager:202:in `getpwnam': no implicit conversion of nil into String (TypeError) from /usr/bin/vim-addon-manager:202:in `parse_cmdline' from /usr/bin/vim-addon-manager:252:in `' Steps to reproduce === I was able to reproduce the error with the following ruby script: test.rb: #!/usr/bin/env ruby require "open3" Open3.popen3("/usr/bin/vim-addon-manager install puppet") do | stdin, stdout, stderr, wait_thr| puts "stdout: " + stdout.read puts "sderr: " + stderr.read end When I executed it with: env -i ruby test.rb Why this is a problem = I would like to be able to be able to run the vim-addon-manager command from within puppet using an exec resource, so the vim-addon-manager command must be able to run in a clean environment without a login shell. The same conditions probably apply if you wanted to run the script from other systems such as chef, cron, etc. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: vim-addon-manager 0.5.4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 5 22:13:38 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-23 (407 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: vim-addon-manager UpgradeStatus: Upgraded to wily on 2015-10-24 (12 days ago) ** Affects: vim-addon-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Patch added: "Fix above issue by switching to getpwuid as recommended at https://github.com/applicationsonline/librarian/pull/174"; https://bugs.launchpad.net/bugs/1513446/+attachment/4513349/+files/0001-fix-ruby-error-when-script-is-run-from-a-non-login-s.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513446 Title: ruby error when running vim-addon-manager in a non-login shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim-addon-manager/+bug/1513446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512066] [NEW] Desktop screen and icon corruption
Public bug reported: This is now the 3 rd time to reinstall 15.10. Previously the 15.04 version has been re-installed. Under 15.04 the problem (bug) was restricted to the desktop background image in that after a few days and new updates loaded the screen became corrupted with the appearance of a view like looking through opaque reed glass. The blame was put on 'Variety' which was in use. Peter Levi terms this problem a 'low key bug'? It makes no difference whether 'Variety' is in use or not As the problem (bug) only affected the desktop background then it was workable. The new release of 15.10 was hoped to iron out the problem, but once again after receiving updates corruption began, and is much more severe in that icons become distorted when the mouse passes over them sections of text work become a. invisible or b. distorted to be unreadable. To date I have re-installed 15.10 four times. Everything is stable until I begin to accept updates. and the corruption begins. I have brought up this problem before since 23 rd October. I cannot be the only individual suffering from this problem. I have two machines and the results are the same on both. I have changed monitors to no avail. The programme was re-installed yesterday and is stable without any updates. I run also windows 10 on this machine but have experienced no problems with display or documents text/ icons ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Nov 1 08:34:28 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3034] Subsystem: Hewlett-Packard Company Device [103c:3034] InstallationDate: Installed on 2015-10-31 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Compaq dc7900 Small Form Factor ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=551edabd-9342-4276-8f47-bf3c3b2b5894 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G1 v01.22 dmi.board.asset.tag: CZC9468YXF dmi.board.name: 3031h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC9468YXF dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G1v01.22:bd08/25/2009:svnHewlett-Packard:pnHPCompaqdc7900SmallFormFactor:pvr:rvnHewlett-Packard:rn3031h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc7900 Small Form Factor dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Nov 1 06:50:42 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512066 Title: Desktop screen and icon corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1512066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
The Ubuntu problem reporter now redirects to this bug whenever there's not enough space on the /boot partition to install a new version of the kernel. This has gotten much more common on systems set up since 2014, because Ubuntu now creates a small, separate /boot partition by default. On systems partitioned with earlier versions of Ubuntu /boot is part of a much larger / partition, so you may never run into this. I've included my workaround to this problem, which I'm now using every couple of weeks when one or another of my Ubuntu systems gets into this state. But I also want to disagree with the resolution proposed by the title of this bug. Even if the "fix" proposed in the title of this bug were implemented, it wouldn't solve the problem or even make it easier for less-technical users to get their systems working again. Ubuntu must manage the set of kernels installed on the system. It must set up a /boot partition capable of holding the number of kernels it expects to see on a normal system. If /boot becomes full it must be able to identify and remove some old kernels. Expecting the end user to manage this means Ubuntu is unsuitable for non-technical users, and I think that goes entirely against Ubuntu's founding principles. Moreover, I don't know why even a technically-minded user would be satisfied with the current state of affairs. There's no reason why the package manager should get into a broken state every few weeks that requires human intervention to fix. These old kernels serve no purpose for the great majority of users, technical or not. For those who are running into this for the first time, here's the workaround I use to fix this problem. Be very careful doing this; deleting the wrong thing can easily render your system unbootable. I use aptitude for package management, so you'll need to install it before you can do this (sudo apt-get install aptitude). At a command prompt: $ aptitude search linux-image | grep ^i This will produce a list of installed kernel images, which look like this: i linux-image-3.19.0-28-generic - Linux kernel image for version 3.19.0 on 686 i linux-image-3.19.0-30-generic - Linux kernel image for version 3.19.0 on 686 You can delete all of them, except the most recent one and the one that's actually running, which may or may not be the same. The most recent one will be the last numbered one on the list. You can find out what's actually running by running this command: $ uname -a Linux gh-narcissus 3.19.0-30-generic #33-Ubuntu SMP Mon Sep 21 20:58:04 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To delete the unused kernels, do this: $ sudo aptitude purge linux-image-3.19.0-28-generic You'll can list more than one image on this command line. Aptitude will warn you that it's going to remove linux-image-extra- packages with the same version numbers as the linux-image packages your purging. That's ok, but make sure the list doesn't include linux-image-generic (which will happen if you accidentally put the latest kernel version on the list). This will sometimes fail, if /boot is completely full. In that case, I remove some of the boot files for the unused kernel images manually, and then run the aptitude purge command again: $ sudo rm /boot/initrd.img-3.19.0-28-generic Usually removing one or two is enough that the package manager will be able to run. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495570] Re: Re-installation of Ubuntu 14.04.2 LTS alongside Windows 8.1 failed.
The laptop was purchased in February 2015 with Windows 8.1 pre- installed. A couple of months later, I installed Ubuntu 12.04.2 from a usb install stick which I had created, alongside the Windows 8.1 system. The installation worked fine as a dual boot system even though I had to go to the boot options menu to select Ubuntu until yesterday (14.09.2015) when the option for Ubuntu from the boot options menu was not amongst the boot options available! Therefore, I backed up the files that I required to a usb drive and proceeded to try a fresh re-install of Ubuntu 14.04.2 alongside Windows 8.1. However, this time, the installation was unsuccessful at the point of creating the grub configuration file, the installation process returning a "fatal error" at this stage! I am now going to try several different options in Terminal given in the askubuntu.co forum as follows: Option 1 - sudo grub-install /dev/sda; sudo grub-mkconfig -0 /boot/grub/grub.cfg Option 2 - sudo apt-get install grub-efi Option 3 - Type "grub" in Terminal, hit tab a few times, looking for "grub-efi-install" or "grub2-install" or something ending in "-install" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495570 Title: Re-installation of Ubuntu 14.04.2 LTS alongside Windows 8.1 failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1495570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495570] [NEW] Re-installation of Ubuntu 14.04.2 LTS alongside Windows 8.1 failed.
Public bug reported: Switching between OS's causes grub file to be overwritten by Windows? My technical knowledge is very limited therefore I am unable to solve the problem? Original installation was Ubuntu 14.04.2 but had been upgraded to Ubuntu 14.04.3. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.340 Date: Tue Sep 15 03:05:33 2015 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper quiet splash -- LiveMediaBuild: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcEnviron: LANGUAGE=en_NZ.UTF-8 PATH=(custom, no user) LANG=en_NZ.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 trusty ubiquity-2.18.8.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495570 Title: Re-installation of Ubuntu 14.04.2 LTS alongside Windows 8.1 failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1495570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470588] Re: Init Script does not contain a status function
** Patch removed: "initStatusFunc.patch" https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1470588/+attachment/4423005/+files/initStatusFunc.patch ** Patch added: "initStatusFunc.patch" https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1470588/+attachment/4423045/+files/initStatusFunc.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470588 Title: Init Script does not contain a status function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1470588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470588] Re: Init Script does not contain a status function
I think I created a patch? I've never used bzr before but I used it to pull the package, made the change, and then did a bzr diff. I'm attaching the resulting file. ** Patch added: "initStatusFunc.patch" https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1470588/+attachment/4423005/+files/initStatusFunc.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470588 Title: Init Script does not contain a status function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1470588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470588] [NEW] Init Script does not contain a status function
Public bug reported: I didn't realize this until I started using puppet to manage the open- vm-tools package. Puppet was attempting to run the status function in the init script for the application and the puppet run was failing due to the script returning a 1. The Red Hat init script for the same package has a status, but I'm guessing since the actual process is called "vmtoolsd" and the name of the script/binary is different it requires a somewhat odd status function. I've written a working status function for this package's init script and asked in #ubuntu irc channel how to submit it and was told to submit a bug report in launchpad. This is on Ubuntu 14.04.2 LTS with open-vm-tools package 2:9.4.0-1280544-5ubuntu6.2 ** Affects: open-vm-tools (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/1470588 Title: Init Script does not contain a status function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1470588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465439] [NEW] "Can't eject cd rom : Inappropriate ioctl for device"
Public bug reported: Can't eject an empty CD-Rom tray. None of the things suggested here (https://bugs.launchpad.net/ubuntu/+source/udev/+bug/875543) work. At best, working from a console, I get the message above. At worst, the CD drawer "grunts" as though trying to eject, but doesn't open. Using a paperclip to push the hidden manual release does work, and once the tray has a CD in it, it ejects every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 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.10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geoff 1662 F pulseaudio geoff 1965 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Tue Jun 16 11:28:07 2015 HibernationDevice: RESUME=UUID=eac9009f-2935-4961-9d6f-db25ad14f170 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. OptiPlex 320 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=8b5a8fc6-806e-425f-a86c-3eec3f7836b0 ro RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 RfKill: SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.2 dmi.board.name: 0MH651 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.2:bd12/04/2006:svnDellInc.:pnOptiPlex320:pvr:rvnDellInc.:rn0MH651:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: OptiPlex 320 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 staging trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465439 Title: "Can't eject cd rom : Inappropriate ioctl for device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438708] Re: frequent lockups asus g705js/GeForce GTX 870M
As I was unable to usefully bisect the ubuntu kernel, I tried again with the mainline kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ This gave a much clearer result: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.37-utopic/ -- works http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ -- crashes on bootup I was also able to reproduce a crash on bootup with: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc4-utopic/ -and- http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/ Thanks, Geoff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438708 Title: frequent lockups asus g705js/GeForce GTX 870M To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1438708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438708] Re: frequent lockups asus g705js/GeForce GTX 870M
Hi Christopher, I've tested a few more kernels by compiling the source packages linked from the kernel bisection page. There is NO clear breakage that I'm able to find, instead I see this: linux-image-3.13.0.48.80 - OK (last fully functional kernel) (self-compiled) linux-image-3.13.0.49.81 - fallback graphics (doesn't seem to crash) ... linux-image-3.16.0-32.42 - fallback graphics (doesn't seem to crash) (self-compiled) linux-image-3.16.0-33.44 - accelerated graphics (crashes) linux-image-3.16.0-34.45 - fallback graphics (doesn't seem to crash ... linux-image-4.0.0-04rc6.201503291935 - accelerated graphics (crashes on shutdown) I self-complied linux-image-3.15.0-1.3 and linux-image-3.15.0-4.8 and these both had fallback graphics and seemed to be stable. Thanks, Geoff Thanks, Geoff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438708 Title: frequent lockups asus g705js/GeForce GTX 870M To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1438708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438708] Re: frequent lockups asus g705js/GeForce GTX 870M
Hi Christopher, I've tried the available pre-built packages but there are graps between the binaries and upstream. The early 3.16.0 kernels work for me but with no graphics acceleration, which I think is why they don't crash. It looks like the later builds switch acceleration back on and thats when the problems occur. So I think the *real* problem must lie somewhere between 3.13.0-44 and the version of the kernel before 3.16.0-23 that still had graphics enabled. Here are the results I've come up with so far: linux-image-3.13.0-44 (trusty) - OK linux-image-3.13.0-44 (trusty) - OK linux-image-3.16.0-23 - Doesn't crash but seems to be using framebuffer video + no sound linux-image-3.16.0-28 - Doesn't crash but seems to be using framebuffer video + no sound linux-image-3.16.0-33 - accelerated graphics working but crashes linux-image-4.0.0-rc6 - seems mostly working but crashes on shutdown (observed twice) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438708 Title: frequent lockups asus g705js/GeForce GTX 870M To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1438708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438708] Re: frequent lockups asus g705js/GeForce GTX 870M
Ok - looks like I spoke too soon. On shutting down after running all day with no problems (largely unattended) the laptop crashed hard after trying to shutdown. I found this in syslog after rebooting -- this is Linux 4.0: Apr 2 20:30:07 monster kernel: [ 69.841098] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150204/nsarguments-95) Apr 2 20:30:07 monster kernel: [ 69.841423] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Apr 2 20:30:07 monster kernel: [ 69.841428] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150204/nsarguments-95) Apr 2 20:30:22 monster kernel: [ 84.853086] nouveau E[ DRM] failed to idle channel 0x0001 [DRM] Apr 2 20:30:22 monster kernel: [ 84.853284] [ cut here ] Apr 2 20:30:22 monster kernel: [ 84.853290] WARNING: CPU: 4 PID: 206 at /home/kernel/COD/linux/drivers/pci/pci.c:1546 pci_disable_device+0xab/0xc0() Apr 2 20:30:22 monster kernel: [ 84.853292] nouveau :01:00.0: disabling already-disabled device Apr 2 20:30:22 monster kernel: [ 84.853293] Modules linked in: dm_crypt bnep rfcomm binfmt_misc asus_nb_wmi uvcvideo asus_wmi sparse_keymap snd_hda_codec_hdmi videobuf2_vmalloc videobuf2_memops videobuf2_core intel_rapl v4l2_common iosf_mbi snd_hda_codec_realtek x86_pkg_temp_thermal videodev intel_powerclamp snd_hda_codec_generic coretemp btusb media bluetooth kvm_intel snd_hda_intel snd_hda_controller kvm snd_hda_codec snd_hwdep snd_pcm crct10dif_pclmul crc32_pclmul snd_seq_midi snd_seq_midi_event ghash_clmulni_intel snd_rawmidi aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_seq snd_seq_device snd_timer joydev serio_raw snd ie31200_edac mei_me mei shpchp soundcore lpc_ich edac_core mac_hid parport_pc ppdev lp nls_iso8859_1 parport nouveau i915 mxm_wmi ttm i2c_algo_bit drm_kms_helper drm psmouse ahci alx libahci mdio wmi video Apr 2 20:30:22 monster kernel: [ 84.853336] CPU: 4 PID: 206 Comm: kworker/4:1 Not tainted 4.0.0-04rc6-generic #201503291935 Apr 2 20:30:22 monster kernel: [ 84.853337] Hardware name: ASUSTeK COMPUTER INC. G750JS/G750JS, BIOS G750JS.208 07/17/2014 Apr 2 20:30:22 monster kernel: [ 84.853341] Workqueue: pm pm_runtime_work Apr 2 20:30:22 monster kernel: [ 84.853342] 060a 880465403b88 817e3106 0007 Apr 2 20:30:22 monster kernel: [ 84.853345] 880465403bd8 880465403bc8 810791b7 880465403be8 Apr 2 20:30:22 monster kernel: [ 84.853346] 88046c366000 88046c366000 880035cd8800 fff0 Apr 2 20:30:22 monster kernel: [ 84.853348] Call Trace: Apr 2 20:30:22 monster kernel: [ 84.853353] [] dump_stack+0x45/0x57 Apr 2 20:30:22 monster kernel: [ 84.853357] [] warn_slowpath_common+0x97/0xe0 Apr 2 20:30:22 monster kernel: [ 84.853359] [] warn_slowpath_fmt+0x46/0x50 Apr 2 20:30:22 monster kernel: [ 84.853363] [] ? pci_save_vc_state+0x40/0x100 Apr 2 20:30:22 monster kernel: [ 84.853368] [] pci_disable_device+0xab/0xc0 Apr 2 20:30:22 monster kernel: [ 84.853399] [] nouveau_pmops_runtime_suspend+0x82/0x110 [nouveau] Apr 2 20:30:22 monster kernel: [ 84.853404] [] pci_pm_runtime_suspend+0x7a/0x160 Apr 2 20:30:22 monster kernel: [ 84.853406] [] ? pci_legacy_suspend_late+0x100/0x100 Apr 2 20:30:22 monster kernel: [ 84.853408] [] __rpm_callback+0x3d/0xc0 Apr 2 20:30:22 monster kernel: [ 84.853411] [] ? dequeue_entity+0x17f/0x440 Apr 2 20:30:22 monster kernel: [ 84.853413] [] rpm_callback+0x2f/0x90 Apr 2 20:30:22 monster kernel: [ 84.853415] [] rpm_suspend+0x107/0x5d0 Apr 2 20:30:22 monster kernel: [ 84.853419] [] ? __switch_to+0xbe/0x5b0 Apr 2 20:30:22 monster kernel: [ 84.853421] [] ? put_prev_task_fair+0x2f/0x50 Apr 2 20:30:22 monster kernel: [ 84.853423] [] pm_runtime_work+0xea/0xf0 Apr 2 20:30:22 monster kernel: [ 84.853425] [] process_one_work+0x144/0x490 Apr 2 20:30:22 monster kernel: [ 84.853427] [] worker_thread+0x11e/0x450 Apr 2 20:30:22 monster kernel: [ 84.853429] [] ? create_worker+0x1f0/0x1f0 Apr 2 20:30:22 monster kernel: [ 84.853432] [] kthread+0xc9/0xe0 Apr 2 20:30:22 monster kernel: [ 84.853434] [] ? flush_kthread_worker+0x90/0x90 Apr 2 20:30:22 monster kernel: [ 84.853437] [] ret_from_fork+0x58/0x90 Apr 2 20:30:22 monster kernel: [ 84.853440] [] ? flush_kthread_worker+0x90/0x90 Apr 2 20:30:22 monster kernel: [ 84.853441] ---[ end trace cb476b19202523ea ]--- Apr 2 20:30:22 monster kernel: [ 84.853466] pci_pm_runtime_suspend(): nouveau_pmops_runtime_suspend+0x0/0x110 [nouveau] returns -16 ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438708 Title: frequent lockups asus g70
[Bug 1438708] Re: frequent lockups asus g705js/GeForce GTX 870M
Relevant portion of syslog from a crash on Linux 3.17: Apr 1 09:49:28 monster kernel: [ 10.722076] nouveau E[ PGRAPH][:01:00.0] HUB_INIT timed out Apr 1 09:49:28 monster kernel: [ 10.722082] nouveau E[ PGRAPH][:01:00.0] 409000 - done 0x0240 Apr 1 09:49:28 monster kernel: [ 10.722087] nouveau E[ PGRAPH][:01:00.0] 409000 - stat 0x 0x 0x 0x Apr 1 09:49:28 monster kernel: [ 10.722091] nouveau E[ PGRAPH][:01:00.0] 409000 - stat 0x 0x 0x0006 0x0001 Apr 1 09:49:28 monster kernel: [ 10.722094] nouveau E[ PGRAPH][:01:00.0] 502000 - done 0x0300 Apr 1 09:49:28 monster kernel: [ 10.722100] nouveau E[ PGRAPH][:01:00.0] 502000 - stat 0x 0x8c00 0x 0x Apr 1 09:49:28 monster kernel: [ 10.722106] nouveau E[ PGRAPH][:01:00.0] 502000 - stat 0x 0x 0x 0x Apr 1 09:49:28 monster kernel: [ 10.722108] nouveau E[ PGRAPH][:01:00.0] 50a000 - done 0x0300 Apr 1 09:49:28 monster kernel: [ 10.722114] nouveau E[ PGRAPH][:01:00.0] 50a000 - stat 0x 0x 0x 0x Apr 1 09:49:28 monster kernel: [ 10.722120] nouveau E[ PGRAPH][:01:00.0] 50a000 - stat 0x 0x 0x 0x Apr 1 09:49:28 monster kernel: [ 10.722122] nouveau E[ PGRAPH][:01:00.0] 512000 - done 0x0300 Apr 1 09:49:28 monster kernel: [ 10.722128] nouveau E[ PGRAPH][:01:00.0] 512000 - stat 0x 0x 0x 0x Apr 1 09:49:28 monster kernel: [ 10.722134] nouveau E[ PGRAPH][:01:00.0] 512000 - stat 0x 0x 0x 0x Apr 1 09:49:28 monster kernel: [ 10.722136] nouveau E[ PGRAPH][:01:00.0] 51a000 - done 0x0300 Apr 1 09:49:28 monster kernel: [ 10.722142] nouveau E[ PGRAPH][:01:00.0] 51a000 - stat 0x 0x 0x 0x Apr 1 09:49:28 monster kernel: [ 10.722148] nouveau E[ PGRAPH][:01:00.0] 51a000 - stat 0x 0x 0x 0x Apr 1 09:49:28 monster kernel: [ 10.722149] nouveau E[ PGRAPH][:01:00.0] init failed, -16 Apr 1 09:49:32 monster NetworkManager[930]: WiFi hardware radio set enabled Apr 1 09:49:35 monster kernel: [ 17.847450] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95) Apr 1 09:49:35 monster kernel: [ 17.847791] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM Apr 1 09:49:35 monster kernel: [ 17.847795] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140724/nsarguments-95) Apr 1 09:49:35 monster crontab[2536]: (root) LIST (root) Apr 1 09:49:36 monster ntpd[2608]: ntpd 4.2.6p5@1.2349-o Fri Feb 6 15:24:12 UTC 2015 (1) Apr 1 09:49:36 monster ntpd[2609]: proto: precision = 0.131 usec Apr 1 09:49:36 monster ntpd[2609]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Apr 1 09:49:36 monster ntpd[2609]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Apr 1 09:49:36 monster puppet-agent[2071]: (/Stage[main]/Ntp::Service/Service[ntp]/ensure) ensure changed 'stopped' to 'running' Apr 1 09:49:36 monster rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="760" x-info="http://www.rsyslog.com";] exiting on signal 15. Apr 1 09:51:25 monster rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="895" x-info="http://www.rsyslog.com";] start Apr 1 09:51:25 monster rsyslogd: rsyslogd's groupid changed to 104 Apr 1 09:51:25 monster rsyslogd: rsyslogd's userid changed to 101 -- at this point the system shows evidence of being rebooted -- Apr 1 09:51:25 monster kernel: [0.00] Initializing cgroup subsys cpuset Apr 1 09:51:25 monster kernel: [0.00] Initializing cgroup subsys cpu Apr 1 09:51:25 monster kernel: [0.00] Initializing cgroup subsys cpuacct ** 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/1438708 Title: frequent lockups asus g705js/GeForce GTX 870M To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1438708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438708] Re: frequent lockups asus g705js/GeForce GTX 870M
Alberto, Appologies for the delay in responding. Good news - I've been able to boot linux 4.0-rc6 and the system is now stable. I used the package linux-image-4.0.0-04rc6-generic for Vivid from the from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc6-vivid/ There are still a bunch of nouveau errors (below) visible in dmesg but the system does NOT crash anymore [0.695552] nouveau [ DEVICE][:01:00.0] BOOT0 : 0x0e4190a2 [0.695556] nouveau [ DEVICE][:01:00.0] Chipset: GK104 (NVE4) [0.695558] nouveau [ DEVICE][:01:00.0] Family : NVE0 [0.762806] nouveau [ VBIOS][:01:00.0] using image from PROM [0.762895] nouveau [ VBIOS][:01:00.0] BIT signature found [0.762899] nouveau [ VBIOS][:01:00.0] version 80.04.f4.00.01 [0.763651] nouveau [ DEVINIT][:01:00.0] adaptor not initialised [0.763681] nouveau [ VBIOS][:01:00.0] running init tables [1.025922] nouveau [ PMC][:01:00.0] MSI interrupts enabled [1.025982] nouveau [ PFB][:01:00.0] RAM type: GDDR5 [1.025984] nouveau [ PFB][:01:00.0] RAM size: 3072 MiB [1.025987] nouveau [ PFB][:01:00.0]ZCOMP: 0 tags [1.028427] nouveau [VOLT][:01:00.0] GPU voltage: 60uv [1.076762] nouveau [ PTHERM][:01:00.0] FAN control: none / external [1.076773] nouveau [ PTHERM][:01:00.0] fan management: automatic [1.076789] nouveau [ PTHERM][:01:00.0] internal sensor: yes [1.076829] nouveau [ CLK][:01:00.0] 07: core 324-405 MHz memory 648 MHz [1.076865] nouveau [ CLK][:01:00.0] 0a: core 405-967 MHz memory 1620 MHz [1.076910] nouveau [ CLK][:01:00.0] 0e: core 405-967 MHz memory 4000 MHz [1.076963] nouveau [ CLK][:01:00.0] 0f: core 405-967 MHz memory 5000 MHz [1.077034] nouveau [ CLK][:01:00.0] --: core 324 MHz memory 648 MHz [1.110733] nouveau E[PBUS][:01:00.0] MMIO read of 0x FAULT at 0x500c30 [ IBUS ] [1.110882] nouveau [ DRM] VRAM: 3072 MiB [1.110884] nouveau [ DRM] GART: 1048576 MiB [1.110888] nouveau [ DRM] TMDS table version 2.0 [1.110891] nouveau [ DRM] DCB version 4.0 [1.110893] nouveau [ DRM] DCB conn 08: 00020846 [1.110896] nouveau [ DRM] DCB conn 09: 0900 [1.117043] nouveau [ DRM] MM: using COPY for buffer copies [1.117049] [drm] Initialized nouveau 1.2.1 20120801 for :01:00.0 on minor 0 [ 11.474194] nouveau E[ PGR][:01:00.0] HUB_INIT timed out [ 11.474201] nouveau E[ PGR][:01:00.0] 409000 - done 0x0240 [ 11.474206] nouveau E[ PGR][:01:00.0] 409000 - stat 0x 0x 0x 0x [ 11.474210] nouveau E[ PGR][:01:00.0] 409000 - stat 0x 0x 0x0006 0x [ 11.474213] nouveau E[ PGR][:01:00.0] 502000 - done 0x0340 [ 11.474218] nouveau E[ PGR][:01:00.0] 502000 - stat 0x8000 0x6500 0x 0x [ 11.474224] nouveau E[ PGR][:01:00.0] 502000 - stat 0x 0x 0x0002 0x [ 11.474227] nouveau E[ PGR][:01:00.0] 50a000 - done 0x0340 [ 11.474233] nouveau E[ PGR][:01:00.0] 50a000 - stat 0x8000 0x8e00 0x 0x [ 11.474239] nouveau E[ PGR][:01:00.0] 50a000 - stat 0x 0x 0x0002 0x [ 11.474241] nouveau E[ PGR][:01:00.0] 512000 - done 0x0340 [ 11.474247] nouveau E[ PGR][:01:00.0] 512000 - stat 0x8000 0x8e00 0x 0x [ 11.474253] nouveau E[ PGR][:01:00.0] 512000 - stat 0x 0x 0x0002 0x [ 11.474255] nouveau E[ PGR][:01:00.0] 51a000 - done 0x0300 [ 11.474261] nouveau E[ PGR][:01:00.0] 51a000 - stat 0x 0x00020d00 0x 0x [ 11.474267] nouveau E[ PGR][:01:00.0] 51a000 - stat 0x 0x 0x 0x [ 11.474269] nouveau E[ PGR][:01:00.0] init failed, -16 [ 35.833502] nouveau E[ DRM] failed to idle channel 0x [DRM] [ 35.878812] pci_pm_runtime_suspend(): nouveau_pmops_runtime_suspend+0x0/0x110 [nouveau] returns -16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438708 Title: frequent lockups asus g705js/GeForce GTX 870M To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1438708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438708] Re: frequent lockups asus g705js/GeForce GTX 870M
Hi Alberto, I skipped recovery mode and installed the kernels directly from my functioning 3.13 system: ii linux-image-3.17.1-031701-generic 3.17.1-031701.201410150735 ii linux-image-3.18.0-031800rc2-generic3.18.0-031800rc2.201410262035 I was unable to boot 3.18 due to it not finding the root device 3.17 looked like it worked so I immediately shutdown from the login screen and it then crashed so hard that magic sysreq didn't even work - I had to hold the power button. Interestingly, last night after running linux 3.13 for a while I rebooted into linux 3.16 via recovery mode, where I waited for approximately 1 minute before booting normally and the system DID seem stable overnight. This morning, I powered the laptop off and attempted to boot 3.16 and it crashed during the boot process so the error is still reproducible. I'll leave 3.17 running and see if it crashes once I'm logged in -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438708 Title: frequent lockups asus g705js/GeForce GTX 870M To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1438708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1438708] [NEW] frequent lockups asus g705js/GeForce GTX 870M
Public bug reported: Summary === I think I am affected by this same bug, I have all the above systems and get hard lockups with Linux kernel 3.16 every 5 - 15 minutes. Attempted upgrading to (x)ubuntu 14.10 to see if this improved stability and laptop crashed so badly during the upgrade that it broke grub and had to be recovered with ubuntu boot-repair. This alowed the system to boot and I was able to complete configuration with dkpg --configure -a --pending System still crashes every few minutes when running (x)ubuntu 14.10 and about 50% of the time crashes before even reaching the login screen. If I'm lucky attempting to swich VCs will resolve things but the system always crashes eventually and has to be powered off by holiding the power button for 10 seconds or via the magic sysreq key. No other key cominations work. Hardware I also have an Asus laptop with an Nvida card which is what led me to this bug report, the following hardware is present: * Laptop model Asus G750JS (ASUS-NotebookSKU) * GK104M [GeForce GTX 870M] * 4th Gen Core Processor Integrated Graphics Controller (i915 - not used) * BCM4352 802.11ac Wireless Network Adapter * QCA8171 Gigabit Ethernet BIOS/DMI information == I tried flashing the latest BIOS from (http://www.asus.com/Notebooks_Ultrabooks/ASUS_ROG_G750JS/HelpDesk_Download/) but it didn't fix anything. Running the commands listed above gives: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date G750JS.208 07/17/2014 Driver info This problem occurs with both the nouveau and nvidia drivers: rc nvidia-331-updates 331.113-0ubuntu0.0.4 (removed by "additional drivers" application) ii xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 Workaround == This configuration is rock solid on kernel 3.13. I was able to boot to a previously installed kernel (3.13.0-44-generic) and the system performs as expected and is stable. Debug info = The system has been generating a bunch of problem reports too so I've been clicking the submit button. Happy to rovide futher info or try a few experiments to get this resolved. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-33-generic 3.16.0-33.44 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: geoff 3257 F pulseaudio CurrentDesktop: XFCE Date: Wed Apr 1 01:05:31 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-23 (189 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: ASUSTeK COMPUTER INC. G750JS ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=3fc94323-d40a-42ca-87c7-28a9e52ebcf4 ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-3.16.0-33-generic N/A linux-backports-modules-3.16.0-33-generic N/A linux-firmware 1.138.1 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2015-03-29 (2 days ago) dmi.bios.date: 07/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G750JS.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G750JS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG750JS.208:bd07/17/2014:svnASUSTeKCOMPUTERINC.:pnG750JS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G750JS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1438708 Title: frequent lockups asus g705js/GeForce GTX 870M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371401] Re: randomly freezing
Apologies, I now realise I should have created a new bug report which I have done: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438708 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371401 Title: randomly freezing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1371401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs