[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 1970062] Re: 22.04 MATE Mutiny dock bug with Caja and trashcan
I have since upgraded from 20.04.4 to 22.04 and can see the same bug. Mutiny layout with Plank dock shows a second icon for Caja when: 1- click on trash icon in dock (when no other Caja window is open) 2- or, plug in an external drive (again, when no other Caja window is open) In both situations, a second Caja icon appears at the bottom of the app list in the dock. Subsequent "new window" requests from the Caja menu add to that second icon. Clicking on the first, pinned Caja icon in the dock opens a new window, again linked to the second icon. Clicking second icon works as expected, switching to Caja / minimising all Caja windows / bringing them back screenshot attached of external drive with both Caja icons. ** Attachment added: "screenshot-with-second-caja.png" https://bugs.launchpad.net/ubuntu-mate/+bug/1970062/+attachment/5591129/+files/screenshot-with-second-caja.png ** Summary changed: - 22.04 MATE Mutiny dock bug with Caja and trashcan + 22.04 MATE Mutiny dock bug with Caja - second icon shown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970062 Title: 22.04 MATE Mutiny dock bug with Caja - second icon shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970062] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1970062/+attachment/5591106/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970062 Title: 22.04 MATE Mutiny dock bug with Caja - second icon shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970062] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1970062/+attachment/5591105/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970062 Title: 22.04 MATE Mutiny dock bug with Caja - second icon shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970062] Re: 22.04 MATE Mutiny dock bug with Caja and trashcan
apport information ** Tags added: apport-collected ** Description changed: - using the live image of 22.04, I could see a second icon created in the - Mutiny layout Dock/panel. If you click on the trashcan when no other - Caja window is open, it creates a new entry in the Dock - as shown in - the attached screenshot. Subsequent Caja windows cluster at the new - entry. + using the live image of 22.04, I could see a second icon created in the Mutiny layout Dock/panel. If you click on the trashcan when no other Caja window is open, it creates a new entry in the Dock - as shown in the attached screenshot. Subsequent Caja windows cluster at the new entry. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: MATE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-01-07 (496 days ago) + InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Package: ubuntu-mate-settings + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 + Tags: jammy + Uname: Linux 5.15.0-30-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-05-15 (3 days ago) + UserGroups: N/A + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1970062/+attachment/5591103/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970062 Title: 22.04 MATE Mutiny dock bug with Caja - second icon shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970062/+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
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 1873923] Update Released
The verification of the Stable Release Update for freeradius has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873923 Title: freeradius with freeradius-python3 fails to start out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1873923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874578] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: Dock has very long load time when show-mounts is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
Yeah, ok. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913775] Update Released
The verification of the Stable Release Update for gtk+3.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949572] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949572 Title: Shell freeze after right click on the app in the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1949572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947445] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947445 Title: Click actions "previews" and "minimize-or-previews" are broken To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1947445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949352] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1949352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951599] Update Released
The verification of the Stable Release Update for gnome-shell-extension- ubuntu-dock has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951599 Title: gnome-shell logs errors when ejecting SD card To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951599/+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 1970658] Update Released
The verification of the Stable Release Update for zenity has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970658 Title: Update zenity to 3.42.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1970658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959047] Update Released
The verification of the Stable Release Update for lxd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959047 Title: systemd ignores RootDirectory option in .service units To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1959047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Update Released
The verification of the Stable Release Update for shadow has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
Yeeah, ok. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+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 1973114] Re: Key trust verification fails on Ubuntu 22.04
Validation of package in Kinetic. The validation was run on Jammy with the Kinetic package installed: I have confirmed the bug on a 22.04 image running on AWS: Jammy stock ec2-instance-connect ssh -vvv output: https://pastebin.ubuntu.com/p/jDCnKrGRFM/plain/ When upgrading the package on the same instance with the one from Kinetic (with backported fix), it works: Jammy upgraded (kinetic) ec2-instance-connect ssh -vvv output: https://pastebin.ubuntu.com/p/bkvGwzZDYB/plain/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973114 Title: Key trust verification fails on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-instance-connect/+bug/1973114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
This bug may be mutter/wayland related as the player seems to work in xorg but not wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+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 1969455] Update Released
The verification of the Stable Release Update for ubiquity has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969455 Title: Install Ubuntu logo needs updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1969455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892825] Update Released
The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892825 Title: update-locale not perform correctly sanity checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918035] Update Released
The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918035 Title: ld-2.31.so is not correctly packaged in libc6-dbg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1918035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928508] Update Released
The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928508 Title: Performance regression on memcpy() calls for AMD Zen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951032] Update Released
The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951032 Title: AArch64: Backport memcpy improvements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1951032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962225] Update Released
The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962225 Title: preinst check that kernel revision < 255 now does more harm than good To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951033] Update Released
The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951033 Title: 20.04 SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cross-toolchain-base/+bug/1951033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915878] Re: RM sl-modem hardware not available
Do these steps need to be taken in any particular order? Does the removal of the ubuntu-drivers-common plugin need to happen before removing sl-modem so as to prevent breakage? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915878 Title: RM sl-modem hardware not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sl-modem/+bug/1915878/+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 1970408] Re: brltty package disconnecting ttyUSB0 used for Arduino
This is currently preventing me from using a Digirig Mobile amatuer radio interface device, which uses the 10c4:ea60 Silicon Labs CP210x UART Bridge. Pop_OS depends on brltty so I can't remove the package. However, I was able to follow comment #2: Edit /etc/brltty.conf, and add line: ``` braille-device usb:: ``` This points brltty as a particular nonexistent device and prevents it from trying to take over the USB serial device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970408 Title: brltty package disconnecting ttyUSB0 used for Arduino To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1970408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
I can confirm that this now builds on all architectures (https://launchpad.net/ubuntu/+source/python- xmlsec/1.3.12-1ubuntu0.22.04.1) as well as being newly installable on s390x: $ apt-cache policy python3-xmlsec python3-xmlsec: Installed: (none) Candidate: 1.3.12-1ubuntu0.22.04.1 Version table: 1.3.12-1ubuntu0.22.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/universe s390x Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971960 Title: [FTBFS] python-xmlsec fails to build on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+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 1908090] Re: ubuntu 20.04 kdump fails
** Package changed: kexec-tools (Ubuntu) => kdump-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908090 Title: ubuntu 20.04 kdump fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1908090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
** Description changed:
+ [Impact]
+
+ python3-xmlsec isn't available to installce on s390x on Jammy.
+
As can be seen in this build log
(https://launchpadlibrarian.net/599963344/buildlog_ubuntu-
focal-s390x.python-xmlsec_1.3.12-1build1~cloud0_BUILDING.txt.gz), the
s390x build fails testing with a lot of errors matching:
___ ERROR at teardown of
TestSignContext.test_set_enabled_key_data_bad_args
self =
def test_set_enabled_key_data_bad_args(self):
ctx = xmlsec.SignatureContext()
> ctx.key = xmlsec.Key.from_file(self.path('rsakey.pem'),
format=consts.KeyDataFormatPem)
E xmlsec.Error: (1, 'cannot read key')
tests/test_ds.py:326: Error
- Captured stderr call
-
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
___ ERROR at teardown of TestSignContext.test_set_enabled_key_data_bad_list
- Digging into it, I see that module seems to be loosing track of the
- passed in key file's argument, leading to the key being none, and unable
- to be read.
+ [Test Plan]
+
+ The unit tests for the build should pass on all architectures, including
+ big-endian (S390X).
+
+ [Where problems could occur]
+
+ Problems could occur in key-loading, given that the issue is identified
+ as specifically relating to code that's loading private keys from the
+ filesystem. This specific test is what caused the build failures on
+ s390x so should be fairly low risk.
+
+ [Other Info]
+
+ The specific issue
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
A fix for this has been uploaded to Kinetic in https://launchpad.net/ubuntu/+source/python-xmlsec/1.3.12-1ubuntu1 ** Also affects: python-xmlsec (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: python-xmlsec (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971960 Title: [FTBFS] python-xmlsec fails to build on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971960] [NEW] [FTBFS] python-xmlsec fails to build on s390x
Public bug reported:
As can be seen in this build log
(https://launchpadlibrarian.net/599963344/buildlog_ubuntu-
focal-s390x.python-xmlsec_1.3.12-1build1~cloud0_BUILDING.txt.gz), the
s390x build fails testing with a lot of errors matching:
___ ERROR at teardown of
TestSignContext.test_set_enabled_key_data_bad_args
self =
def test_set_enabled_key_data_bad_args(self):
ctx = xmlsec.SignatureContext()
> ctx.key = xmlsec.Key.from_file(self.path('rsakey.pem'),
> format=consts.KeyDataFormatPem)
E xmlsec.Error: (1, 'cannot read key')
tests/test_ds.py:326: Error
- Captured stderr call -
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
___ ERROR at teardown of TestSignContext.test_set_enabled_key_data_bad_list
Digging into it, I see that module seems to be loosing track of the
passed in key file's argument, leading to the key being none, and unable
to be read.
** Affects: python-xmlsec (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/1971960
Title:
[FTBFS] python-xmlsec fails to build on s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+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 1969771] Re: Fix beacon loss for rtl8821ce on certain platforms
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969771 Title: Fix beacon loss for rtl8821ce on certain platforms To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969771/+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 1969984] Re: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen
Hello Michael, or anyone else affected, Accepted kubuntu-settings into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kubuntu- settings/1:22.04.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: kubuntu-settings (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969984 Title: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969984] Re: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen
To what extent is this a minimal change to fix the issue? I'm unfamiliar with Plymouth scripting, but wouldn't it be simpler to fix the existing theme than to wholesale replace it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969984 Title: [SRU] Kubuntu Plymouth Theme Shows Badly on Multi-Screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1969984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919261] Re: Upgrading Ceph from 14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails when ceph-mds is installed
This bug was fixed in the package ceph - 15.2.16-0ubuntu0.20.04.1~cloud0 --- ceph (15.2.16-0ubuntu0.20.04.1~cloud0) bionic-ussuri; urgency=medium . * New update for the Ubuntu Cloud Archive. . ceph (15.2.16-0ubuntu0.20.04.1) focal; urgency=medium . [ James Page ] * d/control: Correct Breaks/Replaces versioning between -common and -mds to resolve issues with upgrades (LP: #1919261). . [ Chris MacNaughton ] * New upstream release (LP: #1964802). * Dropped patches in latest relese: - d/p/rgw_clear_buckets_before_calling_list_buckets.patch - d/p/bug1955345.patch * d/p/misc-32-bit-fixes.patch: Refreshed. * d/rules, d/ceph-osd.install: Update ceph-osd-smartctl to ceph-smartctl. ** Changed in: cloud-archive/ussuri Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919261 Title: Upgrading Ceph from 14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails when ceph-mds is installed To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1919261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919261] Update Released
The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919261 Title: Upgrading Ceph from 14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails when ceph-mds is installed To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1919261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964802] Re: [SRU] ceph 15.2.16
This bug was fixed in the package ceph - 15.2.16-0ubuntu0.20.04.1~cloud0 --- ceph (15.2.16-0ubuntu0.20.04.1~cloud0) bionic-ussuri; urgency=medium . * New update for the Ubuntu Cloud Archive. . ceph (15.2.16-0ubuntu0.20.04.1) focal; urgency=medium . [ James Page ] * d/control: Correct Breaks/Replaces versioning between -common and -mds to resolve issues with upgrades (LP: #1919261). . [ Chris MacNaughton ] * New upstream release (LP: #1964802). * Dropped patches in latest relese: - d/p/rgw_clear_buckets_before_calling_list_buckets.patch - d/p/bug1955345.patch * d/p/misc-32-bit-fixes.patch: Refreshed. * d/rules, d/ceph-osd.install: Update ceph-osd-smartctl to ceph-smartctl. ** Changed in: cloud-archive/ussuri Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964802 Title: [SRU] ceph 15.2.16 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1964802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964802] Update Released
The verification of the Stable Release Update for ceph has completed successfully and the package has now been released to -updates. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964802 Title: [SRU] ceph 15.2.16 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1964802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919261] Re: Upgrading Ceph from 14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails when ceph-mds is installed
I see the same thing as Tyler with the latest package in the Train UCA as well. In addition, I can confirm that an upgrade from the UCA Train version of ceph-mds to bionic-ussuri (proposed, verified with: 15.2.16-0ubuntu0.20.04.1~cloud0) or to focal (proposed, verified with: 15.2.16-0ubuntu0.20.04.1) works as expected, and the upgrade progresses correctly. ** Tags removed: verification-needed verification-needed-focal verification-ussuri-needed ** Tags added: verification-done verification-done-focal verification-ussuri-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919261 Title: Upgrading Ceph from 14.2.11-0ubuntu0.19.10.1~cloud4 to 15.2.8-0ubuntu0.20.04.1~cloud0 fails when ceph-mds is installed To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1919261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1970985] Re: package openmpi-bin 4.1.2-2ubuntu1 failed to install/upgrade: installed openmpi-bin package post-installation script subprocess returned error exit status 2
On 02/05/2022 11:03, America wrote: > sudo apt install openmpi-bin seemed to work for me too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970985 Title: package openmpi-bin 4.1.2-2ubuntu1 failed to install/upgrade: installed openmpi-bin package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openmpi/+bug/1970985/+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 1958224] Re: brltty claiming cp210x devices on 22.04
I have the same issue connecting to Onion Omega2 IoT devices, since they use cp210x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1970807] Re: Incompatible graphmath.ppu unit
I don't know where a log would be. But the upgrade did remove bothe Lazarus and fpc on both machines. On 2022-04-30 2:45 p.m., Paul Gevers wrote: > The upgrade process *should not* remove lazarus and fpc, that's a bug. > Do you happen to have the logs of when this happened such that we can > figure out why there were removed? > > However, the install process doesn't put anything in .lazarus. If > anything, that's left over from the previous version (as stuff in the > home folder is not to be touched during removal). Apparently lazarus > doesn't handle old local files in the home folder gracefully. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970807 Title: Incompatible graphmath.ppu unit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lazarus/+bug/1970807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1970807] Re: Incompatible graphmath.ppu unit
I had the problem when trying to compile form1 on ubuntu 22.04 (jammy) that had been upgraded from 21.10 (impish). The upgrade removed lazarus and fpc from my machine and I had to re-install lazarus. Whatever the package install process does, it puts an incompatible graphmath.ppu in your .lazarus directory structure. Removing that ppu solves the problem as then lazarus seems to use the unit in the usr/lib directory structure. This bug occurred on 2 separate machines. On 4/29/2022 2:49 AM, Paul Gevers wrote: > I'm not sure how useful this info is, but I just compiled Form1 on > Debian (bookworm) and I don't see any issues. > > @ginggs, Ubuntu applied one patch, do you think that may be related? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970807 Title: Incompatible graphmath.ppu unit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lazarus/+bug/1970807/+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 1970985] [NEW] package openmpi-bin 4.1.2-2ubuntu1 failed to install/upgrade: installed openmpi-bin package post-installation script subprocess returned error exit status 2
Public bug reported: ubuntu 22.04 doesn't install properly on my dell machine ProblemType: Package DistroRelease: Ubuntu 22.04 Package: openmpi-bin 4.1.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-40.45-lowlatency 5.13.19 Uname: Linux 5.13.0-40-lowlatency x86_64 NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv compat ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 29 15:59:34 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X79 DuplicateSignature: package:openmpi-bin:4.1.2-2ubuntu1 Setting up openmpi-bin (4.1.0-10ubuntu1) ... update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc dpkg: error processing package openmpi-bin (--configure): installed openmpi-bin package post-installation script subprocess returned error exit status 2 ErrorMessage: installed openmpi-bin package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2020-11-02 (542 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: openmpi Title: package openmpi-bin 4.1.2-2ubuntu1 failed to install/upgrade: installed openmpi-bin package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openmpi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970985 Title: package openmpi-bin 4.1.2-2ubuntu1 failed to install/upgrade: installed openmpi-bin package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openmpi/+bug/1970985/+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 1967988] Re: Support different Cirrus audio codec configurations on Dell laptops
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967988 Title: Support different Cirrus audio codec configurations on Dell laptops To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1967988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965882] Re: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)
I think what you are saying is that nouveau is not maintained by Ubuntu. I am just curious if Ubuntu made a config changed that caused this issue, or if it was an update to nouveau itself. I personally like nouveau because it allows automatic graphics switching, and the last time I tried the native Nvidia drivers, it ate a lot of battery. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965882 Title: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1965882/+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 1970807] [NEW] Incompatible graphmath.ppu unit
Public bug reported: The solution is to remove the graphmath unit ppu file in the .lazarus user directory and then have lazarus recompile or use the unit in the usr/lib directory. I've only tested with the default lazarus empty form program, but this problem shows up immediately. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lazarus 2.2.0+dfsg1-5ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 17:41:33 2022 InstallationDate: Installed on 2020-03-06 (783 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: lazarus UpgradeStatus: Upgraded to jammy on 2022-04-28 (0 days ago) ** Affects: lazarus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970807 Title: Incompatible graphmath.ppu unit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lazarus/+bug/1970807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969625] Re: ERROR: Could not resolve symbol: /proc/self/exec:BEGIN_trigger
It appears that you can work around this by installing the bpftrace debugging symbols. After following the general directions of https://wiki.ubuntu.com/Debug%20Symbol%20Packages I installed bpftrace- dbgsym and now bpftrace appears to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969625 Title: ERROR: Could not resolve symbol: /proc/self/exec:BEGIN_trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/1969625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969625] Re: ERROR: Could not resolve symbol: /proc/self/exec:BEGIN_trigger
This is apparently because the bpftrace binary is stripped. An issue reporting a similar problem in the upstream is https://github.com/iovisor/bpftrace/issues/954 ** Bug watch added: github.com/iovisor/bpftrace/issues #954 https://github.com/iovisor/bpftrace/issues/954 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969625 Title: ERROR: Could not resolve symbol: /proc/self/exec:BEGIN_trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpftrace/+bug/1969625/+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 1970663] Snap.Info.gtk-common-themes.txt
apport information ** Attachment added: "Snap.Info.gtk-common-themes.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584470/+files/Snap.Info.gtk-common-themes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Snap.Info.gnome-3-38-2004.txt
apport information ** Attachment added: "Snap.Info.gnome-3-38-2004.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584469/+files/Snap.Info.gnome-3-38-2004.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Snap.Info.firefox.txt
apport information ** Attachment added: "Snap.Info.firefox.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584468/+files/Snap.Info.firefox.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Snap.Info.core20.txt
apport information ** Attachment added: "Snap.Info.core20.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584467/+files/Snap.Info.core20.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Snap.Connections.txt
apport information ** Attachment added: "Snap.Connections.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584466/+files/Snap.Connections.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584465/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584464/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584463/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Snap.Info.gtk-common-themes.txt
apport information ** Attachment added: "Snap.Info.gtk-common-themes.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584462/+files/Snap.Info.gtk-common-themes.txt ** Description changed: Since a few day I've updated to Ubuntu Mate 22.04 with the firefox snap. Since then I've been having this strange bug. I have a 4k screen which I'm running at a 2180p resolution with scaling on HiDPI. This runs just fine except for in firefox. In the new firefox snap I get a really tiny mouse cursor. I also checked other snap, it is not the case there. Regards, Chris --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: MATE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-02-02 (83 days ago) + InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: ubuntu-mate-artwork + ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 + Snap: firefox 99.0.1-1 (stable) + Snap.Changes: no changes found + Tags: jammy + Uname: Linux 5.15.0-27-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Snap.Info.gnome-3-38-2004.txt
apport information ** Attachment added: "Snap.Info.gnome-3-38-2004.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584461/+files/Snap.Info.gnome-3-38-2004.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Snap.Info.firefox.txt
apport information ** Attachment added: "Snap.Info.firefox.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584460/+files/Snap.Info.firefox.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Snap.Info.core20.txt
apport information ** Attachment added: "Snap.Info.core20.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584459/+files/Snap.Info.core20.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970663] Snap.Connections.txt
apport information ** Attachment added: "Snap.Connections.txt" https://bugs.launchpad.net/bugs/1970663/+attachment/5584458/+files/Snap.Connections.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970663 Title: Tiny mouse cursor in firefox snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1970663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
