[Group.of.nepali.translators] [Bug 1649213] Re: Support rootfs on xhci-plat-hcd attached storage
This issue for linux is fix-committed in xenial yakkety and zesty. Delete affects package ** Changed in: initramfs-tools (Ubuntu Zesty) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: initramfs-tools (Ubuntu Xenial) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: initramfs-tools (Ubuntu Trusty) Assignee: (unassigned) => Ike Panhc (ikepanhc) ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1649213 Title: Support rootfs on xhci-plat-hcd attached storage Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools source package in Trusty: New Status in linux source package in Trusty: New Status in initramfs-tools source package in Xenial: New Status in linux source package in Xenial: New Status in initramfs-tools source package in Zesty: New Status in linux source package in Zesty: Incomplete Bug description: [Impact] If you install Ubuntu onto USB storage behind a Platform USB host controller, it will not be able to boot because the generated initramfs will not include the host controller driver. [Test Case] Install to a USB stick attached to platform USB controller and reboot. Booting will fail because it will be unable to find the root file system. [Regression Risk] Driver is only loaded when system requires xhci-plat-hcd, minimizing the impact to all other systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1649213/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1649361] Re: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1649361 Title: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.8.0-32.34~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1649358 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1649361/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1649361] Re: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1649361 Title: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.8.0-32.34~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1649358 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1649361/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1066406] Re: Installing to /usr/share/php/libzend-framework-php/Zend/ isn't the best idea
** Changed in: zend-framework (Ubuntu) Status: New => Invalid ** Changed in: zend-framework (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1066406 Title: Installing to /usr/share/php/libzend-framework-php/Zend/ isn't the best idea Status in zend-framework package in Ubuntu: Invalid Status in zend-framework source package in Xenial: In Progress Bug description: The libzend-framework-php package installs its files to /usr/share/php /libzend-framework-php/Zend/ This isn't a good idea, because PHP applications don't find it there (because of the .../libzend-framework-php/... subdirectory, which is not in the include_path) I know that the package also ships /etc/php5/conf.d/zend-framework.ini which would add this directory to the include_path - if the line wasn't commented out :-( If there isn't a very good reason for the subdirectory, why don't you just package the files into /usr/share/php/Zend/ ? This would avoid lots of problems ;-) Sidenotes: - this interesting[tm] packaging just caused a quite long debugging session with a user of PostfixAdmin (I'm upstream developer of it) - I checked the filelist on http://packages.ubuntu.com/precise/all/libzend-framework-php/filelist - personally, I'm using openSUSE ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zend-framework/+bug/1066406/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1574250] Re: icingaweb2 2.1.0 can't find Zend library
@lousigab: thanks for the quick response/testing! I'm uploading the
fixes now for SRU.
** Description changed:
+ [Impact]
+
+ * After running `apt install icingaweb2`, the icinga frontend does not
+ successfully load.
+
+ * The root cause of this issue is two-fold: 1) icingaweb2 only ships a
+ configuration for apache, but 16.04 defaults to php-fpm being used to
+ satsify the php dependency. [16.10 does not have this issue.] 2) zend-
+ framework installs to /usr/share/php/libzend-framework-php but the .ini
+ file that accompanies ships with the required include_path change
+ commented-out (due to an old bug now fixed in PHP5).
+
+ [Test Case]
+
+ * Install icingaweb2 and attempt to navigate to http:///icingaweb2.
+ A failing case will lead to the icinga login page not being displayed. A
+ working case will display the login page.
+
+ [Regression Potential]
+
+ * The icingaweb2 change is low in regression, as it only changes the
+ dependencies for the package. If a user had installed php on 16.04 (and
+ thus got php-fpm), there will be an additional package installed such
+ that icingaweb2 now works -- this will be overhead if the user figured
+ out how to configure fpm to host icingaweb2, but that would be outside
+ the packaged conffiles.
+
+ * The zend-framework change is possibly higher risk, as it installs
+ files into a new path (directly into /usr/share/php rather than
+ /usr/share/php/libzend-framework-php). However, we also put in a symlink
+ for the old path pointing at /usr/share/php, in case anyone is using the
+ old path explicitly in their code, which seems like the likeliest
+ regression source.
+
+ ---
+
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ apt-cache policy icingaweb2
icingaweb2:
- Installed: 2.1.0-1ubuntu1
- Candidate: 2.1.0-1ubuntu1
- Version table:
- *** 2.1.0-1ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
- 500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
- 100 /var/lib/dpkg/status
+ Installed: 2.1.0-1ubuntu1
+ Candidate: 2.1.0-1ubuntu1
+ Version table:
+ *** 2.1.0-1ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
+ 500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
+ 100 /var/lib/dpkg/status
I've installed Ubuntu 16.04 from the latest ISO and did a "apt update && apt
upgrade" to be certain I use the latest updates.
Then I've installed icingaweb2 via "sudo apt install icingaweb2":
What was still missing after that was mod-php (the issue was a white
page when browsing http:///icingaweb2/). Thus, to get it
working I had to run "sudo apt install libapache2-mod-php".
With that the white page has been resolved but then I got the following
error:
Warning: Uncaught ErrorException:
require_once(Zend/Loader/Autoloader.php): failed to open stream: No such file
or directory in /usr/share/php/Icinga/Application/ClassLoader.php:276
Stack trace:
#0 /usr/share/php/Icinga/Application/ClassLoader.php(276):
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}(2,
'require_once(Ze...', '/usr/share/php/...', 276, Array)
#1 /usr/share/php/Icinga/Application/ClassLoader.php(276): require_once()
#2 /usr/share/php/Icinga/Application/ClassLoader.php(294):
Icinga\Application\ClassLoader->requireZendAutoloader()
#3 [internal function]:
Icinga\Application\ClassLoader->loadClass('Zend_Controller...')
#4 /usr/share/php/Icinga/Web/Request.php(13):
spl_autoload_call('Zend_Controller...')
#5 /usr/share/php/Icinga/Application/ClassLoader.php(301):
require('/usr/share/php/...')
#6 [internal function]:
Icinga\Application\ClassLoader->loadClass('Icinga\\Web\\Requ...')
#7 /usr/share/php/Icinga/Application/EmbeddedWeb.php(82):
spl_autoload_call('Icinga\\Web\\Requ...')
#8 /usr/ in /usr/share/php/Icinga/Application/ClassLoader.php on line
276
Fatal error: Icinga\Application\ClassLoader::requireZendAutoloader():
Failed opening required 'Zend/Loader/Autoloader.php'
(include_path='/usr/share/icingaweb2/library/vendor:.:/usr/share/php') in
/usr/share/php/Icinga/Application/ClassLoader.php on line 276
The error is reproducible on all servers that I've tried so far
(installed from scratch or updated from 14.04 LTS to 16.04 LTS).
When I manually add "/usr/share/php/libzend-framework-php" to the
"include_path" I can get rid of the error but then I'm stuck with the
error described in
https://bugs.launchpad.net/ubuntu/+source/icingaweb2/+bug/1571402
** No longer affects: icingaweb2 (Ubuntu Yakkety)
** Description changed:
[Impact]
* After running `apt install icingaweb2`, the icinga frontend does not
successfully load.
* The root cause of this issue is two-fold: 1) icingaweb2 only ships a
configuration for apache, but 16.04 defaults to php-fpm being used to
satsify the php depende
[Group.of.nepali.translators] [Bug 1649361] Re: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1649361 Title: linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.8.0-32.34~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1649358 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1649361/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1647708] Re: Ephemeral disk on xenial is not mounted at boot
** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Critical ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Medium => High ** Description changed: When I boot the latest xenial Azure image (containing cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end up mounted (though it is formatted appropriately). Restarting the mnt.mount service does mount it, which suggests there is an issue in the ordering of the services at boot. $ mount | grep mnt - $ sudo systemctl status mnt.mount + $ sudo systemctl status mnt.mount ● mnt.mount - /mnt -Loaded: loaded (/etc/fstab; bad; vendor preset: enabled) -Active: inactive (dead) - Where: /mnt - What: /dev/disk/cloud/azure_resource-part1 - Docs: man:fstab(5) -man:systemd-fstab-generator(8) - $ sudo journalctl -u mnt.mount + Loaded: loaded (/etc/fstab; bad; vendor preset: enabled) + Active: inactive (dead) + Where: /mnt + What: /dev/disk/cloud/azure_resource-part1 + Docs: man:fstab(5) + man:systemd-fstab-generator(8) + $ sudo journalctl -u mnt.mount -- No entries -- - $ cat /etc/fstab + $ cat /etc/fstab # CLOUD_IMG: This file was created/modified by the Cloud Image build process UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34 /ext4 defaults,discard0 0 /dev/disk/cloud/azure_resource-part1 /mntauto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2 $ sudo systemctl restart mnt.mount $ mount | grep mnt /dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered) $ ls /mnt/ lost+found - $ sudo systemctl status mnt.mount + $ sudo systemctl status mnt.mount ● mnt.mount - /mnt -Loaded: loaded (/etc/fstab; bad; vendor preset: enabled) -Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago - Where: /mnt - What: /dev/sdb1 - Docs: man:fstab(5) -man:systemd-fstab-generator(8) - Process: 1916 ExecMount=/bin/mount /dev/disk/cloud/azure_resource-part1 /mnt -o defaults,x-systemd.requires=cloud-init.service,comment=cloudconfig (code=exited, status=0/SUCCESS) - Tasks: 0 -Memory: 88.0K - CPU: 15ms + Loaded: loaded (/etc/fstab; bad; vendor preset: enabled) + Active: active (mounted) since Tue 2016-12-06 12:49:06 UTC; 6s ago + Where: /mnt + What: /dev/sdb1 + Docs: man:fstab(5) + man:systemd-fstab-generator(8) + Process: 1916 ExecMount=/bin/mount /dev/disk/cloud/azure_resource-part1 /mnt -o defaults,x-systemd.requires=cloud-init.service,comment=cloudconfig (code=exited, status=0/SUCCESS) + Tasks: 0 + Memory: 88.0K + CPU: 15ms Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounting /mnt... Dec 06 12:49:06 xenial-161206-1345 systemd[1]: Mounted /mnt. + + Related bugs: + * bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM + * bug 1642383: Unable to configure swap space on ephemeral disk in Azure -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1647708 Title: Ephemeral disk on xenial is not mounted at boot Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Bug description: When I boot the latest xenial Azure image (containing cloud-init 0.7.8-49-g9e904bb-0ubuntu1~16.04.1), the ephemeral disk does not end up mounted (though it is formatted appropriately). Restarting the mnt.mount service does mount it, which suggests there is an issue in the ordering of the services at boot. $ mount | grep mnt $ sudo systemctl status mnt.mount ● mnt.mount - /mnt Loaded: loaded (/etc/fstab; bad; vendor preset: enabled) Active: inactive (dead) Where: /mnt What: /dev/disk/cloud/azure_resource-part1 Docs: man:fstab(5) man:systemd-fstab-generator(8) $ sudo journalctl -u mnt.mount -- No entries -- $ cat /etc/fstab # CLOUD_IMG: This file was created/modified by the Cloud Image build process UUID=6a8554fa-8e1d-4916-ba03-4ca3837feb34 /ext4 defaults,discard0 0 /dev/disk/cloud/azure_resource-part1 /mntauto defaults,nofail,x-systemd.requires=cloud-init.service,comment=cloudconfig 0 2 $ sudo systemctl restart mnt.mount $ mount | grep mnt /dev/sdb1 on /mnt type ext4 (rw,relatime,data=ordered) $ ls /mnt/ lost+found $ sudo systemctl status mnt.mount ● mnt.mount - /mnt Loaded: loaded (/etc/fstab; bad; vendor preset:
[Group.of.nepali.translators] [Bug 1502173] Re: Python warnings: modules imported without specifying a version first
Just to prevent more bug reports about this we might as well fix it in
16.04.
** Also affects: apport (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: apport (Ubuntu Xenial)
Status: New => Triaged
** Changed in: apport (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.2
** Changed in: apport (Ubuntu Xenial)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1502173
Title:
Python warnings: modules imported without specifying a version first
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Xenial:
Triaged
Bug description:
Hi,
here is the problem:
$ /usr/share/apport/apport-gtk
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
/usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without
specifying a version first. Use gi.require_version('GdkX11', '3.0') before
import to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: apport-gtk 2.19-0ubuntu1
Uname: Linux 4.2.2-040202-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Oct 2 16:17:14 2015
EcryptfsInUse: Yes
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1502173/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1646253] Re: I am getting frequent DRM hangs while playing Cities: Skylines from Steam
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Zesty) Importance: Medium Status: Triaged ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) Status: New => Triaged ** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Medium ** Tags added: yakkety zesty -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1646253 Title: I am getting frequent DRM hangs while playing Cities: Skylines from Steam Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Yakkety: Triaged Status in linux source package in Zesty: Triaged Bug description: It happens during normal gameplay. Have tried reducing settings. Seems like a legitimate driver bug. The program crashes, but X does not. [16868.151225] [drm] stuck on render ring [16868.155458] [drm] GPU HANG: ecode 8:0:0x84dffefc, in Cities.x64 [21076], reason: Ring hung, action: reset [16868.155472] [ cut here ] [16868.155503] WARNING: CPU: 1 PID: 13959 at /build/linux-j9zxaP/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11311 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]() [16868.155505] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips)) [16868.155506] Modules linked in: [16868.155508] tcp_diag inet_diag hid_microsoft hid_generic snd_usb_audio usbhid hid snd_usbmidi_lib usb_serial_simple usbserial ctr ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 ipt_REJECT nf_reject_ipv4 xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rfcomm aufs bnep arc4 iwlmvm uvcvideo mac80211 videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 intel_rapl videobuf2_core x86_pkg_temp_thermal v4l2_common intel_powerclamp cdc_mbim snd_hda_codec_hdmi coretemp cdc_wdm snd_hda_codec_realtek snd_hda_codec_generic cdc_ncm videodev joydev iwlwifi [16868.155545] input_leds cdc_acm btusb usbnet serio_raw media btrtl snd_hda_intel mii btbcm rtsx_pci_ms thinkpad_acpi snd_hda_codec btintel memstick snd_hda_core cfg80211 bluetooth snd_hwdep snd_seq_midi snd_seq_midi_event intel_pch_thermal nvram snd_rawmidi lpc_ich snd_pcm mei_me mei shpchp snd_seq snd_seq_device snd_timer snd soundcore kvm_intel mac_hid kvm irqbypass parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt rtsx_pci fb_sys_fops ahci psmouse ptp drm libahci pps_core wmi fjes video [16868.155589] CPU: 1 PID: 13959 Comm: kworker/1:0 Tainted: GW OE 4.4.0-51-generic #72-Ubuntu [16868.155591] Hardware name: LENOVO 20CLS5N900/20CLS5N900, BIOS N10ET36W (1.15 ) 06/19/2015 [16868.155617] Workqueue: events intel_mmio_flip_work_func [i915] [16868.155619] 0286 dd043c13 880382bbbd20 813f5fc3 [16868.155622] 880382bbbd68 c03a7ab8 880382bbbd58 810812b2 [16868.155624] 8802970af040 88042dc56500 88042dc5ae00 0040 [16868.155626] Call Trace: [16868.155632] [] dump_stack+0x63/0x90 [16868.155637] [] warn_slowpath_common+0x82/0xc0 [16868.155639] [] warn_slowpath_fmt+0x5c/0x80 [16868.155643] [] ? __switch_to+0x437/0x5c0 [16868.155667] [] intel_mmio_flip_work_func+0x38e/0x3d0 [i915] [16868.155672] [] process_one_work+0x165/0x480 [16868.155674] [] worker_thread+0x4b/0x4c0 [16868.155677] [] ? process_one_work+0x480/0x480 [16868.155679] [] kthread+0xd8/0xf0 [16868.155681] [] ? kthread_create_on_node+0x1e0/0x1e0 [16868.155685] [] ret_from_fork+0x3f/0x70 [16868.155687] [] ? kthr
[Group.of.nepali.translators] [Bug 1574250] Re: icingaweb2 2.1.0 can't find Zend library
** Changed in: icingaweb2 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: zendframework (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1574250
Title:
icingaweb2 2.1.0 can't find Zend library
Status in icingaweb2 package in Ubuntu:
Fix Released
Status in zend-framework package in Ubuntu:
Invalid
Status in zendframework package in Ubuntu:
Fix Released
Status in icingaweb2 source package in Xenial:
New
Status in zend-framework source package in Xenial:
New
Status in icingaweb2 source package in Yakkety:
New
Status in zend-framework source package in Yakkety:
New
Bug description:
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
$ apt-cache policy icingaweb2
icingaweb2:
Installed: 2.1.0-1ubuntu1
Candidate: 2.1.0-1ubuntu1
Version table:
*** 2.1.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
100 /var/lib/dpkg/status
I've installed Ubuntu 16.04 from the latest ISO and did a "apt update && apt
upgrade" to be certain I use the latest updates.
Then I've installed icingaweb2 via "sudo apt install icingaweb2":
What was still missing after that was mod-php (the issue was a white
page when browsing http:///icingaweb2/). Thus, to get it
working I had to run "sudo apt install libapache2-mod-php".
With that the white page has been resolved but then I got the
following error:
Warning: Uncaught ErrorException:
require_once(Zend/Loader/Autoloader.php): failed to open stream: No such file
or directory in /usr/share/php/Icinga/Application/ClassLoader.php:276
Stack trace:
#0 /usr/share/php/Icinga/Application/ClassLoader.php(276):
Icinga\Application\ApplicationBootstrap->Icinga\Application\{closure}(2,
'require_once(Ze...', '/usr/share/php/...', 276, Array)
#1 /usr/share/php/Icinga/Application/ClassLoader.php(276): require_once()
#2 /usr/share/php/Icinga/Application/ClassLoader.php(294):
Icinga\Application\ClassLoader->requireZendAutoloader()
#3 [internal function]:
Icinga\Application\ClassLoader->loadClass('Zend_Controller...')
#4 /usr/share/php/Icinga/Web/Request.php(13):
spl_autoload_call('Zend_Controller...')
#5 /usr/share/php/Icinga/Application/ClassLoader.php(301):
require('/usr/share/php/...')
#6 [internal function]:
Icinga\Application\ClassLoader->loadClass('Icinga\\Web\\Requ...')
#7 /usr/share/php/Icinga/Application/EmbeddedWeb.php(82):
spl_autoload_call('Icinga\\Web\\Requ...')
#8 /usr/ in /usr/share/php/Icinga/Application/ClassLoader.php on line
276
Fatal error: Icinga\Application\ClassLoader::requireZendAutoloader():
Failed opening required 'Zend/Loader/Autoloader.php'
(include_path='/usr/share/icingaweb2/library/vendor:.:/usr/share/php') in
/usr/share/php/Icinga/Application/ClassLoader.php on line 276
The error is reproducible on all servers that I've tried so far
(installed from scratch or updated from 14.04 LTS to 16.04 LTS).
When I manually add "/usr/share/php/libzend-framework-php" to the
"include_path" I can get rid of the error but then I'm stuck with the
error described in
https://bugs.launchpad.net/ubuntu/+source/icingaweb2/+bug/1571402
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icingaweb2/+bug/1574250/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1630238] Re: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1630238 Title: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11 Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: 16.10 beta 2, as installed fresh, has working keyboard and touchscreen on my Acer Chromebook R11. However, after dist-upgrade they're lost, so touchscreen doesn't work and I need to use external keyboard. Looking at config diff, the likely culprit is: +CONFIG_PINCTRL_AMD=y CONFIG_PINCTRL_BAYTRAIL=y -CONFIG_PINCTRL_CHERRYVIEW=y -CONFIG_PINCTRL_INTEL=y -CONFIG_PINCTRL_BROXTON=y -CONFIG_PINCTRL_SUNRISEPOINT=y +CONFIG_PINCTRL_CHERRYVIEW=m +CONFIG_PINCTRL_INTEL=m +CONFIG_PINCTRL_BROXTON=m +CONFIG_PINCTRL_SUNRISEPOINT=m As indicated at https://github.com/GalliumOS/galliumos- distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.". So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to m instead of y causes at least the touchscreen regression, and probably the keyboard one too. --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timo 1922 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/21/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630238/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1649330] Re: [SRU] bubblewrap unavailable on xenial
** Also affects: bubblewrap (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1649330 Title: [SRU] bubblewrap unavailable on xenial Status in bubblewrap package in Ubuntu: New Status in bubblewrap source package in Xenial: New Bug description: [Impact] I'm writing a snapcraft plugin that uses bubblewrap for sandboxing purposes, but since bubblewrap isn't available on xenial while snapcraft is, it's currently blocked from landing. Besides that, bubblewrap is a generally useful tool for running commands in a sandbox, similar to a chroot, but can be run by an unprivileged user, or like lxc, but more lightweight. [Test Case] Type bwrap in a xenial terminal. The command isn't found. [Regression Potential] This package is already available in yakkety and zesty, and it depends only on libc6 and libselinux1. It contains no services. The bwrap binary is setuid root. [Other Info] From the project page: "The maintainers of this tool believe that it does not, even when used in combination with typical software installed on that distribution, allow privilege escalation. It may increase the ability of a logged in user to perform denial of service attacks, however. In particular, bubblewrap uses PR_SET_NO_NEW_PRIVS to turn off setuid binaries, which is the traditional way to get out of things like chroots." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1649330/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1579609] Re: os-prober bug resulting in possible FS corruption
This bug was fixed in the package os-prober - 1.70ubuntu4 --- os-prober (1.70ubuntu4) zesty; urgency=medium * Fixing FS probes in os-probes/common/50mounted-tests (LP: #1579609). -- Eric Desrochers Tue, 06 Dec 2016 10:02:36 -0500 ** Changed in: os-prober (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1579609 Title: os-prober bug resulting in possible FS corruption Status in os-prober package in Ubuntu: Fix Released Status in os-prober source package in Xenial: In Progress Bug description: [Impact] This bug generate some warnings in system log and in some cases it also might cause FS corruption as seen with a user using MySQL for his Openstack env. [Test Case] As of today, there is 3 reported way to reproduce the problem so far : #1 Reboot system $ sudo update-grub then check the log again: $ journalctl -p err -b -k --no-pager #2 Placing a VM under IO load (basically just ran dd if=/dev/vda of=/dev/null) and then ran update-grub on the hypervisor host. #3 Simply run: os-prober, on an hypervisor some VM with LVM storage backend. [Regression Potential] none expected A test package has been tested by several users experiencing the issue, and positives feedbacks has been provided in all cases. [Other Info] Workaround: - Disable os-prober - Uninstall os-prober Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788062 (Merged 648208 788062 806273 810121) Debian Patch: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=806273;filename=v2-0001-use-grub-mount-as-the-sole-source-of-partition-pr.patch;msg=30 [Original Description] According to this it should be fixed https://bugs.launchpad.net/ubuntu/+source/os- prober/+bug/1374759/comments/32 But on my system I intended to install on /dev/sdb1 and noticed these warning message in my system log. Steps to reproduce: 1. reboot system 2. $ sudo update-grub then check the log again: $ journalctl -p err -b -k --no-pager -- Logs begin at Sun 2016-05-08 10:47:49 CST, end at Mon 2016-05-09 11:42:04 CST. -- May 08 10:47:50 X230 kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A May 08 10:47:50 X230 kernel: [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun May 08 10:55:34 X230 kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem May 08 10:55:34 X230 kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem May 08 10:55:34 X230 kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem May 08 10:55:34 X230 kernel: FAT-fs (sdb1): invalid media value (0x7d) May 08 10:55:34 X230 kernel: squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sdb1 May 08 10:55:34 X230 kernel: FAT-fs (sdb1): invalid media value (0x7d) May 08 10:55:34 X230 kernel: qnx4: no qnx4 filesystem (no root dir). May 08 10:55:34 X230 kernel: ufs: You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep- cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old May 08 10:55:34 X230 kernel: ufs: ufs_fill_super(): bad magic number May 08 10:55:34 X230 kernel: EXT4-fs (sdb4): VFS: Can't find ext4 filesystem May 08 10:55:34 X230 kernel: EXT4-fs (sdb4): VFS: Can't find ext4 filesystem May 08 10:55:34 X230 kernel: EXT4-fs (sdb4): VFS: Can't find ext4 filesystem May 08 10:55:34 X230 kernel: FAT-fs (sdb4): bogus number of reserved sectors May 08 10:55:34 X230 kernel: squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sdb4 May 08 10:55:34 X230 kernel: FAT-fs (sdb4): bogus number of reserved sectors May 08 10:55:34 X230 kernel: qnx4: no qnx4 filesystem (no root dir). May 08 10:55:34 X230 kernel: ufs: You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep- cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old May 08 10:55:34 X230 kernel: ufs: ufs_fill_super(): bad magic number May 08 10:55:52 X230 kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem May 08 10:55:52 X230 kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem May 08 10:55:52 X230 kernel: EXT4-fs (sdb1): VFS: Can't find ext4 filesystem May 08 10:55:52 X230 kernel: FAT-fs (sdb1): invalid media value (0x7d) May 08 10:55:52 X230 kernel: squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sdb1 May 08 10:55:52 X230 kernel: FAT-fs (sdb1): invalid media value (0x7d) May 08
[Group.of.nepali.translators] [Bug 1647467] Re: InRelease file splitter treats getline() errors as EOF
This bug was fixed in the package apt - 1.0.1ubuntu2.17 --- apt (1.0.1ubuntu2.17) trusty-security; urgency=high * SECURITY UPDATE: gpgv: Check for errors when splitting files (CVE-2016-1252) Thanks to Jann Horn, Google Project Zero for reporting the issue (LP: #1647467) -- Julian Andres Klode Thu, 08 Dec 2016 15:31:29 +0100 ** Changed in: apt (Ubuntu Trusty) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1647467 Title: InRelease file splitter treats getline() errors as EOF Status in apt package in Ubuntu: Fix Committed Status in apt source package in Trusty: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Yakkety: Fix Released Status in apt source package in Zesty: Fix Committed Bug description: We have just been made aware of a security bug upstream that affects the validation of signatures on InRelease file. This bug is to track progress for it. It allows for attacking a repository via MITM attacks, circumventing the signature of the InRelease file. It works by making a call to getline() fail with ENOMEM, which is not documented as an error for that but follows from the fact that getline() can allocate memory. In such a case, apt would treat the first part of the file as a valid release file. = Original bug report = From: Jann Horn To: secur...@debian.org Cc: Date: Mon, 5 Dec 2016 18:33:09 +0100 Subject: apt: repository signing bypass via memory allocation failure == Vulnerability == When apt-get updates a repository that uses an InRelease file (clearsigned Release files), this file is processed as follows: First, the InRelease file is downloaded to disk. In a subprocess running the gpgv helper, "apt-key verify" (with some more arguments) is executed through the following callchain: gpgv.cc:main -> pkgAcqMethod::Run -> GPGVMethod::URIAcquire -> GPGVMethod::VerifyGetSigners -> ExecGPGV ExecGPGV() splits the clearsigned file into payload and signature using SplitClearSignedFile(), calls apt-key on these two files to perform the cryptographic signature verification, then discards the split files and only retains the clearsigned original. SplitClearSignedFile() ignores leading and trailing garbage. Afterwards, in the parent process, the InRelease file has to be loaded again so that its payload can be processed. At this point, the code isn't aware anymore whether the Release file was clearsigned or split-signed, so the file is opened using OpenMaybeClearSignedFile(), which first attempts to parse the file as a clearsigned (InRelease) file and extract the payload, then falls back to treating the file as the file as a split-signed (Release) file if the file format couldn't be recognized. The weakness here is: If an attacker can create an InRelease file that is parsed as a proper split-signed file during signature validation, but then isn't recognized by OpenMaybeClearSignedFile(), the "leading garbage" that was ignored by the signature validation is interpreted as repository metadata, bypassing the signing scheme. It first looks as if it would be impossible to create a file that is recognized as split-signed by ExecGPGV(), but isn't recognized by OpenMaybeClearSignedFile(), because both use the same function, SplitClearSignedFile(), for parsing the file. However, multiple executions of SplitClearSignedFile() on the same data can actually have different non-error results because of a bug. SplitClearSignedFile() uses getline() to parse the input file. A return code of -1, which signals that either EOF or an error occured, is always treated as EOF. The Linux manpage only lists EINVAL (caused by bad arguments) as possible error code, but because the function allocates (nearly) unbounded amounts of memory, it can actually also fail with ENOMEM if it runs out of memory. Therefore, if an attacker can cause the address space in the main apt-get process to be sufficiently constrained to prevent allocation of a large line buffer while the address space of the gpgv helper process is less constrained and permits the allocation of a buffer with the same size, the attacker can use this to fake an end-of-file condition in SplitClearSignedFile() that causes the file to be parsed as a normal Release file. A very crude way to cause such a constraint on a 32-bit machine is based on abusing ASLR. Because ASLR randomizes the address space after each execve(), thereby altering how much contiguous virtual memory is available, an allocation that attempts to use the average available virtual memory should ideally succeed 50% of the time, resulting in an upper limit of 25% for the success rate of the whole
[Group.of.nepali.translators] [Bug 1641678] Re: rename password file to consistent name
This is now fixed in zesty, but missed the changelog entry. 0.33ubuntu1 should have said: * overlayroot: change name of password file from randomly generated filename /run/initramfs/overlayroot.XX to /run/initramfs/overlayroot.passwd (LP: #1641678). ** Changed in: cloud-initramfs-tools (Ubuntu Zesty) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1641678 Title: rename password file to consistent name Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in cloud-initramfs-tools source package in Xenial: Confirmed Status in cloud-initramfs-tools source package in Zesty: Fix Released Bug description: When overlayroot is used with config of: overlayroot=crypt:dev=/dev/vdc,debug=1,mkfs=1 Then the password that is used for the mount is recorded to a file in in /run/initramfs (or /dev/.initramfs on older initramfs-tools). The file name is currently: overlayroot.XX where the 'XX' is random as it is the result of mktemp overlayroot.XX There doesn't seem to be any value in having that filename be random. Some things to note: a.) file is on a tmpfs (initially created in the initramfs and then moved with the pivot) b.) file does (and should) have root:root permissions and 0600 It seems a general better idea to make that /run/initramfs/overlayroot.passwd ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: overlayroot 0.31ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 14 12:28:29 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (480 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) PackageArchitecture: all SourcePackage: cloud-initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1641678/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1642383] Re: Unable to configure swap space on ephemeral disk in Azure
This is currently fixed in cloud-init in zesty 0.7.8-67-gc9c9197-0ubuntu1 . I've verified it functional with the user-data provided in the description on todays Azure image. ** Changed in: cloud-init (Ubuntu Zesty) Status: Confirmed => Fix Released ** Description changed: I'm following the instructions to send cloud-config and repartition the ephemeral disk in Azure: https://wiki.ubuntu.com/AzureSwapPartitions. These instructions fail on Ubuntu 14.04 and 16.04 (did not test 12.04 yet). Repro: 1) Add the following content to a file such as customdata.txt: #cloud-config disk_setup: ephemeral0: table_type: mbr layout: [66, [33, 82]] overwrite: True fs_setup: - device: ephemeral0.1 filesystem: ext4 - device: ephemeral0.2 filesystem: swap mounts: - ["ephemeral0.1", "/mnt2"] - ["ephemeral0.2", "none", "swap", "sw", "0", "0"] 2) Create a VM in Azure with this cloud-config: $ azure group create ubtest 'east us' $ azure vm create ubtest ubtest-1604 Linux --image-urn canonical:UbuntuServer:16.04.0-LTS:latest --admin-username azureuser --admin-password '' --nic-name ubtest-1604 --location "East US" --vnet-name "ubtest" --vnet-address-prefix "10.0.0.0/24" --vnet- subnet-name "ubtest" --vnet-subnet-address-prefix "10.0.0.0/24" --public-ip-name "ubtest" --public-ip-domain-name "ubtest" --custom-data ./customdata.txt Expected Result: - /dev/disk/cloud/azure_resource should have two partitions; one ext4 and a second swap - /dev/disk/cloud/azure_resource-part1 should be mounted on /mnt2 - /dev/disk/cloud/azure_resource-part2 should be active swap space - /etc/fstab should be configured correctly Actual Results: - /dev/disk/cloud/azure_resource-part1 is properly mounted on /mnt2. - On Ubuntu 14.04, /dev/disk/cloud/azure_resource is re-partitioned as expected. - On Ubuntu 16.04, /dev/disk/cloud/azure_resource is *not* re-partitioned. There is only a single partition (no swap space). - On Ubuntu 14.04 and 16.04, /etc/fstab includes an incorrect entry for the swap space: ephemeral0.2noneswapsw,comment=cloudconfig 0 0 This clearly won't work, it should resolve to "/dev/disk/cloud /azure_resource-part2". I do notice that on Ubuntu 14.04, the ephemeral disk is re-partitioned correctly, but there is no symlink in /dev/disk/azure/ to the second partition. These symlinks are created by /lib/udev/rules.d/66-azure-ephemeral.rules. Perhaps cloud-init needs to re-trigger this udev rule after repartitioning the disk. FYI, I also tested with the latest cloud-init that is currently in xenial-proposed (0.7.8-47-gb6561a1-0ubuntu1~16.04.1) with the same results. Related bugs: - * bug 1460715: MBR disk setup fails because sfdisk no longer accepts M as a valid unit + * bug 1460715: MBR disk setup fails because sfdisk no longer accepts M as a valid unit + * bug 1647708: azure ephemeral disk not mounted at boot -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1642383 Title: Unable to configure swap space on ephemeral disk in Azure Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Fix Released Bug description: I'm following the instructions to send cloud-config and repartition the ephemeral disk in Azure: https://wiki.ubuntu.com/AzureSwapPartitions. These instructions fail on Ubuntu 14.04 and 16.04 (did not test 12.04 yet). Repro: 1) Add the following content to a file such as customdata.txt: #cloud-config disk_setup: ephemeral0: table_type: mbr layout: [66, [33, 82]] overwrite: True fs_setup: - device: ephemeral0.1 filesystem: ext4 - device: ephemeral0.2 filesystem: swap mounts: - ["ephemeral0.1", "/mnt2"] - ["ephemeral0.2", "none", "swap", "sw", "0", "0"] 2) Create a VM in Azure with this cloud-config: $ azure group create ubtest 'east us' $ azure vm create ubtest ubtest-1604 Linux --image-urn canonical:UbuntuServer:16.04.0-LTS:latest --admin-username azureuser --admin-password '' --nic-name ubtest-1604 --location "East US" --vnet-name "ubtest" --vnet-address-prefix "10.0.0.0/24" --vnet- subnet-name "ubtest" --vnet-subnet-address-prefix "10.0.0.0/24" --public-ip-name "ubtest" --public-ip-domain-name "ubtest" --custom- data ./customdata.txt Expected Result: - /dev/disk/cloud/azure_resource should have two partitions; one ext4 and a second swap - /dev/disk/cloud/azure_resource-part1 should be mounted on /mnt2 - /
[Group.of.nepali.translators] [Bug 1621340] Re: [SRU]'multipath -r' causes /dev/mapper/ being removed
** Also affects: multipath-tools (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1621340
Title:
[SRU]'multipath -r' causes /dev/mapper/ being removed
Status in multipath-tools package in Ubuntu:
In Progress
Status in multipath-tools source package in Xenial:
In Progress
Status in multipath-tools source package in Yakkety:
New
Bug description:
[Impact]
"multipath -r" causes the /dev/mapper/ to disappear momentarily,
which leads to some issue in consumer applications as such OpenStack.
[Test Case]
* connect to an multipath iscsi target
* multipath -r
* /dev/mapper/ disappears momentarily
[Regression Potential]
* None
"multipath -r" causes the /dev/mapper/ to disappear momentarily, which
leads to some issue in consumer applications as such OpenStack. After some
investigation, I found that /dev/mapper/ was deleted by udev during the
reload, and it was re-created soon later by multipathd (livdevmapper code of
cause). Detailed findings are as follows:
For reload in domap (rename as well),
case ACT_RELOAD:
r = dm_addmap_reload(mpp, params);
if (r)
r = dm_simplecmd_noflush(DM_DEVICE_RESUME, mpp->alias,
0, MPATH_UDEV_RELOAD_FLAG);
break;
it passes 0 to dm_simplecmd_noflush as argument for needsync, which
makes dm_task_set_cookie call being skipped in dm_simplecmd,
if (udev_wait_flag && !dm_task_set_cookie(dmt, &cookie,
((conf->daemon)? DM_UDEV_DISABLE_LIBRARY_FALLBACK : 0) | udev_flags)) {
dm_udev_complete(cookie);
goto out;
}
because of the short-circuit evaluation. Thus _do_dm_ioctl in
libdevmapper will add DM_UDEV_DISABLE_DM_RULES_FLAG flag to
dmi->event_nr, and that will eventually be used in the udev rules
(55-dm.rules),
ENV{DM_UDEV_DISABLE_DM_RULES_FLAG}!="1", ENV{DM_NAME}=="?*",
SYMLINK+="mapper/$env{DM_NAME}"
Since the DM_UDEV_DISABLE_DM_RULES_FLAG is set, the rule will not
match. As a result the link is removed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1577460] Re: mkinitramfs --help > Core dumped
** Changed in: ubuntu-z-systems Status: Fix Released => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1577460 Title: mkinitramfs --help > Core dumped Status in Ubuntu on IBM z Systems: In Progress Status in glibc package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: New Status in glibc source package in Xenial: Fix Released Status in util-linux source package in Xenial: New Bug description: Problem Description == root@zlin060:~# mkinitramfs --help Segmentation fault (core dumped) W: non-GNU getopt root@zlin060:~# == Comment: #9 - Heinz-Werner Seeck - 2016-05-02 10:09:34 == With Ubuntu 14.40 login via ssh: Following cmd : 'getopt -o c:d:ko:r:v -n /usr/sbin/mkinitramfs -- --help' Following call-stack occured (creates coredump): #0 __strncmp_c (s1=0x2e6575634a500a6d , s1@entry=0x2e6575634a500a6a , s2=0x3fff7fff7ae "p", s2@entry=0x3fff7fff7ab "gelp", n=n@entry=4) at ../string/strncmp.c:44 #1 0x03ff7e9d4252 in _getopt_internal_r (argc=, argv=0x40, optstring=0x20030 , longopts=, longind=, long_only=0, d=0x3ff7ea8c330 , posixly_correct=0) at getopt.c:546 #2 0x03ff7e9d51f2 in _getopt_internal (argc=, argv=, optstring=, longopts=, longind=0x3fff7ffe674, long_only=0, posixly_correct=0) at getopt.c:1175 #3 0x03ff7e9d52b6 in getopt_long (argc=, argv=, options=, long_options=, opt_index=0x3fff7ffe674) at getopt1.c:65 #4 0x02aa236821d8 in ?? () #5 0x02aa23681c22 in main () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1577460/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
** Also affects: isc-dhcp (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: isc-dhcp (Ubuntu) Status: In Progress => Fix Released ** Changed in: isc-dhcp (Ubuntu Xenial) Status: New => Fix Released ** Changed in: isc-dhcp (Ubuntu Yakkety) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: In Progress Status in isc-dhcp source package in Xenial: Fix Released Status in isc-dhcp source package in Yakkety: Fix Released Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] * none expected I did the split such that users will automatically get isc-dhcp-client-ddns installed but users bothered by this bug then will have the option to switch to the one without it by uninstalling (isc-dhcp-client-ddns), so existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client-ddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port Without isc-dhcp-client-ddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Note that this is how Xenial does it. [Other Info] * See : https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to look at my discussion with rbasak on if that approach would be acceptable for SRU. [Original Description] Ubuntu 13.04 Server 64-bit. Fresh install. Only one network adapter. dhclient process is listening on two randomly chosen udp ports in addition to the usual port 68. This appears to be a bug in the discovery code for probing information on interfaces in the system. Initial research of the code also suggested omapi, but adding omapi port to /etc/dhcp/dhclient.conf only opened a forth port with the two random udp ports still enabled. Version of included distro dhclient was 4.2.4. I also tested with the latest isc-dhclient-4.2.5-P1 and got the same results. Debian has the same bug: http://forums.debian.net/viewtopic.php?f=10&t=95273&p=495605#p495605 One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown. Example netstat -lnp output: udp0 0 0.0.0.0:21117 0.0.0.0:* 2659/dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 2659/dhclient udp6 0 0 :::45664:::* 2659/dhclient To manage notif
[Group.of.nepali.translators] [Bug 1646195] Re: linux-hwe-edge: 4.8.0-29.31~16.04.1 -proposed tracker
*** This bug is a duplicate of bug 1649361 *** https://bugs.launchpad.net/bugs/1649361 ** This bug is no longer a duplicate of bug 1648038 linux-hwe-edge: 4.8.0-31.33~16.04.1 -proposed tracker ** This bug has been marked a duplicate of bug 1649361 linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1646195 Title: linux-hwe-edge: 4.8.0-29.31~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: Confirmed Status in Kernel SRU Workflow prepare-package-signed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.8.0-29.31~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true kernel-stable-master-bug: 1646194 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1646195/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1648038] Re: linux-hwe-edge: 4.8.0-31.33~16.04.1 -proposed tracker
*** This bug is a duplicate of bug 1649361 *** https://bugs.launchpad.net/bugs/1649361 ** This bug has been marked a duplicate of bug 1649361 linux-hwe-edge: 4.8.0-32.34~16.04.1 -proposed tracker -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1648038 Title: linux-hwe-edge: 4.8.0-31.33~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.8.0-31.33~16.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true kernel-stable-master-bug: 1648034 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1648038/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1578431] Re: tmux session in weird semi-zombie state
According to the comment "I have removed the backoff timer so this should be resolved in master." in https://github.com/tmux/tmux/issues/298 this should be fixed in 2.3, so zesty is fine. ** Bug watch added: github.com/tmux/tmux/issues #298 https://github.com/tmux/tmux/issues/298 ** Also affects: tmux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: tmux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: tmux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: tmux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: tmux (Ubuntu Xenial) Importance: Medium => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1578431 Title: tmux session in weird semi-zombie state Status in tmux package in Ubuntu: Fix Released Status in tmux source package in Xenial: Confirmed Bug description: Guys, The tmux version shipped on Ubuntu, freezes from time to time. Problem reported here: https://github.com/tmux/tmux/issues/298 Thanks, Thiago ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tmux 2.1-3build1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 4 20:07:53 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-30 (95 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130) SourcePackage: tmux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1578431/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1644022] Re: White Screen Black Screen Crash after Upgrade to Linux version 4.4.0-47-generic
Because the Problem was resolved under the same Kernel, i think it was *not* a Bug in the Linux-Kernel. As no contrary Answer followed, i closed as invalid. ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1644022 Title: White Screen Black Screen Crash after Upgrade to Linux version 4.4.0-47-generic Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This Bug is about Linux version 4.4.0-47-generic, NOT about Linux version 4.4.0-45-generic, which worked, so i could file this Bug-Report: > Terminal > ubuntu-bug linux (So there may appear the wrong Kernel-Version in the automatic Data) --- Description: After (in German: )> Aktualisierungsverwaltung > "Teilweise Systemaktualisierung" the System upgraded to Linux version 4.4.0-47-generic. Booting with this Kernel leads to a Screen with a brown and white Oval getting smaller within the black Frame. The System is totally crashed, CTRL+ALT+F2 does not work. I reproduced this Error. --- When i boot with Grub-2: "Erweiterte Optionen für Ubuntu" and chose one Kernel-Version down: "Ubuntu, mit Linux 4.4.0-45-generic" my System starts normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-45-generic 4.4.0-45.66 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin-user 1558 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 22 22:21:18 2016 HibernationDevice: RESUME=UUID=dd015f17-7b6c-4dfb-ac57-823edbd74f8c InstallationDate: Installed on 2015-04-13 (588 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Sony Corporation VGN-CR42S_P PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=fef1de2d-e465-46d6-8613-fbba6a7601d4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-45-generic N/A linux-backports-modules-4.4.0-45-generic N/A linux-firmware1.157.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R3040Q0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR3040Q0:bd02/27/2008:svnSonyCorporation:pnVGN-CR42S_P:pvrC102JR5R:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-CR42S_P dmi.product.version: C102JR5R dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644022/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1627656] Re: missing alembic migrations due to use of git based workflows
Reviewed: https://review.openstack.org/376381 Committed: https://git.openstack.org/cgit/openstack/tap-as-a-service/commit/?id=55a387744dacb837b92556d714d2b6b5bb6c0e4f Submitter: Jenkins Branch:master commit 55a387744dacb837b92556d714d2b6b5bb6c0e4f Author: James Page Date: Mon Sep 26 11:45:35 2016 +0100 Include alembic migrations in module Explicitly include all alembic data in installed python module, ensuring that installations directly from git repositories are fully functional when compared to use of sdist generated tarballs from tarballs.openstack.org or pypi. Closes-Bug: 1627656 Change-Id: I445481445b6b5c0649a95f775042ba4067e83aa3 ** Changed in: tap-as-a-service Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1627656 Title: missing alembic migrations due to use of git based workflows Status in networking-l2gw: New Status in networking-odl: Fix Released Status in networking-sfc: Fix Released Status in tap-as-a-service: Fix Released Status in networking-l2gw package in Ubuntu: Fix Released Status in networking-odl package in Ubuntu: Fix Released Status in neutron-taas package in Ubuntu: Fix Released Status in networking-l2gw source package in Xenial: New Status in networking-odl source package in Xenial: Triaged Status in neutron-taas source package in Xenial: Invalid Status in networking-l2gw source package in Yakkety: Fix Released Status in networking-odl source package in Yakkety: Fix Released Status in neutron-taas source package in Yakkety: Fix Released Bug description: Various openstack related packages are missing required neutron database migrations due to the direct use of a git based workflow of merging upstream tags and generating orig.tar.xz directly from the git tree for packaging. This is *not* the same process as generated a sdist tarball, and as a result, files that need to reside in the python module get missed - this includes alembic migrations. Known impacts: networking-odl vmware-nsx (bug 1574610) A simple fix is to switch to using the upstream published release artefacts, rather than directly using git. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-l2gw/+bug/1627656/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1640919] Re: pcs cluster setup hangs
This bug was fixed in the package pcs - 0.9.155-1ubuntu1
---
pcs (0.9.155-1ubuntu1) zesty; urgency=medium
* Patch d/p/0011-Find-on-specific-directories-only.patch (LP: #1640919)
Cleaning files when destroying a cluster was taking too long in /var/lib.
Specifying /var/lib/pacemaker for "finding" leftovers solves the issue.
-- Rafael David Tinoco Fri, 09 Dec 2016
03:33:30 +
** Changed in: pcs (Ubuntu Zesty)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1640919
Title:
pcs cluster setup hangs
Status in pcs package in Ubuntu:
Fix Released
Status in pcs source package in Xenial:
In Progress
Status in pcs source package in Yakkety:
In Progress
Status in pcs source package in Zesty:
Fix Released
Status in pcs package in Debian:
Fix Released
Bug description:
[Impact]
* PCS might take too much time when destroying a cluster.
* There is a look for leftovers over /var/lib/ using "find".
* If lxcfs is too big that might take awhile.
[Test Case]
* Install PCS
* Configure a pacemaker cluster using PCS
* Make sure /var/lib/ is huge
* Try to destroy the cluster using PCS
[Regression Potential]
* Purging leftovers could be affected.
* Almost none.
[Other Info]
Fixing together (same SRU):
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580035 (xenial)
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1580045 (xenial)
And this one (yakkety & zesty)
[Original Description]
PCS cluster setup hangs, apparently due to a "find" command attempting to
search through a fuse mountpoint directory (/var/lib/lxcfs/*).
->%-
lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
-%<-
apt-cache policy pcs
pcs:
Installed: 0.9.149-1
Candidate: 0.9.149-1
Version table:
*** 0.9.149-1 500
->%-
PCS cluster setup hangs when cleaning up old cluster configurations,
apparently due to a "find" command attempting to search through a fuse
mountpoint directory (/var/lib/lxcfs/*).
sudo pcs cluster setup --name jmclus1 uby2 uby3
Destroying cluster on nodes: uby2, uby3...
uby2: Stopping Cluster (pacemaker)...
uby3: Stopping Cluster (pacemaker)...
---setup hangs here
The setup seems to hang because of this line in /usr/lib/python2.7
/dist-packages/pcs/cluste r.py (which attempts to delete stale cluster
configuration xml files:
os.system("find /var/lib -name '"+name+"' -exec rm -f \{\} \;")
sudo find /var/lib -name 'cib-*' 2>&1 | grep 'Permission denied' | wc -l
426
Changing this line to:
os.system("find /var/lib/pacemaker -name '"+name+"' -exec rm -f \{\} \;") to
avoid searching under /var/lib/lxcfs (the fuse mountpoint) provided a
workaround for me.
sosreport-J.Meisel.1640923-20161115104001.tar.xz -- this is an
sosreport from before installing pcs / pacemaker / corosync
sosreport-J.Meisel.1640919-20161115105845.tar.xz -- this is an
sosreport while pcs cluster setup hung
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1640919/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Bug watch added: Linux Kernel Bug Tracker #190221 http://bugzilla.kernel.org/show_bug.cgi?id=190221 ** Also affects: kernel via http://bugzilla.kernel.org/show_bug.cgi?id=190221 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in linux: Unknown Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Vivid: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1619918/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
