[Bug 1699004] Re: APST gets enabled against explicit kernel option
Nils, what the actual failure mode on a bad kernel? Do you have dmesg output? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699004 Title: APST gets enabled against explicit kernel option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686592] Re: APST quirk needed for Intel NVMe
For those of you with problematic Intel devices, could you post the relevant line from 'lspci -nn'? It looks like there are a few known firmware issues with some Intel SSDs and a fix is in the works. Meanwhile, I want to quirk the correct set of devices. (I'm hoping they're all 8086:f1a5) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686592 Title: APST quirk needed for Intel NVMe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
@jdrewes: just for completeness, can you post the nvme-related log messages from the beginning of that boot? I want to verify that I programmed the controller the way I meant to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
Hi @keihengfeng, Could you build a test kernel with the two test patches here applied: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/log/?h=nvme/power&id=1115e17962c597d8e6dd140d903a51a58d0ec2c0 I'd like to get some testing to see whether that works on the problematic Samsung and Intel machines. (Those delete the quirk and replace the APST table computation with something closer to what Intel RSTe does.) Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686592] Re: APST quirk needed for Intel NVMe
@kaihengfeng, I'm not sure what your test kernel is, but could you build one with the two patches here: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/log/?h=nvme/power&id=1115e17962c597d8e6dd140d903a51a58d0ec2c0 Those delete the earlier quirk and replace the APST table computation with something closer to what Intel RSTe does. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686592 Title: APST quirk needed for Intel NVMe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
The quirk updates have landed here in the linux-block tree here: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux- block.git/commit/?h=for- linus&id=be56945c4edd5a3da15f8254b68d1ddb1588d0c4 Reporters, could you test that kernel? (Or Kai-Heng, is there a way you could build a test kernel that people could use?) The current 4.11 queue does not disable APST entirely on Samsung devices. Instead it turns off the deepest sleep state on the affected drives on the affected laptops. Hopefully this covers all the problematic cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678184 Title: APST quirk needed for Samsung 512GB NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381743] Re: Please consider backporting a p11-kit deadlock fix
Here are my attempts to answer the questions in the SRU template. I'm not an Ubuntu developer, and I don't speak Debian package language (I speak RPM, but that's rather different), so I'm not going to send an actual debdiff or whatever it's called. Note, however, that I confused myself with the git history. The latest upstream release in the 0.20 series is 0.20.7, and 0.20.7 does not have the fix. The fix I linked applies directly on top of 0.20.7. This bug should therefore be fixed in Vivid before worrying about backports. The fix does *not* apply to 0.20.3 as is. I can try to backport it, but I'd want confirmation that it would be likely to be applied (as opposed to bumping p11-kit to a newer microrelease or just leaving it unfixed). [Impact] Multithreaded programs that use p11-kit and call fork can deadlock due to a race. More complex programs that use certain malloc replacements and link to libraries like libvmime may deadlock when forking as well, even if they don't use p11-kit. The deadlock is caused by the use of non async-signal-safe functions in an atfork handler in p11-kit. [Test Case] Compile and run the attached program. With a buggy p11-kit, it is very likely to deadlock. With a fixed p11-kit, it will exit after about five seconds. [Regression Potential] When I looked at the patch, it looked straightforward. ** Attachment added: "p11kit_hang.c" https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1381743/+attachment/4264589/+files/p11kit_hang.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381743 Title: Please consider backporting a p11-kit deadlock fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1381743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381743] Re: Please consider backporting a p11-kit deadlock fix
This package doesn't seem to be set up with an upstream tracker link. Here's the upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=84567 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381743 Title: Please consider backporting a p11-kit deadlock fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1381743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381743] [NEW] Please consider backporting a p11-kit deadlock fix
Public bug reported: Linking against p11-kit or gnutls (especially the outdated gnutls in Trusty) can cause fork() to deadlock randomly. Please consider backporting the stable fix here: http://cgit.freedesktop.org/p11-glue/p11-kit/commit/?h=stable&id=0ecc141f372b375ddd2087a8ca406797976f03bf ** Affects: p11-kit (Ubuntu) Importance: Undecided Status: New ** Bug watch added: freedesktop.org Bugzilla #84567 https://bugs.freedesktop.org/show_bug.cgi?id=84567 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381743 Title: Please consider backporting a p11-kit deadlock fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p11-kit/+bug/1381743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245713] [NEW] Nasty libstdc++ bug, fixed upstream (PR58800)
Public bug reported: libstdc++ PR58800 (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58800) is a really nasty regression that is causing lots of crashes for us. It's fixed upstream, but it may be bad enough to warrant a new build of gcc, etc. (I'm kind of surprised it's not causing all kinds of random crashes.) ** Affects: gcc-defaults Importance: Unknown Status: Unknown ** Affects: gcc-defaults (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GCC Bugzilla #58800 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58800 ** Also affects: gcc-defaults via http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58800 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245713 Title: Nasty libstdc++ bug, fixed upstream (PR58800) To manage notifications about this bug go to: https://bugs.launchpad.net/gcc-defaults/+bug/1245713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244384] [NEW] python-cap-ng is missing the python module
Public bug reported: python-cap-ng doesn't work in saucy. It's probably because there's no actual code in the package. See: http://packages.ubuntu.com/saucy/amd64/python-cap-ng/filelist Compare to: http://packages.ubuntu.com/raring/amd64/python-cap-ng/filelist ** Affects: libcap-ng (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244384 Title: python-cap-ng is missing the python module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap-ng/+bug/1244384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041790]
The patch seems to have helped -- my box survived a couple days with the patch applied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183128] [NEW] Adding a vlan brings up all interfaces
Public bug reported: I have a relatively straightforward /etc/network/interfaces configuration, like this (excerpted): auto p3p2.1 iface p3p2.1 inet static vlan-raw-device p3p2 ... configuration here... auto p3p2.2 iface p3p2.2 inet static vlan-raw-device p3p2 ... configuration here... The problem is that ifup p3p2.1 (or ifup p3p2.2) brings up both p3p2.1 and p3p2.2. In fact, vconfig add p3p2 1 brings up both interfaces. The problem seems to be that /etc/init/network-interface.conf says "start on net-device-added". The intent is (presumably) to start the interface when p3p2 is added, but not to start p3p2.x when p3p2.y is added. This is particularly annoying because ifdown p3p2.2 deletes the interface, so I can't reliably bring down two vlans and then bring just one of them back up. ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183128 Title: Adding a vlan brings up all interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1183128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172951] Re: gcc 4.7.3-1ubuntu10 c++11 bogus errors (reduced, not reproducible upstream)
I think this is c++/56388 upstream. r198010 on the 4.7 branch seems to fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172951 Title: gcc 4.7.3-1ubuntu10 c++11 bogus errors (reduced, not reproducible upstream) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1172951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172951] [NEW] gcc 4.7.3-1ubuntu10 c++11 bogus errors (reduced, not reproducible upstream)
Public bug reported:
This code:
namespace NS {
struct A
{
static void foo(int);
template
void func(Func f)
{
[&](){
do {
do {
if (1)
foo(0);
} while(0);
} while (0);
};
}
};
}
void caller()
{
NS::A a;
a.func([&]{});
}
Fails like this on Raring:
redeclaration_bug.cc: In instantiation of 'NS::A::func(Func) [with Func =
caller()::]::':
redeclaration_bug.cc:14:11: required from 'struct NS::A::func(Func) [with
Func = caller()::]::'
redeclaration_bug.cc:10:5: required from 'void NS::A::func(Func) [with Func =
caller()::]'
redeclaration_bug.cc:26:15: required from here
redeclaration_bug.cc:14:11: error: redeclaration of 'NS::A* const
NS::A::func(Func) [with Func = caller()::]__this'
redeclaration_bug.cc:14:11: note: previous declaration 'NS::A* const
NS::A::func(Func) [with Func = caller()::]__this'
redeclaration_bug.cc:14:11: error: redeclaration of 'NS::A* const this'
redeclaration_bug.cc:14:11: error: 'NS::A* const this' previously declared here
redeclaration_bug.cc: In instantiation of 'void NS::A::func(Func) [with Func =
caller()::]':
redeclaration_bug.cc:26:15: required from here
redeclaration_bug.cc:10:5: error: too many initializers for 'NS::A::func(Func)
[with Func = caller()::]::'
It compiles fine on Fedora 18's gcc 4.7.2 as well as a version of the
upstream 4.7 branch that I just built today. (The latter calls itself
4.7.4.)
** Affects: gcc-defaults (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172951
Title:
gcc 4.7.3-1ubuntu10 c++11 bogus errors (reduced, not reproducible
upstream)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1172951/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055811] [NEW] do-release-upgrade configuration prompts fail to handle SIGINT
Public bug reported: This bug occurred while upgrading Oneiric to Precise. The 'Z : start a shell to examine the situation' prompt does not handle SIGINT. This is a severe bug, which just risked hosing my box. do-release-upgrade said: Configuration file `/etc/mysql/my.cnf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** my.cnf (Y/I/N/O/D/Z) [default=N] ? z Type `exit' when you're done. root@code:/# I typed a few characters, realized I typed the wrong thing, and hit Ctrl-C. I got: A fatal error occurred Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade has aborted. Your original sources.list was saved in /etc/apt/sources.list.distUpgrade. Traceback (most recent call last): File "/tmp/update-manager-9cwRNH/precise", line 7, in sys.exit(main()) File "/tmp/update-manager-9cwRNH/DistUpgradeMain.py", line 226, in main if app.run(): File "/tmp/update-manager-9cwRNH/DistUpgradeController.py", line 1721, in run return self.fullUpgrade() File "/tmp/update-manager-9cwRNH/DistUpgradeController.py", line 1690, in fullUpgrade if not self.doDistUpgrade(): File "/tmp/update-manager-9cwRNH/DistUpgradeController.py", line 1065, in doDistUpgrade res = self.cache.commit(fprogress,iprogress) File "/tmp/update-manager-9cwRNH/DistUpgradeCache.py", line 256, in commit apt.Cache.commit(self, fprogress, iprogress) File "/usr/lib/python2.7/dist-packages/apt/deprecation.py", line 98, in deprecated_function return func(*args, **kwds) File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 473, in commit res = self.install_archives(pm, install_progress) File "/usr/lib/python2.7/dist-packages/apt/deprecation.py", line 98, in deprecated_function return func(*args, **kwds) File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 436, in install_archives res = install_progress.run(pm) File "/tmp/update-manager-9cwRNH/DistUpgradeView.py", line 211, in run res = os.WEXITSTATUS(self.wait_child()) File "/tmp/update-manager-9cwRNH/DistUpgradeView.py", line 174, in wait_child select.select([self.statusfd], [], [], self.select_timeout) KeyboardInterrupt === Command terminated with exit status 1 (Mon Sep 24 14:19:12 2012) === And there went my upgrade. (The decorative spacing comes from do- release-upgrade. That's a separate bug, presumably.) The system is still sitting there, with dpkg in some mysterious state, stuck, because the 'precise' process is waiting for I/O that's never going to happen. If you're going to spawn a shell, *give it proper control of the tty so it handles signals*. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: dist-upgrade ** Tags added: dist-upgrade -- You received this bug notification because you are a member of Ubun
[Bug 1044532] [NEW] icedtea-netx 0.11.10.3 isn't installing the javaws alternative on Oneiric
Public bug reported: A recent update on two Oneiric computers removed /usr/bin/javaws and /var/lib/dpkg/alternatives/javaws. This is problematic. The latest icedtea-netx on Precise is okay. (Something's obviously buggy here. Running 'javaws' suggets installing icedtea-netx, but icedtea-netx isn't symlinking it any more.) ** Affects: icedtea-web (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1044532 Title: icedtea-netx 0.11.10.3 isn't installing the javaws alternative on Oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1044532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577114] Re: Wireless and Bluetooth switch does not work correctly on lenovo ideapad s10-3
This happened to my nephew's laptop, and I tracked down the problem. Details are here: http://www.spinics.net/lists/linux-acpi/msg32938.html The attachment to that email is a Python script that restored wireless function on that laptop. Depending on your point of view, it could be more or less scary than pulling the battery. *** WARNING: that script has magic numbers hardcoded. If I were you, I would check that your DSDT has the same magic numbers before you even think about running the script. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577114 Title: Wireless and Bluetooth switch does not work correctly on lenovo ideapad s10-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/577114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 171243] Re: implement clip-rule:evenodd
I've attached a patch that implements loading, saving, and computing of clip-rule. It doesn't address rendering or the UI, but at least we won't destroy otherwise-correct clip-rule styles now. ** Patch added: "Implement loading and saving of clip-rule" https://bugs.launchpad.net/inkscape/+bug/171243/+attachment/1908049/+files/clip_rule.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/171243 Title: implement clip-rule:evenodd -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 583122]
I see this bug on Fedora 14 with latest (3.6) packages. It's not (just) caused by sleep/hibernate -- I just saw it on a machine that never sleeps. Whenever this bug is happening, it reliably causes: - Characters I type into the 'Lookup forecast by "City, St"' box at weather.gov - Whenever I type one or two characters into the subject field when composing a message in gmail, they get highlighted. To continue typing without losing those characters, I have to hit the right arrow or otherwise deselect them. - The awesomebar isn't awesome. That is, it just acts like a plain text box and doesn't pop up any hints. The most recent time it triggered, I fixed it by defocusing Firefox and then refocusing it. Restarting Firefox always fixes it for awhile. I have no idea how to trigger it in the first place, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/583122 Title: firefox occasionally highlights contents of form fields while typing thereby overwriting previously entered keystrokes -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148381] Re: right-click menu closes and selects items when it can't fit below mouse pointer
For me it seems to do random things without showing the menu at all. Not seeing the menu could be related to running compiz, I suppose. This is firefox-3 on hardy. It's persisted across several versions (currently b4), and it appears to be a regression since firefox-2. It's pretty annoying when I right-click a link and something random happens. -- right-click menu closes and selects items when it can't fit below mouse pointer https://bugs.launchpad.net/bugs/148381 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
