[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Documentation is horribly insufficient in this regard. To quote the link given, "Ubuntu Desktop flavour now always tracks HWE kernel (hardware enablement). It means that from 20.04.2 release Ubuntu Desktop will gain new major kernel versions every 6 months through to summer of 2022". The words "from 20.04.2 release Ubuntu Desktop will gain new major kernel versions every 6 months" speak volumes, sadly incorrect volumes. 20.04.2 is not even due for release until next month but we've been getting HWE kernel updates for a couple of weeks already! All of the following documentation needs serious updating and must include methods to remain on the GA kernel if one wishes: The first, also from the release notes, states clearly "Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4": https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Updated_Packages None of these have been updated to adequately reflect the change to opt- out of HWE rather than opt-in if using original (20.04) or first point release (20.04.1) installation media as had always been the case previously. https://wiki.ubuntu.com/Kernel/LTSEnablementStack https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack https://ubuntu.com/kernel/lifecycle -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS:
[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
I filed bug #1912032 concerning the failure of nvidia drivers to install during a fresh installation of Ubuntu 20.04.1 because when download updates is selected it auto-updates to a 5.8 series kernel during installation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
I updated the bug description to better explain why I believe this is a bug, but I left the original content below the break. ** Description changed: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at - downgrading the X stack in 16.04 and 18.04 were always successful! But + downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was
[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
I added the packaging tag because this was a packaging error in the 20.04 and 20.04.1 images. ** Tags added: packaging ** Description changed: + Beginning about January 8th Focal users that installed Focal using + either the Ubuntu 20.04 or 20.04.1 installation media began getting + updated to the 5.8 series linux kernel. Those who had installed using + the Ubuntu Focal Beta were not effected. This is because Focal Beta was + properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images + were built with ‘linux-generic-hwe-20.04‘. This can be easily verified + by looking at the iso manifest: + + https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- + amd64.manifest + + Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be + downloaded here: + + https://old-releases.ubuntu.com/releases/20.04/ + + The expected behavior is for Ubuntu Focal users to remain on the 5.4 + series kernel unless they install with 20.04.2 or later images as + indicated here: + + https://wiki.ubuntu.com/Kernel/LTSEnablementStack + + While not entirely updated it says “if one wants to remain on the + original GA (General Availability) stacks, the options [include]; + Install from a previous + 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point + release and update”. + + Jump just below that to the Focal specific notes and it says “The + 20.04.2 and newer point releases will ship with an updated kernel and X + stack by default for the desktop”. Since 20.04.2 is not even due for + release until next month it makes no sense for updates to the 5.8 series + kernel to be occurring unless the focal-proposed repos are enabled even + if HWE protocols had been changed. + + It’s also worth noting that thankfully no accompanying HWE X stack is + yet available in the repos. I say thankfully because my efforts at + downgrading the X stack in 16.04 and 18.04 were always successful! But + the lack of a matching X stack may explain the many complaints on the + forums about broken graphics??? + + It’s also worth noting that even the release notes say that “Ubuntu + 20.04 LTS is based on the long-term supported Linux release series 5.4“. + + https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel + + Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are + supposed to be supported with the 5.4 series kernel for the entire 5 + year life span: + + https://ubuntu.com/kernel/lifecycle + + The other flavors’ 20.04 and 20.04.1 images were all built correctly + with ‘linux-generic’ with the possible exception of Ubuntu Studio which + uses a kernel stack I’m not familiar with. I’m also uncertain about + Ubuntu server because I’m simply not familiar with it. + + Original bug description below: + + ## + Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were
[Touch-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Unfortunately apport-collect just says "no additional info collected" (see pic added). I presume because 'ubuntu-meta' is not an installed package? I struggled a bit trying to decide what the best way was to report a bug like this because it's not actually a bug in the kernel itself, it's just that I believe the 5.8 series kernel should not be installed without specific user action to do so. That had been the case in the past. LTS installs using the original iso or the first point release iso would remain on the original GA (General Availability) throughout the duration of the 5 year support cycle. In fact I see the HWE Wiki has been updated to say "The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop": https://wiki.ubuntu.com/Kernel/LTSEnablementStack And 20.04.2 is not due for release until early February. It's worth mentioning that LTS point releases are frequently delayed by a week or two if bugs are encountered. Anyway I would expect an installation performed with 20.04.2 media to include the HWE kernel. You'll also notice that they do say "kernel and X stack" and as mentioned above the HWE X stack is not yet even in the repos! I will probably be testing the 20.04.2 daily build very soon and I'll then report a bug against 'linux-generic-hwe-20.04' making note that the accompanying X stack is missing. And yes, this does effect only Ubuntu Desktop because as mentioned above I checked some of the other flavors manifests. Only the Ubuntu isos have the HWE version of kinux-generic installed. ** Attachment added: "Screenshot from 2021-01-14 19-45-49.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+attachment/5453132/+files/Screenshot%20from%202021-01-14%2019-45-49.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: New Bug description: Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1911614] [NEW] Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Public bug reported: Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic Status in ubuntu-meta package in Ubuntu: New Bug description: Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584509] Re: hybrid CDs/DVDs not mounted in xenial
If you have util-linux - 2.27.1-6ubuntu3.1 this should be fixed. Have you updated Lubuntu since installing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1584509 Title: hybrid CDs/DVDs not mounted in xenial Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Released Bug description: * Impact some CDs are not listed in the desktop UIs * Test case under unity7 insert a video DVD in your drive, you should get prompted about it and have the device listed in the launcher/nautilus * Regression potential check that devices keep being correctly listed/mounted This bug affects both the X64 and X32 bit versions of the latest ubuntu 16.04 it does not occur with ubuntu 15.10 or earlier. The problem is when a known good CD-R is placed in the drive, it is not mounted automatically. However, if it is a bootable CD-R and you select the boot option of the BIOS it will function normally. Also, When a blank CD-R is inserted into the drive, it is mounted automatically, but disk creation software reports an erroneous amount of free space available. Such as 247 MB or 512 MB when the disk is a 700 MB disk. However, if you proceed to record to the disk, even with an ISO image greater than the supposed available capacity, it records just fine. Other disk types such as DVD, audio, small cd-r work fine. This only seems to affect the larger, full size cd-r's ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: karl 1886 F pulseaudio /dev/snd/controlC0: karl 1886 F pulseaudio CurrentDesktop: Unity Date: Sun May 22 14:38:13 2016 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=03cb5141-d254-414a-950b-2235e068035a HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-03-09 (73 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Gateway DX4380G ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=da27bf85-d849-43b8-a8f2-8fdac4f37784 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 14:38:31.725: The udisks-daemon is running (name-owner :1.96). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-A1 dmi.board.name: DX4380G dmi.board.vendor: Gateway dmi.board.version: 1.02 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr: dmi.product.name: DX4380G dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1584509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584509] Re: hybrid CDs/DVDs not mounted in xenial
Wily reaches EOL this month: https://wiki.ubuntu.com/Releases -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1584509 Title: hybrid CDs/DVDs not mounted in xenial Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Released Bug description: * Impact some CDs are not listed in the desktop UIs * Test case under unity7 insert a video DVD in your drive, you should get prompted about it and have the device listed in the launcher/nautilus * Regression potential check that devices keep being correctly listed/mounted This bug affects both the X64 and X32 bit versions of the latest ubuntu 16.04 it does not occur with ubuntu 15.10 or earlier. The problem is when a known good CD-R is placed in the drive, it is not mounted automatically. However, if it is a bootable CD-R and you select the boot option of the BIOS it will function normally. Also, When a blank CD-R is inserted into the drive, it is mounted automatically, but disk creation software reports an erroneous amount of free space available. Such as 247 MB or 512 MB when the disk is a 700 MB disk. However, if you proceed to record to the disk, even with an ISO image greater than the supposed available capacity, it records just fine. Other disk types such as DVD, audio, small cd-r work fine. This only seems to affect the larger, full size cd-r's ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: karl 1886 F pulseaudio /dev/snd/controlC0: karl 1886 F pulseaudio CurrentDesktop: Unity Date: Sun May 22 14:38:13 2016 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=03cb5141-d254-414a-950b-2235e068035a HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-03-09 (73 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Gateway DX4380G ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=da27bf85-d849-43b8-a8f2-8fdac4f37784 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 14:38:31.725: The udisks-daemon is running (name-owner :1.96). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-A1 dmi.board.name: DX4380G dmi.board.vendor: Gateway dmi.board.version: 1.02 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr: dmi.product.name: DX4380G dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1584509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584509] Re: hybrid CDs/DVDs not mounted in xenial
Do we need to take any additional action to move this from Xenial- proposed to updates now that verification is done? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1584509 Title: hybrid CDs/DVDs not mounted in xenial Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Bug description: * Impact some CDs are not listed in the desktop UIs * Test case under unity7 insert a video DVD in your drive, you should get prompted about it and have the device listed in the launcher/nautilus * Regression potential check that devices keep being correctly listed/mounted This bug affects both the X64 and X32 bit versions of the latest ubuntu 16.04 it does not occur with ubuntu 15.10 or earlier. The problem is when a known good CD-R is placed in the drive, it is not mounted automatically. However, if it is a bootable CD-R and you select the boot option of the BIOS it will function normally. Also, When a blank CD-R is inserted into the drive, it is mounted automatically, but disk creation software reports an erroneous amount of free space available. Such as 247 MB or 512 MB when the disk is a 700 MB disk. However, if you proceed to record to the disk, even with an ISO image greater than the supposed available capacity, it records just fine. Other disk types such as DVD, audio, small cd-r work fine. This only seems to affect the larger, full size cd-r's ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-22-generic 4.4.0-22.40 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: karl 1886 F pulseaudio /dev/snd/controlC0: karl 1886 F pulseaudio CurrentDesktop: Unity Date: Sun May 22 14:38:13 2016 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=03cb5141-d254-414a-950b-2235e068035a HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2016-03-09 (73 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Gateway DX4380G ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=da27bf85-d849-43b8-a8f2-8fdac4f37784 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 14:38:31.725: The udisks-daemon is running (name-owner :1.96). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-A1 dmi.board.name: DX4380G dmi.board.vendor: Gateway dmi.board.version: 1.02 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr: dmi.product.name: DX4380G dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1584509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)
*** This bug is a duplicate of bug 1584509 *** https://bugs.launchpad.net/bugs/1584509 ** This bug has been marked a duplicate of bug 1584509 hybrid CDs/DVDs not mounted in xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1577768 Title: 16.04 some dvd do not mount automatically (but do in 14.04) Status in gvfs package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Bug description: Hi, here is a dvd. And ubuntu 16.04. When I insert that dvd, it does not show anywhere, neither in launcher nor in nautilus. But I'm able to read that dvd using vlc through menu media / open a disc. I can manually mount that dvd with sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/ Once mounted there's a dvd icon in launcher and it appears also in nautilus left panel. That same dvd automatically mounts when running ubuntu 14.04 on the same computer. I have also tested other dvd's on ubuntu 16.04 and *most* of them show / mount as expected. But *all* of them automatically show / mount in ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1577768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)
** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1577768 Title: 16.04 some dvd do not mount automatically (but do in 14.04) Status in gvfs package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: Hi, here is a dvd. And ubuntu 16.04. When I insert that dvd, it does not show anywhere, neither in launcher nor in nautilus. But I'm able to read that dvd using vlc through menu media / open a disc. I can manually mount that dvd with sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/ Once mounted there's a dvd icon in launcher and it appears also in nautilus left panel. That same dvd automatically mounts when running ubuntu 14.04 on the same computer. I have also tested other dvd's on ubuntu 16.04 and *most* of them show / mount as expected. But *all* of them automatically show / mount in ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1577768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial
We're 99% of the way there. Setting auto-login during install still doesn't work though so I filed bug 1571415. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1547297 Title: No auto login in Ubuntu GNOME Xenial Status in Ubuntu GNOME: Confirmed Status in accountsservice package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Confirmed Status in sddm package in Ubuntu: Confirmed Bug description: Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto login during installation, but once the installation was complete and I booted into Ubuntu GNOME I was asked for my password. I looked in the user UI and auto login was set to off, so I unlocked it, selected auto login = on, clicked on lock again, and rebooted but was once again asked for my password and the user UI once again showed auto login = off. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gdm3 3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Feb 18 20:26:14 2016 InstallationDate: Installed on 2016-02-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1547297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555237] Re: Upgrade from 14.04.4→ 16.04 dies midway taking out the session.
@ Tim Lunn, I typically turn off screen lock and set blank screen to never before beginning my upgrade tests but I suppose this time I should leave screen lock on and just increase blank screen to 30 minutes or so. Then if things seem even remotely buggy I'll compare the results between Ubuntu and Ubuntu GNOME release upgrades, and file a new bug report as needed. I should have time to do that this weekend so we'll have time to address any gdm or GNOME specific issues prior to release. If you have any other thoughts about performing the next round of release-upgrade tests please send me a PM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1555237 Title: Upgrade from 14.04.4→ 16.04 dies midway taking out the session. Status in dbus package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: STEPS: 1. Install 14.04.4 on a uefi securebooted system 2. update it 3. Install openssh-server for debug access 4. reboot 5. Hit alt+f2 6. Type update-manager -d and hit enter EXPECTED: I expected a smooth transition to 16.04 ACTUAL: System is completely taken out mid way through the process killing the session and x also no tty when hitting ctrl+alt+f1-6 --- TESTS RESULTS (from cyphermox): On amd64 (no EFI) under qemu/libvirt, qxl graphics: - upgrading just libglib2.0-0 from 16.04 on top of 14.04.4: PASS - upgrading ubuntu-desktop (running gnome-shell) 14.04.4 to 16.04: PASS - upgrading ubuntu-desktop (running xubuntu-session) 14.04.4 to 16.04: PASS - manually upgrading compiz and other packages to 16.04 versions; after adding xenial sources: - compiz and related packages (http://paste.ubuntu.com/15415280/) : PASS - xserver-xorg and related: PASS - unity and related: PASS - ubuntu-desktop: PASS - libgl1-mesa-dri: PASS - apt-get dist-upgrade: FAIL (screensaver may have kicked in) - standard upgrading 14.04.4 to 16.04; screensaver disabled: FAIL (looked fine, but upgrade eventually froze, might well be a different issue) - re-enabling screensaver after upgrade, before reboot: TODO (above failed) On ppc64el: - upgrading ubuntu-server 14.04.4 -> 16.04: PASS --- ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:0.220.8 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CrashDB: ubuntu Date: Wed Mar 9 17:01:27 2016 InstallationDate: Installed on 2016-03-04 (5 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Beta amd64 (20160224) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-03-09 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1555237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059872] Re: Error formatting disk using disk utility
@ Phillip Susi, if that's an indication that this bug won't be fixed in
Trusty then please change the status from Triaged to Won't fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1059872
Title:
Error formatting disk using disk utility
Status in DarGUI:
New
Status in OEM Priority Project:
New
Status in udisks2 package in Ubuntu:
Invalid
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux source package in Trusty:
Triaged
Status in util-linux package in Debian:
Fix Released
Bug description:
[Impact]
Formatting a SD card using the disk utility fails with an error
message
"Error formatting disk - Error synchronizing after initial wipe: Timed
out waiting for object (udisks-error-quark, 0)"
The underlying problem is that the "wipefs" tool from util-linux does
not work any more.
You can work around this bug in gnome-disk-utility using these steps:
* After selecting the SD card, instead of clicking the gear icon to format,
click the partition in the "Volumes" section.
* Delete the partition ("minus" icon)
* Create a new partition
[Test Case]
$ sudo modprobe scsi_debug dev_size_mb=200
# this creates a new /dev/sdX, usually /dev/sdb; check dmesg!
# now create a partition table
$ cat
[Touch-packages] [Bug 1547505] Re: package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
** Tags added: release-upgrader -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1547505 Title: package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: error occurred while updating from 15.10 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-6-generic 4.4.0-6.21 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: naveen 1479 F pulseaudio /dev/snd/controlC1: naveen 1479 F pulseaudio CRDA: country IN: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 20), (N/A) (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 20), (N/A) Date: Fri Feb 19 18:20:10 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=d9abc4f7-9e91-4ecd-842c-097a41546ed3 InstallationDate: Installed on 2015-12-13 (68 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 021: ID 04f3:0447 Elan Microelectronics Corp. Bus 001 Device 002: ID 0bda:579c Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20404 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed root=UUID=38b413f2-788a-4715-895f-8dae3d2bb707 ro noprompt persistent quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: Upgraded to xenial on 2016-02-19 (0 days ago) dmi.bios.date: 10/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A0CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Flex 2-14 dmi.board.vendor: LENOVO dmi.board.version: 31900059 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Flex 2-14 dmi.modalias: dmi:bvnLENOVO:bvrA0CN31WW:bd10/08/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoFlex2-14: dmi.product.name: 20404 dmi.product.version: Lenovo Flex 2-14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1547505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs
** Tags added: xenial ** Tags added: gvfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Two processes attempt to mount blank optical discs Status in OEM Priority Project: New Status in glib2.0 package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: This behavior can be reproduced using either a live USB or an installed version of the effected flavors. Simply insert a blank optical disc in the drive. The behavior differs slightly in Ubuntu GNOME as the notification to either Open with CD/DVD Creator or Eject is displayed twice - that is after simply clicking on the X to close that notification it closes but a new duplicate notification appaers immediately. The GNOME Classic session is not effected at all. In all other effected flavors and/or desktop environments a notification appears stating "Unable to mount Blank disc. Location is already mounted". Effected flavors and DE's include Ubuntu w/Unity, gnome-session-flashback, and Ubuntu MATE. Versions effected include Trusty, Utopic, and Vivid. I assume that two separate processes are actually attempting to mount the blank optical media, rather than just the file manager attemting to do so, because both Nautilus and Caja are effected (based on some of the comments below possibly also Nemo). While purely cosmetic in nature I'd certainly be willing to try and troubleshoot this if someone more tech savvy would provide some debugging instructions. Original content begins below: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497688] Re: dmsetup and libdevmapper1.02.1 fail to install, depend on each other
@ Willy, under Software & Updates > Updates tab did you have Notify me of a new Ubuntu version set to For LTS only or For any new release? If it's still set for LTS only that may explain the failure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1497688 Title: dmsetup and libdevmapper1.02.1 fail to install, depend on each other Status in apt package in Ubuntu: Invalid Status in apt source package in Trusty: Fix Committed Bug description: Test Case - 1) Install Ubuntu 14.04 LTS 2) Ensure /etc/update-manager/release-upgrades says normal 3) Try to upgrade to Vivid (15.04) 4) Observe a failure due to libdevmapper and dmsetup With the version of the package from -proposed the upgrade will complete successfully. Problem occured when I did a distribution upgrade with the "Software Updater" ProblemType: PackageDistroRelease: Ubuntu 15.04 Package: systemd-sysv (not installed) ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Sun Sep 20 08:44:57 2015 DuplicateSignature: package:systemd-sysv:(not installed):pre-dependency problem - not installing systemd-sysv ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2014-05-18 (490 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)SourcePackage: systemd Title: package systemd-sysv (not installed) failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1497688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497688] Re: dmsetup and libdevmapper1.02.1 fail to install, depend on each other
Why incomplete? Based on the original bug filing and Martin Pitt's follow up in comment #2 the problem is (or was) dmsetup and libdevmapper depending on each other. Has that dependency issue been addressed? I'm not complaining, just curious. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1497688 Title: dmsetup and libdevmapper1.02.1 fail to install, depend on each other Status in apt package in Ubuntu: Incomplete Bug description: Problem occured when I did a distribution upgrade with the "Software Updater" ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd-sysv (not installed) ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Sun Sep 20 08:44:57 2015 DuplicateSignature: package:systemd-sysv:(not installed):pre-dependency problem - not installing systemd-sysv ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2014-05-18 (490 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd Title: package systemd-sysv (not installed) failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1497688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs
This does still effect Ubuntu Ubuntu Mate Wily as well as Debian Mate Jessie. I'll try to file a Debian bug report ASAP (it'll be my first). Anyone that has suggestions might find my forum post useful: http://ubuntuforums.org/showthread.php?t=2280658 The challenge is trying to figure out what process in addition to the file manager is mounting the blank media. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Two processes attempt to mount blank optical discs Status in OEM Priority Project: New Status in glib2.0 package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: This behavior can be reproduced using either a live USB or an installed version of the effected flavors. Simply insert a blank optical disc in the drive. The behavior differs slightly in Ubuntu GNOME as the notification to either Open with CD/DVD Creator or Eject is displayed twice - that is after simply clicking on the X to close that notification it closes but a new duplicate notification appaers immediately. The GNOME Classic session is not effected at all. In all other effected flavors and/or desktop environments a notification appears stating Unable to mount Blank disc. Location is already mounted. Effected flavors and DE's include Ubuntu w/Unity, gnome-session-flashback, and Ubuntu MATE. Versions effected include Trusty, Utopic, and Vivid. I assume that two separate processes are actually attempting to mount the blank optical media, rather than just the file manager attemting to do so, because both Nautilus and Caja are effected (based on some of the comments below possibly also Nemo). While purely cosmetic in nature I'd certainly be willing to try and troubleshoot this if someone more tech savvy would provide some debugging instructions. Original content begins below: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs
Hi Tim, I assume that Nautilus (or Caja in the case of Ubuntu Mate) is actually responsible for the media already mounted warning because if you open dconf-editor and go to org/gnome/desktop/media-handling (or org/mate/desktop/media-handling) and change both automount and automount-open to false then the media already mounted warning goes away. The downside is that doing so interferes with mounting usb drives, cameras, etc so it's not a truly viable workaround. The descriptions in dconf certainly mention Nautilus and Caja specifically: If set to true, then Nautilus will automatically mount media such as user-visible hard disks and removable media on start-up and media insertion. If set to true, then Nautilus will automatically open a folder when media is automounted. This only applies to media where no known x-content/* type was detected; for media where a known x-content type is detected, the user configurable action will be taken instead. If set to true, then Caja will automatically mount media such as user- visible hard disks and removable media on start-up and media insertion. If set to true, then Caja will automatically open a folder when media is automounted. This only applies to media where no known x-content/* type was detected; for media where a known x-content type is detected, the user configurable action will be taken instead. So I really assume that some file managers (Nautilus, Caja, and possibly Nemo) attempt to mount the blank media after gvfs has already mounted it and therefore produce that warning. I'll grant you that it's only a cosmetic issue but it's certainly one of those bugs that just shouts not ready for prime time and sends users looking elsewhere for a reliable distro. I'd think there'd be a way to have Nautilus and Caja just see if media is already mounted by gvfs and if so say nothing rather than displaying a useless and meaningless warning. Since this does also effect the Mate DE I took the liberty of subscribing Martin Wimpress, so apologies in advance to Martin. My intention is not to be pushy but only to inform. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Two processes attempt to mount blank optical discs Status in OEM Priority Project: New Status in glib2.0 package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: This behavior can be reproduced using either a live USB or an installed version of the effected flavors. Simply insert a blank optical disc in the drive. The behavior differs slightly in Ubuntu GNOME as the notification to either Open with CD/DVD Creator or Eject is displayed twice - that is after simply clicking on the X to close that notification it closes but a new duplicate notification appaers immediately. The GNOME Classic session is not effected at all. In all other effected flavors and/or desktop environments a notification appears stating Unable to mount Blank disc. Location is already mounted. Effected flavors and DE's include Ubuntu w/Unity, gnome-session-flashback, and Ubuntu MATE. Versions effected include Trusty, Utopic, and Vivid. I assume that two separate processes are actually attempting to mount the blank optical media, rather than just the file manager attemting to do so, because both Nautilus and Caja are effected (based on some of the comments below possibly also Nemo). While purely cosmetic in nature I'd certainly be willing to try and troubleshoot this if someone more tech savvy would provide some debugging instructions. Original content begins below: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs
** Tags added: caja ubuntu-mate wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Two processes attempt to mount blank optical discs Status in OEM Priority Project: New Status in glib2.0 package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: This behavior can be reproduced using either a live USB or an installed version of the effected flavors. Simply insert a blank optical disc in the drive. The behavior differs slightly in Ubuntu GNOME as the notification to either Open with CD/DVD Creator or Eject is displayed twice - that is after simply clicking on the X to close that notification it closes but a new duplicate notification appaers immediately. The GNOME Classic session is not effected at all. In all other effected flavors and/or desktop environments a notification appears stating Unable to mount Blank disc. Location is already mounted. Effected flavors and DE's include Ubuntu w/Unity, gnome-session-flashback, and Ubuntu MATE. Versions effected include Trusty, Utopic, and Vivid. I assume that two separate processes are actually attempting to mount the blank optical media, rather than just the file manager attemting to do so, because both Nautilus and Caja are effected (based on some of the comments below possibly also Nemo). While purely cosmetic in nature I'd certainly be willing to try and troubleshoot this if someone more tech savvy would provide some debugging instructions. Original content begins below: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs
** Summary changed: - Unable to mount Blank CD-R disc. Location is already mounted. + Two processes attempt to mount blank optical discs ** Description changed: + This behavior can be reproduced using either a live USB or an installed + version of the effected flavors. Simply insert a blank optical disc in + the drive. + + The behavior differs slightly in Ubuntu GNOME as the notification to + either Open with CD/DVD Creator or Eject is displayed twice - that is + after simply clicking on the X to close that notification it closes but + a new duplicate notification appaers immediately. The GNOME Classic + session is not effected at all. + + In all other effected flavors and/or desktop environments a notification + appears stating Unable to mount Blank disc. Location is already + mounted. Effected flavors and DE's include Ubuntu w/Unity, gnome- + session-flashback, and Ubuntu MATE. + + Versions effected include Trusty, Utopic, and Vivid. I assume that two + separate processes are actually attempting to mount the blank optical + media, rather than just the file manager attemting to do so, because + both Nautilus and Caja are effected (based on some of the comments below + possibly also Nemo). + + While purely cosmetic in nature I'd certainly be willing to try and + troubleshoot this if someone more tech savvy would provide some + debugging instructions. + + Original content begins below: + This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: - LANGUAGE=en_GB:en - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_GB.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Two processes attempt to mount blank optical discs Status in OEM Priority Project: New Status in glib2.0 package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: This behavior can be reproduced using either a live USB or an installed version of the effected flavors. Simply insert a blank optical disc in the drive. The behavior differs slightly in Ubuntu GNOME as the notification to either Open with CD/DVD Creator or Eject is displayed twice - that is after simply clicking on the X to close that notification it closes but a new duplicate notification appaers immediately. The GNOME Classic session is not effected at all. In all other effected flavors and/or desktop environments a notification appears stating Unable to mount Blank disc. Location is already mounted. Effected flavors and DE's include Ubuntu w/Unity, gnome-session-flashback, and Ubuntu MATE. Versions effected include Trusty, Utopic, and Vivid. I assume that two separate processes are actually attempting to mount the blank optical media, rather than just the file manager attemting to do so, because both Nautilus and Caja are effected (based on some of the comments below possibly also Nemo). While purely cosmetic in nature I'd certainly be willing to try and troubleshoot this if someone more tech savvy would provide some debugging instructions. Original content begins below: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash
[Touch-packages] [Bug 1432843] Re: Lubuntu failed to boot
** Attachment added: freeze_i386.JPG https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+attachment/4361870/+files/freeze_i386.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432843] Re: Lubuntu failed to boot
No idea why the explanatory text disappeared with comment #24 but that's a pic of what the screen displays when the i386 image freezes. This pic is what the screen displays when the amd64 image freezes. ** Attachment added: freeze_amd64.JPG https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+attachment/4361871/+files/freeze_amd64.JPG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432843] Re: Lubuntu failed to boot
I've tested both the Lubuntu 20150330 i386 and amd64 images on two totally different sets of hardware. Both fail to boot to the live DE on this hardware: Intel Atom CPU 230 @ 1.60GHz Intel 82945G/GZ Integrated Graphics Controller (rev 02) Intel N10/ICH 7 Family High Definition Audio Controller (rev 01) Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) 2GB DDR2 RAM The i386 image fails to boot to the live DE, but the amd64 image does boot to the live DE while producing bug #1438605 on this hardware: AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM But the installation freezes at the second screen on that second set of hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.
Actually a variant of this still exists in Ubuntu GNOME Vivid (as of 20150318) the difference being that, instead of getting the already mounted warning as you do in a flashback session, in a GNOME Shell session if you click the close button on the Open with CD/DVD creator or Eject notification as soon as it closes it pops right back up until you click it a second time. I haven't checked the flashback session in Vivid yet but I will in the next few days. I suspect that more than one process is attempting to handle this, one being Nautilus . I'm clueless what the other might be. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Unable to mount Blank CD-R disc. Location is already mounted. Status in OEM Priority Project: New Status in glib2.0 package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417792] [NEW] Trusty proposed updates enabled by default
Public bug reported: I'm testing Ubuntu GNOME Trusty 20150203 i386 and the proposed updates are still enabled via /etc/apt/sources.list.d: lance@lance-AMD-desktop:~$ ls /etc/apt apt.conf.d sources.listtrustdb.gpg trusted.gpg.d preferences.d sources.list.d trusted.gpg lance@lance-AMD-desktop:~$ ls /etc/apt/sources.list.d proposed.list lance@lance-AMD-desktop:~$ cat /etc/apt/sources.list.d/proposed.list deb http://archive.ubuntu.com/ubuntu/ trusty-proposed main restricted universe These need to be turned off before 14.04.2 is released. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.3 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: GNOME Date: Tue Feb 3 16:18:13 2015 InstallationDate: Installed on 2015-02-03 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release i386 (20150203) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1417792 Title: Trusty proposed updates enabled by default Status in software-properties package in Ubuntu: New Bug description: I'm testing Ubuntu GNOME Trusty 20150203 i386 and the proposed updates are still enabled via /etc/apt/sources.list.d: lance@lance-AMD-desktop:~$ ls /etc/apt apt.conf.d sources.listtrustdb.gpg trusted.gpg.d preferences.d sources.list.d trusted.gpg lance@lance-AMD-desktop:~$ ls /etc/apt/sources.list.d proposed.list lance@lance-AMD-desktop:~$ cat /etc/apt/sources.list.d/proposed.list deb http://archive.ubuntu.com/ubuntu/ trusty-proposed main restricted universe These need to be turned off before 14.04.2 is released. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.3 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: GNOME Date: Tue Feb 3 16:18:13 2015 InstallationDate: Installed on 2015-02-03 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release i386 (20150203) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1417792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417792] Re: Trusty proposed updates enabled by default
Also affects Ubuntu Trusty 20150203.2 i386. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1417792 Title: Trusty proposed updates enabled by default Status in software-properties package in Ubuntu: New Bug description: I'm testing Ubuntu GNOME Trusty 20150203 i386 and the proposed updates are still enabled via /etc/apt/sources.list.d: lance@lance-AMD-desktop:~$ ls /etc/apt apt.conf.d sources.listtrustdb.gpg trusted.gpg.d preferences.d sources.list.d trusted.gpg lance@lance-AMD-desktop:~$ ls /etc/apt/sources.list.d proposed.list lance@lance-AMD-desktop:~$ cat /etc/apt/sources.list.d/proposed.list deb http://archive.ubuntu.com/ubuntu/ trusty-proposed main restricted universe These need to be turned off before 14.04.2 is released. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.3 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: GNOME Date: Tue Feb 3 16:18:13 2015 InstallationDate: Installed on 2015-02-03 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release i386 (20150203) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1417792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403103] Re: Utopic - Vivid upgrade fails because no Vivid extras repo exists
I assume this can just be retired when the actual fix for bug #1409555 drops??? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1403103 Title: Utopic - Vivid upgrade fails because no Vivid extras repo exists Status in software-properties package in Ubuntu: Confirmed Bug description: Sorry if I filed this against the wrong package but it was a best guess. In anticipation of Ubuntu GNOME Vivid Alpha 1 I attempted and upgrade from Utopic to Vivid and get this error message: W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/source/Sources 404 Not Found , W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/binary-i386/Packages 404 Not Found , E:Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.94 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: GNOME Date: Tue Dec 16 08:58:40 2014 InstallationDate: Installed on 2014-10-18 (58 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to utopic on 2014-12-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1403103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403103] Re: Utopic - Vivid upgrade fails because no Vivid extras repo exists
@ Bruce Pieterse, if you need the packages offered by the extras/independent repos you can use the Utopic versions of just those repos for the time being until the Vivid versions are built. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1403103 Title: Utopic - Vivid upgrade fails because no Vivid extras repo exists Status in software-properties package in Ubuntu: Confirmed Bug description: Sorry if I filed this against the wrong package but it was a best guess. In anticipation of Ubuntu GNOME Vivid Alpha 1 I attempted and upgrade from Utopic to Vivid and get this error message: W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/source/Sources 404 Not Found , W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/binary-i386/Packages 404 Not Found , E:Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.94 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: GNOME Date: Tue Dec 16 08:58:40 2014 InstallationDate: Installed on 2014-10-18 (58 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to utopic on 2014-12-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1403103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403103] [NEW] Utopic - Vivid upgrade fails because no Vivid extras repo exists
Public bug reported: Sorry if I filed this against the wrong package but it was a best guess. In anticipation of Ubuntu GNOME Vivid Alpha 1 I attempted and upgrade from Utopic to Vivid and get this error message: W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/source/Sources 404 Not Found , W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/binary-i386/Packages 404 Not Found , E:Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.94 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: GNOME Date: Tue Dec 16 08:58:40 2014 InstallationDate: Installed on 2014-10-18 (58 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to utopic on 2014-12-16 (0 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1403103 Title: Utopic - Vivid upgrade fails because no Vivid extras repo exists Status in software-properties package in Ubuntu: New Bug description: Sorry if I filed this against the wrong package but it was a best guess. In anticipation of Ubuntu GNOME Vivid Alpha 1 I attempted and upgrade from Utopic to Vivid and get this error message: W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/source/Sources 404 Not Found , W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/binary-i386/Packages 404 Not Found , E:Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.94 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: GNOME Date: Tue Dec 16 08:58:40 2014 InstallationDate: Installed on 2014-10-18 (58 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to utopic on 2014-12-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1403103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403103] Re: Utopic - Vivid upgrade fails because no Vivid extras repo exists
The upgrade starts as expected if you first disable the extras/independent repos in software sources. ** Tags added: release-upgrader vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1403103 Title: Utopic - Vivid upgrade fails because no Vivid extras repo exists Status in software-properties package in Ubuntu: New Bug description: Sorry if I filed this against the wrong package but it was a best guess. In anticipation of Ubuntu GNOME Vivid Alpha 1 I attempted and upgrade from Utopic to Vivid and get this error message: W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/source/Sources 404 Not Found , W:Failed to fetch http://extras.ubuntu.com/ubuntu/dists/vivid/main/binary-i386/Packages 404 Not Found , E:Some index files failed to download. They have been ignored, or old ones used instead. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.94 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CurrentDesktop: GNOME Date: Tue Dec 16 08:58:40 2014 InstallationDate: Installed on 2014-10-18 (58 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to utopic on 2014-12-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1403103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401677] Re: hwdb.bin does not exist
I get the same error message during boot after upgrading Ubuntu GNOME
from Utopic to Vivid, and running the suggested command makes no
difference.
** Attachment added: IMG_4793.JPG
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1401677/+attachment/4282462/+files/IMG_4793.JPG
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1401677
Title:
hwdb.bin does not exist
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Using the current daily build of vivid for Ubuntu Gnome in Virtualbox,
after the welcome screen is displayed and switching to tty1 on the
live CD I see:
starting version 217
hwdb.bin does not exist, please run udevadm hwdb --update
Network interface NamePolicy= disabled on kernel commandline, ignoring.
invalid key/value pair in file /lib/udev/rules.d/97-dmraid.rules on line 8,
starting at character 95 ('a')
[45.279072] systemd-logind[3430]: Failed to start user service: Unknown unit:
user@999.service
Welcome to Ubuntu Vivid Vervet (development branch)
...snip...
Last week the above output was present post-installation. Currently
this is not present post-installation with the current daily build.
However the system-logind error (Unknown init) persists and is
currently present post-installation with slight difference of user@999
becoming user@1000.
I found this bug report which has been marked as Fix released but
not sure if these are related or not:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1190947.
I have a screenshot from last week which I installed a daily build
image on physical hardware. Some of the errors in that screenshot are
no longer present (whoopsie basename). If you need it please let me
know.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: udev 217-3ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Dec 11 23:32:03 2014
InstallationDate: Installed on 2014-12-11 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141211)
Lsusb:
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic
root=UUID=c0cdf4f1-f502-41e5-8d1f-26b30d67242d ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1401677/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.
Also effects Ubuntu Utopic so I added the utopic tag and removed quantal tag since Quantal is EOL. ** Tags added: utopic ** Tags removed: quantal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Unable to mount Blank CD-R disc. Location is already mounted. Status in OEM Priority Project: New Status in “glib2.0” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347721] Re: Saucy - Trusty upgrade failed: procps fails to configure
Installed and updated Saucy, enabled proposed, and ran apt-get install apt: Start-Date: 2014-08-11 23:15:49 Commandline: apt-get install apt Upgrade: apt:i386 (0.9.9.1~ubuntu3.2, 0.9.9.1~ubuntu3.3), libapt-pkg4.12:i386 (0.9.9.1~ubuntu3.2, 0.9.9.1~ubuntu3.3) End-Date: 2014-08-11 23:16:02 Then disabled proposed, refreshed the cache using update-manager and was offered the upgrade via GUI so I proceeded and all went perfectly so I'm marking this verification-done. Many thanks. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1347721 Title: Saucy - Trusty upgrade failed: procps fails to configure Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Saucy: Fix Committed Status in “apt” source package in Trusty: Triaged Status in “apt” source package in Utopic: Fix Released Bug description: Test Case: 1. Install Saucy + the task ubuntu-dekstop^ 2. Upgrade with do-release-upgrade Result: Upgrade fails with: Setting up libprocps3:i386 (1:3.3.9-1ubuntu2) ... dpkg: dependency problems prevent configuration of procps: procps depends on initscripts; however: Package initscripts is not configured yet. dpkg: error processing package procps (--configure): dependency problems - leaving unconfigured == Original Description == I'm just performing 14.04.1 pre-release testing and decided to try a Saucy - Trusty upgrade even though Saucy recently reached EOL. I'd expected to be told no upgrade was available (or was impossible) early in the process if it were not possible at this point in time but the upgrade appeared to be in progress until the attached warning appeared (I'd guess about half-way into the upgrade process based on lapsed time) . No idea what will happen on reboot so I wanted to file this prior to reboot. I'll follow up later. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CrashDB: ubuntu CurrentDesktop: GNOME Date: Wed Jul 23 09:03:39 2014 InstallationDate: Installed on 2014-07-17 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131015) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2014-07-23 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1347721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347721] Re: Saucy - Trusty upgrade failed: procps fails to configure
@Adam, I'm installing Saucy now - will follow up ASAP. @Jim, be sure to check and see what kernel you're now running via uname -r as I did in comment #4. As best I recall I seemed to be able to recover simply by running update-grub and apt-get -f install (and following suggestions provided by -f install), possibly a few times until things appeared to resolve. But I was using a test installation that was long since erased. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1347721 Title: Saucy - Trusty upgrade failed: procps fails to configure Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Saucy: Fix Committed Status in “apt” source package in Trusty: Triaged Status in “apt” source package in Utopic: Fix Released Bug description: Test Case: 1. Install Saucy + the task ubuntu-dekstop^ 2. Upgrade with do-release-upgrade Result: Upgrade fails with: Setting up libprocps3:i386 (1:3.3.9-1ubuntu2) ... dpkg: dependency problems prevent configuration of procps: procps depends on initscripts; however: Package initscripts is not configured yet. dpkg: error processing package procps (--configure): dependency problems - leaving unconfigured == Original Description == I'm just performing 14.04.1 pre-release testing and decided to try a Saucy - Trusty upgrade even though Saucy recently reached EOL. I'd expected to be told no upgrade was available (or was impossible) early in the process if it were not possible at this point in time but the upgrade appeared to be in progress until the attached warning appeared (I'd guess about half-way into the upgrade process based on lapsed time) . No idea what will happen on reboot so I wanted to file this prior to reboot. I'll follow up later. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CrashDB: ubuntu CurrentDesktop: GNOME Date: Wed Jul 23 09:03:39 2014 InstallationDate: Installed on 2014-07-17 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131015) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2014-07-23 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1347721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
