[Bug 1269883] Re: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port
gouri, the latest mainline kernel is 4.3-rc6. Is this what you tested with? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1269883 Title: 0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device on USB3 port To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1269883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509265] Re: package linux-headers-3.13.0-66-generic 3.13.0-66.108 failed to install/upgrade: error creating symbolic link `./usr/src/linux-headers-3.13.0-66-generic/include/linux/firewire.h': No
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509265 Title: package linux-headers-3.13.0-66-generic 3.13.0-66.108 failed to install/upgrade: error creating symbolic link `./usr/src/linux- headers-3.13.0-66-generic/include/linux/firewire.h': No space left on device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504834] Re: pcsx assert failure: pcsx: ../libpcsxcore/ix86_64/ix86-64.c:158: MEMADDR_OP: Assertion `!isreg || reg != 0' failed.
When running PCSX I cannot load ISOs or even real Playstation discs. I've tried changing between OpenGL and X11 graphics driver, as well as switching between the actual PSX BIOS and the "Simulated" BIOS that comes with PCSX. None of it makes a difference. Have ran these games on this hardware in older versions of Ubuntu and PCSX without issue. PCSX Version: 1.9.92 OS: Ubuntu 15.10 64bit (amd64) Terminal Output when trying to launch a game RGB mode found. id: 18424752, depth: 24 pcsx: ../libpcsxcore/ix86_64/ix86-64.c:158: MEMADDR_OP: Assertion `!isreg || reg != 0' failed. Aborted (core dumped) Attached is a system summary generated by "hardinfo" in html format that lists all the dirty details of my system. ** Attachment added: "hardinfo_report.html" https://bugs.launchpad.net/ubuntu/+source/pcsxr/+bug/1504834/+attachment/4503627/+files/hardinfo_report.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504834 Title: pcsx assert failure: pcsx: ../libpcsxcore/ix86_64/ix86-64.c:158: MEMADDR_OP: Assertion `!isreg || reg != 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsxr/+bug/1504834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509265] Re: package linux-headers-3.13.0-66-generic 3.13.0-66.108 failed to install/upgrade: error creating symbolic link `./usr/src/linux-headers-3.13.0-66-generic/include/linux/firewire.h': No
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509265 Title: package linux-headers-3.13.0-66-generic 3.13.0-66.108 failed to install/upgrade: error creating symbolic link `./usr/src/linux- headers-3.13.0-66-generic/include/linux/firewire.h': No space left on device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1139453] Re: NVidia HDMI sound plays only on one monitor
svecpetr, thank you for reporting this and helping make Ubuntu better. Could you please run the following command from a terminal in a supported release, as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1139453 Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information. ** Package changed: nvidia-graphics-drivers-310 (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1139453 Title: NVidia HDMI sound plays only on one monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1139453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008772] Re: package openafs-modules-dkms 1.6.1-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 10
** Changed in: openafs (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/1008772 Title: package openafs-modules-dkms 1.6.1-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1008772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1499421] Re: kernel panic on boot after upgrade to ubuntu 15.10
Hi, since 3 weeks I have tried to track the reasons for a kernel panic I had with my Thinkpad T450s. Unfortunately, the panic happen only one in many hours and isolating the true reasons was very difficult. I'm quite sure now that it's not related to intel graphics nor the intel wifi driver (graphics was my ideal suspect). What I have found (95% certitude): - the panic occur only on when on battery - removing the TLP package solve the issue (so, it's probably a driver flag set by TLP that causes the issue) - Upgrading to upstream kernel 4.3RC4/5 definitely solve the problem. FYI: when the panic occurs, the screen/image completely freezes, no kernel logs, no magic key working. Hope it helps ! Lorenzo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1499421 Title: kernel panic on boot after upgrade to ubuntu 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509326] Re: Various instabilities after resuming from standby
Joachim Durchholz, thank you for reporting this and helping make Ubuntu better. As per http://www.nvidia.com/download/driverResults.aspx/92826/en-us , the latest version of the nvidia driver available for your card is 352. Hence, could you please update to Wily, and advise if this is still reproducible with https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-352 ? ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509326 Title: Various instabilities after resuming from standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 516007] Re: package openafs-client 1.4.11+dfsg-1+ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: openafs (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/516007 Title: package openafs-client 1.4.11+dfsg-1+ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/516007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504834] Re: pcsx assert failure: pcsx: ../libpcsxcore/ix86_64/ix86-64.c:158: MEMADDR_OP: Assertion `!isreg || reg != 0' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pcsxr (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/1504834 Title: pcsx assert failure: pcsx: ../libpcsxcore/ix86_64/ix86-64.c:158: MEMADDR_OP: Assertion `!isreg || reg != 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsxr/+bug/1504834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509577] Re: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured
*** This bug is a duplicate of bug 1509574 *** https://bugs.launchpad.net/bugs/1509574 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1509574, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1509574 package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509577 Title: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1509577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509362] Re: linux-lts-utopic: 3.16.0-52.71~14.04.1 -proposed tracker
All builds are complete, packages in this bug can be copied to -proposed. ** Changed in: kernel-sru-workflow/prepare-package Status: New => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques (henrix) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques (henrix) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the 3.16.0-52.71~14.04.1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 23. October 2015 13:30 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Friday, 23. October 2015 13:30 UTC + kernel-stable-phase:CopyToProposed + kernel-stable-Prepare-package-end:Saturday, 24. October 2015 00:02 UTC + kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 00:02 UTC + kernel-stable-phase-changed:Saturday, 24. October 2015 00:02 UTC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509362 Title: linux-lts-utopic: 3.16.0-52.71~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1509362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509480] Re: linux: 4.2.0-17.21 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Brad Figg (brad-figg) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509480 Title: linux: 4.2.0-17.21 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1509480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509574] Re: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509574 Title: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1509574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509305] Re: Kernel not upgraded during upgrade from Vivid to Wily if linux-generic not installed
Of course, it could be argued, that ubuntu-release-upgrader should double check if linux-image-generic is installed. It is kind of essential, but maybe it should be possible to upgrade without getting the latest kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509305 Title: Kernel not upgraded during upgrade from Vivid to Wily if linux-generic not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1509305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509574] Re: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured
Error updating Ubuntu from version 15.04 to new version 15.10 Wily Werewolf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509574 Title: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1509574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509574] [NEW] package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured
Public bug reported: Error updating Ubuntu from version 15.04 to new version 15.10 Wily Werewolf ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libuuid1:i386 2.25.2-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu3 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Oct 23 19:30:50 2015 DuplicateSignature: package:libuuid1:i386:2.25.2-4ubuntu3:package libuuid1:i386 is already installed and configured ErrorMessage: package libuuid1:i386 is already installed and configured InstallationDate: Installed on 2014-10-26 (362 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: dpkg Title: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509574 Title: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1509574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509575] [NEW] package libblkid1 2.25.2-4ubuntu3 failed to install/upgrade: 37.1319:package libblkid1:amd64 is already installed and configured
Public bug reported: Error updating Ubuntu from version 15.04 to new version 15.10 Wily Werewolf ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libblkid1 2.25.2-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu3 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Oct 23 19:57:20 2015 DuplicateSignature: package:libblkid1:2.25.2-4ubuntu3:37.1319:package libblkid1:amd64 is already installed and configured ErrorMessage: 37.1319:package libblkid1:amd64 is already installed and configured InstallationDate: Installed on 2014-10-26 (362 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: util-linux Title: package libblkid1 2.25.2-4ubuntu3 failed to install/upgrade: 37.1319:package libblkid1:amd64 is already installed and configured UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509575 Title: package libblkid1 2.25.2-4ubuntu3 failed to install/upgrade: 37.1319:package libblkid1:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1509575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509576] Re: package libblkid1:amd64 2.25.2-4ubuntu3 failed to install/upgrade: package libblkid1:amd64 is already installed and configured
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509576 Title: package libblkid1:amd64 2.25.2-4ubuntu3 failed to install/upgrade: package libblkid1:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1509576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509576] [NEW] package libblkid1:amd64 2.25.2-4ubuntu3 failed to install/upgrade: package libblkid1:amd64 is already installed and configured
Public bug reported: Error updating Ubuntu from version 15.04 to new version 15.10 Wily Werewolf ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libblkid1:amd64 2.25.2-4ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu3 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Oct 23 19:30:50 2015 DuplicateSignature: package:libblkid1:amd64:2.25.2-4ubuntu3:package libblkid1:amd64 is already installed and configured ErrorMessage: package libblkid1:amd64 is already installed and configured InstallationDate: Installed on 2014-10-26 (362 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: dpkg Title: package libblkid1:amd64 2.25.2-4ubuntu3 failed to install/upgrade: package libblkid1:amd64 is already installed and configured UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509576 Title: package libblkid1:amd64 2.25.2-4ubuntu3 failed to install/upgrade: package libblkid1:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1509576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509577] [NEW] package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured
Public bug reported: Error updating Ubuntu from version 15.04 to new version 15.10 Wily Werewolf ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libuuid1:i386 2.26.2-6ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu3 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Fri Oct 23 19:30:50 2015 DuplicateSignature: package:libuuid1:i386:2.25.2-4ubuntu3:package libuuid1:i386 is already installed and configured ErrorMessage: package libuuid1:i386 is already installed and configured InstallationDate: Installed on 2014-10-26 (362 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: util-linux Title: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package i386 need-duplicate-check wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509577 Title: package libuuid1:i386 2.25.2-4ubuntu3 failed to install/upgrade: package libuuid1:i386 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1509577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509326] Re: Various instabilities after resuming from standby
** Description changed:
None of these problems are readily reproducible, I'm having a roughly
- 30:70 chance of a successful standby or shutdown cycle.
-
- Things that I have seen happen:
+ 30:70 chance of a successful standby. Things that I have seen happen:
1) Click on Whisker menu -> Logoff ("Abmelden") button ->
Logoff/Restart/Reboot/Standby dialog (no Hibernate option, I think it's
blacklisted for my machine) -> Click on "Shutdown" -> no shutdown, I get
the login screen.
2) Trying to go to standby from the Logoff button in the login screen
after seeing (1) -> monitor switches off, then on, login screen again.
3) After (2), close the lid, open it, standby procedure from login
screen -> works. Sometimes.
4) After (2), remove machine from docking station, standby procedure
from login screen -> works. Sometimes.
5) Machine is in standby, I press the power button, I get some text mode
messages, monitor flashes and shows graphic content (mostly a mouse
cursor on some background, too fast to properly see), then the screen
goes dark. Ctrl-Alt-F1 works, Ctrl-Alt-F7 simply makes the screen dark
again (both the builtin laptop screen and one of the external,
connected-through-docking-station screens).
6) The effects from (5) can also happen right after cold booting the
machine.
7) I *think* on a few occasions, I tried to shutdown the machine and
nothing happened at all.
8) On some rarer occasions, nothing would happen after the shutdown
command, and trying to issue another shutdown resulted in a message
amounting to "can't do another action while the previous action is in
progress"; I remember pstree reported some hung process that was
connected to shutdown, and I couldn't kill it (not even kill -9). I
cannot reproduce this, and I didn't take notes so I can't be more
specific.
I have no idea which of these effects are related to a common cause and which
are independent.
I have been unable to find out anything given that no individual phenomenon
is reproducible with any reliability.
I hope the attached debug info will help, but I fully expect this to require
much more diagnosis.
Hardware:
- - Dell Precision M4600
- - did a BIOS update a while ago (that changed the problems, slightly for the
better I think)
- Docking station PR02X
- Two 2560x1440 Dell U2515H monitors, one on each video output of the docking
station
- nVidia Quadro 2000M, using the proprietary driver (Nouveau cannot drive two
2560x1440 screens)
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
- NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
- GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
+ NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21
PDT 2015
+ GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Oct 23 13:40:40 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
- bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
- bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
- bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
- nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
+ bbswitch, 0.7, 3.19.0-28-generic, x86_64: installed
+ bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
+ bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
+ nvidia-346, 346.96, 3.19.0-31-generic, x86_64: installed
GraphicsCard:
- NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
-Subsystem: Dell Device [1028:04a3]
+ NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00
[VGA controller])
+ Subsystem: Dell Device [1028:04a3]
InstallationDate: Installed on 2015-08-24 (59 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmGreeterLogOld:
- upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
- upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
+ upstart: indicator-sound-main-Prozess (11841) wurde von TERM-Signal beendet
+ upstart: indicator-application-main-Prozess (11843) wurde von TERM-Signal
beendet
MachineType: Dell Inc. Precision M4600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic
root=/dev/mapper/xubuntu--vg-root ro quiet splash
SourcePackage: xorg
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden:
'/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.n
[Bug 1509572] [NEW] Kate missing Text Filter plugin
Public bug reported: The Text Filter plugin for Kate was previously present in Kubuntu 14.10 (and earlier), but isn't there in 15.10. This was reported in KDE and patched in July: https://bugs.kde.org/show_bug.cgi?id=347243 Here's the commit: https://quickgit.kde.org/?p=kate.git&a=commit&h=07f60d0afa789e23421da7b8c44908dd01dd6df0 In looking at Kate's git repository, those files appear to be present under their tags for 15.08: https://quickgit.kde.org/?p=kate.git Following the links for the tag 15.08.0, you can see the files in the tree here: https://quickgit.kde.org/?p=kate.git&a=tree&h=dad9965fb5ebcd7f27c7225bdc1b2544fdc96b04&hb=f7e8905912c130399b0195158941f544d565ed62&f=addons%2Ftextfilter So, it looks like that plugin should have made it into KDE Applications 15.08, and therefore made it into Kubuntu 15.10. You can open Kate -> Settings -> Configure Kate -> Plugins to see it's not there. So can that get added back? Ubuntu release: Ubuntu 15.10 Package version: 4:15.08.2-0ubuntu1 from About->Kate: Version 15.08.2 KDE Frameworks 5.15.0 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: kate 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 23 17:27:48 2015 InstallationDate: Installed on 2015-10-23 (0 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kate UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kate (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509572 Title: Kate missing Text Filter plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1509572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509570] [NEW] efivar-0.21 fails to create boot entry when device min number > 127, breaks efibootmgr
Public bug reported: This bug has also been reported and fixed on github, but is present in the version of libefivar0 present in Ubuntu 15.10: https://github.com/rhinstaller/efivar/issues/33 This bug breaks efibootmgr when trying to setup an EFI boot entry for a device with a minor number > 127: E.g. $ sudo efibootmgr --create --disk /dev/sdk --part 1 --label "GRUB2 Shim" --loader "\\EFI\\ubuntu\\shimx64.efi" efibootmgr: Could not set variable: No such file or directory efibootmgr: Could not prepare boot variable: No such file or directory $ lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdk 8:160 1 3.8G 0 disk └─sdk18:161 1 1G 0 part /boot/efi This also seems to break Ubuntu 15.10 upgrades and install on system where the EFI boot device has a minor number >127. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libefivar0 0.21-1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 23 17:41:28 2015 Dependencies: gcc-5-base 5.2.1-22ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-22ubuntu2 InstallationDate: Installed on 2014-04-27 (544 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: efivar UpgradeStatus: Upgraded to wily on 2015-10-23 (0 days ago) ** Affects: efivar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509570 Title: efivar-0.21 fails to create boot entry when device min number > 127, breaks efibootmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1509570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509326] Re: Various instabilities around hibernate, standby, and display control
** Tags added: latest-bios-a16 ** Summary changed: - Various instabilities around hibernate, standby, and display control + Various instabilities after resuming from standby -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509326 Title: Various instabilities after resuming from standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501041] Re: No visible display in non gnome sessions when using nvidia drivers via nvidia-prime until screen goes to sleep, then waked up
** Summary changed: - No visible display in ubuntu session when using nvidia drivers via nvidia-prime until screen goes to sleep, then waked up + No visible display in non gnome sessions when using nvidia drivers via nvidia-prime until screen goes to sleep, then waked up -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501041 Title: No visible display in non gnome sessions when using nvidia drivers via nvidia-prime until screen goes to sleep, then waked up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1501041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1487524] Re: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range
Berg Lloyd-Haig, as this report is closed, it has nothing to do with your problem. Hence, it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1487524 Title: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1487524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400068] Re: [ASUS X200MA] Brightness keys do not work
In Ubuntu 15.10 the fn brightness key problem is still persistent. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400068 Title: [ASUS X200MA] Brightness keys do not work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1400068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1487524] Re: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: 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/1487524 Title: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1487524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509305] Re: Kernel not upgraded during upgrade from Vivid to Wily if linux-generic not installed
I see. Nice catch Brian. Thanks. Shouldn't this bug report be closed then? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509305 Title: Kernel not upgraded during upgrade from Vivid to Wily if linux-generic not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1509305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1487524] Re: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range
** Project changed: linux => ubuntu ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1487524 Title: 14e4:43ba Broadcom BCM43602 not seeing 5Ghz range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1487524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508892] Re: cursor not clicking at the login screen after suspend
sanekt, please again see https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1508892/comments/2 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508892 Title: cursor not clicking at the login screen after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1508892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509470] Re: Sound very low in subwoofer.
http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a9059be749b6043d6cbc5b79652e8a4adda8994e http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=979f19a434733afba0480e2ba45698362e05 you got low sound because other four channels will get a high-pass filter but your subwoofer are using the stereo sigmal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509470 Title: Sound very low in subwoofer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1509470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501345] Re: linux-image-3.13.0-65-generic breaks serial communication
I can confirm that my Weather sensors->Arduino->USB->(Python+Apache+XUbuntu) serial communication is back to reporting my weather 24/7 as normal. Your assistance in fixing this quickly for us is greatly appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501345 Title: linux-image-3.13.0-65-generic breaks serial communication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1501345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508407] Re: libre office impress display broken gradient in slide show
Biji, could you please run the following command from a terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1508407 Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information. ** No longer affects: libreoffice (Ubuntu) ** Package changed: xserver-xorg-video-intel (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508407 Title: libre office impress display broken gradient in slide show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1508407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452405] Re: wmctrl cannot move windows into certain positions
The bug still exists in a freshly-updated 15.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452405 Title: wmctrl cannot move windows into certain positions To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1452405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508574] kili (amd64) - tests ran: 1, failed: 1
tests ran: 1, failed: 1; http://kernel.ubuntu.com/testing/3.19.0-32.37~14.04.1/kili__3.19.0-32.37~14.04.1__2015-10-23_19-17-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508574 Title: linux-lts-vivid: 3.19.0-32.37~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1508574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495112] Re: Keyboard doesn't work for crypt passphrase on bootup
mash, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495112/comments/14 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495112 Title: Keyboard doesn't work for crypt passphrase on bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507091] Re: Corrupted low memory on Ubuntu 15.04
llewellyn709, it will help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507091 Title: Corrupted low memory on Ubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509470] Re: Sound very low in subwoofer.
http://support.creative.com/kb/showarticle.aspx?sid=4699 4.1 Analog Speaker System In a 4.1 configuration, 4 satellites (front left and right, rear left), and 1 subwoofer. There are total of 5 speakers. The subwoofer only outputs lower frequencies from a stereo signal, not from a true subwoofer signal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509470 Title: Sound very low in subwoofer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1509470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509565] Re: CVE-2015-7885
CVE-2015-7885 ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Vivid) Status: New => Inva
[Bug 1509565] [NEW] CVE-2015-7885
*** This bug is a security vulnerability *** Public security bug reported: info leak in dgnc ioctl Break-Fix: - 4b6184336ebb5c8dc1eae7f7ab46ee608a748b05 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-flo (Ubuntu) Importance: Undecided Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-goldfish (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-raring (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-saucy (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Affects: linux-mako (Ubuntu) Importance: Undecided Status: New ** Affects: linux-manta (Ubuntu) Importance: Undecided Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance: Low
[Bug 1509566] [NEW] /usr/bin/nm-connection-editor:11:_gtk_tree_path_new_from_rbtree:gtk_tree_view_size_allocate:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager-applet. This problem was most recently seen with version 0.9.10.1-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/884a5701d173f4ed76953bba323d7905525db346 contains more details. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: kylin-14.10 kylin-15.04 trusty utopic vivid wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509566 Title: /usr/bin/nm-connection- editor:11:_gtk_tree_path_new_from_rbtree:gtk_tree_view_size_allocate:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1509566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509567] [NEW] /usr/sbin/lightdm-gtk-greeter:11:FcValueCanonicalize:FcConfigCompareValue:FcListValueListMatchAny:FcListPatternMatchAny:FcConfigPatternsMatch
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding lightdm-gtk-greeter. This problem was most recently seen with version 2.0.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/95295b8712e288d5ef225ef309badcaf3a09102c contains more details. ** Affects: lightdm-gtk-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: trusty utopic vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509567 Title: /usr/sbin/lightdm-gtk- greeter:11:FcValueCanonicalize:FcConfigCompareValue:FcListValueListMatchAny:FcListPatternMatchAny:FcConfigPatternsMatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1509567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509564] [NEW] CVE-2015-7884
*** This bug is a security vulnerability *** Public security bug reported: info leak in vivid-osd ioctl Break-Fix: - eda98796aff0d9bf41094b06811f5def3b4c333c ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-flo (Ubuntu) Importance: Undecided Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-goldfish (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-raring (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-saucy (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Affects: linux-mako (Ubuntu) Importance: Undecided Status: New ** Affects: linux-manta (Ubuntu) Importance: Undecided Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Low Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Low Status: New ** Affects: linux (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Low Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Low Status: Invalid ** Affects: linux (Ubuntu Vivid) Importance:
[Bug 1406612] Re: Black screen while playing youtube video in chrome.
CoffeeandNicotine, it will help immensely if you filed a new report with Ubuntu via a terminal: ubuntu-bug xorg Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Also, alease feel free to subscribe me to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1406612 Title: Black screen while playing youtube video in chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509564] Re: CVE-2015-7884
CVE-2015-7884 ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Vivid) Status: New => Inva
[Bug 1503979] Re: ubuntu-support-status throws exeption No date tag found (regression)
Note that on a trusty host I have where ubuntu-support-status doesn't throw a traceback, the following files exist: -rw-r--r-- 1 root root 64441 Oct 22 23:53 /var/lib/apt/lists/ubuntu-mirror.nxnw.org_ubuntu_dists_trusty-security_InRelease -rw-r--r-- 1 root root 63459 Oct 1 23:28 /var/lib/apt/lists/ubuntu-mirror.nxnw.org_ubuntu_dists_trusty-security_Release The latter being outdated with respect to the former. apt should probably be cleaning these out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503979 Title: ubuntu-support-status throws exeption No date tag found (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1503979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506562] Re: Ubuntu 15.10 Beta 2 fonts change after reboot
I just installed freshly Ubuntu 15.10 using the Greek locale. I did not make any changes to the settings. Indeed, the fonts look terrible and different from previous versions of Ubuntu. The reason is that, instead of showing the Ubuntu font family, the Dejavu font family is shown by default. Something has changed that makes Ubuntu 15.10 to show Dejavu instead of the Ubuntu font. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1506562 Title: Ubuntu 15.10 Beta 2 fonts change after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1506562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495983] Re: [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32
So when a new ISO will be released? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495983 Title: [Hyper-V] kernel panic occurs when installing Ubuntu Server 15.10 x32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508856] Re: CVE-2015-7872
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Description changed: Keyrings crash triggerable by unprivileged user - Break-Fix: - ce1fad2740c648a4340f6f6c391a8a83769d2e8c + Break-Fix: - f05819df10d7b09f6d1eb6f8534a8f68e5a4fe61 + Break-Fix: - 911b79cde95c7da0ec02f48105358a36636b7a71 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508856 Title: CVE-2015-7872 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416445] Re: fonts selector misses fonts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-tweak-tool (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/1416445 Title: fonts selector misses fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweak-tool/+bug/1416445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509563] Re: CVE-2015-7837
CVE-2015-7837 ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-mvl-dove (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ec2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-ti-omap4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: linux-lts-trusty (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-trusty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-armadaxp (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-mvl-dove (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Vivid) Status: New => Inva
[Bug 1509563] [NEW] CVE-2015-7837
*** This bug is a security vulnerability *** Public security bug reported: Linux kernel - securelevel/secureboot bypass. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-armadaxp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ec2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-flo (Ubuntu) Importance: Undecided Status: New ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-goldfish (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-maverick (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-raring (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-saucy (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-trusty (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Affects: linux-lts-vivid (Ubuntu) Importance: Undecided Status: New ** Affects: linux-mako (Ubuntu) Importance: Undecided Status: New ** Affects: linux-manta (Ubuntu) Importance: Undecided Status: New ** Affects: linux-mvl-dove (Ubuntu) Importance: Undecided Status: New ** Affects: linux-ti-omap4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-ec2 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Precise) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-raring (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-trusty (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux-lts-utopic (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-lts-vivid (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mako (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Precise) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Precise) Importance: Medium Status: New ** Affects: linux (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-armadaxp (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ec2 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-flo (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-fsl-imx51 (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-goldfish (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-backport-maverick (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-backport-natty (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-lts-quantal (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-raring (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-saucy (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-trusty (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-lts-utopic (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-lts-vivid (Ubuntu Trusty) Importance: Medium Status: New ** Affects: linux-mako (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-manta (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-mvl-dove (Ubuntu Trusty) Importance: Medium Status: Invalid ** Affects: linux-ti-omap4 (Ubuntu Trusty) Importance: Medium Status: I
[Bug 1493888] Re: FGLRX incompatible with kernel 4.2
Yes - in the nicest possible way, HTF was this allowed to survive unfixed at release and WTF isn't this documented in the release notes for the Ubuntu-MATE flavour for one? Just how bad does a bug have to be to block a release? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1493888 Title: FGLRX incompatible with kernel 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1499606] Re: CVE-2015-5257
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => 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/1499606 Title: CVE-2015-5257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1499609] Re: CVE-2015-5283
** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => 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/1499609 Title: CVE-2015-5283 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1492189] Re: CVE-2015-0272
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-lts-utopic (Ubuntu Trusty) Status: New => 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/1492189 Title: CVE-2015-0272 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441108] Re: CVE-2015-2925
** Changed in: linux-lts-trusty (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => Fix Committed ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: New => 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/1441108 Title: CVE-2015-2925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1441108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502032] Re: CVE-2015-7613
** Changed in: linux-armadaxp (Ubuntu Precise) Status: New => 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/1502032 Title: CVE-2015-7613 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1502032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447256] Re: "Force UEFI" dialog displayed if user selects custom partitioning
I've confirmed Simos's observation. I've identified two variants of the problem, doing a test installation under VirtualBox: 1) The disk is unpartitioned (either with no partition table or with a GPT in which no partitions are defined) when ubiquity is launched. In this case, the error message appears AFTER the manual partitioning screen. Importantly, it does not appear to be possible to continue past this error in this case; both the "Continue" and "Go back" buttons are unresponsive. Thus, the claim in the release notes that this bug "is harmless since... you can proceed with the installation" is flat-out wrong. 2) The disk contains at least one partition when ubiquity is launched. (I tested with a single partition flagged as an ESP, but holding no filesystem.) In this case, the error appears BEFORE the manual partitioning screen, and the "Continue" button works. (I didn't test the "Go back" button.) In this case, the error is confusing but is not nearly so important. Because there seems to be no way out in the first case except to terminate ubiquity (by rebooting or using command-line tools to kill the process), and because the only fix is the (non-obvious) workaround of creating a partition table and at least one partition, I consider this bug to be serious. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447256 Title: "Force UEFI" dialog displayed if user selects custom partitioning To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1447256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1488815] Re: Kernel traces with skb_warn_bad_offload showing up during an AIO deployment on Ubuntu 14.04
** Changed in: openstack-ansible/trunk Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1488815 Title: Kernel traces with skb_warn_bad_offload showing up during an AIO deployment on Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1488815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509562] [NEW] no icons for menu, folders, directories, files
Public bug reported: no icons for menu, folders, directories, files I am using Xubuntu 15.10 as the Guest in Virtualbox 5.0.8 r103449. This happened after a recent Xubuntu update. Info: $ apt-cache policy dolphin dolphin: Installed: 4:15.08.2-0ubuntu1 Candidate: 4:15.08.2-0ubuntu1 Version table: *** 4:15.08.2-0ubuntu1 0 500 http://mirror.cogentco.com/pub/linux/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dolphin 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 23 17:35:08 2015 InstallationDate: Installed on 2015-06-01 (144 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150521) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dolphin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1509562/+attachment/4503565/+files/dolphin_noicons.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509562 Title: no icons for menu, folders, directories, files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1509562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1509556] [NEW] Kubuntu Wily upgrade screen glitch with 4.2 kernel
Note there is no such issue onthe same system's Debian partition using Debian's 4.2 kernel. Today I installed the latest mainline 4.3 ubuntu kernel and the issue remains. On 24 October 2015 at 08:10, Bryan Cebuliak <1509...@bugs.launchpad.net> wrote: > Public bug reported: > > On recent update from 15.04 to 15.10, the new 4.2 kernel is > associated withgraphics instability after a few seconds of GUI > use with mouse and keyboard making the GUI unusable. See > another person's same experience with intel graphics here: > askubuntu.com/questions/688649/kubuntu-wily-upgrade-screen-glitch > > Downgrading to the last 15.04kernel solves my issue. > > See result of ubuntu-bug linux from the terminal attached. > > ** Affects: ubuntu > Importance: Undecided > Status: New > > ** Attachment added: "ubuntu-bug linux output for new 4.2 kernel" > > https://bugs.launchpad.net/bugs/1509556/+attachment/4503556/+files/apport.linux-image-4.2.0-16-generic.tzsu1qt7.apport > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1509556 > > Title: > Kubuntu Wily upgrade screen glitch with 4.2 kernel > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1509556/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509556 Title: Kubuntu Wily upgrade screen glitch with 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1509556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509305] Re: Kernel not upgraded during upgrade from Vivid to Wily if linux-generic not installed
** Summary changed: - Kernel not upgraded during upgrade from Vivid to Wily + Kernel not upgraded during upgrade from Vivid to Wily if linux-generic not installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509305 Title: Kernel not upgraded during upgrade from Vivid to Wily if linux-generic not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1509305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508157] Re: wily kernel version removed after upgrade to wily
*** This bug is a duplicate of bug 1509305 *** https://bugs.launchpad.net/bugs/1509305 I've recreated this by removing linux-generic and not running sudo apt- get remove, so the root cause is the same as bug 1509305. Given that bug 1509305 is more succinct, I'm going to mark this as a duplicate of that. ** This bug has been marked a duplicate of bug 1509305 Kernel not upgraded during upgrade from Vivid to Wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508157 Title: wily kernel version removed after upgrade to wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1508157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459871] Re: arm64 images built w/ setjump module fail w/ license error
Here's a pull request against debian's git: The following changes since commit f71c8970804848681afe0eb0a597aefb9d4463a2: releasing package grub2 version 2.02~beta2-29 (2015-10-13 23:40:21 +0100) are available in the git repository at: https://git.launchpad.net/~dannf/grub2 people/dannf/arm64-setjmp- license for you to fetch changes up to 269a263bb6c706329fec0efa0b68d7bd100d4fbc: merge patched-people/dannf/arm64-setjmp-license into people/dannf/arm64-setjmp-license (2015-10-23 16:25:25 -0600) dann frazier (2): arm64/setjmp: Add missing license macro merge patched-people/dannf/arm64-setjmp-license into people/dannf/arm64-setjmp-license debian/.git-dpm| 4 +-- debian/changelog | 6 .../arm64-setjmp-Add-missing-license-macro.patch | 33 ++ debian/patches/series | 1 + grub-core/lib/arm64/setjmp.S | 2 ++ 5 files changed, 44 insertions(+), 2 deletions(-) create mode 100644 debian/patches/arm64-setjmp-Add-missing-license-macro.patch ** Description changed: - Including the setjmp module in an arm64-efi image will cause it to - immediately exit with an "incompatible license" error. + [Impact] + Any ARM64 GRUB image that includes the setjmp module will fail, reporting an "incompatible license" error. Ubuntu doesn't normally include this module in most images. The one exception I know of is MAAS which, by default, includes all modules when generating EFI images. MAAS currently has a hack to blacklist setjmp on arm64 because a fix wasn't available at the time - but I fear other users will try to do the same thing and hit this issue which can be difficult to track down. - http://lists.gnu.org/archive/html/grub-devel/2015-05/msg00150.html + [Test Case] + PXE boot a grub image on arm64 that includes the setjmp module: + + $ grub-mkimage -v -o grubaa64.efi -O arm64-efi -d + /usr/lib/grub/arm64-efi setjmp + + [Regression Risk] + The patch merely adds a license section to the module and it has been tested to work. ** Changed in: grub2 (Ubuntu Trusty) Status: New => Confirmed ** Changed in: grub2 (Ubuntu Xenial) Status: New => Confirmed ** Changed in: grub2 (Ubuntu Wily) Status: New => Confirmed ** Changed in: grub2 (Ubuntu Vivid) 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/1459871 Title: arm64 images built w/ setjump module fail w/ license error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1459871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Final proposed patch for now. Uploaded to ppa:serge-hallyn/lxc-natty for wily. Installing this on a fresh ubuntu-cloud wily container (i.e. a broken one) results in working lxcbr0 on new subnet. ** Patch added: "lxcnet8.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+attachment/4503564/+files/lxcnet8.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1506562] Re: Ubuntu 15.10 Beta 2 fonts change after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: 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/1506562 Title: Ubuntu 15.10 Beta 2 fonts change after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1506562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509559] [NEW] Lack sensitivity mouse option
Public bug reported: The sensitivity of my gamer mouse (Multilaser M3T4L W4R M0207) is high, there isn't sensitivity option in Ubuntu 15.10, I'm running a script to correct speed: #!/bin/bash xinput --set-prop "11" "Device Accel Constant Deceleration" 1.5 Please check this ... Thank you!!! ** Affects: 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/1509559 Title: Lack sensitivity mouse option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1509559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509559] Re: Lack sensitivity mouse option
Ubuntu 15.10 x64, there isn't sensitivity option. ** Attachment added: "Captura de tela de 2015-10-23 11-56-18.png" https://bugs.launchpad.net/ubuntu/+bug/1509559/+attachment/4503563/+files/Captura%20de%20tela%20de%202015-10-23%2011-56-18.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509559 Title: Lack sensitivity mouse option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1509559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459871] Re: arm64 images built w/ setjump module fail w/ license error
** Also affects: grub2 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Wily) 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/1459871 Title: arm64 images built w/ setjump module fail w/ license error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1459871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1278780] Re: apport takes too long to write crash report, appears to lock up phone
On Fri, Oct 23, 2015 at 01:07:16PM -, Martin Pitt wrote: > Steve Langasek [2015-10-22 18:11 -]: > > > * If we really want to dump, we could investigate into sendfile. I'm not > > > * entirely sure that it works with data coming in via stdin, but it's > > > * worth a try as we would avoid the kernel -> userspace copy. > > This is an interesting suggestion. It would imply requiring a second > > post-processing stage, to combine this file with the rest of the crash > > report in proper (compressed, base64-encoded) format; > How would that help? In any case you first need to put the core dump > from stdin onto the disk, and that's precisely the bit that we are > doing now (and not much more) and which takes so long. The difference is precisely in the putting of the core dump onto the disk. Today we write it out from apport; that means we copy the data out from the kernel into userspace, gzip it, base64 encode it, and then hand it back to the kernel (by writing it to the file). With sendfile(), we would be directly moving the core to the file of our choosing, *in kernel space*, without any userspace processing. It's not even necessary that we flush the disk buffers, so the slow disk writes don't necessarily happen before apport returns. This doesn't guarantee that sendfile will actually be faster. But I think we need to measure this and find out, rather than assuming one way or the other. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278780 Title: apport takes too long to write crash report, appears to lock up phone To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1278780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508574] onza (i386) - tests ran: 153, failed: 0
tests ran: 153, failed: 0; http://kernel.ubuntu.com/testing/3.19.0-32.37~14.04.1/onza__3.19.0-32.37~14.04.1__2015-10-23_19-43-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508574 Title: linux-lts-vivid: 3.19.0-32.37~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1508574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509558] Re: package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509558 Title: package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1509558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509558] [NEW] package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Cannot install new softwares ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata 2015g-0ubuntu0.14.04 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 Date: Fri Oct 23 17:06:56 2015 DuplicateSignature: package:tzdata:2015g-0ubuntu0.14.04:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-28 (56 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: tzdata Title: package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509558 Title: package tzdata 2015g-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1509558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503979] Re: ubuntu-support-status throws exeption No date tag found (regression)
Here's what I see on wily when making the following change:
--- /usr/bin/ubuntu-support-status 2015-10-08 22:07:36.0 -0700
+++ ./ubuntu-support-status 2015-10-23 14:49:44.092719697 -0700
@@ -48,7 +48,7 @@
# check the release date and show support information
# based on this
if not time_t:
-raise Exception("No date tag found")
+raise Exception("No date tag found for %s on package %s" % (releasef,
pkgname))
release_date = datetime.datetime.fromtimestamp(time_t)
now = datetime.datetime.now()
$ python3 ./ubuntu-support-status
Traceback (most recent call last):
File "./ubuntu-support-status", line 135, in
pkg.name, support_tag)
File "./ubuntu-support-status", line 51, in get_maintenance_status
raise Exception("No date tag found for %s on package %s" % (releasef,
pkgname))
Exception: No date tag found for
/var/lib/apt/lists/ubuntu-mirror.nxnw.org_ubuntu_dists_wily_Release on package
abi-compliance-checker
There is no /var/lib/apt/lists/ubuntu-
mirror.nxnw.org_ubuntu_dists_wily_Release available, the specific file
is /var/lib/apt/lists/ubuntu-mirror.nxnw.org_ubuntu_dists_wily_InRelease
(note the difference between Release and InRelease).
Looking at https://wiki.debian.org/RepositoryFormat both Release and
InRelease files are legitimate entries (the former is externally signed
by gpg, the latter inline signed), so it looks like
get_release_filename_for_pkg() from python-apt should be verifying that
the release file exists before returning it.
** Also affects: python-apt (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/1503979
Title:
ubuntu-support-status throws exeption No date tag found (regression)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1503979/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508993] bantam (amd64) - tests ran: 194, failed: 0
*** This bug is a duplicate of bug 1509480 *** https://bugs.launchpad.net/bugs/1509480 tests ran: 194, failed: 0; http://kernel.ubuntu.com/testing/4.2.0-17.20/bantam__4.2.0-17.20__2015-10-23_19-00-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508993 Title: linux: 4.2.0-17.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1508993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508993] dwalin (amd64) - tests ran: 66, failed: 66
*** This bug is a duplicate of bug 1509480 *** https://bugs.launchpad.net/bugs/1509480 tests ran: 66, failed: 66; http://kernel.ubuntu.com/testing/4.2.0-17.20/dwalin__4.2.0-17.20__2015-10-23_21-26-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508993 Title: linux: 4.2.0-17.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1508993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460192] Re: new themes in lxappareance does not apply until after login and logout.
Wasn't aware that I have the permission to do that, but it worked :P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460192 Title: new themes in lxappareance does not apply until after login and logout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1460192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509305] Re: Kernel not upgraded during upgrade from Vivid to Wily
I've recreated this by removing linux-generic and then running sudo apt- get autoremove. I then upgraded from Vivid to Wily and the kernel was not updated. ** Changed in: ubuntu-release-upgrader (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509305 Title: Kernel not upgraded during upgrade from Vivid to Wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1509305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460192] Re: new themes in lxappareance does not apply until after login and logout.
Fix now available in Wily FINAL version (out on Oct 22, 2015) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460192 Title: new themes in lxappareance does not apply until after login and logout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1460192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508157] Re: wily kernel version removed after upgrade to wily
** Summary changed: - Kernel not upgraded during Vivid -> Wily upgrade + wily kernel version removed after upgrade to wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508157 Title: wily kernel version removed after upgrade to wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1508157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507224] Re: mplayer keyboard controls don't work with audio files
Nobody else with this issue? I reported the issue on askubuntu as well: http://askubuntu.com/questions/682781/mplayer-suddenly-stopped- responding-to-keyboard-commands-what-gives Fruitless for now, just like here. No suggestions, anyone? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507224 Title: mplayer keyboard controls don't work with audio files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1507224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509556] [NEW] Kubuntu Wily upgrade screen glitch with 4.2 kernel
Public bug reported: On recent update from 15.04 to 15.10, the new 4.2 kernel is associated withgraphics instability after a few seconds of GUI use with mouse and keyboard making the GUI unusable. See another person's same experience with intel graphics here: askubuntu.com/questions/688649/kubuntu-wily-upgrade-screen-glitch Downgrading to the last 15.04kernel solves my issue. See result of ubuntu-bug linux from the terminal attached. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "ubuntu-bug linux output for new 4.2 kernel" https://bugs.launchpad.net/bugs/1509556/+attachment/4503556/+files/apport.linux-image-4.2.0-16-generic.tzsu1qt7.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509556 Title: Kubuntu Wily upgrade screen glitch with 4.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1509556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460192] Re: new themes in lxappareance does not apply until after login and logout.
FIXED! Definitely. Thanks to the dev team. (using wily FINAL, no beta crud) ** Changed in: lxappearance (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lubuntu-artwork (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460192 Title: new themes in lxappareance does not apply until after login and logout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1460192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460192] Re: new themes in lxappareance does not apply until after login and logout.
^^ I wrote this above in "Comment on this change" but it appeared here. Tough luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460192 Title: new themes in lxappareance does not apply until after login and logout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/1460192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447256] Re: "Force UEFI" dialog displayed if user selects custom partitioning
Workaround #1: Create partition table using "gparted". Create one 200MB partition with filesystem FAT32. Then click Appy so that "gparted" applies the change. Then, change the flag of the partition (right-click on partition, then Manage Flags) in order to add the "efi" flag. Save and exit. It should be possible to using the installer (ubiquity) and complete the installation. Workaround #2: Do not use the "Something else" option in the installer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447256 Title: "Force UEFI" dialog displayed if user selects custom partitioning To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1447256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426887] Re: Full screen app has a white stripe on top after switching to another window
This has been fixed in Ubuntu 15.04 ** Changed in: gnome-panel (Ubuntu) Status: New => Fix Released ** Changed in: metacity (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426887 Title: Full screen app has a white stripe on top after switching to another window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1426887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
Action plan: Stage 1 - Configure lxc-net at boot rather than at install. * This addresses the network failure for 15.10 containers started on 15.10 hosts (patch above in comment #6) Stage 2 - Start lxc-net through systemd on the first launch of an LXC container. * This mitigates the unroutable 10.0.x.0/16 network issue for general cloud image users. With this step we’re back to Trusty function. * This will work for privileged users, like Juju, without any interaction. Unprivileged users will be directed to start the service on the first container launch. Next action: - serge-hallyn working on patch (last update in comment #7) and code in ppa:serge-hallyn/lxc-natty. Patch is not yet ready for upload and serge will update as he progresses. - Once ready, uploaded, and published in -proposed, email ring rcj/utlemming and we'll ensure cloud image builder picks this up ASAP to build -proposed images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508799] Re: No BLUETOOTH adapters have been found on laptop sony vaio pcg-71c12v
In terminal do sudo modprobe -v ath3k Any errors? I am using the same bluetooth chipset with the same kernel and it works without any issue but I know Atheros bluetooth devices need ath3k loaded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508799 Title: No BLUETOOTH adapters have been found on laptop sony vaio pcg-71c12v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1320634] Re: The "blacklisted-media-players" key doesn't work
I think that this bug is not low importance. Just search Google to see how many people are trying to solve this problem with hacking around and waisting time to solve this. Unfortunately you can't disable sound menu integration any more in VLC and neither have I found a related setting in Rhythmbox. To be honest I haven't seen any media player where I was able to configure sound menu integration. >From what I have seen a media player has either no sound menu integration or >if it has one you can't disable it. So it turns out that the idea that "applications have UI to disable integration" was not realized in practice. Currently the only way for VLC to remove the integration I have found is: sudo mv -vi /usr/lib/vlc/plugins/control/libdbus_plugin.so /usr/lib/vlc/plugins/control/libdbus_plugin.so.backup Is this really a good way to go? I would really be happy to see support for "blacklisted-media-players" removed only after all the media players that have sound menu integration have also the option to disable it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1320634 Title: The "blacklisted-media-players" key doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1320634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447256] Re: "Force UEFI" dialog displayed if user selects custom partitioning
The installer is stuck at this dialog box. Neither button (Go Back or Continue) work. The user is unable to complete the installation (and has to either reboot or kill ubiquity before trying again). ** Attachment added: "force-uefi-installation-stuck.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1447256/+attachment/4503551/+files/force-uefi-installation-stuck.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447256 Title: "Force UEFI" dialog displayed if user selects custom partitioning To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1447256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447256] Re: "Force UEFI" dialog displayed if user selects custom partitioning
I am installing Ubuntu 15.10 (final) and I encountered this issue (exactly as described by the original poster). This issue is mentioned in https://wiki.ubuntu.com/WilyWerewolf/ReleaseNotes as well, in the Known Issues section. However, in my case the Force UEFI dialog cannot be closed, thus, it is not possible to continue the installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447256 Title: "Force UEFI" dialog displayed if user selects custom partitioning To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1447256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
** Summary changed: - lxc postinst script checks available interfaces, can choose + pre-installed lxc in cloud image produces broken lxc (and later lxd) containers ** Description changed: [Problem] The released wily image preinstalls lxc, which breaks the assumption that lxc's preinst packaging script makes: It inspects the network to try to pick a 10.0.N.0 network that isn't being used, with N starting at 3, so this appears to have picked 10.0.3.0 when it was installed on whatever system was generating the - image. This conflicts with the network that eth0 gets attached to when - the image is brought up in a container, because it gets attached to the - host's lxcbr0, which is using 10.0.3.x. + image. - This affects LXC, and should affect LXD but doesn't currently, as the metadata used for lxd images is still pointing to a beta2 release. - The easiest way to reproduce this is to use the ubuntu-cloud lxc template on a wily host: + When a container is started, it will dhcp on eth0 and get 10.0.3.X as + expected. The problem comes when the lxc-net service that is already + installed in that container starts and configures *its* lxcbr0 with + 10.0.3.X. The networking inside the container is broken at that point. + + This affects LXC containers, and should affect LXD containers but + doesn't currently, as the metadata used for lxd images is still pointing + to a beta2 release (bug 1509390). + + The easiest way to reproduce this is to use the ubuntu-cloud lxc + template on a wily host. [Test Case] 1.) Verify expectation for each image - -disk1.img cloud image, check for file - -root.tar.xz image (used by lxd) and check for file - -root.tar.gz image (used by lxc) For each of those images, verify: a.) A cloud image should not have /etc/default/lxc-net b.) lxd should be installed (dpkg-query --show | grep lxd) 2.) Start instance from updated image and start instance in lxc inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxc-create -t ubuntu-cloud -n bugcheck -- --release=wily --stream=daily # wait until lxc-ls --fancy shows 'running' lxc-attach -n bugcheck wget http://ubuntu.com 3.) Start instance from updated image and start instance in lxd inside launch instance on openstack or kvm or other verify lxcbr0 bridge exists lxd import-images ubuntu wily lxc launch ubuntu # wait some amount lxc attach bugcheck wget http://ubuntu.com [Regression Potentional] The highest chance for fallout is a change in the /16 network that is chosen conflicting with some existing service. [Other Info] Default apt install of lxc has always picked some 10.0.X.0/16 network to use for its lxcbr0 bridge. That network (often 10.0.3.0/16) would then be unreachable from the host. The same behavior occurs with libvirt-bin and many other such services. We are moving that logic to happen the first time that 'lxc-net' service starts. This means first boot for a cloud instance rather than cloud-image build time. [Work around] To patch / fix an existing cloud image to make lxc and lxd guests start simply change the config of /etc/default/lxc-net to have something other than 10.0.3.0. - sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && - sudo service lxc-net stop && - sudo service lxc-net start + sudo sed -i '/^LXC.*10[.]0[.][0-9][.]/s/10.0.[0-9]./10.0.4./g' /etc/default/lxc-net && + sudo service lxc-net stop && + sudo service lxc-net start -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with kernel 4.2
Same here of course. Thanks to all involved in reporting, and fixing--- Rant:How is it possible that 15.10 goes to release with a bug like this, affecting so many users (yes, the ubuntu releases should be tested on nvidia and amd moderna cards before release). Yes, I do love Ubuntu, and Yes I know it should be AMD releasing their source and specs, but still -- shouldnẗ this be a release blocker. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1493888 Title: FGLRX incompatible with kernel 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508993] ms10-35-mcdivittB0 (arm64) - tests ran: 167, failed: 3
*** This bug is a duplicate of bug 1509480 *** https://bugs.launchpad.net/bugs/1509480 tests ran: 167, failed: 3; http://kernel.ubuntu.com/testing/4.2.0-17.20/ms10-35-mcdivittB0__4.2.0-17.20__2015-10-23_18-57-00/results-index.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508993 Title: linux: 4.2.0-17.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1508993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509414] Re: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers
new patch. It upgrades a broken container fine, but lxc-net is not properly started until I manually call /usr/lib/x86_64-linux-gnu/lxc/lxc-net stop /usr/lib/x86_64-linux-gnu/lxc/lxc-net start or reboot ** Patch added: "lxcnet6.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+attachment/4503549/+files/lxcnet6.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509414 Title: pre-installed lxc in cloud image produces broken lxc (and later lxd) containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437846] Re: akonadi mysql 5.6 crash with signal 11
I've had similar problems. It seems to me that the default Akonadi options for MySQL include a table_cache parameter, but it's been deprecated since 5.1 and in 5.6 prevents a start of the database. Removing this options did the trick for me. In MariaDB documentation there's a remark that "all versions of MariaDB are based on MySQL 5.1 and greater, thus the table_cache option is deprecated in favor of table_open_cache." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437846 Title: akonadi mysql 5.6 crash with signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1437846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
