[Bug 1741264] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1741264/+attachment/5031056/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741264 Title: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741264] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1741264/+attachment/5031059/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741264 Title: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741264] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1741264/+attachment/5031050/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741264 Title: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741264] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1741264/+attachment/5031055/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741264 Title: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741264] Re: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+attachment/5031060/+files/Xorg.0.log ** 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/1741264 Title: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741264] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1741264/+attachment/5031058/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741264 Title: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741264] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1741264/+attachment/5031048/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741264 Title: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741264] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1741264/+attachment/5031049/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741264 Title: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741264] Re: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install
** Attachment added: "devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+attachment/5031045/+files/devices ** Tags added: apport-collected ** Description changed: Hi, I've a fresh installed Ubuntu 16.04 on an Asus Zenbook UX32VD laptop. The touchpad does not work at all. It is not even listed in xinput. I'm not sure about the manufacturer but I think it is Elan I've tested with fresh install of Ubuntu 16.04.3 LTS I've also tested with live USB of Ubuntu 17.10, 14.04 LTS An USB connected mouse works perfectly. Thank you for your time + --- + ApportVersion: 2.20.4-0ubuntu4 + Architecture: amd64 + AudioDevicesInUse: + Cannot stat file /proc/2288/fd/17: Stale file handle + Cannot stat file /proc/2288/fd/18: Stale file handle + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 2208 F pulseaudio + CasperVersion: 1.380 + DistroRelease: Ubuntu 17.04 + LiveMediaBuild: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) + MachineType: ASUSTeK COMPUTER INC. UX32VD + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: file=/preseed/hostname.seed noprompt boot=casper iso-scan/filename=/hostname-17.04-desktop-amd64.iso quiet -- + ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.10.0-19-generic N/A + linux-backports-modules-4.10.0-19-generic N/A + linux-firmware 1.164 + Tags: zesty + Uname: Linux 4.10.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 01/29/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX32VD.214 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX32VD + 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.name: UX32VD + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741264 Title: Touchpad (Elan !?) not detected on Asus Zenbook UX32VD after new install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Lenovo Flex 3-1130 also fixed by step 8 in the description. Thank you all! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713004] Re: Temporary files left under /var/tmp by mkinitramfs
> There are tons of reds in the autopkg tests for initramfs-tools on trusty, > were those > considered and deemed flaky tests or something? Those fail due to bug 1723223 which I am working on; it's a problem with the 'ubuntu-regression-suite' linux autopkgtest and can be ignored. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713004 Title: Temporary files left under /var/tmp by mkinitramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1713004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424342] Re: CIFS remote shares freeze on resume after suspend
Call trace from Ubuntu 16.04 and cifs-utils 2:6.4-1ubuntu1.1 on 4.10.0-42-generic: [19936.692679] INFO: task ls:15421 blocked for more than 120 seconds. [19936.692683] Tainted: GW 4.10.0-42-generic #46~16.04.1-Ubuntu [19936.692685] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [19936.692687] ls D0 15421 15411 0x [19936.692691] Call Trace: [19936.692694] __schedule+0x232/0x700 [19936.692698] schedule+0x36/0x80 [19936.692701] schedule_preempt_disabled+0xe/0x10 [19936.692704] __mutex_lock_slowpath+0x193/0x290 [19936.692708] mutex_lock+0x2f/0x40 [19936.692728] cifs_reconnect_tcon+0x95/0x340 [cifs] [19936.692733] ? __find_get_block+0x22c/0x260 [19936.692736] ? __check_block_validity.constprop.75+0x31/0x70 [19936.692756] smb_init+0x2a/0x50 [cifs] [19936.692777] CIFSSMBQPathInfo+0x63/0x2e0 [cifs] [19936.692805] cifs_query_path_info+0x6f/0x1a0 [cifs] [19936.692809] ? __kmalloc+0x1c7/0x200 [19936.692812] ? ext4_htree_store_dirent+0x3e/0x120 [19936.692816] ? lookup_fast+0xe3/0x2f0 [19936.692819] ? kmem_cache_alloc_trace+0x152/0x1c0 [19936.692844] cifs_get_inode_info+0x4a3/0x970 [cifs] [19936.692847] ? unlazy_walk+0xf8/0x180 [19936.692851] ? __kmalloc+0x178/0x200 [19936.692874] ? build_path_from_dentry+0xe2/0x3e0 [cifs] [19936.692895] ? build_path_from_dentry+0xe2/0x3e0 [cifs] [19936.692918] cifs_revalidate_dentry_attr+0x1d5/0x250 [cifs] [19936.692941] cifs_getattr+0x51/0x110 [cifs] [19936.692946] vfs_getattr_nosec+0x29/0x40 [19936.692949] vfs_getattr+0x26/0x30 [19936.692953] vfs_fstatat+0x78/0xc0 [19936.692958] SYSC_newlstat+0x31/0x60 [19936.692963] SyS_newlstat+0xe/0x10 [19936.692967] entry_SYSCALL_64_fastpath+0x1e/0xad [19936.692969] RIP: 0033:0x7f927b0afc55 [19936.692971] RSP: 002b:7ffc7a297c98 EFLAGS: 0246 ORIG_RAX: 0006 [19936.692974] RAX: ffda RBX: 7f927b37db20 RCX: 7f927b0afc55 [19936.692975] RDX: 0159ed60 RSI: 0159ed60 RDI: 7ffc7a297ca0 [19936.692977] RBP: 8041 R08: R09: 03c0 [19936.692978] R10: 01cc R11: 0246 R12: 7f927b37db78 [19936.692980] R13: 7f927b37db78 R14: 2710 R15: 00404ad0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424342 Title: CIFS remote shares freeze on resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1424342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521174] Re: [MIR] amd64-microcode (multiverse -> main)
This simple report is more than two years old, and the wiki clearly states what "incomplete" means: (https://wiki.ubuntu.com/Bugs/Bug%20statuses) You say the solution is to handle all by yourselves. But we actually see that it's quite the opposite. Or I am mistaken, and MIR is been great success? Come on! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521174 Title: [MIR] amd64-microcode (multiverse -> main) To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1521174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732735] Re: bind_policy hard broken in ldap.conf in 17.10
@Andreas: hallo Andreas, this is the changed part of my nsswitch.conf: ... passwd: files ldap group: files ldap shadow: files ldap hosts: files dns [NOTFOUND=return] mdns4_minimal mdns4 ... ldap01 & ldap02 should be resolved via dns and domain search in resolv.conf, so it is possible to move ldap-servers to different IPs. There are no additional entrances in /etc/hosts. There is one admin-user "worker" and one standard-user "user" on the host, who should work even without any network. All other user come from an LDAP-Tree and have nfs-home-dir. my servers are set up with scripts from: https://github.com/edvapp/networkbox and clients are set up & managed with scripts from: https://github.com/edvapp/autoinstall/tree/master/laus/scriptsForClasses/APP1804 https://github.com/edvapp/autoinstall/blob/master/laus/scriptsForClasses/APP1804/410-createLDAPClient.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732735 Title: bind_policy hard broken in ldap.conf in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/1732735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668105] Re: xhci_hcd module turns off usb host controller on boot
Update: I've compiled the 4.13.19 kernel without USB 3 support (in the hope that it would fall back to the USB 2 module - it doesn't - you end up with no keyboard or trackpad). If you're running a system that has a BIOS, and it allows you to turn off USB 3.0 support, that seems to be the only option. Otherwise it appears that you're stuck with intermittent USB. It sucks that MacBooks don't have ethernet... I'm using a shared wifi AP even though I have a gigabit cable on my desk :( There's a ton of USB 3.0 kernel bug tickets on launchpad, and in most cases they end up expiring due to lack of updates. This one will likely go the same way. If ANYONE with a MacBook has managed to get it to work without USB 3.0 in the kernel, post here or PM me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668105 Title: xhci_hcd module turns off usb host controller on boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1668105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716160] Re: System goes to sleep with external monitor and lid closed after login
It looks like this bug might be covered by: https://bugzilla.gnome.org/show_bug.cgi?id=788915 In that case the fix is apparently coming in mutter version 3.26.3 ... https://git.gnome.org/browse/mutter/commit/?h=gnome-3-26=ea538537ec2d3d2e58b4a301572de2eac3686c93 https://git.gnome.org/browse/mutter/commit/?h=gnome-3-26=205dc28eae33fa8278bf1a32827023c600a79d20 ** Bug watch added: GNOME Bug Tracker #788915 https://bugzilla.gnome.org/show_bug.cgi?id=788915 ** Also affects: mutter via https://bugzilla.gnome.org/show_bug.cgi?id=788915 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Invalid => Confirmed ** Changed in: mutter (Ubuntu) Assignee: Andrea Azzarone (azzar1) => (unassigned) ** Changed in: mutter (Ubuntu Artful) Assignee: Andrea Azzarone (azzar1) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716160 Title: System goes to sleep with external monitor and lid closed after login To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1716160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741215] Re: synaptic crashed with SIGSEGV in _XReply()
*** This bug is a duplicate of bug 1701845 *** https://bugs.launchpad.net/bugs/1701845 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1701845, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1741215/+attachment/5030990/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1741215/+attachment/5030992/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1741215/+attachment/5030997/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1741215/+attachment/5030998/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1741215/+attachment/5030999/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1741215/+attachment/5031000/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1741215/+attachment/5031001/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1701845 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741215 Title: synaptic crashed with SIGSEGV in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1741215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737911] Re: linux: 3.13.0-138.187 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-138.187 /trusty-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737911 Title: linux: 3.13.0-138.187 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738415] Re: package fancontrol 1:3.4.0-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for filing this bug in Ubuntu. Could you please send us the output of this command: sudo systemctl status fancontrol.service It should show us the reason why the service failed to start. Thanks ** Changed in: lm-sensors (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1738415 Title: package fancontrol 1:3.4.0-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1738415/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1714810] Re: gnome-terminal shrinks window to nothing
*** This bug is a duplicate of bug 1569638 *** https://bugs.launchpad.net/bugs/1569638 ** This bug has been marked a duplicate of bug 1569638 Terminal height shrinking when it loses focus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714810 Title: gnome-terminal shrinks window to nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1714810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741253] Re: [snap] camera access doesn't work, even after connecting camera interface
Nevermind, it works if I don't have another browser tab already capturing video. ** Changed in: chromium-browser (Ubuntu) Status: New => Opinion ** Changed in: chromium-browser (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741253 Title: [snap] camera access doesn't work, even after connecting camera interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740927] Re: FTBFS: unknown type name ‘errcode_t’
** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740927 Title: FTBFS: unknown type name ‘errcode_t’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1740927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740927] Re: FTBFS: unknown type name ‘errcode_t’
** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/1740927 Title: FTBFS: unknown type name ‘errcode_t’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1740927/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1738415] Re: package fancontrol 1:3.4.0-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for filing this bug in Ubuntu. Could you please send us the output of this command: sudo systemctl status fancontrol.service It should show us the reason why the service failed to start. Thanks ** Changed in: lm-sensors (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738415 Title: package fancontrol 1:3.4.0-4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1738415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741244] Re: Failing to start up ovs-dpdk with 17.11
That said while they can exist in the archive together, we have to make the packages conflict prior versions to avoid this issue for now. There might be a more complex solution with something like modversions in the kernel. But then this was meant to be a drop-in for 3rd party drivers, which would loose much of it's eas-of-use. After a short discussion we agreed on a middle ground. We make the dir versioned. So installs in Debian/Ubuntu work as they should by default. And 3rd party driver providers can still drop them in, but have to either a) link into all driver dirs (not very careful but working if the driver is ok) b) link their driver to versioned DIRs they really support/qualified ** Changed in: dpdk (Ubuntu) Status: New => Triaged ** Changed in: dpdk (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741244 Title: Failing to start up ovs-dpdk with 17.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1741244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1740051] Re: USB keys 3.0 dont work on USB 3.0 port with kernel 4.13.0-21
Hello, This bug occurs with version 4.13.0-21 (unrecognized all my usb 3.0 keys but he sees usb keys 2), my system is more stable with version 4.10.0-42, there is no link with an update. I do not want to test the kernel v4.15-rc6. My motherboard has Intel components (chipset X99). The key I use the most is a : SanDisk Extreme 64GB USB 3.0 Flash Drive SDCZ80-064G With kernel 4.10.0-42 the beginning of write speed may be at 180 Mb / sec, after a moment the speed becomes that of usb 2 (30 Mb / sec) and the speed decreases to 8 Mb / sec after a moment. When I want to eject my key, I have to wait very very long because all the data has not been written It seems that USB 3 is not correctly implemented / managed. Excuse my for my bad english. Best regards and happy new year 2018 to you. 2018-01-02 18:41 GMT+01:00 Joseph Salisbury: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.15 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc6/ > > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1740051 > > Title: > USB keys 3.0 dont work on USB 3.0 port with kernel 4.13.0-21 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Most of my UBS 3.0 Keys are not recognized on USB 3.0 ports with > kernel 4.13.0-21 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1740051/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740051 Title: USB keys 3.0 dont work on USB 3.0 port with kernel 4.13.0-21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665072] Re: clicking 'relaunch' on gnome-terminal error vertically shrinks window
*** This bug is a duplicate of bug 1569638 *** https://bugs.launchpad.net/bugs/1569638 ** This bug has been marked a duplicate of bug 1569638 Terminal height shrinking when it loses focus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665072 Title: clicking 'relaunch' on gnome-terminal error vertically shrinks window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/665072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741227] Re: apparmor denial to several paths to binaries
And btw - we had such rules for /bin and /usr/bin already - maybe even for the same reasons. Chances are that the actual change is that /usr/local/bin and /usr/local/sbin are now in PATH of the service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741227 Title: apparmor denial to several paths to binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
** Description changed: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: - * BIOS settings cannot be saved - * USB Boot impossible - * EFI entries read-only. + * BIOS settings cannot be saved + * USB Boot impossible + * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G - Dell Inspiron 15-3531 (not fixed by 4.14.9) + Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ -f25l32pa, 0x8c2016 -f25l32qa, 0x8c4116 -f25l64qa, 0x8c4117 + f25l32pa, 0x8c2016 + f25l32qa, 0x8c4116 + f25l64qa, 0x8c4117 /* GigaDevice */ -gd25q16, 0xc84015 -gd25q32, 0xc84016 -gd25lq32, 0xc86016 -gd25q64, 0xc84017 -gd25lq64c, 0xc86017 -gd25q128, 0xc84018 -gd25q256, 0xc84019 + gd25q16, 0xc84015 + gd25q32, 0xc84016 + gd25lq32, 0xc86016 + gd25q64, 0xc84017 + gd25lq64c, 0xc86017 + gd25q128, 0xc84018 + gd25q256, 0xc84019 /* Winbond */ -w25q16dw, 0xef6015 -w25q32dw, 0xef6016 -w25q64dw, 0xef6017 -w25q128fw, 0xef6018 + w25q16dw, 0xef6015 + w25q32dw, 0xef6016 + w25q64dw, 0xef6017 + w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data
Well, network-manager depends on iproute2, as do many other things. When I try to remove iproute2 from my system I get this: The following packages will be REMOVED: gnome-control-center* ifupdown* iproute2* isc-dhcp-client* keepalived* network-manager* network-manager-config-connectivity-ubuntu* network-manager-gnome* network-manager-openvpn* network-manager-openvpn-gnome* network-manager-pptp* network-manager-pptp-gnome* openvpn* pppoeconf* ubuntu-desktop* Of these I use extensively openvpn (via network manager) and, although it's not listed as a dependency, lxd (in the host), which I just confirmed uses iproute2 to set up its bridges and networking. That being said, this is on artful, not xenial. The xenial dep8 tests in the excuses page are all green, though. I'll setup up a xenial vm, with a lot of networking "things" (nics, bridges, server software), update iproute2, and let it boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732032 Title: ip maddr show and ip maddr show dev enP20p96s0 show different data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1732032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739418] Re: Please build minimized images in a 1GiB image
We discussed the change with Steve Langasek again and agreed that the initial image should not be changed and the size of the final images produced by livecd-rootfs should be monitored. The change already made in trunk will be reverted soon. ** Changed in: livecd-rootfs (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: livecd-rootfs (Ubuntu) Status: Fix Released => Won't Fix ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: Balint Reczey (rbalint) => (unassigned) ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739418 Title: Please build minimized images in a 1GiB image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1739418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data
I installed the updated package on an existing maas server on xenial/amd64, and deployed a new node (also xenial/amd64) where I also installed the updated package plus some server software. No visible side effects. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732032 Title: ip maddr show and ip maddr show dev enP20p96s0 show different data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1732032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729075] Re: Merge git 1:2.15.1-3 (main) from Debian unstable (main)
This bug was fixed in the package git - 1:2.15.1-1ubuntu2 --- git (1:2.15.1-1ubuntu2) bionic; urgency=medium * debian/gitweb.apache2: use lynx instead of the deprecated transitional lynx-cur package. -- Łukasz 'sil2100' ZemczakThu, 14 Dec 2017 19:51:49 +0100 ** Changed in: git (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729075 Title: Merge git 1:2.15.1-3 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1729075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740768] Re: CVE-2017-15365: Replication in sql/event_data_objects.cc occurs before ACL checks
The 10.1 series update for 17.04 is now available. Please use git-buildpackage to fetch and build from the ubuntu-17.04 branch at http://anonscm.debian.org/cgit/pkg- mysql/mariadb-.git/log/?h=ubuntu-17.04 The repository uses pristine-tar, so there is no need to separately download the sources. You can just check the signature/SHA1SUM directly from the git-buildpackage generated tarball. Test builds and testsuite passed on all platforms at https://launchpad.net/~mysql- ubuntu/+archive/ubuntu/mariadb-10.1/+builds?build_text=_state=all As a reminder, debdiffs can be browsed directly from the repo like this: https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.1.git/diff/debian/?id=ubuntu/10.1.30-0ubuntu0.17.04.1=ubuntu/10.1.25-0ubuntu0.17.04.1 Or in a local clone with 'git diff .. debian/' Security sponsor note these: https://wiki.ubuntu.com/SecurityTeam/PublicationNotes#Sponsoring_MariaDB_Security_Updates ** Changed in: mariadb-10.1 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740768 Title: CVE-2017-15365: Replication in sql/event_data_objects.cc occurs before ACL checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1740768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740608] Re: USN-3459-1: partially applies to MariaDB too
Corrected diff link: https://anonscm.debian.org/cgit/pkg- mysql/mariadb-5.5.git/diff/debian/?id=ubuntu/5.5.58-1ubuntu0.14.04.1=ubuntu/5.5.57-1ubuntu0.14.04.1 The fix for 10.0 is already done, I am only waiting for builds to complete and confirm that all is OK at https://launchpad.net/~mysql- ubuntu/+archive/ubuntu/mariadb-10.0/+builds?build_text=_state=all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740608 Title: USN-3459-1: partially applies to MariaDB too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.0/+bug/1740608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724650] Re: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)
> Why would an Nvidea card need anything Nouveau? nouveau is the open-source driver for Nvidia cards: https://nouveau.freedesktop.org/wiki/ Your booting problem is most likely not related to this issue. It seems to me like your issue is with the X server (graphics) not correctly starting. As this is a bug report for a specific problem that is likely unrelated to your installation problem, I suggest seeking more general installation help from better sources, such as IRC: https://wiki.ubuntu.com/IRC/ChannelList or general installation help: https://help.ubuntu.com/community/Installation Finally, if you are new to Linux, it is probably better for you to try installing the Ubuntu Long-Term-Support (LTS) release. The current LTS release is Xenial 16.04, which you can download here: http://releases.ubuntu.com/16.04/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724650 Title: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1724650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173457] Re: Ubuntu Installer uses wrong bootloader location for USB UEFI installs
Dylan, yes, your description at https://answers.launchpad.net/ubuntu/+question/662540 is an instance of this bug. Your repair was OK, but a bit overkill. Specifically, a chroot was not really necessary, since the file-juggling could all be done without that. Of course, as this is a bug in ubiquity, no fix SHOULD be necessary; it should be fixed there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173457 Title: Ubuntu Installer uses wrong bootloader location for USB UEFI installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1173457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569638] Re: Terminal height shrinking when it loses focus
this error affects third-party gtk issues, for example, the paper-gtk-theme package ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569638 Title: Terminal height shrinking when it loses focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1569638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739674] Re: virsh Fails at Hot Plugging Network Device with model virtio
Note: checked against latest libvirt plus all my incoming libvirt improvements on security domain callbacks - still affected. The generated profile on the replace triggers: operation="profile_replace" info="same as current profile, skipping" Note: workaround for now if you are affected Add /dev/vhost-net rw, to /etc/apparmor.d/abstractions/libvirt-qemu (Sad that we have local overrides for all but the guest templates, might want to add that later) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739674 Title: virsh Fails at Hot Plugging Network Device with model virtio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1739674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures
Is there anyone from ubuntu-fan developers willing to satisfy SRU requirements below? > Blocked on: > > * SRU paperwork > * Fixes for future stable releases > * Fix for Bionic I could try those, but it's not ideal since I have to go through sponsorship processes and guess the intention of the patch. This bug is critical to me since the proposed workaround for MAAS deployments as adding -proposed in MAAS is not realistic in production cloud because: - MAAS is not capable to add ubuntu-release aware apt line for -proposed using the custom repository management (trusty nodes will also have xenial-proposed apt line unexpectedly) - MAAS cannot specify the pin-priority of xenial-proposed using the custom repository management so unnecessary kernels and grub will be installed from -proposed I ended up using a little bit verbose late_commands in curtin_userdata which is not so handy: https://paste.ubuntu.com/26319353/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737640 Title: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Again, as Fabio mentioned https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/comments/452 What can we do if we have no way of running linux ? With possibility to boot into Windows ONLY ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741272] [NEW] php-redis package is broken
Public bug reported: php-redis v3.1.4 has a critical bug whereby the extension crashes on attempted usage. I believe the issue is resolved in v3.1.5/6 ** Affects: php5 (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/1741272 Title: php-redis package is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1741272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521174] Re: [MIR] amd64-microcode (multiverse -> main)
please see https://wiki.ubuntu.com/MainInclusionProcess for the description of MIR bug statuses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521174 Title: [MIR] amd64-microcode (multiverse -> main) To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1521174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741274] [NEW] package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging tot overschrijven van gedeelde '/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere exem
Public bug reported: the crash popped up out of the blue, was just working without any indication that installing/upgrading was happening. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libperl5.26 5.26.0-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-lowlatency 4.13.13 Uname: Linux 4.13.0-21-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Thu Jan 4 12:49:36 2018 ErrorMessage: poging tot overschrijven van gedeelde '/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere exemplaren van pakket libperl5.26:i386 InstallationDate: Installed on 2017-03-09 (301 days ago) InstallationMedia: Ubuntu-Studio 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: perl Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging tot overschrijven van gedeelde '/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere exemplaren van pakket libperl5.26:i386 UpgradeStatus: Upgraded to artful on 2017-10-21 (74 days ago) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741274 Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: poging tot overschrijven van gedeelde '/usr/share/doc/libperl5.26/changelog.Debian.gz', dat verschilt van andere exemplaren van pakket libperl5.26:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1741274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
The issue is with the systemd resolver not with glibc. With systemd-resolve IP in /etc/resolv.conf: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 $ time ./test not-a-hostname Trying to resolve: not-a-hostname getaddrinfo errno: No such file or directory getaddrinfo() return value: -2 (Name or service not known) real0m10.076s user0m0.001s sys 0m0.000s Without systemd-resolve in /etc/resolv.conf. I changed it to point to my local DNS server directly. # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. #nameserver 127.0.0.53 nameserver 192.168.1.1 $ time ./test not-a-hostname Trying to resolve: not-a-hostname getaddrinfo errno: No such file or directory getaddrinfo() return value: -2 (Name or service not known) real0m0.097s user0m0.001s sys 0m0.000s ** Changed in: glibc (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/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 8 (vethJWPPL8) Current Scopes: LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 4 (lxdbr0) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (eno1) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.1.1 Link 2 (enp4s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741277] [NEW] manage_etc_hosts default is unhelpful
Public bug reported: Except for existing setups, almost everyone will want manage_etc_hosts: localhost by default. Without this, various things end up broken because a system can't look up its own hostname. Are there any use cases where a default of manage_etc_hosts: localhost will cause problems? To avoid stepping on people's toes, I'm not suggesting making the change retrospectively. But if new Ubuntu releases start doing it (eg. with Bionic) and old releases maintain existing behaviour, then we'd get there over time. Is there any existing mechanism or process for changing cloud-init defaults like this? ** Affects: cloud-init (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/1741277 Title: manage_etc_hosts default is unhelpful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1741277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
The scsi/iscsi team has accepted by fix proposal and merged the patch for 4.16 merge window: https://www.mail-archive.com/open-iscsi@googlegroups.com/msg10111.html I'll propose the cherry-pick as SRU for Ubuntu kernels as soon as it is merged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1569925 Title: Shutdown hang on 16.04 with iscsi targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1569925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741096] Re: test-mic can fail / writes to qemu-nbd device do not persist
I considered the fact that maybe the partitioned image that test-mic was creating was somehow invalid. To test that, I modifed mount-image-callback to set the mount device in MOUNT_DEV, and then did: cp "$pt1" /tmp/part1.img cp "$pt2" /tmp/part2.img mount-image-callback --read-only --part=1 "$img_mbr" -- sh -c 'dd if=$MOUNT_DEV of=/tmp/part1.mbr.img' mount-image-callback --read-only --part=2 "$img_mbr" -- sh -c 'dd if=$MOUNT_DEV of=/tmp/part2.mbr.img' mount-image-callback --read-only --part=1 "$img_gpt" -- sh -c 'dd if=$MOUNT_DEV of=/tmp/part1.gpt.img' mount-image-callback --read-only --part=2 "$img_gpt" -- sh -c 'dd if=$MOUNT_DEV of=/tmp/part2.gpt.img' then an 'md5sum' shows that the 'dd'd image is identical to the partition image. It seems to me that that validates the partition table and the data. I was somewhat concerned that maybe my partition/sector math in test-mic was truncating the partition or filesystem. that does not seem to be the case. So, it seems that this is either an issue in a.) qemu-nbd b.) kernel c.) mount-image-callback assumptions on qemu-nbd usage. for 'c', the assumption is that this is valid: DEV=/dev/nbd0 # unused nbd device BNAME=$(basename $DEV) PARTNUM=2 PART_PATH=${DEV}p${PARTNUM} FILE=/tmp/my-2partition-mbr.img 1.) qemu-nbd --format=raw --connect $DEV $FILE 2.) wait until a 'pid' file appears in /sys/block/$BNAME/pid) 3.) wait until $PART_PATH exists 4.) mount $PART_PATH to MOUNTPOINT 5.) execute user code that operates on on MOUNTPOINT 6.) umount MOUNTPOINT (and anything under it) 7.) qemu-disconnect --disconnect $DEV I have assumed that 'umount' would block until all file descriptors are flushed to the backing /dev/nbd device, and that 'qemu-disconnect' would block until any writes already sent were written through to the backing file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741096 Title: test-mic can fail / writes to qemu-nbd device do not persist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1741096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)
** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739672 Title: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1739672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Hi...same problem...i format hdd after see the problem ...no boot from any usb...or pxe or cd..ni ubuntu ...no windows...pls help... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739525] Re: gnome-shell segfault at e8 in libgdk-3.so.0
Bah; after sleep + resume, my GDM login had the dreaded "constantly trying to press enter" problem on it ... (had this in Fedora long time ago ... can't remember how I fixed it) - anyway - had to CTRL+ALT+BACKSPACE to kill the gnome-shell and login again ... re- initiating gdb run -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739525 Title: gnome-shell segfault at e8 in libgdk-3.so.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728354] Re: ntfs: unsupported reparse point
hi Jean, any new advise / feedback you can share based on my feedback .. thanks & Happy New Year :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728354 Title: ntfs: unsupported reparse point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs