[Bug 2063984] Re: package chromium-browser 1:124.0.6367.78-0ubuntu0.22.04.1sav0 failed to install/upgrade: le sous-processus nouveau chromium-browser paquet pre-installation script a renvoyé un état d
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709.ReportingBugs. The package of chromium for 24.04/noble is https://bugs.launchpad.net/ubuntu/+source/chromium- browser/2:1snap1-0ubuntu2 which is not what you're using. If you wish to file a bug report on your chromium package, you'd have to file it with whomever packaged it (PPA owner), as it's not a Ubuntu 24.04 package. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063984 Title: package chromium-browser 1:124.0.6367.78-0ubuntu0.22.04.1sav0 failed to install/upgrade: le sous-processus nouveau chromium-browser paquet pre-installation script a renvoyé un état de sortie d'erreur 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063500] Re: GIMP crashed with a fatal error: fatal error: Erreur de segmentation
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2063500 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. (The pasted details are intended for filing bugs upstream with GNU Gimp; Ubuntu system details have not been provided) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063500 Title: GIMP crashed with a fatal error: fatal error: Erreur de segmentation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2063500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063516] Re: GIMP crashes on close
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2063516 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. (The pasted details are intended for filing bugs upstream with GNU Gimp; Ubuntu system details have not been provided) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063516 Title: GIMP crashes on close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2063516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063513] Re: torbrowser unusable - not accepting keyboard input
*** This bug is a duplicate of bug 2056578 *** https://bugs.launchpad.net/bugs/2056578 ** This bug has been marked a duplicate of bug 2056578 Tor Browser - keyboard not functioning -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063513 Title: torbrowser unusable - not accepting keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2063513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063545] Re: package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063545 Title: package click 0.5.2-2ubuntu4 failed to install/upgrade: new click package pre-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/2063545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063502] Re: 24.04: dvd image wont fit on dvd and missing libraries
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. The capacity of a dual layer DVDR(W) is 8.3-8.5GB (8.5GB unformatted), which will fit a Ubuntu ISO though you didn't specify what Ubuntu product/ISO you're meaning; eg. a Ubuntu Desktop 24.04 LTS ISO is smaller (5.7GB) than this size for example. A single layer DVD is of course smaller, but the intended install media today has been a USB flash drive for some time. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709. Thank you! ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063502 Title: 24.04: dvd image wont fit on dvd and missing libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2063502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063417] Re: Fix system hang while entering suspend with AMD Navi3x graphics
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Tags added: oem-priority originate-from-2048051 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063417 Title: Fix system hang while entering suspend with AMD Navi3x graphics To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2063417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063476] Re: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2
Ok, this was introduced upstream somewhere between 2.36.0 (jammy release) and 2.44.0 (jammy-updates). webkit2gtk now detects whether gbm_bo_create_with_modifiers2 exists at build time; if so, it uses them. This is not a problem for the main archive, as the libgbm that mesa provides includes those symbols, but some proprietary drivers include their own libgbm (notably, here, the ARM MALI drivers) and this change has accidentally and silently broken the effective driver ABI for Ubuntu 22.04. In this case here it seems like it will be easy enough to patch the code to dynamically resolve gbm_bo_create_with_modifiers2 - the upstream code already has an implementation for where this is not available at build time. That's not an archive-wide solution, though. It's not *entirely* obvious to me whether this should be considered an SRU regression - I'm inclined to think so, but I don't hold that opinion strongly. I'll take the temperature of the SRU team on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063476 Title: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
Thank you Mate for working out issue & great explanation.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063417] [NEW] Fix system hang while entering suspend with AMD Navi3x graphics
Public bug reported: SRU Jusitification for Kernel [Impact] The system with AMD W7500/W7600/W7700 graphics will randomly hang when entering suspend. The page fault would keep happening and the system can't handle other tasks. BUG: unable to handle page fault for address: 0a980148 [Fix] Backport the fix from upstream drm/amdgpu: skip to program GFXDEC registers for suspend abort · torvalds/linux@0326de4 · GitHub drm/amdgpu: Reset dGPU if suspend got aborted · torvalds/linux@8b2be55 · GitHub https://patchwork.freedesktop.org/patch/590570/ [patchwork.freedesktop.org] [Test Case] 1. Install AMD W7500/W7600/W7700 graphics 2. Install latest firmware with dcn_3_2_0_dmcub.bin for Navi31 and 32 and dcn_3_2_1_dmcub.bin for Navi33. 3. Running fwts s3 stress test to check if system hangs [Where problems could occur] Improve the error handling when suspend and add the fallback mechanism in MES engine. Only observed on particular AMD models. Need to test w/ more combinations = SRU Jusitification for linux-firmware [Impact] The system will randomly hang due to page fault while suspending. [Fix] Add release FW binary from AMD to linux-firmware dcn_3_2_0_dmcub.bin for Navi31 and 32: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=eb06e8bbe56cea19b8c2a23c154e2dcefd79fa47 [git.kernel.org] dcn_3_2_1_dmcub.bin for Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_1_dmcub.bin?id=8b8ac15f9bce35d555b8253156053a7e2b661f6a [git.kernel.org] [Test Case] 1. Install AMD W7500/W7600/W7700 graphics 2. Test with latest linux kernel and linux-firmware 3. Running fwts s3 stress test to check if system hangs [Where problems could occur] The dcn_3_2_0_dmcub only for Navi31 and dcn_3_2_1_dmcub only for Navi33. The impact are restricted to particular series. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063417 Title: Fix system hang while entering suspend with AMD Navi3x graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062135] Re: Add Cirrus Logic CS35L56 amplifier support
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062135 Title: Add Cirrus Logic CS35L56 amplifier support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2062135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
install using Lubuntu 20240425 ISO (latest RC as of now) and issue reoccurred. on ISO is calamares 3.3.5-0ubuntu4 as before - erase disk & install to dc7700 - install alongside (slider moved random amount as usual, so size [of partitions] aren't critical - install & re-use SDA1 (first installed partition; what was shrunk) and critically NO-FORMAT is used on reboot, no grub menu appears. if I go to terminal and `sudo update-grub`... no other OS is shown, with 'OS_PROBER will not be executed' message appears.. I can't boot into the other OS that was present before this QA-install test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@ Paramvir Could you try new kernel and update the information? Thanks ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063357] Re: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS
Thank you for taking the time to report this bug and helping to make Ubuntu better. You mention it was "Reported 1 year 8 months ago" if so please provide the bug report link, as you only provided reference to a support site (which isn't a bug report). FYI: I'd have appreciated a picture of the image in english; the picture provided via link to askubuntu alas wasn't in english. If you update your LXQt using Lubuntu backports, does the issue still occur ?? ie. your report here mentions using lxqt-powermanagement 0.17.1-0ubuntu1 where the version in Lubuntu backports (for 22.04/jammy) is 1.4.0-0ubuntu2~ppa1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063357 Title: attempting to use idle brightness in lxqt-powermanagement leads to crash on 22.04.4 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822
Booted an install made earlier today on hp_compaq_dc7700 of lubuntu noble (20240424) ; https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300235/testcases/1701/results/ sudo apt update; sudo apt full-upgrade & no updates are available. (software-properties-qt 0.99.48.1) Following the "Intended Functionality" listed in the Bug.Description at the top of this bug report and behavior is what I'd expect. The `/etc/apt/sources.list` file contained comments only ; with all subsequent changes being reflected in `/etc/apt/sources.list.d/ubuntu.sources` and looked appropriate to me. However I'm tired, and fear I've missed something (that I can't 'put my finger on'), but I've repeated steps 1..7 twice & didn't locate what 'irks' me sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061214 Title: [SRU] Software Sources is not compatible with deb822 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
( another FYI I mentioned it's no longer re-creatable with Xubuntu due to forced FORMAT currently with `ubuntu-desktop-installer` ... the issue i'm referring to is/was https://bugs.launchpad.net/ubuntu- desktop-provision/+bug/2058638 .. current 'fix' being to force format , but my understanding is that will be reverted once time is available to correct the current 'regression' format triggers with 24.04 over 23.10 & earlier) This bug (2060624) thus can only be triggered (I believe) by the calamares installer used Lubuntu, Kubuntu & Ubuntu.Unity; as ubuntu-desktop-installer is forcing format (at least for now). ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
Just an FYI... but on the two cases I've encountered this issue I didn't install as per #14. I'll have always performed a 1. full disk install (any prior partitioning erased); noble (may not have been lubuntu) but single partition only 2. install alongside (calamares wording; auto-resize type creating a second install) (ie. I did two install types & achieved same result as steps 1 & 2 as Mate (mkukri) in comment #14) At step 3 my usual thing is a 'replace partition' (calamares wording) install using one of the partitions (this is a FORMAT install).. where which partition I use is ~random (usually opting to keep the partition I'll most recognize as untouched; the install where I changed the wallpaper usually so easily recognized).. Any testing of 'install using existing partition' for me would be 4th (or 5th) install almost guaranteed I believe.. My point is it can be triggered in other ways I believe, but again very few users will encounter it... I rarely encountered it! (then again what I listed ^ is what I did today, do most days probably too.. maybe why I've not experienced it much as I suspect i re-use SDA2 most days (& not sda1); ie. changing wallpaper on that first install (of the day) so its recognized on the many installs that usually follow...) I concur with view not a release blocker. -- said by me on #lubuntu-devel (matrix) > It may worthwhile (if not fixed & I doubt it will be) for me to create a page > on [lubuntu]discourse(doco) for users should they encounter this issue ... > to me it's not a big issue; I've only encountered it rarely, it requires > specific conditions I doubt many will encounter.. but could be mentioned in > release notes as well with somewhere we can point users too... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
I completed an install on dc7700 - two systems (noble) exist on drive - boot install media (lubuntu noble RC) - select partition (I selected SDA2, ignoring SDA1) for `/` WITHOUT FORMAT - let it install (this system is OLD, legacy-BIOS so no ESP; Lubuntu's calamares doesn't create one by default for BIOS machine; iso.qa report at https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300140/testcases/1701/results/) on reboot; two options appeared in grub. - SDA1 was in grub & when booted looked untouched - SDA2 contained new install, file-system system directories all time-stamped mins ago (not hours ago) as expected for new install.. packages I added are present (fortune, clementine etc).. I COULD NOT RE-CREATE THIS ISSUE.. Only difference between this and prior install could have been I selected second partition (SDA2) where last time I selected SDA1?? but I can't see that as making an difference; could it?? Given I've only experienced this issue twice, and could not re-create.. I'd be happy with marking bug as INCOMPLETE.. I could re-try by installing to SDA1 (same type of install) if you think there is any chance of difference.. but I couldn't re-create issue today (me attempting same type of install on same box) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
I have made many installs of various boxes, and exploring logs of the iso.qa.ubu link in comment #3 i see only two references to this issue (within a few days of each other), which include the following --- hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt) testcase: install using existing partition --- I've made four installs on that box today (https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300140/testcases/1701/results/) yet did NOT experience the issue. Currently the box has two installs (first was full disk, then auto-resize equiv.. ) so I'll try and repeat the install I made in the next hour+ and see if it occurs. Lubuntu testcases are described here - https://discourse.lubuntu.me/t/testing-checklist-understanding-the- testcases/2743 but an INSTALL USING EXISTING PARTITION means - boot install media - using manual partitioning, selecting an existing partition (for /) BUT DO NOT FORMAT (ie. re-use it...) This is NO longer possible with Xubuntu as FORMAT is now mandatory (due to another bug, scheduled for fix post-release of noble..) I'll add some non-standard packages to one of my installed systems on dc7700 (per testcase; something for installer to re-install), then attempt to re-create this issue & reply back in an hour (or three) and see if it re-occurs... then provide detailed description of what I did (if issue re-occurs). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2013074] Re: changing monitor configuration & on next login, only one monitor is fully usable to LXQt
Another boot on next box - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) This box shares same screens, so pretty much same change in monitor.settings; except I didn't have to change the primary.display as what booted in live mode is what I prefer. identical issue & behavior though as last comment (#12) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2013074 Title: changing monitor configuration & on next login, only one monitor is fully usable to LXQt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2013074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2013074] Re: changing monitor configuration & on next login, only one monitor is fully usable to LXQt
first boot of lubuntu noble RC on - hp prodesk 400 g1 sff (i5-4570, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) live test, on adjusting displays to match my config... what was by default.right monitor below the default.left, plus making my.bottom (what was default.right) monitor the primary.display.. my.top monitor (what was default.right) now has no background, and right-click on black has the options of - terminal emulator - web browser - applications - obconf - reconfigure - restart - exit operation of system though is not impacted.. and with play (3-5 mins) I know I can revert the issue anyway (historically anyway) --- i was going to close down LIVE testing.. so used the (on display) EXIT menu to exit to see what it did... On clicking the EXIT on obmenu - both wallpapers now display - lxqt-panel is now gone (would be annoying for non-technical users) - right-click on background on both displays now shows LXQt menu - no borders in the windows I had open (fair enough given I exited openbox).. the wallpaper appearing on the BLACK SCREEN is what surprised me, thus why this add of detail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2013074 Title: changing monitor configuration & on next login, only one monitor is fully usable to LXQt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2013074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063103] Re: Remove ROS duplicated packages imported from Debian
Confirmed I was able to pull all of liborocos-kdl1.5, liborocos-kdl-dev, python3-pykdl, libapriltag3t64, apriltag, and libapriltag-dev down. This unblocks ROS 2. Thank you for the quick resolution of the problem. We'll keep testing and will report back if we see any other issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063103 Title: Remove ROS duplicated packages imported from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ros-catkin/+bug/2063103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063103] Re: Remove ROS duplicated packages imported from Debian
The removal of orocos-kdl is a show-stopper for ROS 2. Right now, we are completely dead in the water without that package. Could you please reinstate that one ASAP? It would also be good to have 'apriltag' back, as we would prefer to use the system version there: https://github.com/ros/rosdistro/issues/35273 ** Bug watch added: github.com/ros/rosdistro/issues #35273 https://github.com/ros/rosdistro/issues/35273 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063103 Title: Remove ROS duplicated packages imported from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ros-catkin/+bug/2063103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
@trurl42, does the sound used to work before (older kernel than 6.5)? From the kernel log, the line out has no trivial problem. I need to know is this a regression or something else. Thanks [5.221075] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC3254: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [5.221080] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062972] [NEW] ntfs partition does not mount
Public bug reported: I am using Ubuntu 24.04 Development Branch (Beta). I am dualbooting it with Windows 11. When I try to mount my NTFS Windows partition via the Ubuntu Dock, I get: "Error mounting /dev/nvme01np3 at /media/chris(my username)/Windows:wrong fs type, bad option, bad superblock on /dev/nvme01np3, missing codepageor helper program, or other error". Output of sudo apt-cache policy ntfs-3g: ntfs-3g: Installed: 1:2022.10.3-1.2ubuntu3 Candidate: 1:2022.10.3-1.2ubuntu3 Version table: *** 1:2022.10.3-1.2ubuntu3 500 500 http://gr.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ntfs-3g 1:2022.10.3-1.2ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 18:25:55 2024 InstallationDate: Installed on 2024-04-20 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ntfs-3g UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ntfs-3g (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062972 Title: ntfs partition does not mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/2062972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056100] Re: sru cloud-init (24.1.3 update) Focal, Jammy, and Mantic
Looks good from an Azure perspective with ~250K+ VM creates, mostly 20.04 with coverage of 22.04 as well. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056100 Title: sru cloud-init (24.1.3 update) Focal, Jammy, and Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062561] [NEW] There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d.
Public bug reported: It looks like 24.04 is changing how apt sources work.. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=23.10 DISTRIB_CODENAME=mantic DISTRIB_DESCRIPTION="Ubuntu 23.10" $ cat /etc/apt/sources.list deb http://archive.ubuntu.com/ubuntu mantic restricted main multiverse universe # deb-src http://archive.ubuntu.com/ubuntu mantic restricted main multiverse universe deb http://archive.ubuntu.com/ubuntu mantic-updates restricted main multiverse universe # deb-src http://archive.ubuntu.com/ubuntu mantic-updates restricted main multiverse universe deb http://archive.ubuntu.com/ubuntu mantic-security restricted main multiverse universe # deb-src http://archive.ubuntu.com/ubuntu mantic-security restricted main multiverse universe deb http://archive.ubuntu.com/ubuntu mantic-backports restricted main multiverse universe # deb-src http://archive.ubuntu.com/ubuntu mantic-backports restricted main multiverse universe $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=24.04 DISTRIB_CODENAME=noble DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)" $ cat /etc/apt/sources.list # Ubuntu sources have moved to /etc/apt/sources.list.d/ubuntu.sources $ cat /etc/apt/sources.list.d/ubuntu.sources Types: deb URIs: http://archive.ubuntu.com/ubuntu/ Suites: noble noble-updates noble-backports Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg Types: deb URIs: http://archive.ubuntu.com/ubuntu/ Suites: noble-security Components: main restricted universe multiverse Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg With this, Landscape is now reporting an alert "Package reporting issues": There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d. ** Affects: landscape-client Importance: Undecided Status: New ** Affects: landscape-client (Ubuntu) Importance: Undecided Status: New ** Also affects: landscape-client Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062561 Title: There are no APT sources configured in /etc/apt/sources.list or /etc/apt/sources.list.d. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2062561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062518] [NEW] package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to install/upgrade: installed linux-headers-6.5.0-28-generic package post-installation script subprocess returned error ex
Public bug reported:
Softweare updater continually failing on this.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-28-generic 6.5.0-28.29
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: chris 1642 F pipewire
chris 1646 F wireplumber
/dev/snd/controlC0: chris 1646 F wireplumber
/dev/snd/seq:chris 1642 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Fri Apr 19 08:58:51 2024
ErrorMessage: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2024-04-17 (1 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64
(20240220)
IwConfig:
lono wireless extensions.
wlp109s0f0 no wireless extensions.
enx7e345242890a no wireless extensions.
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic
root=UUID=5db60d46-8e67-48c1-a78a-be0d6b68e193 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2024-04-18 (1 days ago)
dmi.bios.date: 03/14/2024
dmi.bios.release: 1.2
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.1
dmi.board.name: 0KVPC9
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.ec.firmware.release: 1.2
dmi.modalias:
dmi:bvnAlienware:bvr1.2.1:bd03/14/2024:br1.2:efr1.2:svnAlienware:pnAlienwarem18R2:pvr:rvnAlienware:rn0KVPC9:rvrA00:cvnAlienware:ct10:cvr:sku0C9D:
dmi.product.family: Alienware
dmi.product.name: Alienware m18 R2
dmi.product.sku: 0C9D
dmi.sys.vendor: Alienware
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package mantic need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062518
Title:
package linux-headers-6.5.0-28-generic 6.5.0-28.29 failed to
install/upgrade: installed linux-headers-6.5.0-28-generic package
post-installation script subprocess returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062518/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062428] Re: Install randomly crashes/fails/hangs on systems with 3GB or less
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2062428 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. No clues as to product are provided (three flavors use calamares, though Kubuntu is used as example so it maybe Kubuntu but we don't know; is this 24.04? as its not said though mentioned too), nor clues as to what ISO was used, nor package version details. It's likely nothing can be done without this detail; as package versions have changed multiple times in the last few days & no useful data (no logs etc) were provided. Please in future use `ubuntu-bug`... which can be run even from terminal even during operation (or calamares-hang). If your system has already gone (ie. I assume it was LIVE and thus after failure you shutdown box), some detail can be added to the report if you BOOT the same ISO on the SAME HARDWARE and run `apport-collect 2062428` as requested there. This will populate most missing fields, even if no calamares-log will be attached (you'd need to re-run the install & have the same issue to get that). As currently little detail is provided, I'll mark this bug as incomplete. If you do run `apport-collect`, please change the status back to "New". Thank you for filing the bug report in attempts to make Ubuntu better. ** Changed in: calamares-settings-ubuntu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062428 Title: Install randomly crashes/fails/hangs on systems with 3GB or less To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2062428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060592] Re: lubuntu noble - another timeout issue (600 secs)
duplicate of https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2062106 maybe??? that message says 900 secs (not 600) ... is there a condition for time of internet (900 for wifi; 600 for cable here.. but cause I see as identical) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060592 Title: lubuntu noble - another timeout issue (600 secs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2060592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062106] Re: lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita -- failed to finish in 900 seconds
repeat only different timeout period? in https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2060592 duplicate? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062106 Title: lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita -- failed to finish in 900 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2062106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055418] Re: autoinstall crashing on 24.04 desktop daily build
Hi Jeff, apologies for the delay in getting back to you. Based on the crash report provided it looks like it was a bug with the tracker package. I think this should be sorted by now though! ** Changed in: subiquity Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062135] Re: Add Cirrus Logic CS35L56 amplifier support
** Tags added: oem-priority originate-from-2057859 stella -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062135 Title: Add Cirrus Logic CS35L56 amplifier support To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2062135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062135] [NEW] Add Cirrus Logic CS35L56 amplifier support
Public bug reported: SRU Jusitification for Kernel [Impact] Add a driver for the Cirrus Logic CS35L56 amplifier. This is not a standalone HDA device; it provides control of the CS35L56 for systems that use a combination of an HDA codec and CS35L56 amplifiers with audio routed through the HDA codec. If it's not enabled on HDA codec with this amplifier, there will be no sound if play audio via built-in speaker. [Fix] Backport the CS35L56 driver from kernel 6.9-rc [Test Case] 1. Install the kernel w/ CS35L56 driver enabled 2. Install the linux-firmware with latest CS35l56 supported 3. Play audio file on machines w/ CS35L56 amplifier and make sure it's OK [Where problems could occur] Only affects models which have CS35L56 amplifier. Should be no risk to others. = SRU Jusitification for linux-firmware [Impact] No sound if no CS35L56 firmware even the driver is enabled in Linux kernel. [Fix] Add release FW binary of CS35L56 to linux-firmware [Test Case] 1. Install the kernel w/ CS35L56 driver enabled 2. Install the linux-firmware with latest CS35l56 supported 3. Play audio file on machines w/ CS35L56 amplifier and make sure it's OK [Where problems could occur] New firmware is only loaded by the CS35L56, we only need to verify it on the target platform. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062135 Title: Add Cirrus Logic CS35L56 amplifier support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062106] Re: lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita -- failed to finish in 900 seconds
If this isn't changed... Lubuntu (me) could always add a page at https://discourse.lubuntu.me/c/documentation/20 In summary; my install worked; except - the third party packages however were not installed, - the `/var/log/installer` directory did NOT exist thus some metadata was missing from the install etc Users have the option of (a) testing their systems, if it was like mine, everything appeared to work perfectly, and they can just add the 3rd party apps themselves & expect no further problems (they're unlikely to notice the missing metadata anyway) OR (b) restart install WITHOUT 3rd party apps... then reboot into their new install, and add the third party apps themselves. This option will ensure they have all their metadata (ie. in the future can look up what media they used for install, details of install etc, details that would be missing with alternative (a)) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062106 Title: lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita -- failed to finish in 900 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2062106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062106] [NEW] lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita -- failed to finish in 900 seconds
Public bug reported:
full install to sony vaio thingy
- sony vaio ultrabook svp11216cgb (i5-9400u, 4gb, intel haswell-ULT)
testcase: testcase: full, encryption, EFI, internet, swap, updates
no ethernet, so limited to wifi (300n so should be that bad, but still
aussie nbn so not fast)
---
2024-04-18 - 13:28:34 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-18 - 13:28:34 [1]: ERROR: Installation failed: "External command
failed to finish."
2024-04-18 - 13:28:34 [6]: .. - message: "External command failed to
finish."
2024-04-18 - 13:28:34 [6]: .. - details: Command snap-seed-glue --seed
/tmp/calamares-root-8p789tsd/var/lib/snapd/seed krita failed to finish in
900 seconds.
There was no output from the command.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.497
CurrentDesktop: LXQt
Date: Thu Apr 18 13:31:43 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.31
calamares-settings-lubuntu 1:24.04.31
xfsprogs 6.6.0-1ubuntu2
btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: calamares (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
** Description changed:
- add more later
+ full install to sony vaio thingy
+ - sony vaio ultrabook svp11216cgb (i5-9400u, 4gb, intel haswell-ULT)
+
+ testcase: testcase: full, encryption, EFI, internet, swap, updates
+
+ no ethernet, so limited to wifi (300n so should be that bad, but still
+ aussie nbn so not fast)
+
+ ---
+ 2024-04-18 - 13:28:34 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ 2024-04-18 - 13:28:34 [1]: ERROR: Installation failed: "External command
failed to finish."
+ 2024-04-18 - 13:28:34 [6]: .. - message: "External command failed to
finish."
+ 2024-04-18 - 13:28:34 [6]: .. - details: Command snap-seed-glue --seed
/tmp/calamares-root-8p789tsd/var/lib/snapd/seed krita failed to finish in
900 seconds.
+ There was no output from the command.
+
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.finished.conf:
- ---
- restartNowMode: user-checked
- restartNowCommand: "systemctl -i reboot"
+ ---
+ restartNowMode: user-checked
+ restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
- crypttabOptions: luks,keyscript=/bin/cat
- efiMountOptions: umask=0077
+ crypttabOptions: luks,keyscript=/bin/cat
+ efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
- ---
- dontChroot: true
- timeout: 30
- script:
- - calamares-logs-helper ${ROOT}
+ ---
+ dontChroot: true
+ timeout: 30
+ script:
+ - calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
- ---
- unpack:
- - source: "/cdrom/casper/filesystem.squashfs"
- sourcefs: "squashfs"
- destination: ""
+ ---
+ unpack:
+ - source: "/cdrom/casper/filesystem.squashfs"
+ sourcefs: "squashfs"
+ destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.497
CurrentDesktop: LXQt
Date: Thu Apr 18 13:31:43 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417)
RelatedPackageVersions:
- calamares-settings-ubuntu-common 1:24.04.31
- calamares-settings-lubuntu 1:24.04.31
- xfsprogs 6.6.0-1ubuntu2
- btrfs-progs 6.6.3-1.1build2
+ calamares-settings-ubuntu-common 1:24.04.31
+ calamares-settings-lubuntu 1:24.04.31
+ xfsprogs 6.6.0-1ubuntu2
+ btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
** Summary changed:
- full install fail
+ lubuntu noble - snap-seed-glue --seed ..calamares..snapd/seed krita --
failed to finish in 900 seconds
--
You received this bug
[Bug 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
This bug is LOW PRIORITY in my view... - not many people will use the INSTALL USING EXISTING PARTITION (non-destructive install) - the error occurs which stops the installer, but most of what is required was already done, so system has booted for me each time I've encountered this error (even if some metadata will be invalid; system has been usable). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060429 Title: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060960] Re: lubuntu noble beta RC says 23.10 (not 24.04)
Possibly obvious, but this appears on installed systems too, as I booted up a recent install on dell optiplex 780 to get details for Aaron yesterday & the 23.10 plymouth was there at boot/shutdown. (d780 another box that uses text plymouth instead of graphic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060960 Title: lubuntu noble beta RC says 23.10 (not 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/2060960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
As requested by Aaron (matrix) I ran a command on dc7700 & reported results... also booted & ran it on d780 (which I'm using now) and results are rather slow. guiverc@d780-noble:~$ time sudo update-initramfs -c -k all update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic update-initramfs: Generating /boot/initrd.img-5.11.0-44-generic update-initramfs: Generating /boot/initrd.img-5.13.0-28-generic update-initramfs: Generating /boot/initrd.img-5.13.0-30-generic update-initramfs: Generating /boot/initrd.img-5.15.0-41-generic update-initramfs: Generating /boot/initrd.img-5.15.0-46-generic update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip update-initramfs: Generating /boot/initrd.img-5.8.0-41-generic W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip update-initramfs: Generating /boot/initrd.img-5.8.0-50-generic W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip update-initramfs: Generating /boot/initrd.img-5.8.0-61-generic W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip update-initramfs: Generating /boot/initrd.img-5.8.0-64-generic W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip update-initramfs: Generating /boot/initrd.img-6.2.0-18-generic update-initramfs: Generating /boot/initrd.img-6.2.0-19-generic update-initramfs: Generating /boot/initrd.img-6.2.0-26-generic update-initramfs: Generating /boot/initrd.img-6.2.0-33-generic update-initramfs: Generating /boot/initrd.img-6.2.0-39-generic update-initramfs: Generating /boot/initrd.img-6.5.0-9-generic update-initramfs: Generating /boot/initrd.img-6.8.0-22-generic real7m6.659s user0m0.007s sys 0m0.006s Even though I initially filed this bug report on dc7700; the testcase is listed as an "INSTALL USING EXISTING PARTITION" which is a no-format install; meaning some old stuff can be found.. thus probably this issue.. The copy/paste of command is from a very recent install of noble on this box. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060429 Title: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
repeated install (using existing partition) to - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) again this issue The install abends (abnormal end) with error & thus doesn't continue/complete install... /var/log/installer/mediainfo OR all contents in /var/log/installer reflect a prior install (many ago).. but this install type is successful .. after all it's a non-destructive install (no-format) so much data survives from pre-install (date/time stamps of system directories match new install though, as most system directories get wiped) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060429 Title: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2060429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061698] Re: Editing image, selecting a region and it crashed GIMP_2_10_36
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2061698 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ( No release, package details were provided, the developers the provided paste was for are upstream developers ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061698 Title: Editing image, selecting a region and it crashed GIMP_2_10_36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2061698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061711] Re: lubuntu noble - full (inc. 3rd party) install is kinda slow
Of no importance.. but the 10 mins nothing will likely be
2024-04-16 - 12:32:43 [6]: .. Running ("/bin/sh", "-c", "snap-seed-glue
--seed /tmp/calamares-root-hazyaxmi/var/lib/snapd/seed krita")
2024-04-16 - 12:45:09 [6]: .. Running ("/bin/sh", "-c", "snap-seed-glue
--seed /tmp/calamares-root-hazyaxmi/var/lib/snapd/seed thunderbird")
after krita I noticed (& mentioned) a kf5 snap.. but that detail would
have come from my viewing `iotop` and the `snap download` command that
showed there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061711
Title:
lubuntu noble - full (inc. 3rd party) install is kinda slow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2061711/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061711] Re: lubuntu noble - full (inc. 3rd party) install is kinda slow
** Description changed:
This is NOT a bug that can be fixed with code.
At most a fix maybe a line in the release notes, that selecting all 3rd
party software for inclusion can be SLOW IF you're using 3rd-world, some
aussie NBN or other older/slower internet connections (or just
infrastructure at canonical end anyway).
This report has been filed ONLY for timing purposes; so I can look, and
have record of how long install actually took (with calamares
running)...
A watched kettle always appears to take longer to boil... I was sitting
watching this install & for a long time is stayed at 90% with slideshow
repeating... I switched to show all messages and it didn't scroll up for
maybe 10 mins there either..
I actually CTRL+ALT+T and opened a terminal, made it full screen on this
boxes other display & `sudo apt install iotop` and let that run... From
there I could see downloads taking place (thru write) & eventually
- notice `snap download` progress to next page (krita, kf5 etc)... but the
- installer window remained at 90%.. then eventually 92%... |
+ notice `snap download` progress to next package (krita, kf5 etc)... but
+ the installer window remained at 90%.. eventually 92%... |
Many users may assume the installer is 'looping' or dead...
2024-04-16 - 02:17:35 (start of calamares)
2024-04-16 - 12:17:43 (calamares switched to local time I assume)
2024-04-16 - 12:48:06 (end calamares)
So ~thirty minutes to install, I didn't let it sit at any dialog.. just
selected items & continued...
This box may not be quick... but I believe issue is mostly internet
speed & what is required to be downloaded.. something we can't do much
about it..
Is a release note worth including??
Could a end-user think the install has failed is looping, when in fact
it isn't
I don't see how we can change anything, as even viewing the messages
calamares provides I didn't see progress for near 10 mins... thus why
I opened terminal & starting watching progress via `iotop`
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
---
dontChroot: false
timeout: 120
firmwareType:
"*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CurrentDesktop: LXQt
Date: Tue Apr 16 12:48:16 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240415)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.28
calamares-settings-lubuntu 1:24.04.28
xfsprogs 6.6.0-1ubuntu2
btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061711
Title:
lubuntu noble - full (inc. 3rd party) install is kinda slow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2061711/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061711] Re: lubuntu noble - full (inc. 3rd party) install is kinda slow
** Description changed:
This is NOT a bug that can be fixed with code.
At most a fix maybe a line in the release notes, that selecting all 3rd
party software for inclusion can be SLOW IF you're using 3rd-world, some
aussie NBN or other older/slower internet connections (or just
infrastructure at canonical end anyway).
This report has been filed ONLY for timing purposes; so I can look, and
have record of how long install actually took (with calamares
running)...
A watched kettle always appears to take longer to boil... I was sitting
watching this install & for a long time is stayed at 90% with slideshow
repeating... I switched to show all messages and it didn't scroll up for
maybe 10 mins there either..
I actually CTRL+ALT+T and opened a terminal, made it full screen on this
boxes other display & `sudo apt install iotop` and let that run... From
there I could see downloads taking place (thru write) & eventually
notice `snap download` progress to next page (krita, kf5 etc)... but the
installer window remained at 90%.. then eventually 92%... |
Many users may assume the installer is 'looping' or dead...
+ 2024-04-16 - 02:17:35 (start of calamares)
+ 2024-04-16 - 12:17:43 (calamares switched to local time I assume)
+ 2024-04-16 - 12:48:06 (end calamares)
+
+ So ~thirty minutes to install, I didn't let it sit at any dialog.. just
+ selected items & continued...
+
+ This box may not be quick... but I believe issue is mostly internet
+ speed & what is required to be downloaded.. something we can't do much
+ about it..
+
+ Is a release note worth including??
+
+ Could a end-user think the install has failed is looping, when in fact
+ it isn't
+
+ I don't see how we can change anything, as even viewing the messages
+ calamares provides I didn't see progress for near 10 mins... thus why
+ I opened terminal & starting watching progress via `iotop`
+
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
- ---
- dontChroot: false
- timeout: 120
- firmwareType:
- "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
+ ---
+ dontChroot: false
+ timeout: 120
+ firmwareType:
+ "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
- ---
- restartNowMode: user-checked
- restartNowCommand: "systemctl -i reboot"
+ ---
+ restartNowMode: user-checked
+ restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
- crypttabOptions: luks,keyscript=/bin/cat
- efiMountOptions: umask=0077
+ crypttabOptions: luks,keyscript=/bin/cat
+ efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
- ---
- dontChroot: true
- timeout: 30
- script:
- - calamares-logs-helper ${ROOT}
+ ---
+ dontChroot: true
+ timeout: 30
+ script:
+ - calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
- ---
- unpack:
- - source: "/cdrom/casper/filesystem.squashfs"
- sourcefs: "squashfs"
- destination: ""
+ ---
+ unpack:
+ - source: "/cdrom/casper/filesystem.squashfs"
+ sourcefs: "squashfs"
+ destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CurrentDesktop: LXQt
Date: Tue Apr 16 12:48:16 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240415)
RelatedPackageVersions:
- calamares-settings-ubuntu-common 1:24.04.28
- calamares-settings-lubuntu 1:24.04.28
- xfsprogs 6.6.0-1ubuntu2
- btrfs-progs 6.6.3-1.1build2
+ calamares-settings-ubuntu-common 1:24.04.28
+ calamares-settings-lubuntu 1:24.04.28
+ xfsprogs 6.6.0-1ubuntu2
+ btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061711
Title:
lubuntu noble - full (inc. 3rd party) install is kinda slow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2061711/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061711] [NEW] lubuntu noble - full (inc. 3rd party) install is kinda slow
Public bug reported:
This is NOT a bug that can be fixed with code.
At most a fix maybe a line in the release notes, that selecting all 3rd
party software for inclusion can be SLOW IF you're using 3rd-world, some
aussie NBN or other older/slower internet connections (or just
infrastructure at canonical end anyway).
This report has been filed ONLY for timing purposes; so I can look, and
have record of how long install actually took (with calamares
running)...
A watched kettle always appears to take longer to boil... I was sitting
watching this install & for a long time is stayed at 90% with slideshow
repeating... I switched to show all messages and it didn't scroll up for
maybe 10 mins there either..
I actually CTRL+ALT+T and opened a terminal, made it full screen on this
boxes other display & `sudo apt install iotop` and let that run... From
there I could see downloads taking place (thru write) & eventually
notice `snap download` progress to next page (krita, kf5 etc)... but the
installer window remained at 90%.. then eventually 92%... |
Many users may assume the installer is 'looping' or dead...
2024-04-16 - 02:17:35 (start of calamares)
2024-04-16 - 12:17:43 (calamares switched to local time I assume)
2024-04-16 - 12:48:06 (end calamares)
So ~thirty minutes to install, I didn't let it sit at any dialog.. just
selected items & continued...
This box may not be quick... but I believe issue is mostly internet
speed & what is required to be downloaded.. something we can't do much
about it..
Is a release note worth including??
Could a end-user think the install has failed is looping, when in fact
it isn't
I don't see how we can change anything, as even viewing the messages
calamares provides I didn't see progress for near 10 mins... thus why
I opened terminal & starting watching progress via `iotop`
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
---
dontChroot: false
timeout: 120
firmwareType:
"*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CurrentDesktop: LXQt
Date: Tue Apr 16 12:48:16 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240415)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.28
calamares-settings-lubuntu 1:24.04.28
xfsprogs 6.6.0-1ubuntu2
btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: calamares (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug iso-testing noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061711
Title:
lubuntu noble - full (inc. 3rd party) install is kinda slow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2061711/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061695] [NEW] package matlab-support 0.0.23 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1
Public bug reported: Install would not accept actual MATLAB directory. However, a launcher that seems to work was created even after a "canceled" installation. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: matlab-support 0.0.23 ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: matlab-support:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Apr 15 19:05:34 2024 ErrorMessage: installed matlab-support package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-03-11 (35 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: matlab-support Title: package matlab-support 0.0.23 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: matlab-support (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061695 Title: package matlab-support 0.0.23 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matlab-support/+bug/2061695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056578] Re: Tor Browser - keyboard not functioning
I'll add another affirmation that what Asciiwolf reports in comment #10 is working for me too on this (my primary) install where I've not had keyboard working for some time (see comment #4; late February 2024) Add line & restart apparmor, and start torbrowser & I can use it for the first time in ages. Thank you Asciiwolf - appreciate the solution. I wonder if the package this bug report is filed against is incorrect; but sorry I don't know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056578 Title: Tor Browser - keyboard not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2056578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061327] Re: 24.04 beta hangs at desktop
duplicate filing of https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061326 ** Changed in: mesa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061327 Title: 24.04 beta hangs at desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060780] Re: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060780 Title: CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
That works! Thanks Andreas. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061049] Re: Fix random HuC/GuC initialization failure of Intel i915 driver
** Tags added: oem-priority originate-from-2051627 stella -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061049] [NEW] Fix random HuC/GuC initialization failure of Intel i915 driver
Public bug reported: [Impact] i915 error can sometimes be found in kernel message when booting the machine w/ power unplugged kernel: i915 :00:02.0: [drm] *ERROR* GT1: GuC initialization failed -EIO kernel: i915 :00:02.0: [drm] *ERROR* GT1: Enabling uc failed (-5) kernel: i915 :00:02.0: [drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged! The GPU won't work with this failure [Fix] Backport the upatream fix for allowing slow HuC loading. [Test] 1. Unplug the power of the laptop and make sure it's charged by battery 2. Cold boot or Warm boot the machine and check the GuC init fail message. 3. Go to settings - > about --> graphics to make sure the GPU information is correct every boot. [Where problems could occur] Simply increase the loading time of HuC still get a working system. Should be low risk of regression. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2051627 stella ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Jammy) Status: New => In Progress ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Jammy) Status: In Progress => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061049 Title: Fix random HuC/GuC initialization failure of Intel i915 driver To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2061049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060894] Re: dialogue won't start, high cpu usage
Could you provide the logs from /var/log/installer/ please? I've yet to run into this on my tests. ** Changed in: subiquity Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060894 Title: dialogue won't start, high cpu usage To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2060894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060960] [NEW] lubuntu noble beta RC says 23.10 (not 24.04)
Public bug reported: On this box (hp 8200) the text plymouth is used... and this it reports as Lubuntu 23.10 during boot. - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) ** expected result On booting a Lubuntu noble beta (24.04) I expect it to say 24.04 ** actual result It reports itself as Lubuntu 23.10 with some dots during boot --- I believe the issue is lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ cat lubuntu-text.plymouth [Plymouth Theme] Name=Lubuntu Text Description=Text mode theme based on kubuntu-logo theme ModuleName=ubuntu-text [ubuntu-text] title=Lubuntu 23.10 black=0x0078C2 white=0xff brown=0x009DFD blue=0x00182C lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ dpkg -S /usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth plymouth-theme-lubuntu-text: /usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: plymouth-theme-lubuntu-text 24.04.4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.496 CurrentDesktop: LXQt Date: Thu Apr 11 12:03:57 2024 LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410) PackageArchitecture: all SourcePackage: lubuntu-artwork UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lubuntu-artwork (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: On this box (hp 8200) the text plymouth is used... and this it reports as Lubuntu 23.10 during boot. + + - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) ** expected result On booting a Lubuntu noble beta (24.04) I expect it to say 24.04 ** actual result It reports itself as Lubuntu 23.10 with some dots during boot --- I believe the issue is - lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ cat lubuntu-text.plymouth + lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ cat lubuntu-text.plymouth [Plymouth Theme] Name=Lubuntu Text Description=Text mode theme based on kubuntu-logo theme ModuleName=ubuntu-text [ubuntu-text] title=Lubuntu 23.10 black=0x0078C2 white=0xff brown=0x009DFD blue=0x00182C - lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ dpkg -S /usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth + lubuntu@lubuntu:/usr/share/plymouth/themes/lubuntu-text$ dpkg -S /usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth plymouth-theme-lubuntu-text: /usr/share/plymouth/themes/lubuntu-text/lubuntu-text.plymouth ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: plymouth-theme-lubuntu-text 24.04.4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.496 CurrentDesktop: LXQt Date: Thu Apr 11 12:03:57 2024 LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410) PackageArchitecture: all SourcePackage: lubuntu-artwork UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060960 Title: lubuntu noble beta RC says 23.10 (not 24.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-artwork/+bug/2060960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
I've NOT encountered this issue with a install.alongside (calamares/lubuntu) or the ubuntu-desktop-installer equivalent (auto(resize) testcase)... as both installs (prior + new) appear in GRUB on second install when that is run. This is where it matters most anyway, and it works perfectly. I've only encountered this on manual.partitioning (something-else equivalent) and manually selecting a pre-existing partition for re-use (ubuntu-desktop-install now marks that as with format compulsory)... This will impact very few users.. and can easily be covered by a RELEASE NOTES message if required anyway, as very few users will be impacted by it (most will have no issue dealing with the PROBER edit).. -- Alas the Xubuntu install no longer exists; that install being overwritten by subsequent QA test installs. I'd have to re-create the issue, which won't be tonight... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
The Xubuntu install was an install into one partition (SDA2) where two partitions exist both with OSes (SDA1 & SDA2). The resulting Xubuntu install booted without grub appearing on boot, and no way for a user to boot into prior SDA1 install of Lubuntu noble. Attempt as in original post of `sudo update-grub` reports Warning: os-prober will not be executed to detect other bootable partitions. thus my prior 24.04 system is not offered as boot option. I've NOT encountered this issue with an auto(resize)/install-alongside install, ONLY with something-else/manual-partitioning type of installs.. so its not all installs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall on dual boot system, grub does appear & offer OS choice
The Xubuntu install was an install into one partition (SDA2) where two partitions exist both with OSes (SDA1 & SDA2). The resulting Xubuntu install booted without grub appearing on boot, and no way for a user to boot into prior SDA1 install of Lubuntu noble. Attempt as in original post of `sudo update-grub` reports Warning: os-prober will not be executed to detect other bootable partitions. thus my prior 24.04 system is not offered as boot option. ** Summary changed: - lubuntu reinstall on dual boot system, grub does appear & offer OS choice + lubuntu/xubuntu reinstall on dual boot system, grub does appear & offer OS choice ** Summary changed: - lubuntu/xubuntu reinstall on dual boot system, grub does appear & offer OS choice + lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060695] Re: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk
I think I know what is happening here. In Ubuntu 20.04 and 22.04, the grub-pc.postinst has a chunk of code that was designed to deal with bug #1889556 by skipping running grub-install on package updates. The initial commit comment by Steve Langasek says: debian/postinst.in: Avoid calling grub-install on upgrade of the grub-pc package, since we cannot be certain that it will install to the correct disk and a grub-install failure will render the system unbootable. LP: #1889556 (commit 3aabdc6fe0ab3b6e129fc5b64238c45cbfd0de47 I believe) This code is, in its final form in 22.04: elif dpkg --compare-versions "$2" ge 2.04-1ubuntu26 && [ -z "$DEBCONF_RECONFIGURE" ]; then # Avoid the possibility of breaking grub on SRU update # due to ABI change : 2.04-1ubuntu26 was the initial grub2 version in 20.04. This version was not updated for 22.04 to the 22.04 base version, but the effect was the same (since they were all more recent than the 20.04 base version). If you force a 22.04 machine to explicitly reconfigure grub-pc with 'dpkg- reconfigure grub-pc', it will fail with the same error message as in 24.04 (until you select the real devices). The reason 24.04 fails here is that the 20.04/22.04 change to grub- pc.postinst wasn't carried forward to 24.04, the way it was for 22.04 (in commit 00e473f4e2b2e7e607b3aad58cb0c085b1f0561a I believe), so grub- pc always tries to run grub-install on package updates and fails here. I don't know if this is a grub-pc 24.04 problem by itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060695 Title: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2060695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916897] Re: [SRU] Center windows option has no effect
Mantic has 1.6.2, which does not have this bug. Marking Ubuntu task as fix-released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916897 Title: [SRU] Center windows option has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obconf-qt/+bug/1916897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916897] Re: [SRU] Center windows option has no effect
Hello Nguyễn, or anyone else affected, Accepted obconf-qt into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/obconf- qt/0.16.0-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: obconf-qt (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy ** Changed in: obconf-qt (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916897 Title: [SRU] Center windows option has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obconf-qt/+bug/1916897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060755] Re: grub fails when trying to install ubuntu 2020.04
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. If you would prefer live chat support, you can find an IRC support channel for your flavor of Ubuntu here: https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. (FYI: PPAs are Personal Package Archives and not supported by the Ubuntu project, but by the PPA owner. Bugs/requests about PPAs should likewise be filed with the PPA owner). ** Changed in: grub-installer (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/grub-installer/+question/809140 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060755 Title: grub fails when trying to install ubuntu 2020.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/2060755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060695] Re: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk
I didn't change grub-pc/install-devices, and on our 22.04 BIOS MBR + mirrored software RAID servers (of which we have a lot), it has the same value (or the same sort of value, naming the md device). A random 22.04 server install is also using 'super 1.2' for its root /dev/md0 device superblock format, which will have come from the installer since we don't change or customize that. We have some remaining 20.04 LTS servers as well with this same mirrored software RAID root and they are also superblock 1.2 format and the same grub-pc/install_devices setting. I think it has been this way in Ubuntu server installs for a long time (for BIOS MBR, UEFI is slightly different in that it also sets grub- efi/install_devices to the UEFI partitions on the boot disks). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060695 Title: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2060695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060695] Re: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk
Both 'dpkg-reconfigure grub-pc' then selecting the /dev/vd* disks and manually running 'grub-install /dev/vda' (and then /dev/vdb) do work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060695 Title: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060695] Re: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk
Also, here's sgdisk output (the two disks have identical output apart from names): isk /dev/vda: 83886080 sectors, 40.0 GiB Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 08D25DA2-9B12-45EA-B7EE-0978D2780899 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 83886046 Partitions will be aligned on 2048-sector boundaries Total free space is 4029 sectors (2.0 MiB) Number Start (sector)End (sector) Size Code Name 120484095 1024.0 KiB EF02 2409683884031 40.0 GiB8300 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060695 Title: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060695] Re: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk
The RAID is on partitions, but there is no LVM involved. The layout was set up through the 24.04 server installer with custom storage layout, selecting both disks as boot disks, and then using all of their space as a single partition for the software RAID. The software RAID itself is unpartitioned. /proc/mdstat: md0 : active raid1 vdb2[1] vda2[0] 41906176 blocks super 1.2 [2/2] [UU] /proc/partitions: 2530 41943040 vda 2531 1024 vda1 2532 41939968 vda2 253 16 41943040 vdb 253 17 1024 vdb1 253 18 41939968 vdb2 90 41906176 md0 /proc/self/mounts of the root filesystem: /dev/md0 / ext4 rw,relatime 0 0 I get this test VM into a state with a post-install grub2 update because I typically work by going through the server installer once, snapshotting the result, and then working from the snapshot to test our post-install actions, which involve updating all packages. This grub-pc problem has happened before several times and previously I've made it go away by rebuilding the initial install using the current daily server ISO. This time I'm reporting a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060695 Title: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060695] [NEW] 24.04 grub-pc cannot upgrade on mirrored software RAID root disk
Public bug reported: I am testing the 24.04 pre-beta in a libvirt virtual machine with two /dev/vd* disks set up as a single mirrored software RAID device, /dev/md0, that is used for the root filesystem. Since this is a libvirt install, it is using BIOS booting, not UEFI (maybe someday libvirt will support snapshots of UEFI based VMs). When I attempt to install Ubuntu updates, the grub-pc install fails with: grub-pc: Running grub-install ... Installing for i386-pc platform. grub-install: warning: File system `ext2' doesn't support embedding. grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. grub-install: error: diskfilter writes are not supported. grub-install failure for /dev/md0 You must correct your GRUB install devices before proceeding: DEBIAN_FRONTEND=dialog dpkg --configure grub-pc dpkg --configure -a dpkg: error processing package grub-pc (--configure): installed grub-pc package post-installation script subprocess returned error exit status 1 'debconf-show' reports (changed) settings as: * grub-efi/cloud_style_installation: false * grub-pc/install_devices: /dev/disk/by-id/md-name-ubuntu-server:0 * grub-pc/install_devices_empty: false The same mirrored root filesystem configuration works on 22.04 LTS. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060695 Title: 24.04 grub-pc cannot upgrade on mirrored software RAID root disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060429] Re: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
Just experienced this again.. Install to - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) this is a newer machine (2008) with faster cpu... alas still 'slow' by todays standards... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060429 Title: lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2060429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu reinstall on dual boot system, grub does appear & offer OS choice
I vaguely recall an indirect discussion with AndreaRighi (or someone) who mentioned a (possible?) change coming thru for noble.. I'm wondering if this is my discovery of what was mentioned.. alas I can't recall the 'comment' this reminds me of My testing today can be read here - https://iso.qa.ubuntu.com/qatracker/milestones/450/builds/299105/testcases/1701/results/ Either way my install is perfect, except the dual-booting option offered by GRUB got lost.. This is behavior I get on Debian, so I know how to fix it, just don't expect it with a Ubuntu re-install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu reinstall on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] [NEW] lubuntu reinstall on dual boot system, grub does appear & offer OS choice
Public bug reported: Warning: os-prober will not be executed to detect other bootable partitions. Lubuntu noble install to - hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt) System had two Lubuntu noble installs on box; original full disk install (sda1) + install alongside (sda2) This box is legacy (BIOS) or pre-uEFI (2005 HP Compaq) so no ESP was created at install time guiverc@dc7700-3:~$ blkid /dev/sda2: LABEL="lubuntu_2404" UUID="4b96ae36-ff60-46ff-888d-bab52f0664fc" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b22c54df-02" /dev/sda1: LABEL="lubuntu_2404" UUID="2466-48e0-47e3-af47-4cd692dcdbd6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b22c54df-01" ** expected result On reboot post-install (Lubuntu so calamares install) I grub did NOT appear, so I could boot into the untouched install & checked it worked (grub offered me two options correctly prior to install). ** actual result No grub menu appeared, so no dual boot option was offered?? No problem, I'll just `update-grub` and that should fix it won't it? guiverc@dc7700-3:~$ sudo update-grub [sudo] password for guiverc: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/lubuntu-grub-theme.cfg' Generating grub configuration file ... Found theme: /usr/share/grub/themes/lubuntu-grub-theme/theme.txt Found linux image: /boot/vmlinuz-6.8.0-22-generic Found initrd image: /boot/initrd.img-6.8.0-22-generic Found memtest86+x64 image: /boot/memtest86+x64.bin Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done The issue is Warning: os-prober will not be executed to detect other bootable partitions. Prior releases of Ubuntu haven't done this (new grub 2.06 change) with a patch (ubuntu-os-prober-auto.patch) carried by Ubuntu that reverses this upstream change.. If this is new behavior (for noble) we (Lubuntu at least) just need to document it, as its a change to mantic, lunar & prior releases (inc. kinetic, jammy which were 2.06 or later, it was default prior to jammy anyway). Maybe I'm missing something... I'll correct/add more as I can ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: grub2-common 2.12-1ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Apr 9 16:21:14 2024 InstallationDate: Installed on 2024-04-09 (0 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: Warning: os-prober will not be executed to detect other bootable partitions. - Lubuntu noble install. + Lubuntu noble install to + - hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt) System had two Lubuntu noble installs on box; original full disk install (sda1) + install alongside (sda2) This box is legacy (BIOS) or pre-uEFI (2005 HP Compaq) so no ESP was created at install time guiverc@dc7700-3:~$ blkid /dev/sda2: LABEL="lubuntu_2404" UUID="4b96ae36-ff60-46ff-888d-bab52f0664fc" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b22c54df-02" /dev/sda1: LABEL="lubuntu_2404" UUID="2466-48e0-47e3-af47-4cd692dcdbd6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b22c54df-01" ** expected result On reboot post-install (Lubuntu so calamares install) I grub did NOT appear, so I could boot into the untouched install & checked it worked (grub offered me two options correctly prior to install). ** actual result No grub menu appeared, so no dual boot option was offered?? No problem, I'll just `update-grub` and that should fix it won't it? - guiverc@dc7700-3:~$ sudo update-grub - [sudo] password for guiverc: + [sudo] password for guiverc: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/lubuntu-grub-theme.cfg' Generating grub configuration file ... Found theme: /usr/share/grub/themes/lubuntu-grub-theme/theme.txt Found linux image: /boot/vmlinuz-6.8.0-22-generic Found initrd image: /boot/initrd.img-6.8.0-22-generic Found memtest86+x64 image: /boot/memtest86+x64.bin Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done The issue is Warning: os-prober will not be executed to detect other bootable partitions. Prior releases of Ubuntu haven't done this (new grub 2.06 change) with a - patch carried by Ubuntu that reverses this upstream
[Bug 2060614] Re: lubuntu lxqt - space between touching monitors
*** This bug is a duplicate of bug 1882411 *** https://bugs.launchpad.net/bugs/1882411 ** Attachment added: "screen.jpg" https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2060614/+attachment/5762421/+files/screen.jpg ** This bug has been marked a duplicate of bug 1882411 lubuntu monitor settings touching screens with gap between ** Description changed: This really is a re-file of https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1882411 - I've blamed OPENBOX here, as I don't experience this issue when I switch - to to xfwm4 + I've blamed OPENBOX here, quick play by switching to xfwm4 though... and + I could replicate issue with xfwm4 so my blaming openbox is incorrect.. + Now marked duplicate. - Lubuntu noble was only re-installed on this box today (re-install of an install earlier today).. - Install went well, at least until I explored monitor position & adjusted to fix minor issue + Lubuntu noble was only re-installed on this box today (re-install of an + install earlier today).. Install went well, at least until I explored + monitor position & adjusted to fix minor issue NOTE my resolution for monitors is NOT identical; which maybe significant in experiencing this issue! This is NOT a new issue either. ** expected result I adjust monitor position so my monitors correctly TOUCH instead of overlap (overlapping was default) and click apply. The attached screen.jpg shows HOW I aligned my monitors.. ** actual result There is a GAP between the monitors; my windows can disappear between them, and there is a delay when I move mouse-pointer between my 'touching' monitors (pointer is in the gap). Note the left side of the clementine music player window cannot be seen. If I drag it a little left, I can have ~2cm of the window appear on both displays however it's useless as almost none of the window is actionable or readable. - - This maybe a wrong filing, and is only a duplicate of aforementioned bug (1882411) report. + This maybe a wrong filing, and is only a duplicate of aforementioned bug + (1882411) report. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: openbox 3.6.1-12build4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Apr 9 15:22:24 2024 InstallationDate: Installed on 2024-04-09 (0 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408) SourcePackage: openbox UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: This really is a re-file of https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1882411 I've blamed OPENBOX here, quick play by switching to xfwm4 though... and I could replicate issue with xfwm4 so my blaming openbox is incorrect.. Now marked duplicate. Lubuntu noble was only re-installed on this box today (re-install of an install earlier today).. Install went well, at least until I explored monitor position & adjusted to fix minor issue - NOTE my resolution for monitors is NOT identical; which maybe significant in experiencing this issue! - This is NOT a new issue either. + NOTE my resolution for monitors is NOT identical; which maybe + significant in experiencing this issue! This is NOT a new issue either. ** expected result I adjust monitor position so my monitors correctly TOUCH instead of overlap (overlapping was default) and click apply. The attached screen.jpg shows HOW I aligned my monitors.. ** actual result There is a GAP between the monitors; my windows can disappear between them, and there is a delay when I move mouse-pointer between my 'touching' monitors (pointer is in the gap). Note the left side of the clementine music player window cannot be seen. If I drag it a little left, I can have ~2cm of the window appear on both displays however it's useless as almost none of the window is actionable or readable. This maybe a wrong filing, and is only a duplicate of aforementioned bug (1882411) report. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: openbox 3.6.1-12build4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Apr 9 15:22:24 2024 InstallationDate: Installed on 2024-04-09 (0 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408) SourcePackage: openbox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060614 Title: lubuntu lxqt - space between touching monitors To
[Bug 2060614] [NEW] lubuntu lxqt - space between touching monitors
*** This bug is a duplicate of bug 1882411 *** https://bugs.launchpad.net/bugs/1882411 Public bug reported: This really is a re-file of https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1882411 I've blamed OPENBOX here, quick play by switching to xfwm4 though... and I could replicate issue with xfwm4 so my blaming openbox is incorrect.. Now marked duplicate. Lubuntu noble was only re-installed on this box today (re-install of an install earlier today).. Install went well, at least until I explored monitor position & adjusted to fix minor issue NOTE my resolution for monitors is NOT identical; which maybe significant in experiencing this issue! This is NOT a new issue either. ** expected result I adjust monitor position so my monitors correctly TOUCH instead of overlap (overlapping was default) and click apply. The attached screen.jpg shows HOW I aligned my monitors.. ** actual result There is a GAP between the monitors; my windows can disappear between them, and there is a delay when I move mouse-pointer between my 'touching' monitors (pointer is in the gap). Note the left side of the clementine music player window cannot be seen. If I drag it a little left, I can have ~2cm of the window appear on both displays however it's useless as almost none of the window is actionable or readable. This maybe a wrong filing, and is only a duplicate of aforementioned bug (1882411) report. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: openbox 3.6.1-12build4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue Apr 9 15:22:24 2024 InstallationDate: Installed on 2024-04-09 (0 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408) SourcePackage: openbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060614 Title: lubuntu lxqt - space between touching monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2060614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060592] Re: lubuntu noble - another timeout issue (600 secs)
On reboot of install, system looks good (I didn't bother checking for the optional components given error..) but standard Lubuntu which even had all updates applied!! was there... EXCEPT no /var/log/installer/ or components; expected given calamares abended with error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060592 Title: lubuntu noble - another timeout issue (600 secs) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2060592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060592] Re: lubuntu noble - another timeout issue (600 secs)
** Description changed:
Lubuntu full install to
- - dc7700
+ - hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt)
- timeout (>600) seconds as I recall the message, and calamares fell over.
+ testcase: FULL, no-encryption, BIOS, internet, swap, updates
- I'll add more shortly.. but I've had a number of timeout type issues on
- this old core2duo box recently
+ snap-seed-glue --seed /tmp/calamares-root-r00b_jf2/var/lib/snapd/seed
+ krita failed to finish in 600 seconds
+
+ I've had a number of timeout type issues on this old core2duo box
+ recently
---
2024-04-09 - 12:00:31 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
- 2024-04-09 - 12:00:31 [1]: ERROR: Installation failed: "External command
failed to finish."
- 2024-04-09 - 12:00:31 [6]: .. - message: "External command failed to
finish."
+ 2024-04-09 - 12:00:31 [1]: ERROR: Installation failed: "External command
failed to finish."
+ 2024-04-09 - 12:00:31 [6]: .. - message: "External command failed to
finish."
2024-04-09 - 12:00:31 [6]: .. - details: Command snap-seed-glue --seed
/tmp/calamares-root-r00b_jf2/var/lib/snapd/seed krita failed to finish in
600 seconds.
There was no output from the command.
---
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
---
dontChroot: false
timeout: 120
firmwareType:
"*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CurrentDesktop: LXQt
Date: Tue Apr 9 12:02:52 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.23
calamares-settings-lubuntu 1:24.04.23
xfsprogs 6.6.0-1ubuntu2
btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060592
Title:
lubuntu noble - another timeout issue (600 secs)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2060592/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060592] [NEW] lubuntu noble - another timeout issue (600 secs)
Public bug reported:
Lubuntu full install to
- hp dc7700 (c2d-e6320, 8gb, amd/ati rv610/radeon hd2400 pro/xt)
testcase: FULL, no-encryption, BIOS, internet, swap, updates
snap-seed-glue --seed /tmp/calamares-root-r00b_jf2/var/lib/snapd/seed
krita failed to finish in 600 seconds
I've had a number of timeout type issues on this old core2duo box
recently
---
2024-04-09 - 12:00:31 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-09 - 12:00:31 [1]: ERROR: Installation failed: "External command
failed to finish."
2024-04-09 - 12:00:31 [6]: .. - message: "External command failed to
finish."
2024-04-09 - 12:00:31 [6]: .. - details: Command snap-seed-glue --seed
/tmp/calamares-root-r00b_jf2/var/lib/snapd/seed krita failed to finish in
600 seconds.
There was no output from the command.
---
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
---
dontChroot: false
timeout: 120
firmwareType:
"*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CurrentDesktop: LXQt
Date: Tue Apr 9 12:02:52 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.23
calamares-settings-lubuntu 1:24.04.23
xfsprogs 6.6.0-1ubuntu2
btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: calamares (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
** Description changed:
- Lubuntu full install to
+ Lubuntu full install to
- dc7700
timeout (>600) seconds as I recall the message, and calamares fell over.
- I'll add more shortly..
+ I'll add more shortly.. but I've had a number of timeout type issues on
+ this old core2duo box recently
+
+ ---
+ 2024-04-09 - 12:00:31 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ 2024-04-09 - 12:00:31 [1]: ERROR: Installation failed: "External command
failed to finish."
+ 2024-04-09 - 12:00:31 [6]: .. - message: "External command failed to
finish."
+ 2024-04-09 - 12:00:31 [6]: .. - details: Command snap-seed-glue --seed
/tmp/calamares-root-r00b_jf2/var/lib/snapd/seed krita failed to finish in
600 seconds.
+ There was no output from the command.
+ ---
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
- ---
- dontChroot: false
- timeout: 120
- firmwareType:
- "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
+ ---
+ dontChroot: false
+ timeout: 120
+ firmwareType:
+ "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
- ---
- restartNowMode: user-checked
- restartNowCommand: "systemctl -i reboot"
+ ---
+ restartNowMode: user-checked
+ restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
- crypttabOptions: luks,keyscript=/bin/cat
- efiMountOptions: umask=0077
+ crypttabOptions: luks,keyscript=/bin/cat
+ efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
- ---
- dontChroot: true
- timeout: 30
- script:
- - calamares-logs-helper ${ROOT}
+ ---
+ dontChroot: true
+ timeout: 30
+ script:
+ - calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
- ---
- unpack:
- - source: "/cdrom/casper/filesystem.squashfs"
- sourcefs: "squashfs"
- destination: ""
+ ---
+ unpack:
+ - source: "/cdrom/casper/filesystem.squashfs"
+ sourcefs: "squashfs"
+ destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CurrentDesktop: LXQt
Date: Tue Apr 9 12:02:52 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
RelatedPackageVersions:
- calamares-settings-ubuntu-common 1:24.04.23
- calamares-settings-lubuntu 1:24.04.23
-
[Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
Yes, a no-change rebuild fixes the issue. Please see attached debdiff for the fix. I have provided a PPA with the build and tests: PPA: https://launchpad.net/~cpete/+archive/ubuntu/upower arm64 autopkgtest log: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete- upower/noble/arm64/u/upower/20240407_191552_37f4e@/log.gz arm64 autopkgtests artifacts: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete- upower/noble/arm64/u/upower/20240407_191552_37f4e@/artifacts.tar.gz ** Patch added: "upower_1.90.2-8build3_1.90.2-8build4.debdiff" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+attachment/5762206/+files/upower_1.90.2-8build3_1.90.2-8build4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060429] Re: lubuntu noble install error
** Description changed:
- dc7700 install, error was like
+ install to
+ - hp dc7700 (c2d-e6230, 7gb, amd/ati rv610/radeon hd2400 pro/xt)
+ testcase: install using existing partition
- Command /usr/libexec/fixconkeys-part2 failed to finish in 30
- seconds.
+
+ Command /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
(i clicked install at try/install & thus copy of error didn't survive
gui start)
- this was NOT a clean install (no format) BUT a 'install using existing
- partition'..
-
- ie. boot & select the SDA1 as / partition without format...
+ this was NOT a clean install (no format) BUT a 'install using existing
partition'..
+ ie. boot & select the SDA1 as / partition without format...
install on that partition was a lubuntu noble install (with some music files
& a few basic packages installs such as music player (audacious i think, or
clementine)
---
2024-04-08 - 15:43:34 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-08 - 15:43:34 [1]: ERROR: Installation failed: "External command
failed to finish."
2024-04-08 - 15:43:34 [6]: .. - message: "External command failed to
finish."
2024-04-08 - 15:43:34 [6]: .. - details: Command
/usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
There was no output from the command.
2024-04-08 - 15:43:34 [6]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
---
+
+ install reported failure..
+
+ On reboot I can login and everything looks okay (will be passing QA
+ test), BUT /var/log/installer/mediainfo shows 0320.1 ISO which was
+ numerous installs ago & not today's ISO (last install failed, different
+ issue but same type of install thus why numerous installs ago)
+
+ viewing / shows many directories date/timestamped matching a new
+ (re-)install, however some system directories do NOT reflect a re-
+ install; ie. calamares reached an error & stopped the system booted
+ correctly, but that's no doubt because it was a functional Lubuntu noble
+ system & it's using setup possibly from prior install...
+
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
---
dontChroot: false
timeout: 120
firmwareType:
"*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CurrentDesktop: LXQt
Date: Mon Apr 8 15:57:10 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.3)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.23
calamares-settings-lubuntu 1:24.04.23
xfsprogs 6.6.0-1ubuntu2
btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
** Summary changed:
- lubuntu noble install error
+ lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060429
Title:
lubuntu noble - /usr/libexec/fixconkeys-part2 failed to finish in 30
seconds.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2060429/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060429] [NEW] lubuntu noble install error
Public bug reported:
dc7700 install, error was like
Command /usr/libexec/fixconkeys-part2 failed to finish in 30
seconds.
(i clicked install at try/install & thus copy of error didn't survive
gui start)
this was NOT a clean install (no format) BUT a 'install using existing
partition'..
ie. boot & select the SDA1 as / partition without format...
install on that partition was a lubuntu noble install (with some music files &
a few basic packages installs such as music player (audacious i think, or
clementine)
---
2024-04-08 - 15:43:34 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-08 - 15:43:34 [1]: ERROR: Installation failed: "External command
failed to finish."
2024-04-08 - 15:43:34 [6]: .. - message: "External command failed to
finish."
2024-04-08 - 15:43:34 [6]: .. - details: Command
/usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
There was no output from the command.
2024-04-08 - 15:43:34 [6]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
---
ProblemType: BugDistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
---
dontChroot: false
timeout: 120
firmwareType:
"*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CurrentDesktop: LXQt
Date: Mon Apr 8 15:57:10 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.3)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.23
calamares-settings-lubuntu 1:24.04.23
xfsprogs 6.6.0-1ubuntu2
btrfs-progs 6.6.3-1.1build2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: calamares (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble third-party-packages
** Description changed:
- dc7700 install, will add more once I get to remind myself of error
- (i clicked install & thus copy of error didn't survive gui start)
+ dc7700 install, error was like
- ProblemType: Bug
- DistroRelease: Ubuntu 24.04
+ Command /usr/libexec/fixconkeys-part2 failed to finish in 30
+ seconds.
+
+ (i clicked install at try/install & thus copy of error didn't survive
+ gui start)
+
+ ---
+ 2024-04-08 - 15:43:34 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ 2024-04-08 - 15:43:34 [1]: ERROR: Installation failed: "External command
failed to finish."
+ 2024-04-08 - 15:43:34 [6]: .. - message: "External command failed to
finish."
+ 2024-04-08 - 15:43:34 [6]: .. - details: Command
/usr/libexec/fixconkeys-part2 failed to finish in 30 seconds.
+ There was no output from the command.
+ 2024-04-08 - 15:43:34 [6]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ ---
+
+
+ ProblemType: BugDistroRelease: Ubuntu 24.04
Package: calamares 3.3.5-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
- ---
- dontChroot: false
- timeout: 120
- firmwareType:
- "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
+ ---
+ dontChroot: false
+ timeout: 120
+ firmwareType:
+ "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
- ---
- restartNowMode: user-checked
- restartNowCommand: "systemctl -i reboot"
+ ---
+ restartNowMode: user-checked
+ restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
- crypttabOptions: luks,keyscript=/bin/cat
- efiMountOptions: umask=0077
+ crypttabOptions: luks,keyscript=/bin/cat
+ efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
- ---
- dontChroot: true
- timeout: 30
- script:
- - calamares-logs-helper ${ROOT}
+ ---
+ dontChroot: true
+ timeout: 30
+ script:
+ - calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
- ---
- unpack:
- - source: "/cdrom/casper/filesystem.squashfs"
- sourcefs: "squashfs"
- destination: ""
+ ---
+ unpack:
+ - source: "/cdrom/casper/filesystem.squashfs"
+
[Bug 2060409] Re: Some slides in the Ubuntu MATE installer are no longer relevant
** Tags added: noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060409 Title: Some slides in the Ubuntu MATE installer are no longer relevant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/2060409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060375] Re: Error appeared when updating Snap on Ubuntu 20
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2060375 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060375 Title: Error appeared when updating Snap on Ubuntu 20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2060375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060244] Re: autokpgtest failure astroml/1.0.2-3 vs numpy/1.25+
Please see the attached debdiff for the fix.
I built and tested this in a PPA with -proposed enabled in the build and
all-proposed in the autopkgtest:
Build PPA: https://launchpad.net/~cpete/+archive/ubuntu/astroml
Autopkgtest artifacts:
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-cpete-
astroml/noble/amd64/a/astroml/20240405_023032_3b686@/artifacts.tar.gz
Autopkgtest log: https://autopkgtest.ubuntu.com/results/autopkgtest-
noble-cpete-astroml/noble/amd64/a/astroml/20240405_023032_3b686@/log.gz
** Patch added: "astroml_1.0.2-3_1.0.2-3ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/astroml/+bug/2060244/+attachment/5761610/+files/astroml_1.0.2-3_1.0.2-3ubuntu1.debdiff
** Changed in: astroml (Ubuntu)
Status: In Progress => New
** Changed in: astroml (Ubuntu)
Assignee: Chris Peterson (cpete) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060244
Title:
autokpgtest failure astroml/1.0.2-3 vs numpy/1.25+
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/astroml/+bug/2060244/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060251] [NEW] module not found: numpy.distutils
Public bug reported: NumPy has deprecated numpy.distutils in NumPy 1.23.0 for Python3.12 [0]. This relates to LP: #2049369 but may not be the only related bug. An example autopkgtest failure can be seen in [1]. [0] https://numpy.org/doc/stable/reference/distutils_status_migration.html [1] https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/c/cython-legacy/20240404_174332_60c06@/log.gz ** Affects: cython-legacy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060251 Title: module not found: numpy.distutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cython-legacy/+bug/2060251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060244] Re: autokpgtest failure astroml/1.0.2-3 vs numpy/1.25+
In progress, awaiting ppa build to publish and will queue autopkgtests ** Changed in: astroml (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060244 Title: autokpgtest failure astroml/1.0.2-3 vs numpy/1.25+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/astroml/+bug/2060244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060346] Re: lubuntu noble install - apt-get failure?? temporary web issue or what?
Install looks good to me.. HOWEVER /var/log/media/installer shows Ubuntu 24.04 20240320.1 and not 20240328 which is listed above.. some directory metadata (date/time stamps) are perfect and show an install only mins ago... HOWEVER some show 28-March-2024 which better fit the 20.1 ISO.. thus I gather calamares aborted & didn't complete install... and the install is making up for missing details from a prior install (given no format was performed).. either way I'm passing install... but it worked in this particular instance (I've done it before I'm sure and had login & looks okay before, but missing metadata; where it's too-old metadata I'd say here) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060346 Title: lubuntu noble install - apt-get failure?? temporary web issue or what? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2060346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060244] Re: autokpgtest failure astroml/1.0.2-3 vs numpy/1.25+
Thanks for the sponsorship ginggs! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060244 Title: autokpgtest failure astroml/1.0.2-3 vs numpy/1.25+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/astroml/+bug/2060244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060346] [NEW] lubuntu noble install - apt-get failure?? temporary web issue or what?
Public bug reported:
I've not yet looked at what happened, calamares just reported failure.
install on dc7700; using existing partition (single sda1), prior install
was Ubuntu Desktop booted ~15 mins prior to install... partitioning
was made by prior full-disk install
---
I tried to copy/paste what I saw from calamares; but on closure the
'pasted' details cleared before LXQt desktop was fully functional, but
following matches what I saw.
2024-04-06 - 19:25:27 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
2024-04-06 - 19:25:27 [1]: ERROR: Installation failed: "External command
failed to finish."
2024-04-06 - 19:25:27 [6]: .. - message: "External command failed to
finish."
2024-04-06 - 19:25:27 [6]: .. - details: Command apt-get -y
full-upgrade failed to finish in 300 seconds.
Even if we can do nothing about this actual problem (SUCH AS IT being a
temporary internet failure..)... maybe we should write up something on
discourse/documentation (not worth manual) on the issue.. even if its
just a retry
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
---
dontChroot: false
timeout: 120
firmwareType:
"*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
crypttabOptions: luks,keyscript=/bin/cat
efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
---
dontChroot: true
timeout: 30
script:
- calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
---
unpack:
- source: "/cdrom/casper/filesystem.squashfs"
sourcefs: "squashfs"
destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.494
CurrentDesktop: LXQt
Date: Sat Apr 6 19:32:23 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240328)
RelatedPackageVersions:
calamares-settings-ubuntu-common 1:24.04.16
calamares-settings-lubuntu 1:24.04.16
xfsprogs 6.6.0-1ubuntu1
btrfs-progs 6.6.3-1.1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: calamares (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
** Description changed:
I've not yet looked at what happened, calamares just reported failure.
install on dc7700; using existing partition (single sda1), prior install
was Ubuntu Desktop booted ~15 mins prior to install... partitioning
was made by prior full-disk install
+
+ ---
+
+ I tried to copy/paste what I saw from calamares; but on closure the
+ 'pasted' details cleared before LXQt desktop was fully functional, but
+ following matches what I saw.
+
+ 2024-04-06 - 19:25:27 [1]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
+ 2024-04-06 - 19:25:27 [1]: ERROR: Installation failed: "External command
failed to finish."
+ 2024-04-06 - 19:25:27 [6]: .. - message: "External command failed to
finish."
+ 2024-04-06 - 19:25:27 [6]: .. - details: Command apt-get -y
full-upgrade failed to finish in 300 seconds.
+
+ Even if we can do nothing about this actual problem (SUCH AS IT being a
+ temporary internet failure..)... maybe we should write up something on
+ discourse/documentation (not worth manual) on the issue.. even if its
+ just a retry
+
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
- ---
- dontChroot: false
- timeout: 120
- firmwareType:
- "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
+ ---
+ dontChroot: false
+ timeout: 120
+ firmwareType:
+ "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
- ---
- restartNowMode: user-checked
- restartNowCommand: "systemctl -i reboot"
+ ---
+ restartNowMode: user-checked
+ restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
- crypttabOptions: luks,keyscript=/bin/cat
- efiMountOptions: umask=0077
+ crypttabOptions: luks,keyscript=/bin/cat
+ efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
- ---
- dontChroot: true
- timeout: 30
- script:
- - calamares-logs-helper ${ROOT}
+ ---
+ dontChroot: true
+ timeout: 30
+ script:
+ - calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
- ---
- unpack:
- - source: "/cdrom/casper/filesystem.squashfs"
- sourcefs: "squashfs"
-
[Bug 2060335] Re: upower/1.90.2-8build3 autopkgtest failure on arm64
I estimate another ncr could fix the issue. Building and testing in a ppa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060335 Title: upower/1.90.2-8build3 autopkgtest failure on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2060335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060335] [NEW] upower/1.90.2-8build3 autopkgtest failure on arm64
Public bug reported: autopkgtests fail, only on arm64, after a no-change-rebuild, with the following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 689s 689s -- 689s Ran 66 tests in 194.378s 689s 689s FAILED (failures=2, errors=1) full log: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/u/upower/20240405_224518_5cff1@/log.gz These test passed in the previous version: https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/arm64/u/upower/20240405_224754_d187c@/log.gz ** Affects: upower (Ubuntu) Importance: Undecided Assignee: Chris Peterson (cpete) Status: In Progress ** Tags: update-excuse ** Description changed: - autopkgtests fail, only on arm64, with the following output: + autopkgtests fail, only on arm64, after a no-change-rebuild, with the + following output: 689s [32mTI:22:39:23 [34mHandling SIGTERM 689s [0m. 689s == 689s ERROR: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/lib/python3.12/shutil.py", line 785, in rmtree 689s _rmtree_safe_fd(fd, path, onexc) 689s File "/usr/lib/python3.12/shutil.py", line 717, in _rmtree_safe_fd 689s onexc(os.unlink, fullname, err) 689s File "/usr/lib/python3.12/shutil.py", line 715, in _rmtree_safe_fd 689s os.unlink(entry.name, dir_fd=topfd) 689s FileNotFoundError: [Errno 2] No such file or directory: 'history-time-full-G935_Gaming_Headset.dat.KL0SL2' - 689s + 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 2558, in test_daemon_restart 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 - 689s + 689s 689s == 689s FAIL: test_daemon_restart (__main__.Tests.test_daemon_restart) 689s -- 689s Traceback (most recent call last): 689s File "/usr/libexec/upower/integration-test.py", line 173, in tearDown 689s self.stop_daemon() 689s File "/usr/libexec/upower/integration-test.py", line 239, in stop_daemon 689s self.assertEqual(self.daemon.wait(timeout=5.0), 0) 689s AssertionError: -15 != 0 - 689s + 689s 689s -- 689s Ran 66 tests in 194.378s - 689s + 689s 689s FAILED (failures=2,
[Bug 2059182] Re: autopkgtests fail for dune-grid/2.9.0-2build1
Ah that worked out, thanks for the update Lucas. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059182 Title: autopkgtests fail for dune-grid/2.9.0-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dune-uggrid/+bug/2059182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059291] Re: autopkgtest failure against libphonenumber/8.12.57+ds-4.2build1
> Added a reference to this bug in the changelog Thank you for catching that! Also, thank you for the sponsorship. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059291 Title: autopkgtest failure against libphonenumber/8.12.57+ds-4.2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pnc/+bug/2059291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060251] Re: module not found: numpy.distutils
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060251 Title: module not found: numpy.distutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cython-legacy/+bug/2060251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060250] Re: autopkgtests are flaky due to threadedness
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060250 Title: autopkgtests are flaky due to threadedness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/contourpy/+bug/2060250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060244] [NEW] autokpgtest failure astroml/1.0.2-3 vs numpy/1.25+
Public bug reported: The autopkgtest fails with following error: 280s ERRORS 280s ___ ERROR collecting tests/test_resample.py 280s ImportError while importing test module '/usr/lib/python3/dist-packages/astroML/tests/test_resample.py'. 280s Hint: make sure your test modules/packages have valid Python names. 280s Traceback: 280s /usr/lib/python3.12/importlib/__init__.py:90: in import_module 280s return _bootstrap._gcd_import(name[level:], package, level) 280s /usr/lib/python3/dist-packages/astroML/tests/test_resample.py:2: in 280s from numpy.testing import assert_allclose, run_module_suite 280s E ImportError: cannot import name 'run_module_suite' from 'numpy.testing' (/usr/lib/python3/dist-packages/numpy/testing/__init__.py) This function was removed in numpy version 1.25 [0] There is a patch in Debian [1] I will cherry pick [0] https://numpy.org/doc/stable/release/1.25.0-notes.html [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067136 ** Affects: astroml (Ubuntu) Importance: Undecided Assignee: Chris Peterson (cpete) Status: New ** Summary changed: - autokpgtest failure against numpy v1.26+ + autokpgtest failure against numpy v1.25+ ** Summary changed: - autokpgtest failure against numpy v1.25+ + autokpgtest failure astroml/1.0.2-3 vs numpy/ v1.25+ ** Summary changed: - autokpgtest failure astroml/1.0.2-3 vs numpy/ v1.25+ + autokpgtest failure astroml/1.0.2-3 vs numpy/1.25+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060244 Title: autokpgtest failure astroml/1.0.2-3 vs numpy/1.25+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/astroml/+bug/2060244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060250] [NEW] autopkgtests are flaky due to threadedness
Public bug reported: It looks likes autopkgtest runners on armhf, ppc64el, s390x are not guaranteed to have multiple threads (perhaps never on ppc64el and 390x) which causes autopkgtest failures like so: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/c/contourpy/20240404_154232_715e2@/log.gz Based on the docs we could change the tests to use: $pytest -k "not threads" or maybe there is a way to request a different resource for these tests in the autopkgtest runners? ** Affects: contourpy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060250 Title: autopkgtests are flaky due to threadedness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/contourpy/+bug/2060250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Hello Alexsander, or anyone else affected, Accepted initramfs-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.136ubuntu6.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056187] Re: fails to configure BOOTIF when using iscsi
Hello Alexsander, or anyone else affected, Accepted initramfs-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.140ubuntu13.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056187 Title: fails to configure BOOTIF when using iscsi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2029473] Re: Backport Ubuntu Pro to Xenial
Hello Nathan, or anyone else affected, Accepted software-properties into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software-properties/0.96.20.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-xenial ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2029473 Title: Backport Ubuntu Pro to Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2029473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060091] Re: lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting..
As I noted in testcase comment at terminal I killed lubuntu-installer-prompt & I had a normal LXQt session appear... At last resort (this issue maybe very rare; if its not transitory..) we can document how to kill lubuntu-installer-prompt as I did on discourse.. no need to mention in release notes even if this is done... After this attempt, I next booted box below this one that uses same keyboard/screens etc & using same thumb-drive have no issues like this at all... no issue with this on - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) I wonder if this relates to video card?? (I'll try another box), then again the Connecting makes me (no doubt end-users) think of internet?? but I could `ubuntu-bug` file on the box so network makes little sense to me... ICMP echo requests (ping) to web are returned -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060091 Title: lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-installer-prompt/+bug/2060091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058035] Re: [SRU] Create directories for apt configuration files if they are absent
Hello Nathan, or anyone else affected, Accepted software-properties into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software-properties/0.96.20.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058035 Title: [SRU] Create directories for apt configuration files if they are absent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060091] [NEW] lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting..
Public bug reported: Booted Lubuntu noble daily on - hp prodesk 400 g1 sff (i5-4570, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) Multiple attempts made, each end in black screens, with a small window on one display titled "Lubuntu" and in the white window below it the word "Connecting..." and a light-dark-blue moving line that doesn't progress.. Multiple boots; and left for >15 mins (one attempt 25+ as I fed birds) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: lubuntu-installer-prompt 24.04.3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.494 Date: Wed Apr 3 06:03:29 2024 LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240328) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=linux XDG_RUNTIME_DIR= SourcePackage: lubuntu-installer-prompt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lubuntu-installer-prompt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060091 Title: lubuntu noble daily never starts.. black screen; Lubuntu box & Connecting.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-installer-prompt/+bug/2060091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
