Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: powerd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590586
Title:
** Changed in: snapcraft
Status: New => Triaged
** Changed in: snapcraft
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590807
Title:
doesn't store build
** Changed in: snapcraft
Status: New => Triaged
** Changed in: snapcraft
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590811
Title:
"clean that part"
Hello dann, or anyone else affected,
Accepted installation-guide into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source
/installation-guide/20160121ubuntu2.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Thank you for reporting this bug to Ubuntu. The 14.10 reached EOL on July 23,
2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
If the bug is still reproducible in a currently supported release then
please advise.
** Package changed: ubuntu =>
I also noticed the clock icon appears randomly in date/time indicator even when
there is no alarm set. It vanishes as soon as I drag down the top panel.
My device is bq E5.
** Attachment added: "screenshot20160610_000823284.png"
** Package changed: ubuntu => sane-backends (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483368
Title:
Saned deamon not running
To manage notifications about this bug go to:
Hello TheBigW, or anyone else affected,
Accepted fwupd into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/fwupd/0.7.0-0ubuntu4.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
My evince just has crashed again (current yakkety). What has triggered
the problem is that I have viewed a bug pdf file and then have changed
this file by attempting another LaTeX run => The file grew and I suspect
that evince tried to display it while it was still being writen. What I
don't know
Hello Alexandre, or anyone else affected,
Accepted musescore into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/musescore/2.0.2
+dfsg-2ubuntu0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new
Same issue as shown in video of comment #2 on:
current build number: 354
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-06-09 06:22:08
version version: 354
version ubuntu: 20160609
version device: 20160606-ab415b2
version custom: 20160505-975-38-9
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590844
Title:
Public bug reported:
GSM specification of SMS-PP allows to enable/disable SMS status reports
in order to get a notification whether outgoing SMS have been received
by the contact or is pending.
So far, there is no way to configure this in my Ubuntu phone (BQ Aquaris
E4.5) and it seems that
Done,
Thank you Ismail!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566302
Title:
Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
4.4.0-16
To manage notifications about
Some news.
I updated the kernel to 4.4.13. Now I don't have error messages is dmesg.
Added radeon.dpm=1 radeon.modeset=1 to /etc/default/grub file (not sure if
everything is needed).
sudo update-grub and reboot
Although I still cannot switch between the cards with DDIS, but I can run
specific
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key kernel-hyper-v
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581131
Title:
create a .config to help apps that wrongly assume
To manage
Tester reported:
Looks good to me.
I enabled the proposed repository, and downgraded multipath-tools-boot
and associated packages to 0.4.9-3ubuntu7.12. I rebooted and confirmed
that the dev_loss_tmos were stuck at 30 despite the config saying to put
them at 5. Then I ran an upgrade which pulled
** Changed in: libertine/trunk
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1570961
Title:
[lxc] Some directories in the user's mapped home has user
** Changed in: libertine/trunk
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580610
Title:
Completion for libertine-container-manager commands
To
** Changed in: libertine/trunk
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1575315
Title:
Remove libertine-demo package
To manage notifications about
: 1.376
Date: Thu Jun 9 17:25:30 2016
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz ---
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160609)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage
the proposed 4.4.0-23 kernel does indeed fix the bug!
Thanks for your hard work on this...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581005
Title:
Dell XPS 15 9550 Freezes when HDMI is
Thank you for reporting this bug to Ubuntu. The Lucid Lynx reached EOL on May
9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
Please upgrade to or install a currently supported version and advise if
you still have a problem.
** Changed in:
This is the output of multipathd show config, which is the effective
multipath.conf file.
** Attachment added: "multipath.config"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1570093/+attachment/4680592/+files/multipath.config
--
You received this bug notification because
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal: apport-
collect 1589091
When reporting bugs in the future please use apport by using 'ubuntu-
Same result for 4.4.10
On Jun 9, 2016 3:56 PM, "Levente Ábrók" wrote:
> Some news.
> I updated the kernel to 4.4.13. Now I don't have error messages is dmesg.
> Added radeon.dpm=1 radeon.modeset=1 to /etc/default/grub file (not sure if
> everything is needed).
> sudo
I have no multipath.conf, we just use the defaults that are built in for
our storage.
multipath -ll for that particular host is not going to look good right
now as I'm having an issue with an Emulex device. Until I get my
hardware issue resolved I don't want to send you an output that will be
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If it's a blank check, I don't see many advantages over asking for
unity7 itself. Once we want to force the declaration, we can just
introduce the actual interface.
Might also be a good thing because unity7 will eventually be deprecated,
and we might use that timeframe to deprecate the general
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libertine/trunk
Status: Fix Committed => Fix Released
** Changed in: libertine/devel
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux-raspi2 - 4.4.0-1012.16
---
linux-raspi2 (4.4.0-1012.16) xenial; urgency=low
[ Andy Whitcroft ]
* Rebase against Ubuntu-4.4.0-23.41
[ Ubuntu: 4.4.0-24.43 ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory
This bug was fixed in the package linux-raspi2 - 4.2.0-1031.41
---
linux-raspi2 (4.2.0-1031.41) wily; urgency=low
[ Kamal Mostafa ]
[ Ubuntu: 4.2.0-38.45 ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux - 3.19.0-61.69
---
linux (3.19.0-61.69) vivid; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux-snapdragon - 4.4.0-1015.18
---
linux-snapdragon (4.4.0-1015.18) xenial; urgency=low
[ Kamal Mostafa ]
[ Ubuntu: 4.4.0-24.42 ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent
This bug was fixed in the package linux - 4.2.0-38.45
---
linux (4.2.0-38.45) wily; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs: forbid
This bug was fixed in the package linux-lts-utopic -
3.16.0-73.95~14.04.1
---
linux-lts-utopic (3.16.0-73.95~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking
This bug was fixed in the package linux - 3.2.0-104.145
---
linux (3.2.0-104.145) precise; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- SAUCE: proc: prevent stacking filesystems on top
- ecryptfs: fix handling of directory opening
- ecryptfs: don't
This bug was fixed in the package linux - 4.2.0-38.45
---
linux (4.2.0-38.45) wily; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs: forbid
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux-lts-trusty -
3.13.0-88.135~precise1
---
linux-lts-trusty (3.13.0-88.135~precise1) precise; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking
This bug was fixed in the package linux-snapdragon - 4.4.0-1015.18
---
linux-snapdragon (4.4.0-1015.18) xenial; urgency=low
[ Kamal Mostafa ]
[ Ubuntu: 4.4.0-24.42 ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent
This bug was fixed in the package linux - 4.2.0-38.45
---
linux (4.2.0-38.45) wily; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs: forbid
This bug was fixed in the package linux - 3.19.0-61.69
---
linux (3.19.0-61.69) vivid; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux - 3.19.0-61.69
---
linux (3.19.0-61.69) vivid; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux - 3.19.0-61.69
---
linux (3.19.0-61.69) vivid; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux-armadaxp - 3.2.0-1667.92
---
linux-armadaxp (3.2.0-1667.92) precise; urgency=low
[ Andy Whitcroft ]
* rebase to 3.2.0-104.145
[ Ubuntu: 3.2.0-104.145 ]
* CVE-2016-1583 (LP: #1588871)
- SAUCE: proc: prevent stacking filesystems on
This bug was fixed in the package linux-ti-omap4 - 3.2.0-1482.109
---
linux-ti-omap4 (3.2.0-1482.109) precise; urgency=low
[ Kamal Mostafa ]
[ Ubuntu: 3.2.0-104.145 ]
* CVE-2016-1583 (LP: #1588871)
- SAUCE: proc: prevent stacking filesystems on top
- ecryptfs: fix
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux-lts-vivid - 3.19.0-61.69~14.04.1
---
linux-lts-vivid (3.19.0-61.69~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking
This bug was fixed in the package linux-lts-wily - 4.2.0-38.45~14.04.1
---
linux-lts-wily (4.2.0-38.45~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems
This bug was fixed in the package linux - 3.19.0-61.69
---
linux (3.19.0-61.69) vivid; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux-snapdragon - 4.4.0-1015.18
---
linux-snapdragon (4.4.0-1015.18) xenial; urgency=low
[ Kamal Mostafa ]
[ Ubuntu: 4.4.0-24.42 ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent
This bug was fixed in the package linux - 4.2.0-38.45
---
linux (4.2.0-38.45) wily; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs: forbid
This bug was fixed in the package linux - 4.2.0-38.45
---
linux (4.2.0-38.45) wily; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs: forbid
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux-lts-trusty -
3.13.0-88.135~precise1
---
linux-lts-trusty (3.13.0-88.135~precise1) precise; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking
This bug was fixed in the package linux-lts-xenial - 4.4.0-24.43~14.04.1
---
linux-lts-xenial (4.4.0-24.43~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking
This bug was fixed in the package linux-lts-xenial - 4.4.0-24.43~14.04.1
---
linux-lts-xenial (4.4.0-24.43~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking
This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs:
This bug was fixed in the package linux-lts-vivid - 3.19.0-61.69~14.04.1
---
linux-lts-vivid (3.19.0-61.69~14.04.1) trusty; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking
This bug was fixed in the package linux-lts-trusty -
3.13.0-88.135~precise1
---
linux-lts-trusty (3.13.0-88.135~precise1) precise; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking
This impacts upstream; I've submitted a bug (stuck in moderation) and a
pull request. I'll give upstream a day or so to digest to see if we can
incorporate an upstream-accepted fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Impact]
lshw crashes when run as non-root:
Though it does warn before crashing that it should be run as super-user,
it should fail gracefully - not abort and dump core. A number of users
have been hitting this since the regression has been introduced:
** Description changed:
The `snapcraft tour` command is currently not exposed.
+
+ [Impact]
+
+ * The tour is the point of entry for new users. This change will make
+ it available to users.
+
+ [Test Case]
+
+ * snapcraft tour
+
+ [Regression Potential]
+
+ * N/A, this command was not
Public bug reported:
root@luweidong401:/home/howard/Downloads/libxml2-2.9.1+dfsg1# sudo apt-get
install --reinstall software-center
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no
Thanks for the explanation, it sound quite right.
However, the combination of the two makes things worse, and it's probably
what makes me react.
I guess I'm going to check the current bugs for Dekko as soon as I have the
time, seeing as it seems to be the real problem in my case.
Thanks, keep
Jan Stutzki, to clarify, did you test hibernate (not suspend) with
4.7-rc2?
** Tags removed: latest-bios-1.2.13
** Tags added: latest-bios-1.2.14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568703
** Attachment added: "dmesg-after-processors.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576909/+attachment/4680671/+files/dmesg-after-processors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello.
Tested with Kernel 4.6.2-040602-generic. The problem happens when
closing the laptop lid. As mentioned, the screen goes black, but disks
and fans keep working and power led does not go off.
I am attaching the trace files according the debugging guide
** Attachment added: "wakeup"
** Attachment added: "suspend_stats"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576909/+attachment/4680670/+files/suspend_stats
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576909
** Attachment added: "dmesg-after-freezer.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576909/+attachment/4680679/+files/dmesg-after-freezer.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg-after-platform.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576909/+attachment/4680677/+files/dmesg-after-platform.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "dmesg-after-core.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576909/+attachment/4680681/+files/dmesg-after-core.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Both the suspension test after using core and platform commands
reproduced the problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1576909
Title:
Suspend not working on Ubuntu 16.04
To manage
*** This bug is a duplicate of bug 1590765 ***
https://bugs.launchpad.net/bugs/1590765
** This bug has been marked a duplicate of bug 1590765
OSK flickers and buttons are sometimes invisble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
after ota-11, now the "TER scope" and "SNCF scope" not able to get the GPS
position
but "activity tracker", "google maps" or "unav" working well
PRO 5 and QB E4.5
** Affects: unity-scopes-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this
I'm also facing the kswap0 99% CPU issue. Typically, I notice it start
minutes after boot time, but restarting the MongoDB process on the
server will temporarily fix it, however the process will usually pop up
again randomly.
I used to run test instances of MongoDB on AWS t2.micros with no issues
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590985
Title:
Wifi non-functional after suspend (Intel
501 - 600 of 997 matches
Mail list logo