[Bug 1977678] Re: Crash 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 1977678 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/1977678 Title: Crash on close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1977678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977676] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation 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 mostly 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/1977676 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977683] Re: Lubuntu error has_option: command not found / no ssh-agent after updating to 22.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Lubuntu has used sddm for all LXQt releases (ie. since Lubuntu 18.10), and the upgrade from an release that used lightdm/LXDE is unsupported due to breakage as was warned about in documentation, eg. https://lubuntu.me/focal-2-released/ "Note, due to the extensive changes required for the shift in desktop environments, the Lubuntu team does not support upgrading from 18.04 or below to any greater release. Doing so will result in a broken system. If you are on 18.04 or below and would like to upgrade, please do a fresh install." The error you are describing is a user-created issue by using unsupported upgrade procedures that were documented as creating issues later, and this is warned about breakage. The fresh install would have prevented this. As such I've marked this bug report as "opinion". If you believe I'm in error, please leave a comment explaining why and the bug report can then be returned to "New" (you may find it'll then be marked as "Won't Fix") ** Changed in: lightdm (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977683 Title: Lubuntu error has_option: command not found / no ssh-agent after updating to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1977683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977461] Re: not able to upgrade from ubuntu 14 lts to 20 lts
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. You may find a support site 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 Do note however that Ubuntu 14.04 LTS reached the end of it's standard support back in April-2019 (5 years after release) thus support options are now limited. This also applies to Ubuntu 16.04 LTS (the release 14.04 upgrades to). - Ubuntu 16.04 (xenial) reached end-of-standard-support on - April 29, 2021. - Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977461 Title: not able to upgrade from ubuntu 14 lts to 20 lts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1977461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976611] Re: There is a problem in Ubuntu 22.04 LTS
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 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 have not filed this report against any particular package; so until the package is determined the required `apport-collect` cannot be run. I am not sure what your video is actually trying to show. I've thus marked this bug as 'incomplete', and suggest you seek support. You can convert this bug report into a Question which is aimed at support. ** 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/1976611 Title: There is a problem in Ubuntu 22.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1976611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976556] Re: [Lenovo 300e 2nd GEN] ELAN Touchpad not working
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 1976556 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. ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (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/1976556 Title: [Lenovo 300e 2nd GEN] ELAN Touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976475] Re: Installer crash when try to enable disk encryption
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 1976475 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. ** Package changed: ubuntu => ubiquity (Ubuntu) ** Changed in: ubiquity (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/1976475 Title: Installer crash when try to enable disk encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976433] Re: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el código de salida d
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. Your title & package details match bionic/18.04 (ie. "chromium-browser | 101.0.4951.64-0ubuntu0.18.04.1 | bionic-security/universe | source, amd64, arm64, armhf, i386") but your release is shown as focal/20.04. Are you sure you wouldn't benefit from support? Bug reporting is mostly 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 I've marked this bug report 'incomplete'; if you believe I'm in error, please leave a comment saying why (or details as to your problem) and the status can be returned to 'new' Thank you! ** Changed in: chromium-browser (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/1976433 Title: package chromium-browser 101.0.4951.64-0ubuntu0.18.04.1 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1976433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976473] Re: Unable to change screen brightness in ubuntu desktop
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 1976473 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. ** Changed in: linux (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/1976473 Title: Unable to change screen brightness in ubuntu desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Re: Ubiquity not using password provided by UI
The media used is not a Ubuntu ISO. For this bug to be explored, an official Ubuntu ISO (eg. 20.04.4) would need to be used, to rule out issues created by the unsupported (by Ubuntu) third party ISO used in the initial filing. I've marked this bug report invalid. If you believe this is a ubiquity bug, please use a Ubuntu ISO to confirm the issue occurs there, and file another bug report using `ubuntu-bug ubiquity` if the problem occurs. You can provide a link to this report so additional details noted here can also be used in locating & providing a fix. Thank you for taking the time to report this bug and helping to make Ubuntu better. ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976177] Re: Ubiquity not using password provided by UI
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 1976177 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. Please note, if this is not Ubuntu official media, the report will likely be closed as invalid, as it should be filed with the creator of the non-Ubuntu media. ** Changed in: ubiquity (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/1976177 Title: Ubiquity not using password provided by UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976167] Re: lubuntu 16.04 frequent crashes
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. FYI: Lubuntu 16.04 LTS reached EOL end of April 2019. FYI: The package you filed against is the installer itself; so if your system installed - it's not involved; but that support ended April 2019. ** Changed in: ubiquity (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/1976167 Title: lubuntu 16.04 frequent crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975635] Re: PC Freeze on 5.13.0.40
Thank you for taking the time to report this bug and helping to make Ubuntu better. 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. Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975635 Title: PC Freeze on 5.13.0.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975393] Re: Calamares - unable to select option "Next" after selecting "No Swap"
filed as #1959 upstream (https://github.com/calamares/calamares/issues/1959) which was marked duplicate of #1953 (https://github.com/calamares/calamares/issues/1953) I looked before filing, but missed it :( ** Bug watch added: Calamares Issues #1953 https://github.com/calamares/calamares/issues/1953 ** Changed in: calamares Status: New => Unknown ** Changed in: calamares Remote watch: Calamares Issues #1959 => Calamares Issues #1953 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975393 Title: Calamares - unable to select option "Next" after selecting "No Swap" To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1975393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975393] Re: Calamares - unable to select option "Next" after selecting "No Swap"
** Bug watch added: Calamares Issues #1959 https://github.com/calamares/calamares/issues/1959 ** Also affects: calamares via https://github.com/calamares/calamares/issues/1959 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975393 Title: Calamares - unable to select option "Next" after selecting "No Swap" To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1975393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975393] Re: Calamares - unable to select option "Next" after selecting "No Swap"
I can confirm this issue... (Lubuntu kinetic daily) I worked around it via clicking Encrypt.system & entering password twice & NEXT showed.. I could then unclick Encrypt to get what was wanted.. What Leó suggested (check/uncheck manual partitioning) is easier - sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975393 Title: Calamares - unable to select option "Next" after selecting "No Swap" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1975393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974479] Re: Kubuntu 22.04 Dolphin authentication dialog failed
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've filed this bug report against `ubiquity` as an installation problem, but have provided no specifics as to what ISO you're trying to install etc. The `ubiquity` installer doesn't use SaMBa. You can convert this bug report into a question, which is aimed at support. I've marked this bug report as 'incomplete' as it appears you'd benefit more from support. If this is changed to a question; after additional details have been added the bug-report can be continued or a new one filed. If you believe I'm in error, please leave a comment as to why and the status can be returned to "New". You'll need to run `apport- collect 1974479` once on the impacted box too so specific details can be obtained. ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete ** Tags added: jammy ** Package changed: ubiquity (Ubuntu) => samba (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974479 Title: Kubuntu 22.04 Dolphin authentication dialog failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1974479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895905] Re: lubuntu groovy; flashing of sddm greeter
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. (I don't think I still have the box this bug report was filed on, but the video card was not my own so I cannot retest with that card) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895905 Title: lubuntu groovy; flashing of sddm greeter To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1895905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
> If you now apply the remedy to the stick > dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462 >then i expect it to be permanently booting in reasonable time. > .. Please confirm. Inserted thumb-drive(2) [Ubuntu-MATE jammy] into box and -- start paste guiverc@d960-ubu2:/de2900/ubuntu_mate_64$ sudo dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462 [sudo] password for guiverc: 16+0 records in 16+0 records out 16 bytes copied, 0.0107609 s, 1.5 kB/s -- end paste booted it on j3400 - motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series) on boot (noting when at grub) it had reached maybe-ubiquity in ~3 mins using room clock (no seconds as digital). I made an error in typing SysRq-REO (intended REISUB) so as no sync.. ignoring this bot. turned box back on & booted again; again at maybe-ubiquity in ~3 mins by room clock. Correctly used SysRq-REISUB to restart another boot & again ~3 mins by room clock. SysRq-REISUO now NOTE: I didn't wait for clock to change minute & press enter this time, thus the extra seconds (making 2+ mins ~3 mins) is just ME not starting hitting the timing at ~:01 secs or hitting ENTER just after minute changes.. Either way ~3 mins is NOT TEN minutes as the slow boot takes to reach maybe-ubiquity. This confirms what I believe you wanted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974268] Re: Does this package conflict with systemd oom?
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974268 Title: Does this package conflict with systemd oom? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/earlyoom/+bug/1974268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
-- reply to @Thomas #112 (start paste) So if we want to propose a workaround for the current layout, it would be a good base if you could confirm that j3400 boots after the plain procedure with no other experiments inbetween: # Patch the ISO already as image on hard disk ISO=ubuntu-22.04-desktop-amd64.iso dd if=/dev/zero bs=1 count=16 of="$ISO" conv=notrunc seek=462 # Put it onto the USB stick as you usually do. E.g. sudo dd bs=4M oflag=sync status=progress of=/dev/sdb if="$ISO" Then you would check if it boots twice on the j3400. If the second boot succeeds and shows a writable big partition as last one, then we could be sure that this procedure is a valid workaround. A run of sudo xorriso -indev stdio:/dev/sdb -report_system_area plain would (hopefully) confirm that there is no second MBR partition with boot flag. Of course it would be enough if you can confirm that you did this already during the experiments, with no intermediate manipulations. But given the curvy way of this bug report, we need to be sure. -- (end paste) I grabbed my thumb-drive 2; Ubuntu-MATE jammy (2022-04-19) - plugged into j3400; enter pressed [just] @12:28 using room clock, plymouth seen at 12:36, maybe-ubiquity appeared at 12:38 This wasn't required/requested; but I omitted `sudo` for last; so added here --- (start paste) guiverc@d960-ubu2:~/uwn/issues/735$ sudo xorriso -indev stdio:/dev/sdb -report_system_area plain [sudo] password for guiverc: xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. xorriso : NOTE : Loading ISO image tree from LBA 0 xorriso : UPDATE : 774 nodes read in 1 seconds libisofs: NOTE : Found hidden El-Torito image for EFI. libisofs: NOTE : EFI image start and size: 1422522 * 2048 , 8496 * 512 xorriso : NOTE : Detected El-Torito boot information which currently is set to be discarded Drive current: -indev 'stdio:/dev/sdb' Media current: stdio file, overwriteable Media status : is written , is appendable Boot record : El Torito , MBR protective-msdos-label grub2-mbr cyl-align-off GPT Media summary: 1 session, 1424812 data blocks, 2783m data, 4849m free Volume id: 'Ubuntu-MATE 22.04 LTS amd64' System area options: 0x4201 System area summary: MBR protective-msdos-label grub2-mbr cyl-align-off GPT ISO image size/512 : 5699248 Partition offset : 16 MBR heads per cyl : 0 MBR secs per head : 0 MBR partition table: N Status TypeStart Blocks MBR partition : 1 0x00 0xee1 15630335 MBR partition : 2 0x80 0x0001 GPT: N Info GPT disk GUID : 92da1293cf19e54b80558e26d983bc85 GPT entry array: 2 248 separated GPT lba range : 64 15630272 15630335 GPT partition name : 1 490053004f003900360036003000 GPT partname local : 1 ISO9660 GPT partition GUID : 1 92da1293cf19e54b80548e26d983bc85 GPT type GUID : 1 a2a0d0ebe5b9334487c068b6b72699c7 GPT partition flags: 1 0x1001 GPT start and size : 1 64 5690024 GPT partition name : 2 41007000700065006e006400650064003200 GPT partname local : 2 Appended2 GPT partition GUID : 2 92da1293cf19e54b80578e26d983bc85 GPT type GUID : 2 28732ac11ff8d211ba4b00a0c93ec93b GPT partition flags: 2 0x GPT start and size : 2 5690088 8496 GPT partition name : 3 4700610070003100 GPT partname local : 3 Gap1 GPT partition GUID : 3 92da1293cf19e54b80568e26d983bc85 GPT type GUID : 3 a2a0d0ebe5b9334487c068b6b72699c7 GPT partition flags: 3 0x1001 GPT start and size : 3 5698584 600 GPT partition name : 4 GPT partition GUID : 4 a77519baa6474c698e9d5848797c7dc5 GPT type GUID : 4 af3dc60f838472478e793d69d8477de4 GPT partition flags: 4 0x GPT start and size : 4 5701632 9928641 guiverc@d960-ubu2:~/uwn/issues/735$ --- (end paste) guiverc@d960-ubu2:/de2900/ubuntu_mate_64$ cp -pv jammy-desktop-amd64.iso jammy-desktop-amd64.iso.scdbackup 'jammy-desktop-amd64.iso' -> 'jammy-desktop-amd64.iso.scdbackup' guiverc@d960-ubu2:/de2900/ubuntu_mate_64$ dd if=/dev/zero bs=1 count=16 of=jammy-desktop-amd64.iso.scdbackup conv=notrunc seek=462 16+0 records in 16+0 records out 16 bytes copied, 0.205961 s, 0.1 kB/s guiverc@d960-ubu2:/de2900/ubuntu_mate_64$ sudo dd bs=4M oflag=sync status=progress of=/dev/sdb if=jammy-desktop-amd64.iso.scdbackup [sudo] password for guiverc: 2918014976 bytes (2.9 GB, 2.7 GiB) copied, 786 s, 3.7 MB/s 695+1 records in 695+1 records out 2918014976 bytes (2.9 GB, 2.7 GiB) copied, 785.505 s, 3.7 MB/s Ejected thumb-drive (2) & booted on plugged into hp.dc7700; it failed to boot :( On j3400; pressed ENTER (at grub) at 13:10 (room clock).. I didn't note time of plymouth but I had maybe-ubiquity @ 13:13 (room clock) for altered version of 2022-04-19 ISO I used SysRq-REISUO to shutdown there.. (I'm reading your instructions as I do it) so I'll now boot twice
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
My thumb-drive K does not boot on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) - hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915) as it stands now.. (No big news as dc7700 & dc7900 usually react the same; but confirmed it won't boot on dc7900) Likely not required; but again -- guiverc@d960-ubu2:~/uwn/issues/735$ xorriso -indev stdio:/dev/sdb -report_system_area plain xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. libburn : SORRY : Failed to open device (a pseudo-drive) : Permission denied xorriso : FAILURE : Cannot acquire drive 'stdio:/dev/sdb' xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' -- Executed -- [sudo] password for guiverc: root@d960-ubu2:~# echo $'\x80' | dd of=/dev/sdb bs=1 count=1 conv=notrunc seek=446 1+0 records in 1+0 records out 1 byte copied, 0.000132766 s, 7.5 kB/s root@d960-ubu2:~# -- Safely ejected thumb-drive; tested and it NOW BOOTS ON - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) - hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915) I only booted to maybe-ubiquity|try/install then used sysrq-REISUO. If you needed me to complete boot & shutdown like a user, you'll have to ask me to do that. I tested boot again on - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) and sysrq-REISUO when it reached maybe-ubiquity|try/install The following would NOT BOOT thumb-drive K now - sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT) (I didn't get it to boot on samsung 700t1c-p10aat either, but I can't rule out me; as I find that device a pain booting external media) Inserting thumb-drive K into my primary box -- guiverc@d960-ubu2:~/uwn/issues/735$ xorriso -indev stdio:/dev/sdb -report_system_area plain xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. libburn : SORRY : Failed to open device (a pseudo-drive) : Permission denied xorriso : FAILURE : Cannot acquire drive 'stdio:/dev/sdb' xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' guiverc@d960-ubu2:~/uwn/issues/735$ xorriso -indev stdio:/dev/sdb -report_system_area plain xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. libburn : SORRY : Failed to open device (a pseudo-drive) : Permission denied xorriso : FAILURE : Cannot acquire drive 'stdio:/dev/sdb' xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' guiverc@d960-ubu2:~/uwn/issues/735$ sudo xorriso -indev stdio:/dev/sdb -report_system_area plain [sudo] password for guiverc: xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. xorriso : NOTE : Loading ISO image tree from LBA 0 xorriso : UPDATE : 940 nodes read in 1 seconds libisofs: NOTE : Found hidden El-Torito image for EFI. libisofs: NOTE : EFI image start and size: 1782345 * 2048 , 8496 * 512 xorriso : NOTE : Detected El-Torito boot information which currently is set to be discarded Drive current: -indev 'stdio:/dev/sdb' Media current: stdio file, overwriteable Media status : is written , is appendable Boot record : El Torito , MBR protective-msdos-label grub2-mbr cyl-align-off GPT Media summary: 1 session, 1784635 data blocks, 3486m data, 4146m free Volume id: 'Ubuntu 22.04 LTS amd64' System area options: 0x4201 System area summary: MBR protective-msdos-label grub2-mbr cyl-align-off GPT ISO image size/512 : 7138540 Partition offset : 16 MBR heads per cyl : 0 MBR secs per head : 0 MBR partition table: N Status TypeStart Blocks MBR partition : 1 0x80 0xee1 15630335 GPT: N Info GPT disk GUID : cfe88ff9575b6a418e0fa695d43fc159 GPT entry array: 2 248 separated GPT lba range : 64 15630272 15630335 GPT partition name : 1 490053004f003900360036003000 GPT partname local : 1 ISO9660 GPT partition GUID : 1 cfe88ff9575b6a418e0ea695d43fc159 GPT type GUID : 1 a2a0d0ebe5b9334487c068b6b72699c7 GPT partition flags: 1 0x1001 GPT start and size : 1 64 7129316 GPT partition name : 2 41007000700065006e006400650064003200 GPT partname local : 2 Appended2 GPT partition GUID : 2 cfe88ff9575b6a418e0da695d43fc159 GPT type GUID : 2 28732ac11ff8d211ba4b00a0c93ec93b GPT partition flags: 2 0x GPT start and size : 2 7129380 8496 GPT partition name : 3 4700610070003100 GPT partname local : 3 Gap1 GPT partition GUID : 3 cfe88ff9575b6a418e0ca695d43fc159 GPT type GUID : 3 a2a0d0ebe5b9334487c068b6b72699c7 GPT partition flags: 3 0x1001 GPT start and size : 3 7137876 600 GPT partition name : 4 GPT partition GUID : 4 8e2bdedd63554344a8fad7869da92b5a GPT type GUID : 4 af3dc60f838472478e793d69d8477de4 GPT partition flags: 4 0x GPT start and size : 4 7139328 8490945 -- BUT PLEASE DO NOTE I didn't complete a single boot; using
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
My thumb-drive K (what was used in #107 & #101) which contains Ubuntu 22.04 LTS (20220416) resulted in PLEASE NOTE: I just noted the ISO date shows it wasn't the released image.. It'll be the last daily/final/RC i actually used in testing... I'd expect 20220419 for the released ISO. I don't expect it'll impair these results though. (parts of lsblk & blkid are included... I'm not sure the provided command xorriso contains I expected) sdb 8:16 1 7.5G 0 disk ├─sdb1 8:17 1 3.4G 0 part /media/guiverc/Ubuntu 22.04 LTS amd64 ├─sdb2 8:18 1 4.1M 0 part ├─sdb3 8:19 1 300K 0 part └─sdb4 8:20 1 4G 0 part /media/guiverc/writable sr0 11:01 1024M 0 rom guiverc@d960-ubu2:~/uwn/issues/735$ xorriso -indev /dev/sdb -report_system_area plain xorriso 1.5.4 : RockRidge filesystem manipulator, libburnia project. xorriso : FAILURE : Drive address '/dev/sdb' rejected because: not MMC and -drive_class 'caution' '/dev' xorriso : HINT : If the address is a legitimate target, prepend "stdio:" xorriso : aborting : -abort_on 'FAILURE' encountered 'FAILURE' guiverc@d960-ubu2:~/uwn/issues/735$ lsblk^Crriso -index /dev/sdb -report_system_area plain guiverc@d960-ubu2:~/uwn/issues/735$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS .. redacting loop devices & my sda disk sdb 8:16 1 7.5G 0 disk ├─sdb1 8:17 1 3.4G 0 part /media/guiverc/Ubuntu 22.04 LTS amd64 ├─sdb2 8:18 1 4.1M 0 part ├─sdb3 8:19 1 300K 0 part └─sdb4 8:20 1 4G 0 part /media/guiverc/writable -- I stopped at this point & haven't performed > This is obviously one of the machines which demand a boot flag in MBR. Does > it boot after you (rawly and naughtily) set the boot flag to MBR Please advise if I should continue, or other (the xorriso output didn't appear right to me) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973827] Re: Laptop freezes when recovering from suspend / sleep mode
Thanks for taking the time to report this bug and helping to make Ubuntu better. Your log indicates you installed Ubuntu 22.04 LTS, are still using it and haven't upgraded to a later release such as Ubuntu kinetic using Ubuntu-release-upgrader. I've thus changed package to gnome-shell. (apologies if still an incorrect package) ** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973827 Title: Laptop freezes when recovering from suspend / sleep mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973843] Re: upgrade from 16.04 to 18.04 failed
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please install a fully supported release of Ubuntu and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. Ubuntu 16.04 is in Extended Support; so if you're using ESM you can use your ESM support options. ** Changed in: ubuntu-release-upgrader (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/1973843 Title: upgrade from 16.04 to 18.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973381] Re: ubuntu get stuck
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 I've marked this issue as "incomplete" as it appears to me you're asking for support. You've filed this bug as an installer issue (against the `ubiquity` installer) which isn't installed as the install completed successfully. If you believe I'm in error, you can return status to "New" after leaving a comment explaining why. The package would need change. A better option maybe turning this filed bug report into a Launchpad Question, which is geared for support purposes. ** Changed in: ubiquity (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/1973381 Title: ubuntu get stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1973381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
Thomas Schmitt in #104 >...> motion computing j3400 > This one is possibly allowed to be somewhat slow. From me (comment #76) > ((or 3 mins 30 secs for `hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)` The time for lubuntu kinetic actually beat a comparison time of one of an old hp.dc7700 I use heaps in QA-testing. > This prompts another test request @ Chris Guiver: > Does it help to remove MBR partition 2 similarly to what i proposed a year > ago to José Marinho and what helped to boot: I performed the command `sudo dd if=/dev/zero bs=1 count=16 of=/dev/sdb conv=notrunc seek=462` to Ubuntu Desktop 22.04 LTS thumb-drive (K) Booted on j3400 (note: times for BOOT1 will be ~3-8 secs slower than reported due my- error operating phone-stopwatch) BOOT1: (I won't give times as I can't be sure which are which) 00:18, 00:27, 01:57, 02:18, 02:45 HOWEVER either way it was fully-operational at 2 min 45 secs (or 3-8 secs after that anyway) system just rebooted (alt-sysreq+reisub) BOOT2: 00:25 screen clears & message(s) 00:28 plymouth seen 02:17 maybe-ubiquity; try/install selection (I may have been a tad slow here in selecting try) 02:41 (i forget sorry) 03:11 system fully-operational Maybe my [estimated] 3-8 secs is inaccurate; but I'd suggest it was similar. FYI: If you need more testing; just ask (or I miss anything I was asked).. I'll boot the thumb-drive on a few boxes to confirm no issues with the I'll go & boot the thumb-drive on some boxes to ensure it's usable elsewhere.. I'll edit this and add boxes it was tested on (I'm not expecting any issues) It booted successfully on - hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600) BUT FAILED TO BOOT on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
I grabbed my phone (stopwatch app) & lubuntu (kinetic; what was used last time) thumb-drive & timed a boot of Lubuntu kinetic (no new write of ISO) Purpose: > (#102) Are those times stable or do they vary by minutes ? I hoped it would be a re-creation of #92 (but didn't read was there so it wouldn't influence result), alas I didn't use stopwatch then & didn't note which option I used > (#92) I didn't set up stopwatch to time correctly; but room clock said 13:16 at start of boot, and system was fully functional just as it hit 13:22 ie. system operation in ~5 mins (<5 I believe as clock had just flipped 13:22 as it appeared), but I didn't say if persistent OR live was used. OPTION USED THIS TIME = LIVE only (not persistent) BOOT 1: LIVE started stopwatch as I pressed ENTER at grub by 2 mins 43 secs the system appeared functional BOOT2: LIVE 00:25 secs & screen blanks & messages 00:35 plymouth visible 01:11 message(s) again & plymouth gone 02:23 system fully-operational BOOT3: LIVE 00:29 secs & screen blanks & messages 00:35 plymouth visible 01:10 message(s) again & plymouth gone 02:25 system fully-operational BOOT4: PERSISTENCE 00:27 secs & screen blanks & messages 00:34 plymount visible 01:41 message(s) again & plymouth gone 03:06 system fully-operational (boot 4 and there was a longer delay between wallpaper being drawn & the menu responding to wacom-pen or SUPER key being pressed & menu appearing which is what I use to detect 'fully-operational) Boot 2 & 3 are identical; any differences will be me needing to press the screen on the phone more than once to get it to register 'lap' time. Re-creating test #101 using Ubuntu Desktop 22.04 LTS (comment #101) > - 00:09 enter pressed at GRUB > - 08:06 screen blacked > - 08:20 ubuntu plymouth first appeared > - 09:52 plymouth is gone, system text message appears > - 10:10 maybe-ubiquity TRY INSTALL prompt > - 10:37 system fully operational (I started time at ENTER PRESSED at GRUB, so 9 secs difference expected) 08:01 screen blanked 08:08 ubuntu plymouth first appeared 09:41 plymouth is gone, system text message(s) appear 10:08 maybe-ubiquity; TRY/INSTALL prompt 10:55 system fully operational Times here start out consistent (9 secs difference expected as I started time with right hand as I hit enter at grub with left, last time it was when I saw 'grub' prior to grub.menu appearing), however at MAYBE- UBIQUITY times differed a bit.. and final-operational differs well beyond any user/me error(s) Picking when a system is 'fully operational' is subjective, so a few secs difference can be just me using wacom-pen touching screen OR hitting SUPER at the right sec, versus a short delay (as I'm not hitting key/pen rapidly), but we have ~30 secs difference (10mins37secs-9sec 10m55s?) > (#102) Are those times stable or do they vary by minutes ? To me as a user they feel ~stable; but BOOT 1 of Lubuntu LIVE was slower than BOOTS 2 & 3 (which were consistent; boot 4 was different mode).. and some some times of Ubuntu Desktop were identical; but by end they differed beyond I believe could be me. They don't vary by minutes though in my opinion; secs like this is all I've generally noted (and some of those secs are likely me/dog; hitting my phone with the wacom pen for the device instead of my finger as I did on last test; I can't see that adding 20 secs though! etc) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973565] Re: Upgrade to 21.10 not working
Thank you for taking the time to report this issue and helping to make Ubuntu better. It looks to me that Unofficial software packages (not provided by Ubuntu) have been added to your system, many from Tuxedo Computers. Foreign: beekeeper-studio containerd.io docker-ce docker-ce-cli docker- ce-rootless-extras docker-scan-plugin firmware-sof-signed helm linux- firmware linux-headers-5.13.0-10039-tuxedo linux- headers-5.15.0-10025-tuxedo linux-headers-tuxedo-20.04 linux- image-5.13.0-10039-tuxedo linux-image-5.15.0-10025-tuxedo linux-image- tuxedo-20.04 linux-modules-5.13.0-10039-tuxedo linux- modules-5.15.0-10025-tuxedo linux-modules-extra-5.13.0-10039-tuxedo linux-modules-extra-5.15.0-10025-tuxedo linux-tuxedo-20.04 linux- tuxedo-5.13-headers-5.13.0-10039 linux-tuxedo-5.15-headers-5.15.0-10025 tuxedo-control-center tuxedo-keyboard tuxedo-one-theme tuxedo-one- wallpapers tuxedo-tomte tuxedo-touchpad-switch tuxedo-two-icons tuxedo- webfai-creator Unofficial software packages not provided by Ubuntu, can be removed using 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. I've marked this 'incomplete', as this issue appears to be created by 3rd party packages (was it a Ubuntu install? or a respin from tuxedo?). If you believe I'm in error, you can return status to 'New' after leaving a message explaining why, or what I've missed. ** Changed in: ubuntu-release-upgrader (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/1973565 Title: Upgrade to 21.10 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973477] Re: unable to upgrade to xubuntu
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've reported your issue relates to installation (ubiquity is the installer), yet your system was installed 24 days ago? You can convert this bug report into a question which is geared at support. I've marked this report as "incomplete" as it doesn't fit an installation (ubiquity) issue & appears you're after support. ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete ** Package changed: ubiquity (Ubuntu) => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973477 Title: unable to upgrade to xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1973477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973564] Re: File dialog doesn't return current filter in Ubuntu 20.04
** Summary changed: - File dialog doesn't return current filter in Ubuntu 20.02 + File dialog doesn't return current filter in Ubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973564 Title: File dialog doesn't return current filter in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1973564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973464] Re: Firefox does not supply name when it asks to open default keyring in Lubuntu 20.04
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 1973464 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. (please run it on the impacted box; so details can be correctly populated allowing exploration using tools) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973464 Title: Firefox does not supply name when it asks to open default keyring in Lubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
Booting the released image of Ubuntu Desktop 22.04 LTS - 00:00 word 'GRUB' appeared on screen (where I started stopwatch, so these results will be ~10 secs slower sorry) - 00:09 enter pressed at GRUB - 08:06 screen blacked - 08:20 ubuntu plymouth first appeared - 09:52 plymouth is gone, system text message appears - 10:10 maybe-ubiquity TRY INSTALL prompt - 10:37 system fully operational quick comparison with comment #90 (https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/comments/90) shows ~minute longer to be fully functional; given a 1-5 secs gets lost as touch 'try ubuntu' it's still longer lubuntu (jammy) plymouth seen at 7:27 (#90) ubuntu (jammy) plymouth seen at 8:20 (#101) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845756] Re: lubuntu - strange movement of wallpaper on monitor.settings change (or next login)
Lubuntu kinetic daily (ISO 2020-04-13) on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) both monitors are landscape currently; only change was swap left & right you'll note background on my-left screen is none, my-right screen has left portion of wallpaper/background ** Tags added: kinetic ** Attachment added: "screen01.jpg" https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/1845756/+attachment/5589796/+files/screen01.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845756 Title: lubuntu - strange movement of wallpaper on monitor.settings change (or next login) To manage notifications about this bug go to: https://bugs.launchpad.net/openbox/+bug/1845756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
I just booted Lubuntu kinetic daily on - motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series) I didn't set up stopwatch to time correctly; but room clock said 13:16 at start of boot, and system was fully functional just as it hit 13:22, which is way faster than comment #90 on same box with jammy ISO. The ISO wasn't cloned to thumb-drive; but written using `sudo -H dus-iso2usb kinetic-desktop-amd64.iso /dev/sdb msdos grub-2.0.4 persistent` guiverc@d960-ubu2:/de2900/lubuntu_64$ apt-cache policy mkusb mkusb: Installed: 22.0.1-1ubuntu2 Candidate: 22.0.1-1ubuntu2 Version table: *** 22.0.1-1ubuntu2 500 500 http://ppa.launchpad.net/mkusb/unstable/ubuntu kinetic/main amd64 Packages This comparison isn't complete; as different ISOs used (jammy vs kinetic) & different writes (clone/dd vs mkusb-altered), but noted here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973393] Re: auto go to left or first page
Thank you for taking the time to report this bug and helping to make Ubuntu better. The Brave browser is a 3rd party browser, and problems with that browser should be reported to the developers of the application. You mention the Ubuntu workspace, but which you like mean `gnome-shell`. If it's occurring in other application besides the 3rd party brave- browser it's not clear to me sorry. I've marked this incomplete due to issue being with 3rd party package. If the issue occurs within GNOME-SHELL or other windows and not just the brave-browser; please return the status to "New" and change the package to 'gnome-shell'. 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 in future, 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 ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Incomplete ** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973393 Title: auto go to left or first page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972889] Re: Screen reader reads the data while computer is locked
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972889 Title: Screen reader reads the data while computer is locked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886129] Re: xubuntu : displays have become blank & unusable
I agree it sounds like nouveau. That box has issues with the 5.13/5.15 kernel with GNOME, KDE with nouveau on occasion, and has for a few releases now (22.04, 21.10 & possible earlier).. but was always good with Lubuntu/Xubuntu (I really use it now only for install tests & have been thinking of switching out video card) I booted Xubuntu 22.04 LTS on the box the bug report was made on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) the external drive is no longer present, so I instead `apt install nfs- common` & mounted a NFS share for the random video files. Display setup was adjusted to match my setup (one screen above the other), then thunar navigated to various directories containing video files, and them dragged to an open parole player. The parole player was adjusted (window size), dragged around, maximized, un-maximized, full-screen, normal, then another video file dragged to it. This was repeated many times with many different files (may not have been the same file type). I did NOT re-create that issue. ALTERNATE/DIFFERENT ISSUE: I did have a case where a new video was started (mp4) in the existing player, the player was dragged to the other screen, then made to be full-screen; the controls went to the bottom of the screen, but the movie-picture did not increase in size; remaining the same identical size/shape as before the 'f' for full-screen was commanded (ie. picture remained small window size). If I hit 'f' again to return it to normal size; it would return to normal, hit 'f' again and it properly went to full size (controls at bottom of screen and video-picture using all of screen size)... hitting 'f' repeatedly to return to window, then back to full-screen (not pressing 'f' quickly; giving it time to cope given this box is old/slow) & the issue of black-background, controls at the bottom but video-picture remaining window-size would re-occur every so often (3rd time, 5th time, 11th time, 12th time, .. On some occasions the small video-picture had the rest of the display black, other times the wallpaper & thunar window was still evident. That however is a different issue.. and again maybe nouveau related so I'm going to ignore unless requested to file a new bug against it (where I'll try & re-create it & explore further, inc. on another box [hp 8200]) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886129 Title: xubuntu : displays have become blank & unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1886129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973126] Re: crash ubiquity during installing Lubuntu 22.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Lubuntu 22.04 LTS is tested & supported only using the `calamares` installer. As such I've marked this bug report as 'invalid'. If you believe I'm in error, please leave a comment explaining why, and the status can be returned to 'new'. FYI: I checked both Lubuntu's jammy manifest & booted a live system and no `ubiquity` was installed. ** Changed in: ubiquity (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/1973126 Title: crash ubiquity during installing Lubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1973126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972750] [NEW] torbrowser-launcher failing to run (first-run) lubuntu jammy
Public bug reported: Fresh install, added the tor-browser package to use tor-browser. On trying to run from menu, nothing occurs. When run from terminal I get --- guiverc@svp11216cgb:~$ torbrowser-launcher Tor Browser Launcher By Micah Lee, licensed under MIT version 0.3.3 https://github.com/micahflee/torbrowser-launcher Icon theme "elementary" not found. Icon theme "breeze" not found. Downloading Tor Browser for the first time. Downloading https://aus1.torproject.org/torbrowser/update_3/release/Linux_x86_64-gcc3/x/en-US Traceback (most recent call last): File "/usr/bin/torbrowser-launcher", line 30, in torbrowser_launcher.main() File "/usr/lib/python3/dist-packages/torbrowser_launcher/__init__.py", line 98, in main gui.move( TypeError: arguments did not match any overloaded call: move(self, QPoint): argument 1 has unexpected type 'float' move(self, int, int): argument 1 has unexpected type 'float' guiverc@svp11216cgb:~$ ubuntu-bug torbrowser-launcher --- I note this has been experienced before; with a possible reason/fix found at https://askubuntu.com/questions/1404606/tor-browser-not- launching-on-ubuntu-22-04 which links to https://github.com/micahflee/torbrowser-launcher/issues/636 and provides a quick workaround. This maybe already fixed upstream, and just a re-package is required. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: torbrowser-launcher 0.3.3-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Tue May 10 12:28:23 2022 InstallationDate: Installed on 2022-04-20 (19 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: torbrowser-launcher UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: torbrowser-launcher (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972750 Title: torbrowser-launcher failing to run (first-run) lubuntu jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1972750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972130] Re: saveas switches to search option when changing name
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 filed the issue as related to the `do-release-upgrade` that upgraded you to 22.04 ~9 days before; once you've rebooted & logged into the new system, the ubuntu-release-upgrade tool's job was completed successfully. You also mention two non-Ubuntu products which should have bugs filed elsewhere (vivaldi, chrome). I suggest support. (FYI: Ubuntu Unity support is mostly on telegram (it's an unofficial remix); refer https://ubuntuunity.org/ ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972130 Title: saveas switches to search option when changing name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-unity-meta/+bug/1972130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972130] Re: saveas switches to search option when changing name
** Package changed: ubuntu-release-upgrader (Ubuntu) => unity (Ubuntu) ** Package changed: unity (Ubuntu) => ubuntu-unity-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972130 Title: saveas switches to search option when changing name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-unity-meta/+bug/1972130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972085] Re: cannot wake from suspend must force shutdown and reboot
Thank you for taking the time to report this bug and helping to make Ubuntu better. The suspend function is not performed in the do-release-upgrade step you have filed this bug against (which was also run/completed 15 days ago). Your issue is likely related to the newer 5.15 kernel (20.04.4 using HWE used 5.13 kernel; thus I've changed package bug is filed against. Bug reporting is mostly 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 ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972085 Title: cannot wake from suspend must force shutdown and reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971694] Re: e1000e not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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/1971694 Title: e1000e not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971673] Re: Xenial powerpc repositories missing
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. FYI: You'll need to be using ppc64el for later releases, which was the only powerpc architecture supported from 16.04/xenial & later (it won't run on your old mac mini) ppc wasn't a fully supported architecture for xenial; being community supported only - please refer https://wiki.ubuntu.com/PowerPCFAQ ** Changed in: 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/1971673 Title: Xenial powerpc repositories missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971638] Re: Second Monitor detected but always turn black screen. If I turn off and on again, the screen will turn back to normal but turn back to black screen after few seconds
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 FYI: You've tagged your bug report is with the `ubuntu-release-upgrader` tool that upgrades a system to a later release (ie. 20.04 to 21.10/22.04), yet appear to not have used that function (ie. `do- release-upgrade`). It may your issue relates to the linux kernel instead, ie. wrongly filed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971638 Title: Second Monitor detected but always turn black screen. If I turn off and on again, the screen will turn back to normal but turn back to black screen after few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1971638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971097] Re: Cannot switch between light/dark theme in the GNOME session
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 1971097 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/1971097 Title: Cannot switch between light/dark theme in the GNOME session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971005] Re: locate returns nothing
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 (Have you tried updating the database; ie. `updatedb`) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971005 Title: locate returns nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1971005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel
Thank you for reporting this bug to Ubuntu. Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Tags removed: disco eoan ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Out of Memory on boot with 5.2.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970894] Re: Grub2 Error Out of Memory
*** This bug is a duplicate of bug 1842320 *** https://bugs.launchpad.net/bugs/1842320 ** This bug has been marked a duplicate of bug 1842320 Out of Memory on boot with 5.2.0 kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970894 Title: Grub2 Error Out of Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970897] Re: google chrome app keeps on crushing since i updated to 22.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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've filed this bug report as related to the upgrade process that migrated you from 21.10 to 22.04, which you're now appear to be running; thus it worked. You also mention google-chrome; which is a 3rd party (Google product) app and thus bugs with google-chrome should be filed with google. I've marked this bug as incomplete. If you believe I'm in error, you can return the status to "New" after leaving a message describing your clearly. 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). Thank you! ** Changed in: ubuntu-release-upgrader (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/1970897 Title: google chrome app keeps on crushing since i updated to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1970897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
Lubuntu 22.04 LTS (jammy) ISO booting on - motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series) 00:10 secs enter pressed at grub (I could reduce 10secs from following times, but have opted not to) BLINKING CURSOR without change until 7:19 (7 mins 19 secs) first boot message 7:27 lubuntu plymouth is seen 8:04 system messages replace plymouth 8:31 Xorg mouse pointer is seen 9:12 lubuntu wallpaper is drawn by 9:20 the system is fully functional ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970707] Re: unable to install new version of '/usr/share/themes/Pop-dark/gtk-3.20/gtk.css': No such file or directory
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 The error message states "No apport report written because the error message indicates an issue on the local system" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970707 Title: unable to install new version of '/usr/share/themes/Pop- dark/gtk-3.20/gtk.css': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pop-gtk-theme/+bug/1970707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970677] Re: switching keyboard layout is unreliable
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 1970677 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/1970677 Title: switching keyboard layout is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon-desktop-environment/+bug/1970677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970275] Re: tried install mate 20.04 a dozen times. ubuntu mate 20.04 installation message: "error creating directory './usr/src/linux-hwe-5.13-headers-5.13.0-40/-arch/sh/include/cpu-sh3':Read-o
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 A RW file-system usually flips to RO (read-only) because issues are detected and flipping to RO prevents data-loss allowing the operator/owner to plan a response that prevents dataloss; as it's usually the result of hardware errors (warning signs of trouble to come). I don't see the `dmesg` output which is where I'd normally look for clues; but your likely answer is related to your hardware & not a Ubuntu install issue. Apr 25 20:48:37 ubuntu-mate kernel: [33576.839722] EXT4-fs error (device dm-1): ext4_validate_inode_bitmap:105: comm dpkg: Corrupt inode bitmap - block_group = 2608, inode_bitmap = 85458960 Apr 25 20:48:37 ubuntu-mate kernel: [33576.839759] Aborting journal on device dm-1-8. Apr 25 20:48:38 ubuntu-mate kernel: [33577.080860] EXT4-fs (dm-1): Remounting filesystem read-only I'll mark this bug incomplete; as the error to me is likely hardware related. If you believe I'm in error, please leave a comment explaining why & you can return the status to "New". The question can also be converted into a question, which is geared for support. ** Changed in: ubiquity (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/1970275 Title: tried install mate 20.04 a dozen times. ubuntu mate 20.04 installation message: "error creating directory './usr/src/linux- hwe-5.13-headers-5.13.0-40/-arch/sh/include/cpu-sh3':Read-only file system". My PC has amd-64 processor, 4G ram... thanks folks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1970275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970292] Re: ubuntu failed upgrade from 21.10 to 22.04
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 1970292 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/1970292 Title: ubuntu failed upgrade from 21.10 to 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1970292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970270] Re: LibreOffice localization is not working out of the box
A quick comparison of jammy manifests notices these (& more) in the Ubuntu but not Lubuntu's libreoffice-l10n-de 1:7.3.2-0ubuntu2 libreoffice-l10n-en-gb 1:7.3.2-0ubuntu2 libreoffice-l10n-en-za 1:7.3.2-0ubuntu2 libreoffice-l10n-es 1:7.3.2-0ubuntu2 libreoffice-l10n-fr 1:7.3.2-0ubuntu2 libreoffice-l10n-it 1:7.3.2-0ubuntu2 libreoffice-l10n-pt 1:7.3.2-0ubuntu2 libreoffice-l10n-pt-br 1:7.3.2-0ubuntu2 libreoffice-l10n-ru 1:7.3.2-0ubuntu2 libreoffice-l10n-zh-cn 1:7.3.2-0ubuntu2 libreoffice-l10n-zh-tw 1:7.3.2-0ubuntu2 but I've not noted what in the seeds causes the difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970270 Title: LibreOffice localization is not working out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1970270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969863] Re: python3-distupgrade and ubuntu-release-upgrader-core attempts to remove kubuntu-desktop and ubuntu-release-upgrader-qt
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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've tagged this is a `ubuntu-release-upgrader` issue, ie. related to a `do-release-upgrade` command that upgrades your release to aonther; a command you don't appear to be asking about. FYI: `apt upgrade` does NOT perform all upgrades (refer to manual) with some packages requiring `full-upgrade` (or `dist-upgrade`) where removal of packages are required. If you have removal of packages; it's likely the result of 3rd party packages you've installed & thus I'd suggest seeking support. No `do-release-upgrade` logs were provided, so I've changed this bug to 'incomplete'. It could be I've missed something, if so please leave a comment as to why, but were you trying to release-upgrade to a later release as your bug filing? as I feel you'd benefit from support & exploration of your 3rd party packages. If you believe I'm in error, you may return the status to "New" after leaving a comment explaining why, or you could convert this bug report into a question (ie. seeking support) ** Changed in: ubuntu-release-upgrader (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/1969863 Title: python3-distupgrade and ubuntu-release-upgrader-core attempts to remove kubuntu-desktop and ubuntu-release-upgrader-qt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1969863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955445] Re: ubuntu mate - on adjusting monitor.preferences maximized screen buttons are covered by panel
On QA-test install of Ubuntu-MATE jammy RC on - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) see http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/247124/testcases/1301/results/ and for subsequent live test see http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/247124/testcases/1303/results/ I'm convinced I experienced this issue again HOWEVER.. In exploring the issue & getting ready to upload my various screendumps using firefox the issue has now gone away & I can no longer produce it...? I've thus removed the tagging of this bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1955445. The (last) change I made was changing the (top) panel to autohide & issue stopped; as HAS NOT re-occurred even after AUTOHIDE of panel was restored to initial setting... As the issue was not tagged on the ISO tracker (I removed the bug tag) this can be seen as an invalid 'update' until verification is done & it'll need a new bug report anyway OF NOTE: I was experiencing nouveau video glitches on the box (issue https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1942561) and they stopped occurring the moment I stopped experiencing this issue, leaving me to conclude - huge co-incidence ?? - they're related somehow ? (unlikely I suspect) - was the video glitches (hugely distracting) leading me to see something that wasn't actually there.. ?? this issue was occurring on the monitor that was suffering from the glitches Ubuntu-MATE has been marked READY I note, so this report is done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955445 Title: ubuntu mate - on adjusting monitor.preferences maximized screen buttons are covered by panel To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1955445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969570] Re: tried to upgrade based on https://help.ubuntu.com/community/HirsuteUpgrades/Kubuntu
Thank you for taking the time to report this bug and helping to make Ubuntu better. I see a number of 3rd party packages, and it appears you're using a Ubuntu based product from Tuxedo Computers, and not Ubuntu 20.04 LTS (no Ubuntu kernel, Oibaf that prevents upgrade etc). For best results with a release-upgrade, you should remove all 3rd party packages (bringing your system back to a pure Ubuntu one, ie. no 3rd party packages) then perform the upgrade. The tool ppa-purge can assist with this. Possibly related to https://bugs.launchpad.net/ubuntu/+source/ubuntu- release-upgrader/+bug/1069133 FYI: Ubuntu 21.04 (hirsute) is EOL - https://fridge.ubuntu.com/2022/01/21/ubuntu-21-04-hirsute-hippo-end-of- life-reached-on-january-20-2022/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969570 Title: tried to upgrade based on https://help.ubuntu.com/community/HirsuteUpgrades/Kubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1969570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969330] Re: package grub-common 2.04-1ubuntu26.15 failed to install/upgrade: installed grub-common package post-installation 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 mostly 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/1969330 Title: package grub-common 2.04-1ubuntu26.15 failed to install/upgrade: installed grub-common package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1969330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969290] Re: lubuntu jammy ISO 2020-04-16 fails to boot when written with mkusb-plug
** Summary changed: - lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot + lubuntu jammy ISO 2020-04-16 fails to boot when written with mkusb-plug ** Changed in: casper (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969290 Title: lubuntu jammy ISO 2020-04-16 fails to boot when written with mkusb- plug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969290] Re: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot
I've marked this incomplete... I re-wrote the ISO to thumb-drive, and it's now booted on dc7700 box... A direct clone boots; where as the first test today was written with `mkusb-plug`, a 3rd party app from PPA - thus the 'incomplete'... (which may become invalid). I suspect mkusb-plug causes the issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969290 Title: lubuntu jammy ISO 2020-04-16 fails to boot when written with mkusb- plug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969290] Re: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot
** Changed in: casper (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/1969290 Title: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969290] Re: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot
Using Ubuntu Desktop ISO - http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/246966/testcases/1303/results/ both boxes booted... so exploring other potential issues (I used `mkusb-plug` to write ISO to thumb-drive as sudodus requested some testing; re-writing using my normal procedure (ie. direct clone of ISO to media & will re-try lubuntu daily on boxes when that completes) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969290 Title: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969290] Re: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot
** Description changed: Failure to boot using - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) - hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915) The ISO 2020-04-15 was used for a number of QA-tests including installs on dc7700 (casper 1.469) but today's ISO will not boot on the boxes As the system cannot boot; I can't run `ubuntu-bug` to file an issue, except using the wrong box, so I attempted to run `apport-collect` from an installed system (dc7700) done yesterday; alas no `casper` was installed thus this failed. + + for box details; view https://launchpad.net/+search?field.text=1969291 + BUT details match yesterday's ISO + + ProblemType: Bug + DistroRelease: Ubuntu 22.04 + Package: apport 2.20.11-0ubuntu82 + ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 + Uname: Linux 5.15.0-25-generic x86_64 + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: LXQt + Date: Sun Apr 17 12:34:57 2022 + InstallationDate: Installed on 2022-04-16 (0 days ago) + InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) + PackageArchitecture: all + SourcePackage: apport + UpgradeStatus: No upgrade log present (probably fresh install) ** Tags added: jammy ** Tags added: amd64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969290 Title: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969290] Re: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot
FYI: These two old HP boxes have had issues before... I can't find the bug report I wanted to use as example; but I'll provide https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040 (that bug impacted other boxes two; these two boxes were impacted by one issue alone that only impacted HP firmware.. awhile ago now in groovy or hirsute cycle I suspect) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969290 Title: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969291] [NEW] apport-collect & ubuntu-bug failing to switch to firefox
Public bug reported: In attempting to file a bug report on Lubuntu jammy ISO (QA-test installed yesterday using ISO 2020-04-15) -- guiverc@dc7700-2re:~$ apport-collect 1969290 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION' --- On attempting to file using `ubuntu-bug apport` --- guiverc@dc7700-2re:~$ ubuntu-bug apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.0 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 96% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?' --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Apr 17 12:34:57 2022 InstallationDate: Installed on 2022-04-16 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969291 Title: apport-collect & ubuntu-bug failing to switch to firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969290] Re: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot
** Description changed: Failure to boot using - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) - hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915) The ISO 2020-04-15 was used for a number of QA-tests including installs on dc7700 (casper 1.469) but today's ISO will not boot on the boxes As the system cannot boot; I can't run `ubuntu-bug` to file an issue, - except using the wrong box, so I'll add an `apport-collect` from an - installed system (dc7700) that was installed using yesterday's ISO, thus - - NOTE --- APPORT-COLLECT run on an older ISO install (2020-04-15) + except using the wrong box, so I attempted to run `apport-collect` from + an installed system (dc7700) done yesterday; alas no `casper` was + installed thus this failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969290 Title: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969290] [NEW] lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot
Public bug reported: Failure to boot using - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) - hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915) The ISO 2020-04-15 was used for a number of QA-tests including installs on dc7700 (casper 1.469) but today's ISO will not boot on the boxes As the system cannot boot; I can't run `ubuntu-bug` to file an issue, except using the wrong box, so I attempted to run `apport-collect` from an installed system (dc7700) done yesterday; alas no `casper` was installed thus this failed. ** Affects: casper (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/1969290 Title: lubuntu jammy ISO 2020-04-16 with casper 1.470 fails to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1969290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969265] Re: Ubuntu 22.04 after Update to latest gdm3 jammy 42.0-1ubuntu4 arm64, I does not logon to Wayland Session anymore
Possible duplicate of https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969243 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969265 Title: Ubuntu 22.04 after Update to latest gdm3 jammy 42.0-1ubuntu4 arm64, I does not logon to Wayland Session anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845756] Re: lubuntu - strange movement of wallpaper on monitor.settings change (or next login)
Lubuntu jammy daily (ISO 2020-04-13) on - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) both monitors are landscape currently; only change was swap left & right ** Attachment added: "screen.jpg" https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/1845756/+attachment/5580952/+files/screen.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845756 Title: lubuntu - strange movement of wallpaper on monitor.settings change (or next login) To manage notifications about this bug go to: https://bugs.launchpad.net/openbox/+bug/1845756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
This is still occurring on Lubuntu jammy 2020-04-13 (daily live; starting libreoffice & seeking help) snapd package is according to `apt-cache policy snapd` Installed: 2.55.3+22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952510] Re: playitslowly won't start on jammy
See prior comment #4 - it was dropped in Debian, and that 'fix' has caused it to be dropped in jammy to.. fixed by removal. :( ** Changed in: playitslowly (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952510 Title: playitslowly won't start on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/playitslowly/+bug/1952510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864787] Re: Lubuntu failed install "sfdisk --force --append /dev/sda"
i repeated a number of installs on d755-8 (box in original post) today using sda8 & sda9 and NO ISSUE today using lubuntu jammy http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/246634/testcases/1701/results/ (mainly reiserfs but also xfs & ext4) - daily 2022-04-07 (I've experienced this before in prior cycles; then a day or so later problems occur again; I'll endeavour to do another (or two) again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864787 Title: Lubuntu failed install "sfdisk --force --append /dev/sda" To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1864787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968506] Re: Xubutnu xfwm4 window tiling shortcuts not working as expected
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 1968506 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. ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968506 Title: Xubutnu xfwm4 window tiling shortcuts not working as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1968506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936695] Re: upgrade to 20.04 doesn't work
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 (Your system needs some general housecleaning, eg. I see a PPA added that supported only a single 12.10 release this should not have been removed long ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936695 Title: upgrade to 20.04 doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1936695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968436] Re: 20.04 upgrade failed
*** This bug is a duplicate of bug 1936695 *** https://bugs.launchpad.net/bugs/1936695 Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 (Your system needs some general housecleaning, eg. I see a PPA added that supported only a single 12.10 release this should not have been removed long ago) ** This bug has been marked a duplicate of bug 1936695 upgrade to 20.04 doesn't work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968436 Title: 20.04 upgrade failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1968436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968414] Re: installing wifi adapter on macbook air 2015 model
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. You seem to need support more than have issues with a bug I believe a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu (this bug report can be converted to a question (which is aimed at support)). 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/1968414 Title: installing wifi adapter on macbook air 2015 model To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1968414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968147] Re: Unable to boot Ubuntu and Ubuntu flavors on older laptops
** Changed in: grub2 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968147 Title: Unable to boot Ubuntu and Ubuntu flavors on older laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1968147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968147] Re: Unable to boot Ubuntu and Ubuntu flavors on older laptops
Thanks for the additional detail. I've replied on the budgie discourse; but can I request you re-try a boot and leave it attempting to boot for at least 20 minutes... (better if 30 mins) (This is a request to see if your issue is this one - https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968147 Title: Unable to boot Ubuntu and Ubuntu flavors on older laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1968147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968147] Re: Unable to boot Ubuntu and Ubuntu flavors on older laptops
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly 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 FYI: I'm replying here on a 2009 dell that is running Lubuntu jammy; and use machines from as old as 2006 in QA-testing Ubuntu and flavors of Ubuntu and have no issues booting. Your issue doesn't rule out invalid ISO (did you verify it as per documentation) or improper write to ISO (far more likely a problem in my experience, did you rule this out? as you've provided few clues as to having done this). I can see you've tried from your explanation though, so thank you. You've provided no hardware specifics (those could be provided by a `apport-collect` using another bootable ISO, but you'd have to clearly state you used an different ISO to provide that detail, as it would report your ISO version/date as from the ISO used when report was made), nor what ISO you're actually using. Ubuntu jammy is currently in testing, so dailies are produced (sometimes more than one per day) with the ISO marked as to which it is. You've not provided this detail, or link the QA-test on the ISO tracker (iso.qa.ubuntu.com/qatracker/milestones/429/builds) which would allow that detail to be obtained via that recording of your test. Please note many support sites do not support Ubuntu jammy (or flavors) as it's not yet a released product. IRC, Ubuntu Forums do however as examples. ** Changed in: grub2 (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/1968147 Title: Unable to boot Ubuntu and Ubuntu flavors on older laptops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1968147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967971] Re: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-US=UNIX=7.3."
I'll mark this incomplete then (assumption I jumped the gun) Thanks @Rick Tzschichholz/ricotz ** Changed in: libreoffice (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/1967971 Title: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967971] Re: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-US=UNIX=7.3."
A check on logs... it's possible not all package upgrades had taken effect, there is a message saying a restart is required because of dbus-deamon upgrade (can't do that on a live system) & lack of disk space on system.. so may require verification when an ISO build completes. The error on this system however matches the following I got earlier today when tested on my installed/primary box --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- that system is NOT live & has all upgrades applied.. It was clean booted this morning -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967971 Title: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967971] Re: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-US=UNIX=7.3."
** Description changed: - Lubuntu jammy live test. + Lubuntu jammy live test on + - samsung 700t1c-p10aat (i5-3317u, 4gb, 3rd gen.core.intel.graphics.4000) ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: Installed: 1:7.3.2-0ubuntu1 Candidate: 1:7.3.2-0ubuntu1 Version table: *** 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Wed Apr 6 01:46:35 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403) SourcePackage: libreoffice 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/1967971 Title: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967971] [NEW] libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-US=UNIX=7.3."
Public bug reported: Lubuntu jammy live test. ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: Installed: 1:7.3.2-0ubuntu1 Candidate: 1:7.3.2-0ubuntu1 Version table: *** 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Wed Apr 6 01:46:35 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: Lubuntu jammy live test. ISOs builds have been failing, so this is an older ISO with upgrades applied. Purpose was exploration of an libreoffice update to fix confinement issue + (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210) Libreoffice package lubuntu@lubuntu:~$ apt-cache policy libreoffice libreoffice: - Installed: 1:7.3.2-0ubuntu1 - Candidate: 1:7.3.2-0ubuntu1 - Version table: - *** 1:7.3.2-0ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:7.3.2-0ubuntu1 + Candidate: 1:7.3.2-0ubuntu1 + Version table: + *** 1:7.3.2-0ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages + 100 /var/lib/dpkg/status ** to re-create To re-create, open libreoffice & hit F1 or use menu to open Help->Libreoffice.Help ** Expected outcome Firefox opens & help page is shown in windows ** Actual outcome Firefox opens, but error instead --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. - Check the file name for capitalization or other typing errors. - Check to see if the file was moved, renamed or deleted. + Check the file name for capitalization or other typing errors. + Check to see if the file was moved, renamed or deleted. --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice 1:7.3.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Wed Apr 6 01:46:35 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220403) SourcePackage: libreoffice 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/1967971 Title: libreoffice help isn't opening - "Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
A quick test using package guiverc@d960-ubu2:/de2900$ apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.3.2-0ubuntu1 Version table: 1:7.3.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages and I'm getting a firefox tab opening with page being --- File not found Firefox can’t find the file at /usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en- US=UNIX=7.3. Check the file name for capitalization or other typing errors. Check to see if the file was moved, renamed or deleted. --- this is an installed system (rebooted this morning), I'll wait and re- test when we have a daily ISO available with this package to confirm if it occurs there, or with a 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/1951210 Title: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967642] Re: Lubuntu 22.04 beta still using Xorg instead of Wayland
You are correct, and I stand corrected. The Lubuntu Development Newsletter #9 was posted by Simon Quigley who was on the Lubuntu Council for some time, retiring only recently. Alas if you look at the issue 10 using the link I provided (an issue raised in 2014) the LWQt project hasn't advanced to the point where it's seen as being stable yet. Yes it's slowly improved with some developers have no issues earlier this year, yet others having issues with the same code on different hardware, as such it's not seen as something the small Lubuntu team can currently support. For now we (Lubuntu) are a LXQt desktop, and do not support LWQt. We do not know when this will change, even though into the future Wayland will replace Xorg; ie. LXQt will get replaced by LWQt, but when that will occur is unknown. It cannot occur for 22.04, and I don't see it happening in 22.10, beyond that we'll have to wait and see. For now Lubuntu is LXQt only. Thank you for the reminder (of Simon's newsletter #9) & correction. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967642 Title: Lubuntu 22.04 beta still using Xorg instead of Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1967642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967648] Re: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox
Package details could be wrong ! I asked on discord (ubuntu testing week rooms) & someone tested on a ubuntu jammy system and reported NO ISSUE. I zsync'd the Xubuntu DAILY (20220402) and had no issues there either, so possibly lubuntu issue only. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967648 Title: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967648] Re: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox
** Description changed: + /usr/bin/xdg-open: 882: firefox: not found + /usr/bin/xdg-open: 882: firefox: not found + xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' + + Lubuntu jammy install test on dell optiplex 780 I adjusted displays as mouse-movements were annoying me, noticed an issue thus filed a bug report using `ubuntu-bug lxqt-config` ** expected output on executing `ubuntu-but lxqt-config` I expected firefox to start ** actual output --- lubuntu@lubuntu:~$ ubuntu-bug lxqt-config *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: - S: Send report (19.6 KB) - V: View report - K: Keep report file for sending later or copying to somewhere else - I: Cancel and ignore future crashes of this program version - C: Cancel + S: Send report (19.6 KB) + V: View report + K: Keep report file for sending later or copying to somewhere else + I: Cancel and ignore future crashes of this program version + C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 98% *** To continue, you must visit the following URL: - https://bugs.launchpad.net/ubuntu/+source/lxqt- + https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. - Choices: - 1: Launch a browser now - C: Cancel + 1: Launch a browser now + C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found - /usr/bin/xdg-open: 882: firefox: not found - xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' + /usr/bin/xdg-open: 882: firefox: not found + xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' --- ie. `firefox` doesn't start as it's now a snap package first attempt to file `ubuntu-bug apport` ended up with --- *** To continue, you must visit the following URL: - https://bugs.launchpad.net/ubuntu/+source/lxqt- + https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. - Choices: - 1: Launch a browser now - C: Cancel + 1: Launch a browser now + C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found - /usr/bin/xdg-open: 882: firefox: not found - xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' + /usr/bin/xdg-open: 882: firefox: not found + xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' lubuntu@lubuntu:~$ --- - ** other notes - I don't know if this only impacts lubuntu, or others too - I've not (yet) looked for other/existing bugs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Sun Apr 3 12:09:05 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: apport 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/1967648 Title: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967651] Re: jammy beta xorg no kb / mouse
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 1967651 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. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967651 Title: jammy beta xorg no kb / mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1967651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845756] Re: lubuntu - strange movement of wallpaper on monitor.settings change (or next login)
** Tags removed: eoan hirsute ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845756 Title: lubuntu - strange movement of wallpaper on monitor.settings change (or next login) To manage notifications about this bug go to: https://bugs.launchpad.net/openbox/+bug/1845756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967647] Re: lubuntu jammy - adjusting screens & wallpaper isn't properly displayed
*** This bug is a duplicate of bug 1845756 *** https://bugs.launchpad.net/bugs/1845756 ** Package changed: lxqt-config (Ubuntu) => openbox (Ubuntu) ** This bug has been marked a duplicate of bug 1845756 lubuntu - strange movement of wallpaper on monitor.settings change (or next login) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967647 Title: lubuntu jammy - adjusting screens & wallpaper isn't properly displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/1967647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967642] Re: Lubuntu 22.04 beta still using Xorg instead of Wayland
Thank you for taking the time to report this bug and helping to make Ubuntu better. Lubuntu uses LXQt or the X.org version and doesn't support Wayland. Lubuntu doesn't support LWQt; which currently is suitable only for testing purposes; see https://github.com/lxqt/lxqt/issues/10 At no time have Lubuntu provided any advice or mention of supporting Wayland, beyond we're watching what upstream do in the open issue, and when it's ready for more than just testing, we'll evaluate what we do then. ** Bug watch added: github.com/lxqt/lxqt/issues #10 https://github.com/lxqt/lxqt/issues/10 ** Package changed: ubuntu => lubuntu-meta (Ubuntu) ** Changed in: lubuntu-meta (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967642 Title: Lubuntu 22.04 beta still using Xorg instead of Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1967642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967648] [NEW] lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox
Public bug reported: Lubuntu jammy install test on dell optiplex 780 I adjusted displays as mouse-movements were annoying me, noticed an issue thus filed a bug report using `ubuntu-bug lxqt-config` ** expected output on executing `ubuntu-but lxqt-config` I expected firefox to start ** actual output --- lubuntu@lubuntu:~$ ubuntu-bug lxqt-config *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (19.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 98% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' --- ie. `firefox` doesn't start as it's now a snap package first attempt to file `ubuntu-bug apport` ended up with --- *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/lxqt- config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+filebug/9f12535a-b2f0-11ec-b9ed-40a8f0305cb4?' lubuntu@lubuntu:~$ --- ** other notes - I don't know if this only impacts lubuntu, or others too - I've not (yet) looked for other/existing bugs ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu80 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Sun Apr 3 12:09:05 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967648 Title: lubuntu jammy - `ubuntu-bug lxqt-config` isn't opening firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1967648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967647] Re: lubuntu jammy - adjusting screens & wallpaper isn't properly displayed
this pic just shows the Monitor.Settings config.. All that was changed was default-left became my-right, default-right became my-left.. (I can't swap left/right cables as one is DVI, the other HDMI, and monitors are best in current position) ** Attachment added: "screen01.jpg" https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1967647/+attachment/5576350/+files/screen01.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967647 Title: lubuntu jammy - adjusting screens & wallpaper isn't properly displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1967647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967647] [NEW] lubuntu jammy - adjusting screens & wallpaper isn't properly displayed
Public bug reported: ** background/general This is not a new issue.. but I'll start a new report as it's a first I believe with jammy/impish or current LXQt/openbox/whatever. Lubuntu jammy QA-test install on dell optiplex 780 My monitors are wrongly positioned as this machine boots (left & right are swapped) so I swap with software. ** steps to perform - open LXQt->Monitor.Settings - adjust left-right screens so they're right-left - click save/apply.. ** expected outcome - left/right monitor positions are swapped - wallpaper covers both screens as before in moved positions ** actual outcome - left/right monitor positions are swapped - left of wallpaper now covers my.right.monitor but my.left.monitor no longer has wallpaper ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lxqt-config 0.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.468 CurrentDesktop: LXQt Date: Sun Apr 3 11:51:20 2022 LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220402) SourcePackage: lxqt-config UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxqt-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "screen.jpg" https://bugs.launchpad.net/bugs/1967647/+attachment/5576346/+files/screen.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967647 Title: lubuntu jammy - adjusting screens & wallpaper isn't properly displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxqt-config/+bug/1967647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] Re: Firefox snap install fails due to disabled networking in upgrade process
*** This bug is a duplicate of bug 1966589 *** https://bugs.launchpad.net/bugs/1966589 ** Package changed: linux (Ubuntu) => ubuntu-release-upgrader (Ubuntu) ** This bug has been marked a duplicate of bug 1966589 release upgrade fails due to `firefox package pre-installation script subprocess returned error exit status 1` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915365] Re: Linux Mint Cinamon installation "tz" data is corrupt
Closed as non-Ubuntu media & packages are involved. ** Changed in: ubiquity (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/1915365 Title: Linux Mint Cinamon installation "tz" data is corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1915365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917993] Re: "Install Ubuntu 20.10" crashed
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: grub-installer (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/1917993 Title: "Install Ubuntu 20.10" crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1917993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
