[Group.of.nepali.translators] [Bug 1750794] Re: eigen3-dev crashes because unstable
** Also affects: eigen3 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: eigen3 (Ubuntu)
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/1750794
Title:
eigen3-dev crashes because unstable
Status in eigen3 package in Ubuntu:
Fix Released
Status in eigen3 source package in Xenial:
New
Bug description:
Description: Ubuntu 16.04.3 LTS
Release: 16.04
libeigen3-dev:
Installed: 3.3~beta1-2
Candidate: 3.3~beta1-2
Version table:
*** 3.3~beta1-2 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
The official version shipped with Ubuntu 16.04 LTS is an unstable branch of
Eigen 3.3 (i.e. Eigen 3.3-beta1)
This is very inconvenient for a LTS version of Ubuntu, considering
that even the following simple code gives SEGFAULT:
#include
#include
using namespace std;
using namespace Eigen;
int main()
{
Eigen::Vector3d b = Eigen::Vector3d::Random();
Eigen::MatrixXd A = Eigen::MatrixXd::Random(3,3);
std::cout << "The following code crashes from Eigen 3.3-beta1 to Eigen
3.3-RC1" << std::endl;
std::cout << -A*b << std::endl;
return 0;
}
I strongly suggest either to upgrade to the stable branch of 3.3 (i.e.
3.3.4) or the stable branch of the 3.2 (i.e., 3.2.10), for which the
problem doesn't hold.
Note that I'd rather prefer not to install one of these stable
versions myself, because lots of other packages for this release are
built on top on the libeigen3-dev.
If I link those packages against my custom libraries, I would have two
different versions of Eigen to co-exist in the same binary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eigen3/+bug/1750794/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
** Changed in: unattended-upgrades (Ubuntu Disco) Importance: Undecided => High ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High ** No longer affects: qemu (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/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prev
[Group.of.nepali.translators] [Bug 1468794] Re: Caja thumbnails are deleted during each login and logout! (only on 32bit)
** Changed in: mate-settings-daemon (Ubuntu Xenial) Status: Triaged => Won't Fix -- 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/1468794 Title: Caja thumbnails are deleted during each login and logout! (only on 32bit) Status in mate-settings-daemon package in Ubuntu: Fix Released Status in mate-settings-daemon source package in Xenial: Won't Fix Bug description: I tested the new Mint 17.2 MATE rc. Whenever I logout all thumbnail files in ~/.cache/thumbnails/normal/* are deleted. I did not find the exact culprit. What I found out so far: - "caja -q" does not delete the thumbnails - write-protecting helps: "chmod a-w ~/.cache/thumbnails/normal" - a script in /etc/X11/Xreset.d/ is called too late to prevent the deletion - symbolic linking ~/.cache/thumbnails from or to ~/.thumbnails does not help First I tried this with a Live USB stick. Then I thought it might be a special "feature" for USB sticks. So I updated my Mint 17.1 to 17.2. But thumbnails on a harddrive are lost too during logout. To upgrade I followed http://mintguide.org/system/448-early-update-linux-mint-17-1 -rebecca-to-linux-mint-17-2-rafaela.html Fedora seems to have had this problem too: https://bugzilla.redhat.com/show_bug.cgi?id=1048409 https://bugzilla.redhat.com/show_bug.cgi?id=1120809 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-settings-daemon/+bug/1468794/+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 1624663] Re: Ubuntu Software Center is unusable when using the BlackMate theme
** Changed in: mate-themes (Ubuntu Xenial) Status: Triaged => Won't Fix -- 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/1624663 Title: Ubuntu Software Center is unusable when using the BlackMate theme Status in mate-themes package in Ubuntu: Fix Released Status in mate-themes source package in Xenial: Won't Fix Bug description: I am using Ubuntu-MATE 16.04 with the mate xenial ppa. When I choose the BlackMATE theme thene, thene both the text and the background of Ubuntu Software Center are white (making them unreadable, except for when something is selected). Changing colors at the Appearance application doesn't change anything. Ways to reproduce: 1) Choose BlackMATE theme from the Appearance application. 2) Open Ubuntu Software Center (the old one from the package software-center not the gnome-software) I attached an image to see the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-themes/+bug/1624663/+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 1732606] Re: CVE-2017-16852 Shibboleth Service Provider Security Advisory [15 November 2017]
** Also affects: shibboleth-sp2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881857 Importance: Unknown Status: Unknown ** Changed in: opensaml2 (Ubuntu) Importance: Undecided => Medium ** Changed in: opensaml2 (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: opensaml2 (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: shibboleth-sp2 (Ubuntu) Importance: Undecided => Medium ** Changed in: shibboleth-sp2 (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: shibboleth-sp2 (Ubuntu Xenial) Importance: Undecided => Medium -- 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/1732606 Title: CVE-2017-16852 Shibboleth Service Provider Security Advisory [15 November 2017] Status in opensaml2 package in Ubuntu: Fix Released Status in shibboleth-sp2 package in Ubuntu: Fix Released Status in opensaml2 source package in Trusty: Fix Released Status in shibboleth-sp2 source package in Trusty: Triaged Status in opensaml2 source package in Xenial: Fix Released Status in shibboleth-sp2 source package in Xenial: Triaged Status in shibboleth-sp2 package in Debian: Unknown Bug description: The developers of the Shibboleth SP have released a security advisory that affects all current versions of shibboleth-sp prior to V2.6.1. This includes the versions currently available for all releases of Ubuntu. The full text of the advisory is available at https://shibboleth.net/community/advisories/secadv_20171115.txt The vulnerability allows a remote attacker to bypass security checks on dynamically loaded metadata, a scenario that's commonly used in federated environments, and thus a likely use-case for this package. It is likely that a significant proportion of users of this package will be affected. From the advisory: "There are no known mitigations to prevent this attack apart from applying this update. Deployers should take immediate steps, and may wish to disable the use of this feature until the upgrade is done." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensaml2/+bug/1732606/+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 1732606] Re: CVE-2017-16852 Shibboleth Service Provider Security Advisory [15 November 2017]
Was fixed in Bionic --- opensaml2 (2.6.1-1) unstable; urgency=high * [0c08870] New upstream release (2.6.1) Security fix for CVE-2017-16853: Rod Widdowson of Steading System Software LLP discovered a coding error in the OpenSAML library, causing the DynamicMetadataProvider class to fail configuring itself with the filters provided and omitting whatever checks they are intended to perform. * [0795c42] Refresh our patches * [1f742ec] Update Standards-Version to 4.1.1 (no changes needed) * [5bed74f] Bump XMLTooling dependency version to 1.6. This isn't strictly required, but the stack is always updated in lockstep, so why not follow the upstream spec file in this respect. -- Ferenc Wágner Mon, 20 Nov 2017 10:46:24 +0100 ** Changed in: opensaml2 (Ubuntu) Status: Incomplete => 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/1732606 Title: CVE-2017-16852 Shibboleth Service Provider Security Advisory [15 November 2017] Status in opensaml2 package in Ubuntu: Fix Released Status in shibboleth-sp2 package in Ubuntu: Fix Released Status in opensaml2 source package in Trusty: Fix Released Status in shibboleth-sp2 source package in Trusty: Triaged Status in opensaml2 source package in Xenial: Fix Released Status in shibboleth-sp2 source package in Xenial: Triaged Bug description: The developers of the Shibboleth SP have released a security advisory that affects all current versions of shibboleth-sp prior to V2.6.1. This includes the versions currently available for all releases of Ubuntu. The full text of the advisory is available at https://shibboleth.net/community/advisories/secadv_20171115.txt The vulnerability allows a remote attacker to bypass security checks on dynamically loaded metadata, a scenario that's commonly used in federated environments, and thus a likely use-case for this package. It is likely that a significant proportion of users of this package will be affected. From the advisory: "There are no known mitigations to prevent this attack apart from applying this update. Deployers should take immediate steps, and may wish to disable the use of this feature until the upgrade is done." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensaml2/+bug/1732606/+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 1614080] Re: PATH contains dot when PATH is unset before running bash
This bug was fixed in the package bash - 5.0-3ubuntu2 --- bash (5.0-3ubuntu2) eoan; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:31:24 +0100 ** Changed in: bash (Ubuntu Eoan) 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/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: In Progress Status in bash source package in Xenial: In Progress Status in bash source package in Bionic: In Progress Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: In Progress Status in bash source package in Eoan: Fix Released Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+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 1825958] Re: Screen freeze after resume from S3 when HDMI monitor plugged on Dell Precision 7740
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1825958 Title: Screen freeze after resume from S3 when HDMI monitor plugged on Dell Precision 7740 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Won't Fix Status in linux-oem source package in Xenial: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: Fix Committed Bug description: [Summary] Screen freeze after resume from S3 when HDMI monitor plugged. This bug can be reproduced in both AC/DC mode. This bug can be reproduced after disabled TLP. In kernel log, [ 73.303742] amdgpu :01:00.0: GPU fault detected: 146 0x480c for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.303750] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 73.303752] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 73.303753] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 0, read from 'TC0' (0x54433000) (72) [ 73.420193] amdgpu :01:00.0: GPU fault detected: 146 0x480c for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.420205] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 73.420207] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 73.420210] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 0, read from 'TC0' (0x54433000) (72) [ 73.486518] amdgpu :01:00.0: GPU fault detected: 146 0x480c for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.486528] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 73.486531] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 73.486535] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 0, read from 'TC0' (0x54433000) (72) [ 73.569653] amdgpu :01:00.0: GPU fault detected: 146 0x480c for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.569667] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 73.569672] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 73.569679] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 0, read from 'TC0' (0x54433000) (72) [ 73.653019] amdgpu :01:00.0: GPU fault detected: 146 0x480c for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.653031] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 73.653036] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 73.653042] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 0, read from 'TC0' (0x54433000) (72) [ 73.686259] amdgpu :01:00.0: GPU fault detected: 147 0x00980801 for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.686271] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x04E1FE13 [ 73.686276] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x08008001 [ 73.686282] amdgpu :01:00.0: VM fault (0x01, vmid 4, pasid 32769) at page 81919507, read from 'TC2' (0x54433200) (8) [ 73.702937] amdgpu :01:00.0: GPU fault detected: 146 0x480c for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.702949] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 73.702953] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 73.702959] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 0, read from 'TC0' (0x54433000) (72) [ 73.786172] amdgpu :01:00.0: GPU fault detected: 146 0x480c for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.786185] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 73.786189] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 73.786195] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 0, read from 'TC0' (0x54433000) (72) [ 73.836124] amdgpu :01:00.0: GPU fault detected: 146 0x480c for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.836136] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 73.836141] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 73.836147] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 0, read from 'TC0' (0x54433000) (72) [ 73.919321] amdgpu :01:00.0: GPU fault detected: 146 0x480c for process Xorg pid 2023 thread Xorg:cs0 pid 2025 [ 73.919333] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x [ 73.919337] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0804800C [ 73.919343] amdgpu :01:00.0: VM fault (0x0c, vmid 4, pasid 32769) at page 0, read from 'TC0' (
[Group.of.nepali.translators] [Bug 1827391] Re: Japanese era Reiwa SRU
** Description changed: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan + + Note reported abi break / crash of chromium at https://bugs.debian.org + /cgi-bin/bugreport.cgi?bug=927933 ** Description changed: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan - Note reported abi break / crash of chromium at https://bugs.debian.org - /cgi-bin/bugreport.cgi?bug=927933 + Note reported abi break / crash of chromium at + + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 ** Bug watch added: Debian Bug tracker #927933 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 ** Also affects: icu (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 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/1827391 Title: Japanese era Reiwa SRU Status in icu package in Ubuntu: New Status in icu source package in Precise: New Status in icu source package in Trusty: New Status in icu source package in Xenial: New Status in icu source package in Bionic: New Status in icu source package in Cosmic: New Status in icu source package in Disco: New Status in icu source package in Eoan: New Status in icu package in Debian: Unknown Bug description: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan Note reported abi break / crash of chromium at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1827391/+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 1614080] Re: PATH contains dot when PATH is unset before running bash
** Also affects: bash (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: bash (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: bash (Ubuntu Eoan) Importance: Medium Status: Fix Released ** Also affects: bash (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: bash (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: bash (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: bash (Ubuntu Eoan) Status: Fix Released => In Progress ** Changed in: bash (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: bash (Ubuntu Disco) Status: New => In Progress ** Changed in: bash (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: bash (Ubuntu Bionic) Status: New => In Progress ** Changed in: bash (Ubuntu Xenial) Status: New => In Progress ** Changed in: bash (Ubuntu Trusty) Status: New => In Progress ** Also affects: bash (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: bash (Ubuntu Precise) 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/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Committed Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: In Progress Status in bash source package in Xenial: In Progress Status in bash source package in Bionic: In Progress Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: In Progress Status in bash source package in Eoan: Fix Committed Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+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 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue
>From the upstream discussion thread it looks like I was on the right track (https://marc.info/?l=linux-netdev&m=155688404826002&w=2). For confirmation I am building another set of test kernel packages and once this can be confirmed will proceed to SRU this into the other series. This looks to have remained unnoticed so far, so anything after 4.18 and all the older kernels which have backported those changes would be affected. ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) Status: New => Triaged ** Changed in: linux (Ubuntu Disco) Importance: Undecided => High ** Changed in: linux (Ubuntu Disco) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1824687 Title: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 After upgrading our server to this Kernel we experience frequent Kernel panics (Attachment). Every 3 hours. Our machine has a throuput of about 600 Mbits/s The Panics are around the area of ip6_expire_frag_queue. __pskb_pull_tail ip6_dst_lookup_tail _decode_session6 __xfrm_decode_session icmpv6_route_lookup icmp6_send It seems similar to Bug Report in Debian. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488 According to the bug finder of above bug it also occurred after using a Kernel with the change of rewrite ip6_expire_frag_queue() Intermediate solution. We disabled IPv6 on this machine to avoid further Panics. Please let me know what information is missing. The ubuntu-bug linux was send. And I hope it is attached to this report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 14 11:40:11 2019 InstallationDate: Installed on 2018-03-18 (391 days ago) InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 21:04 seq crw-rw 1 root audio 116, 33 Apr 12 21:04 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1 InstallationDate: Installed on 2018-03-18 (393 days ago) InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 RelatedPackageVersions: linux-restricted-modules-4.4.0-145-generic N/A linux-backports-modules-4.4.0-145-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial Uname: Linux 4.4.0-145-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-10-21 (176 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 10/08/2012 dmi.bios.vendor: American
[Group.of.nepali.translators] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value
** Also affects: libreoffice (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openjdk-lts (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openjdk-lts (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: openjdk-lts (Ubuntu Xenial) ** No longer affects: openjdk-lts (Ubuntu Bionic) ** Changed in: libreoffice (Ubuntu Xenial) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice (Ubuntu Bionic) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice (Ubuntu Bionic) Status: New => Triaged ** Changed in: libreoffice (Ubuntu Xenial) Status: New => Triaged -- 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/1822839 Title: LibreOffice doesn't detect JVM because of unexpected java.vendor property value Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in openjdk-lts package in Ubuntu: New Status in libreoffice source package in Xenial: Triaged Status in libreoffice source package in Bionic: Triaged Status in libreoffice package in Debian: New Bug description: libreoffice autopkgtests are failing on disco with openjdk 11.0.3+4-2ubuntu1. The likely culprit is that change: +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium + + * Sync packages with 11.0.3+4-2: +[ Matthias Klose ] +- Configure with vendor flags. Indeed with version 11.0.3+4-1ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Oracle Corporation And with version 11.0.3+4-2ubuntu1: $ java -XshowSettings -version 2>&1 | grep "java.vendor " java.vendor = Private Build Looking at the code in Libreoffice that looks for a JVM, it validates the vendor against a hardcoded list of known vendors: https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33 Not sure what the purpose of that upstream code is, but this means the new openjdk-11 build in Ubuntu breaks it. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 17:06:25 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (1003 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: openjdk-lts UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+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 1605761] Re: Main Menu editor destroys applications menu when processing a non-ASCII character.
** Changed in: mozo (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
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/1605761
Title:
Main Menu editor destroys applications menu when processing a non-
ASCII character.
Status in Ubuntu MATE:
Fix Released
Status in mozo package in Ubuntu:
Fix Released
Status in mozo source package in Xenial:
Won't Fix
Bug description:
There is a entry in my applications menu named "Life Is Strange™"
(note the ™ character). When using the Main Menu editor to make
adjustments to the layout of the menus, a serious error occurs while
processing the ™ character and as a result, destroys the entire
~/.config/menus/mate-applications.menu file to 0 kB. Occurs in Ubuntu
MATE 16.04.1.
A workaround is to rename the affecting program's name in a text
editor before using the Main Menu tool.
This is the back trace from mate-panel:
-
/usr/lib/python2.7/dist-packages/Mozo/MenuEditor.py:533: UnicodeWarning:
Unicode equal comparison failed to convert both arguments to Unicode -
interpreting them as being unequal
if node.childNodes[0].nodeName == 'Filename' and
node.childNodes[0].childNodes[0].nodeValue == filename:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/Mozo/MainWindow.py", line 430, in
on_menu_tree_drag_data_received
self.editor.copyItem(item, new_parent)
File "/usr/lib/python2.7/dist-packages/Mozo/MenuEditor.py", line 298, in
copyItem
self.save()
File "/usr/lib/python2.7/dist-packages/Mozo/MenuEditor.py", line 68, in save
fd.write(re.sub("\n[\s]*([^\n<]*)\n[\s]*\n', '')))
File "/usr/lib/python2.7/xml/dom/minidom.py", line 61, in toprettyxml
return writer.getvalue()
File "/usr/lib/python2.7/StringIO.py", line 271, in getvalue
self.buf += ''.join(self.buflist)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 15:
ordinal not in range(128)
** (mate-panel:12720): WARNING **: Error loading menu layout from
"/home/luke/.config/menus/mate-applications.menu": Error on line 1
char 1: Document was empty or contained only whitespace
-
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1605761/+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 1579447] Re: mate-screenshot defaults to a file name that is incompatible with some file systems
** Changed in: mate-utils (Ubuntu Xenial) Status: Triaged => Won't Fix -- 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/1579447 Title: mate-screenshot defaults to a file name that is incompatible with some file systems Status in mate-utils package in Ubuntu: Fix Released Status in mate-utils source package in Xenial: Won't Fix Bug description: mate-screenshot has colons in the file name which causes errors when saving to windows compatible file systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-utils/+bug/1579447/+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 1673486] Re: Don't suppress the shutdown menu on LTSP clients
** Changed in: mate-panel (Ubuntu Xenial) Status: New => Won't Fix -- 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/1673486 Title: Don't suppress the shutdown menu on LTSP clients Status in mate-panel package in Ubuntu: Fix Released Status in mate-panel source package in Xenial: Won't Fix Bug description: I've already reported this upstream, but I'd like to SRU it to 16.04 after it's fixed upstream. This (https://github.com/mate-desktop/mate- panel/commit/8c25e1bdd328a8712735c0b00cf4aede7993da1d) commit, 9 years ago, aimed at hiding the shutdown menu on LTSP clients, because they were remote sessions to the LTSP server, and we didn't want remote users to shut down the server by accident. Nowadays it prevents LTSP fat clients from shutting down. Fat clients is the recommended LTSP setup, and they run the session locally on the client, so having a shutdown button there is required. As for thin clients, preventing server shutdown is taken care of by policykit, there's no need to check for an environment variable in the MATE code (btw I'm an LTSP developer). So, I'd like to ask you to please revert commit 8c25e1b. [Test Case] Log in to an LTSP client running Ubuntu MATE. Enable the Redmond menu, where the shutdown menu should be shown. Verify that the shutdown menu is missing, and that it's displayed when the commit is reverted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1673486/+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 1827451] Re: Japanese new era "Reiwa(令和)" support
Note that this patch is in the upcoming 6.1.6 release, which will be SRU'd independently to cosmic when it's out. ** Also affects: libreoffice (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Cosmic) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice (Ubuntu Cosmic) Status: New => Triaged -- 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/1827451 Title: Japanese new era "Reiwa(令和)" support Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Xenial: Triaged Status in libreoffice source package in Bionic: Triaged Status in libreoffice source package in Cosmic: Triaged Bug description: Japanese new era "Reiwa(令和)" has began at 2019-05-01. These patches add Reiwa support for Libreoffice Bionic/Xenial. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 3 10:44:42 2019 InstallationDate: Installed on 2018-07-21 (285 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64(20180506.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827451/+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
