[Bug 1989976]
(In reply to Robert Townley from comment #10) > The short answer is the analogy falls down a little here because these are > master keys. Imagine you have one automobile - a . > You do not have a single Chevy key, but you do have keys for a 78 Mazda GLC, > a BMW, and your house. None of those would work! But you try them and it > is like magic, all three of these master keys unlock the 1957 Chevy Bel Air. [Cross-Device Authentication (CDA)](https://passkeys.dev/docs/reference/terms/#cross-device- authentication-cda) allows your iPhone to vouch for your logon attempt on your Desktop because it is cabled to it or within BlueTooth range. About the time the pandemic arrived in the US, almost all Credit Cards had these chips on them. The contactless nature of these credit cards meant germs were not spread as much. The chip stores a private key. Effectively, TPM hardware in your desktop or laptop or iPhone has one of these credit card chips. The public key can travel all over the internet, but the private key should never ever leave the device it was created on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1989976 Title: [upstream] wishlist: Passkeys should be supported To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1989976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1989976]
The short answer is the analogy falls down a little here because these are master keys. Imagine you have one automobile - a . You do not have a single Chevy key, but you do have keys for a 78 Mazda GLC, a BMW, and your house. None of those would work! But you try them and it is like magic, all three of these master keys unlock the 1957 Chevy Bel Air. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1989976 Title: [upstream] wishlist: Passkeys should be supported To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1989976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1989976]
(In reply to Mildred Ki'Lya from comment #7) > It seems Firefox implemented passkeys for Windows and MacOS but lack support > for Linux as shown in https://www.passkeys.io/compatible-devices > > I don't quite understand what is so platform specific. Of course, integration > in the native platform password manager is nice but not mandatory. Firefox > already stores its passwords and can sync them with Firefox Sync. What's so > different with passkeys and what's the status of this feature? > > As a web developer if I can provide passkeys as the primary login method, > this would be a great step forward, but it'd be better to have full browser > compatibility. PassKeys.io is really saying there is a workaround when they write ["Phone passkeys (QR code flow) and physical security keys only"](https://www.passkeys.io/compatible-devices). The private part of the passkey should never leave the device it was created on, so by design, it should not sync anywhere else. However, if you have a passkey on your cellphone or YubiKey but want to authenticate on your Linux desktop, then Bluetooth ( or a USB cable) connected to your desktop should offer a workaround. It worked for me before but not sure which Linux PC and which web browser on which Linux machine. If your Linux desktop has supported TPM hardware, then i do not see why it would not work. US DOD does it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1989976 Title: [upstream] wishlist: Passkeys should be supported To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1989976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237941]
(In reply to avada from comment #51) > (In reply to Dave Martin from comment #50) > > I've highlighted this bug many times and (have just checked) my first > > report was 18 years ago in bug 118394 which is still open. Eighteen > > years, please, let's have a fix !!This bug and the lack of a vertical > > tabs option in base Firefox (I use a 3rd party addon, tree style tab, > > wonderful) are major detractions to this browser. > > Just let it go, not going to happen. Use the above mentioned for this > functionality, and other useful ones such as jumping to the searched > bookmark/folder's location on the tree: > https://addons.mozilla.org/firefox/addon/bookmark-search-plus-2/ > It opens in the sidebar the same way as the built in sidebar. But a month ago, Mozilla had not announced they were inserting artificial intelligence into our browser. Those neural nets need to vacuum up my 101,109 bookmarks and let me search folders. Better yet, the a.i. will tell us what folder we want before we type it in. [https://www.reddit.com/r/firefox/comments/1de7bu1/were_the_firefox_leadership_team_at_mozilla_ama/?utm_campaign=Reddit+AMA+with+Firefox+leadership_medium=bitly_source=SUMO+Banner]( Mozilla leadership will be promising that today. They will lean on a.i. to squash all these outstanding bugs. ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/237941 Title: Bookmarking Folder Location To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/237941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble
The new package has been working good for me EXCEPT wordpress thinks it isn't running even though it is AND it acts on the WordPress filters and jails I have installed. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Tue, 11 Jun 2024, Brian Murray wrote: > Date: Tue, 11 Jun 2024 20:05:13 - > From: Brian Murray <2055...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble > > Hello Robert, or anyone else affected, > > Accepted fail2ban into noble-proposed. The package will build now and be > available at > https://launchpad.net/ubuntu/+source/fail2ban/1.0.2-3ubuntu0.1 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- > noble to verification-done-noble. If it does not fix the bug for you, > please add a comment stating that, and change the tag to verification- > failed-noble. 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: fail2ban (Ubuntu Noble) > Status: Confirmed => Fix Committed > > ** Tags added: verification-needed verification-needed-noble > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2055114 > > Title: > fail2ban is broken in 24.04 Noble > > Status in fail2ban package in Ubuntu: > Fix Released > Status in fail2ban source package in Noble: > Fix Committed > Status in fail2ban source package in Oracular: > Fix Released > > Bug description: > [ Impact ] > * fail2ban fails to start on Ubuntu 24.04, due to new Python and deprecated > classes (now vendored upstream) > > [ Test Plan ] > * Install and check systemctl status fail2ban. > > [ Where problems could occur ] > * Nowhere, fixing a program failing to start > > [ Other info ] > Was working in 22.04, but after upgrading to 24.04 I get this: > > × fail2ban.service - Fail2Ban Service > Loaded: loaded (/etc/systemd/system/fail2ban.service; enabled; preset: > enabled) > Active: failed (Result: exit-code) since Sun 2024-02-25 02:27:29 PST; 1 > day 18h ago > Duration: 2.330s > Docs: man:fail2ban(1) > Process: 1130 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, > status=0/SUCCESS) > Process: 1133 ExecStart=/usr/local/bin/fail2ban-server -xf start > (code=exited, status=255/EXCEPTION) > Main PID: 1133 (code=exited, status=255/EXCEPTION) > CPU: 660ms > > Feb 25 02:27:26 mx1 systemd[1]: Starting fail2ban.service - Fail2Ban > Service... > Feb 25 02:27:26 mx1 systemd[1]: Started fail2ban.service - Fail2Ban Service. > Feb 25 02:27:28 mx1 fail2ban-server[1133]: 2024-02-25 02:27:28,952 fail2ban > [1133]: ERROR No module named 'asynchat' > Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Main process exited, > code=exited, status=255/EXCEPTION > Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Failed with result > 'exit-code'. > > grep fail2ban syslog > 2024-02-25T02:25:17.813593-08:00 mx1 systemd[1]: Stopping fail2ban.service - > Fail2Ban Service... > 2024-02-25T02:27:26.625640-08:00 mx1 systemd[1]: Starting fail2ban.service - > Fail2Ban Service... > 2024-02-25T02:27:26.678572-08:00 mx1 systemd[1]: Started fail2ban.service - > Fail2Ban Service. > 2024-02-25T02:27:28.954548-08:00 mx1 fail2ban-server[1133]: 2024-02-25 > 02:27:28,952 fail2ban[1133]: ERROR No module named > 'asynchat' > 2024-02-25T02:27:29.004733-08:00 mx1 systemd[1]: fail2ban.service: Main > process exited, code=exited, status=255/EXCEPTION > 2024-02-25T02:27:29.004834-08:00 mx1 systemd[1]: fail
[Bug 320140] Re: can't copy between two sftp connections
I can't reproduce the issue, it is solved. ** Changed in: krusader (Ubuntu) Status: Incomplete => 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/320140 Title: can't copy between two sftp connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krusader/+bug/320140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068747] [NEW] Impossible d'évaluer la mise à niveau
Public bug reported: could not upgrade to 23.10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 5.15.0-112.122-generic 5.15.152 Uname: Linux 5.15.0-112-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 17:53:00 2024 InstallationDate: Installed on 2024-06-07 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-06-07 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2024-06-07T17:43:12.981472 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages 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/2068747 Title: Impossible d'évaluer la mise à niveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2068747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065925] Re: connexion to server lost
ran version 0.5 without issues on ubuntu 22.04, after upgrade to 24.04 still on 0.5, but I now get "the connection to the server has been lost" whenever the game starts (continue, quick start, single player+start, pick saved game ...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065925 Title: connexion to server lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeorion/+bug/2065925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067940] [NEW] package linux-headers-6.8.0-35-generic 6.8.0-35.35 failed to install/upgrade: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error ex
Public bug reported: I clicked on the update that was offered to me through the standard software updater. ProblemType: Package DistroRelease: Ubuntu 24.04 Package: linux-headers-6.8.0-35-generic 6.8.0-35.35 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Mon Jun 3 14:48:41 2024 ErrorMessage: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error exit status 11 InstallationDate: Installed on 2024-05-14 (21 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: LENOVO 20EGS0RA02 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=138ba324-feb2-4704-bb05-dc37105666e0 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.8.0-35-generic 6.8.0-35.35 failed to install/upgrade: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error exit status 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2021 dmi.bios.release: 2.42 dmi.bios.vendor: LENOVO dmi.bios.version: GNET94WW (2.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EGS0RA02 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrGNET94WW(2.42):bd06/02/2021:br2.42:efr1.14:svnLENOVO:pn20EGS0RA02:pvrThinkPadW541:rvnLENOVO:rn20EGS0RA02:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20EG: dmi.product.family: ThinkPad W541 dmi.product.name: 20EGS0RA02 dmi.product.sku: LENOVO_MT_20EG dmi.product.version: ThinkPad W541 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067940 Title: package linux-headers-6.8.0-35-generic 6.8.0-35.35 failed to install/upgrade: installed linux-headers-6.8.0-35-generic package post-installation script subprocess returned error exit status 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041727] Re: "netplan apply" produces ovsdb-server.service WARNING even when openvswitch-switch not installed
Xubuntu 22.04.03 This bug suddenly appeared about 2024 05 20. Seems to be preventing DN resolution on internal network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041727 Title: "netplan apply" produces ovsdb-server.service WARNING even when openvswitch-switch not installed To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2041727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066315] Re: Users who upgraded to rejected SRU 1.72.4-0ubuntu0.22.04.1 aren't restored
Verified on Jammy in AWS workspaces. Test plan: 1. Upgrade from 1.72.4-0ubuntu0.22.04.1 to 1.72.4-0ubuntu0.22.04.3~really.is.1.72.2.0ubuntu2 2. Monitor system for couple of days Done in 3 VMs, no issues detected. I'll keep VMs running for couple of days doing random GUI operations and update this case if anything will be detected. ** 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/2066315 Title: Users who upgraded to rejected SRU 1.72.4-0ubuntu0.22.04.1 aren't restored To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2066315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117514] Re: seahorse does not synchronize keys with keyserver
In 24.04 desktop if you choose two keys to sync, the program will crash. Also, does not look like the sync even works. I had to use the below command to get my key to sync. gpg --send-keys --keyserver keyserver.ubuntu.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/117514 Title: seahorse does not synchronize keys with keyserver To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/117514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064548] Re: kwallet will not accept passw; nor let me change it
If you need to reset the password and it’s not accepting the current one, you might need to delete the wallet file to reset it. The wallet file is usually located at /home//.local/share/kwalletd/kdewallet.kwl. Deleting this file will prompt the creation of a new wallet and allow you to set a new password. https://www-netbenefits.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064548 Title: kwallet will not accept passw; nor let me change it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwalletmanager/+bug/2064548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061986] Re: Mount CIFS fails with Permission denied
Verified issue on both linux/5.4.0-186.206 and linux/5.15.0-111.121. Following steps from description I was not able to reproduce issue nor I did not hit any new problems. Marking as verified. ** Tags removed: verification-needed-focal-linux verification-needed-jammy-linux ** Tags added: verification-done-focal-linux verification-done-jammy-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061986 Title: Mount CIFS fails with Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064647] Re: Documentation for how to enable gnome-remote-desktop on a completly headless system
From Upstream I tried to enable using some commands through grdctl with no such luck grdctl enable [20:15:58:493] [60992:ee40] [ERROR][com.freerdp.crypto] - [x509_utils_from_pem]: BIO_new failed for certificate RDP server certificate is invalid. Usage: grdctl [OPTIONS...] COMMAND [SUBCOMMAND]... grdctl --headless enable [20:[61000:ee48] [ERROR][com.freerdp.crypto] - [x509_utils_from_pem]: BIO_new failed for certificate 16:02:476] RDP server certificate is invalid. Init TPM credentials failed because No TPM device found, using GKeyFile as fallback. Usage: grdctl [OPTIONS...] COMMAND [SUBCOMMAND]... grdctl --system enable Error changing to home directory /var/lib/gnome-remote-desktop: No such file or directory From @pnowack That's a packaging issue. Please report that to your distro. g-r-d installs both a sysusers and a tmpfiles file for the user for the system daemon and its config dirs. The sysusers and tmpfiles hooks usually run on a reboot, but they also MUST run when installing the respective pkg, in particular: after the decompression of the files (post-installation hooks). This works fine on other distros, like Arch (pacman automatically detects such sysusers- or tmpfiles-file installation and runs the respective hooks for that). apt or dpkg must also be able to correctly handle this (regardless of the pkg). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064647 Title: Documentation for how to enable gnome-remote-desktop on a completly headless system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2064647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064685] Re: write says write: effective gid does not match group of /dev/pts/5
This does not really fix security because one aspect of security is availability to legitimate users and this breaks the latter. Seems there are better ways to fix such as restricting what this can write to with apparmor? Or just fixing the coding so it does parse the input more carefully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064685 Title: write says write: effective gid does not match group of /dev/pts/5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2064685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064647] [NEW] Documentation for how to enable gnome-remote-desktop on a completly headless system
Public bug reported: Asked to create a new bug from https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/206 I am on a completely headless system starting from a minimal ubuntu-server 24.04 installation. I have installed the desktop using apt install ubuntu-desktop I want to use the new gnome-remote-desktop so that I can create a developer machine in a VM environment that can be accessed through a thin client as an example using Microsoft RDP I suspect there is some missing documentation. Starting the service using systemctl start gnome-remote-desktop.service results in: journalctl -xeu gnome-remote-desktop.service Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 2929. Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. Running sudo systemd-sysusers does create some new users, restarting the remote desktop now gives: May 02 14:27:47 localhost gnome-remote-de[36906]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback May 02 14:27:47 localhost gnome-remote-de[36906]: Init file credentials failed: Error creating directory /var/lib/gnome-remote-desktop: Permission denied May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ** May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: Bail out! ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 02 14:27:47 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=dumped, status=6/ABRT As a headless system I can not use any UI controls so I suspect there is some command / config that needs to to be set before launching rdp ** Affects: gnome-remote-desktop (Ubuntu) Importance: Low Status: Triaged ** Description changed: Asked to create a new bug from https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/206 - I am on a completely headless system starting from a minimal ubuntu-server 24.04 installation. - I have installed the desktop using apt install ubuntu-desktop + I am on a completely headless system starting from a minimal ubuntu-server 24.04 installation. + I have installed the desktop using apt install ubuntu-desktop I want to use the new gnome-remote-desktop so that I can create a developer machine in a VM environment that can be accessed through a - thin client using Microsoft RDP + thin client as an example using Microsoft RDP I suspect there is some missing documentation. Starting the service using systemctl start gnome-remote-desktop.service results in: journalctl -xeu gnome-remote-desktop.service Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 2929. Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. - Running sudo systemd-sysusers does create some new users, restarting the remote desktop now gives: May 02 14:27:47 localhost gnome-remote-de[36906]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback May 02 14:27:47 localhost gnome-remote-de[36906]: Init file credentials failed: Error creating directory /var/lib/gnome-remote-desktop: Permission denied May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ** May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]:
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
I using it in a cloud provider using ssh, I want to be able to configure it completely headless. I can not log into the UI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Nothing really reported from running the above command /usr/libexec/gnome-remote-desktop-daemon --system ** (gnome-remote-desktop-daemon:36048): WARNING **: 11:01:25.879: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback But no ports are open netstat -tnlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN 29997/cupsd tcp0 0 127.0.0.54:53 0.0.0.0:* LISTEN 16105/systemd-resol tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN 16105/systemd-resol tcp6 0 0 ::1:631 :::*LISTEN 29997/cupsd tcp6 0 0 :::22 :::*LISTEN 1/systemd I restarted GDM3 ps -aux | grep gnome gdm35757 0.0 0.6 233060 6144 tty1 Ssl+ 11:01 0:00 /usr/libexec/gdm-wayland-session dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm35761 0.0 0.2 6500 2432 tty1 S+ 11:01 0:00 dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm35763 0.0 1.8 518252 18304 tty1 Sl+ 11:01 0:00 /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart gdm35772 1.0 22.0 3251940 217456 tty1 Sl+ 11:01 0:01 /usr/bin/gnome-shell gdm35799 0.0 0.7 236060 7552 tty1 Sl+ 11:01 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session gdm35822 0.0 2.7 2590472 26852 tty1Sl+ 11:01 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.Shell.Notifications gdm36027 0.0 2.7 2590464 26860 tty1Sl+ 11:01 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.ScreenSaver root 36090 0.0 1.7 439656 16896 ttyS0Sl+ 11:02 0:00 /usr/libexec/gnome-remote-desktop-daemon --system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Also seeing the same issue on a headless server (Linode) 24.04 Ubuntu server Installed ubuntu-desktop cat /etc/os-release PRETTY_NAME="Ubuntu 24.04 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=noble LOGO=ubuntu-logo journalctl -xeu gnome-remote-desktop.service Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 2929. Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061228] Re: Upgrading Ubuntu Jammy to Ubuntu Noble fails with error message
*** This bug is a duplicate of bug 2054761 *** https://bugs.launchpad.net/bugs/2054761 Got the same or similar error. While doing a do-release-update from 22.04 to 24.04 it crashed halfway the installation of packages. After rebooting could only get a terminal window using ctrl-alt-F2. I tried to do a dpkg --configure -a but that feild due to too many errors. It turned out that networking did not work because the resolv wa not there. I do not know how to reinstall that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061228 Title: Upgrading Ubuntu Jammy to Ubuntu Noble fails with error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061986] Re: Mount CIFS fails with Permission denied
Attaching tcpdump output without patch ** Attachment added: "base_5_15_104_filtered.pcap" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766752/+files/base_5_15_104_filtered.pcap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061986 Title: Mount CIFS fails with Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061986] Re: Mount CIFS fails with Permission denied
Attaching tcpdump output with patch ** Attachment added: "base_5_15_104_with_patch_filtered.pcap" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766753/+files/base_5_15_104_with_patch_filtered.pcap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061986 Title: Mount CIFS fails with Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061986] [NEW] Mount CIFS fails with Permission denied
Public bug reported: [ Impact ] * Mounting SMB share from server without Key Exchange capability is failing with Access Denied error * Even though SMB server during Session Setup Response in NTLMSSP_CHALLANGE message does not advertise Key Exchange capabilities SMB client < 5.16 will forcefully use it leading to error response during TCON requests. * Issue can be reproduced on 5.15 or older Kernels, there is no reproduction on 6.5 Kernel * This scenario was fixed in upstream commit 9de0737d5ba0425c3154d5d83da12a8fa8595c0f * An example of server without Key Exchange capability is Oracle Solaris 11.4 SMB zfs, meaning mounting share from that server will result in ACCESS_DENIED error. [ Test Plan ] * So far issue was reported only with Oracle Solaris 11.04 smb server and Ubuntu with Kernel <= 5.15 * To reproduce, setup Oracle Solaris SMB server and try to mount share on 22.04/20.04 (5.15/5.04) Steps to configure SMB server: 1. Download the ISO for Oracle Solaris Common Build Edition [1] 2. Create a VM with at least 16 GB of memory - I have experienced installation issues with less memory 3. Install Oracle Solaris using the downloaded ISO a. Make sure to create a test user 4. Log into the VM as the root user 5. Create a test directory for the share: a. mkdir /smbshare && chmod 777 /smbshare 6. Disable the normal Samba daemon: [2] a. svcadm disable svc:/network/samba b. svcadm disable svc:/network/wins 7 Configure the server to serve Samba shares using ZFS in Workgroup mode [3] a. svcadm enable -r smb/server b. smbadm join -w workgroup 8 Update the /etc/pam.d/other file to require authentication by adding the following line: a. password requiredpam_smb_passwd.so.1nowarn 9. Reset the password for the test user so that it is updated in the SMB password database 10. Create the pool and share it using Samba: [4] a. zfs create -o mountpoint=/smbshare/ rpool/smbshare b. zfs share -o share.smb=on rpool/smbshare%share [1] <https://www.oracle.com/solaris/solaris11/downloads/solaris-downloads.html> [2] <https://docs.oracle.com/cd/E26502_01/html/E29004/migratingfromsamba.html#scrolltoc> [3] <https://docs.oracle.com/cd/E26502_01/html/E29004/configuringoperationmodetm.html#configureworkgroupmodetask> [4] <https://docs.oracle.com/cd/E26502_01/html/E29004/managingsmbshares.html#createstaticsmbsharezfstask> * With server configured, mount share using ubuntu SMB client Expected result: mount operation should succeed Actual result: mount returns following error: root@ubuntu20:/mnt# mount -t cifs -o username=rmalz //192.168.50.217/smbshare test Password for rmalz@//192.168.50.217/smbshare: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) [ Where problems could occur ] * Upstream patch is changing smb client behavior based on server NTLMSSP_CHALLENGE Negotiate Flags, if server does not advertise Key Exchange Capability but requires it from client communication might be broken. It is unknown if such servers are used, such instance should be treated as a server bug. * Patch is available in upstream kernel since 5.16, any issues associated with it should be already detected. * Patch adds additional requirement checks on server NTLM flags, although it is possible to hit these checks, I was not able to find any instances of that occurring. * To lower regression potential, upstream patch backported to Ubuntu 5.15 and 5.04 Kernels have been tested in following environments: smb server: Oracle Solaris 11.04, Ubuntu 22.04 HWE smb client: Ubuntu 22.04, Ubuntu 20.04 During testing no issues have been detected. [ Other Info ] * Error message coming from SMB client is the same as providing incorrect credentials, which might confuse users. * Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and without patch. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Robert Malz (rmalz) Status: New ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Robert Malz (rmalz) Status: New ** Affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Robert Malz (rmalz) Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Robert Malz (rmalz) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Robert Malz (rmalz) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Robert Malz (rmalz) ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy)
[Bug 1898783] Re: kcmshell5 user_manager autologin (with sddm) fail on user deletion
Expected behavior: Display error message and/or show logon screen User is able to make GUI unusable when deleting account configured with autologin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898783 Title: kcmshell5 user_manager autologin (with sddm) fail on user deletion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm-kcm/+bug/1898783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898783] Re: kcmshell5 user_manager autologin (with sddm) fail on user deletion
Not solved in kubuntu 23.10 Easier way to reproduce: Create file /etc/sddm.conf.d/kde_settings.conf with content [Autologin] Relogin=false Session=plasma User=nonexistentuser ** Changed in: sddm-kcm (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/1898783 Title: kcmshell5 user_manager autologin (with sddm) fail on user deletion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm-kcm/+bug/1898783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051720]
(In reply to Luiz Von Dentz from comment #16) > Can you guys try with the following change: > > https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201- > 1-luiz.de...@gmail.com/ I have the same issue and applied this patch to my kernel, but it seems to have broken the btintel module. I get a null pointer deref on boot and bluetooth is broken: [2.317366] BUG: kernel NULL pointer dereference, address: 0070 [2.317699] #PF: supervisor read access in kernel mode [2.317993] #PF: error_code(0x) - not-present page [2.318280] PGD 0 P4D 0 [2.318283] Oops: [#1] PREEMPT SMP NOPTI [2.318842] CPU: 3 PID: 185 Comm: kworker/u33:0 Not tainted 6.8.3-gentoo-dist #1 [2.318844] Hardware name: AZW SER/SER, BIOS SER7PRO_P5C8V30 09/15/2023 [2.318845] Workqueue: hci0 hci_alloc_dev_priv [bluetooth] [2.319426] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel] [2.320365] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06 00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70 0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44 [2.320691] RSP: 0018:a215005cfd48 EFLAGS: 00010202 [2.321452] RAX: RBX: RCX: 8026 [2.321760] RDX: 8027 RSI: d3238404d700 RDI: [2.322437] RBP: 91a940ccc6c8 R08: 8027 R09: 8026 [2.322438] R10: 0001 R11: R12: 91a940ccc6d0 [2.322439] R13: 91a947f50c00 R14: 91a940ccc000 R15: 91a940ccca88 [2.322441] FS: () GS:91af820c() knlGS: [2.323737] CS: 0010 DS: ES: CR0: 80050033 [2.323739] CR2: 0070 CR3: 00010dfa2000 CR4: 00f50ef0 [2.323740] PKRU: 5554 [2.323740] Call Trace: [2.323743] [2.326248] ? __die_body+0x68/0xb0 [2.326253] ? page_fault_oops+0x3a3/0x400 [2.326256] ? exc_page_fault+0x60/0xf0 [2.326265] ? asm_exc_page_fault+0x26/0x30 [2.326269] ? btintel_configure_setup+0x245/0x970 [btintel] [2.328091] ? btintel_configure_setup+0x16c/0x970 [btintel] [2.328093] ? __ia32_compat_sys_sysinfo+0x230/0x270 [2.329006] hci_dev_open_sync+0x166/0x1610 [bluetooth] [2.329013] ? srso_alias_return_thunk+0x5/0xfbef5 [2.329015] ? srso_alias_return_thunk+0x5/0xfbef5 [2.329016] ? srso_alias_return_thunk+0x5/0xfbef5 [2.329018] hci_alloc_dev_priv+0x164e/0x1bc0 [bluetooth] [2.329023] process_scheduled_works+0x24b/0x450 [2.329026] worker_thread+0x2c3/0x420 [2.329028] ? __pfx_worker_thread+0x10/0x10 [2.329030] kthread+0xe8/0x110 [2.329032] ? __pfx_kthread+0x10/0x10 [2.329033] ret_from_fork+0x37/0x50 [2.329036] ? __pfx_kthread+0x10/0x10 [2.329038] ret_from_fork_asm+0x1b/0x30 [2.329043] [2.329043] Modules linked in: amdxcp(+) ac97_bus(+) iwlwifi(+) snd_hda_codec(+) btusb snd_pcm_dmaengine gpu_sched vfat btbcm snd_pci_ps drm_suballoc_helper btintel i2c_algo_bit fat snd_rpl_pci_acp6x kvm(+) drm_ttm_helper snd_hda_core snd_acp_pci btrtl ttm snd_acp_legacy_common btmtk snd_pci_acp6x irqbypass drm_exec snd_hwdep snd_pci_acp5x snd_pcm drm_display_helper bluetooth snd_rn_pci_acp3x wmi_bmof cfg80211 snd_timer snd_acp_config rapl cec snd_soc_acpi snd pcspkr drm_buddy soundcore i2c_piix4 k10temp snd_pci_acp3x rfkill amd_pmc fuse loop nfnetlink crct10dif_pclmul crc32_pclmul crc32c_intel nvme polyval_clmulni polyval_generic ghash_clmulni_intel thunderbolt sha512_ssse3 sha256_ssse3 sha1_ssse3 nvme_core amd_sfh ccp sp5100_tco r8169 nvme_auth realtek video wmi i2c_hid_acpi i2c_hid serio_raw [2.329083] CR2: 0070 [2.329085] ---[ end trace ]--- [2.329087] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel] [2.329089] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06 00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70 0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44 [2.329090] RSP: 0018:a215005cfd48 EFLAGS: 00010202 [2.329091] RAX: RBX: RCX: 8026 [2.329092] RDX: 8027 RSI: d3238404d700 RDI: [2.329093] RBP: 91a940ccc6c8 R08: 8027 R09: 8026 [2.329093] R10: 0001 R11: R12: 91a940ccc6d0 [2.329094] R13: 91a947f50c00 R14: 91a940ccc000 R15: 91a940ccca88 [2.329095] FS: () GS:91af820c() knlGS: [2.329096] CS: 0010 DS: ES: CR0: 80050033 [2.329096] CR2: 0070 CR3: 00010dfa2000 CR4: 00f50ef0 [2.329097] PKRU: 5554 [2.329098] note: kworker/u33:0[185] exited with irqs disabled -- You received this bug notification because you are a member of
[Bug 2055761] Re: tracker-extract-3 crashed with SIGSYS in epoll_wait()
This is a new computer with the following specs: MB: MSI X670E tomahawk proc: AMD 7950X VIdeo: Nvidia 4070 ti Super Mem: 128 GB Kingston fury 6000 Installed Ubuntu 24.04 daily because 22.04 did not work with this hardware and the latest nvidia driver -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055761 Title: tracker-extract-3 crashed with SIGSYS in epoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/2055761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058491] [NEW] (mate-appearance-properties : GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process
Public bug reported: Appears to be cross-compiled with both GTK+2 and GTK+3 flags. Fails to start due to error: (mate-appearance-properties:15895): Gtk-ERROR **: 17:02:39.177: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported I know this is coming from a rather old version of Ubuntu 18.04, but there is a reason why I'm running an old installation, and the lack of resources is why I am running Mate. Thought I should at least let you know this is happening. ** Affects: ubuntu-mate-settings (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/2058491 Title: (mate-appearance-properties : GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/2058491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054872] Re: Cannot change IRQ 70 affinity: Input/output error
irqbalance 1.9.3-2ubuntu4 verified on 6.8.0-11-generic Issue no longer reproduces. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054872 Title: Cannot change IRQ 70 affinity: Input/output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2054872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058143] Re: Decoding glitchy on GM45 - MR has been pending since 2020
So the MR fixing the particular glitch I'm seeing on my Thinkpad T400 / GM45 is https://github.com/intel/intel-vaapi-driver/pull/514 . Including that would be enough to close this bug - it's pretty small and straight forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058143 Title: Decoding glitchy on GM45 - MR has been pending since 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/2058143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058143] [NEW] Decoding glitchy on GM45 - MR has been pending since 2020
Public bug reported: Ubuntu 24.04 will ship with Gstreamer 1.24, which finally promoted many "va*" plugins to primary, i.e. enabled them by default and will thus be used by more apps than in the past. I tested this on an old Thinkpad T400 / Intel GM45 and ran into a glitch. Fortunately there's pending MR (see below) fixing that - but Intel does not seem to maintain https://github.com/intel/intel-vaapi- driver any more, so it will likely never get merged or released. I'd thus like to request to add the MR in question to the Debian/Ubuntu package. However, while on it, it might sense to add a few more fixes that have accumulated: - All new commits on the master branch (~7?) - https://github.com/intel/intel-vaapi-driver/pull/566, which will be needed for upcoming Wayland compositor changes. - https://github.com/intel/intel-vaapi-driver/pull/514 which fixes glitches for e.g. Gstreamer based players on very old generations (GM45). I tested/verified this one myself. - Potentially: https://github.com/intel/intel-vaapi-driver/pull/530 - unfortunately I don't have the hardware to verify this one. If you prefer, I can also try to open a MR at https://salsa.debian.org/multimedia-team/intel-vaapi- driver/-/merge_requests - but I'm not very used to the debian packaging workflow. Thanks for considering :) ** Affects: intel-vaapi-driver (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/2058143 Title: Decoding glitchy on GM45 - MR has been pending since 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/2058143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2024937]
For those looking for a work around: I use gnupg instead and it works for me even better than ssh agent. Gnupg can be autostarted via systemd. The configuration was not obvious though. A few pointers: - https://wiki.archlinux.org/title/GnuPG#SSH_agent - https://unix.stackexchange.com/a/423516 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024937 Title: ssh-agent is not started via startplasma-wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/2024937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054872] Re: Cannot change IRQ 70 affinity: Input/output error
174955 233311 126152
160532 145524 171051 153168 119414 134045 Function call interrupts
+ TLB: 94988 98433 115358 96450 118525 98758 124773 94916 123529 90824 119527
95110 120917 98504 107344 96577 TLB shootdowns
+ TRM: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Thermal event interrupts
+ THR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Threshold APIC interrupts
+ DFR: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Deferred Error APIC interrupts
+ MCE: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Machine check exceptions
+ MCP: 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 15 Machine check polls
+ ERR: 1
+ MIS: 0
+ PIN: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt notification event
+ NPI: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Nested posted-interrupt event
+ PIW: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Posted-interrupt wakeup event
** Patch added: "noble.debdiff"
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2054872/+attachment/5756029/+files/noble.debdiff
** Changed in: irqbalance (Ubuntu)
Importance: Undecided => Medium
** Changed in: irqbalance (Ubuntu)
Status: Incomplete => In Progress
** Changed in: irqbalance (Ubuntu)
Assignee: (unassigned) => Robert Malz (rmalz)
** Also affects: irqbalance (Ubuntu Noble)
Importance: Medium
Assignee: Robert Malz (rmalz)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054872
Title:
Cannot change IRQ 70 affinity: Input/output error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2054872/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble
This does make it run. Thank you.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Sun, 10 Mar 2024, Åka Sikrom wrote:
> Date: Sun, 10 Mar 2024 12:30:18 -
> From: Åka Sikrom <2055...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 2055114] Re: fail2ban is broken in 24.04 Noble
>
> As of this commit from 12 Dec 2023:
> https://github.com/fail2ban/fail2ban/commit/1024452fe1befeb5a0a014386a81ec183cd45bb5
> upstream ships its source with the missing async* libraries embedded,
> which solves the issue for now.
>
>
> Here is a suggested workaround for Noble until the fix hopefully finds its
> way into the repos.
>
> DISCLAMER: Try at your own risk. I am not an Ubuntu/Debian developer.
> Next time you receive a proper package update of fail2ban via apt, any
> of the manually-downloaded files below may cause conflicts and break
> your system.
>
> mkdir -m 0755 /usr/lib/python3/dist-packages/fail2ban/compat
> wget -O /usr/lib/python3/dist-packages/fail2ban/compat/asynchat.py
> https://github.com/fail2ban/fail2ban/raw/1024452fe1befeb5a0a014386a81ec183cd45bb5/fail2ban/compat/asynchat.py
> wget -O /usr/lib/python3/dist-packages/fail2ban/compat/asyncore.py
> https://github.com/fail2ban/fail2ban/raw/1024452fe1befeb5a0a014386a81ec183cd45bb5/fail2ban/compat/asyncore.py
> cp -p
> /usr/lib/python3/dist-packages/fail2ban/server/asyncserver.py{,.original}
> wget -O /usr/lib/python3/dist-packages/fail2ban/server/asyncserver.py
> https://github.com/fail2ban/fail2ban/raw/1024452fe1befeb5a0a014386a81ec183cd45bb5/fail2ban/server/asyncserver.py
>
> My custom-boostrapped Noble test system is also missing the required
> 'distutils' Python module by default. The fail2ban package does not have
> 'python3-setuptools' listed under "Depends" in its control file, which
> it possibly should at this point. Official Ubuntu images may already
> have it installed via other packages, but if not, you will need to
> install it as well:
>
> apt install python3-setuptools
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2055114
>
> Title:
> fail2ban is broken in 24.04 Noble
>
> Status in fail2ban package in Ubuntu:
> Confirmed
>
> Bug description:
> Was working in 22.04, but after upgrading to 24.04 I get this:
>
> × fail2ban.service - Fail2Ban Service
> Loaded: loaded (/etc/systemd/system/fail2ban.service; enabled; preset:
> enabled)
> Active: failed (Result: exit-code) since Sun 2024-02-25 02:27:29 PST; 1
> day 18h ago
> Duration: 2.330s
> Docs: man:fail2ban(1)
> Process: 1130 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited,
> status=0/SUCCESS)
> Process: 1133 ExecStart=/usr/local/bin/fail2ban-server -xf start
> (code=exited, status=255/EXCEPTION)
> Main PID: 1133 (code=exited, status=255/EXCEPTION)
> CPU: 660ms
>
> Feb 25 02:27:26 mx1 systemd[1]: Starting fail2ban.service - Fail2Ban
> Service...
> Feb 25 02:27:26 mx1 systemd[1]: Started fail2ban.service - Fail2Ban Service.
> Feb 25 02:27:28 mx1 fail2ban-server[1133]: 2024-02-25 02:27:28,952 fail2ban
> [1133]: ERROR No module named 'asynchat'
> Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Main process exited,
> code=exited, status=255/EXCEPTION
> Feb 25 02:27:29 mx1 systemd[1]: fail2ban.service: Failed with result
> 'exit-code'.
>
> grep fail2ban syslog
> 2024-02-25T02:25:17.813593-08:00 mx1 systemd[1]: Stopping fail2ban.service -
> Fail2Ban Service...
> 2024-02-25T02:27:26.625640-08:00 mx1 systemd[1]: Starting fail2ban.service -
> Fail2Ban Service...
> 2024-02-25T02:27:26.678572-08:00 mx1 systemd[1]: Started fail2ban.service -
> Fail2Ban Service.
> 2024-02-25T02:27:28.954548-08:00 mx1 fail2ban-server[1133]: 2024-02-25
> 02:27:28,952 fail2ban[1133]: ERROR No module named
> 'asynchat'
> 2024-02-25T02:27:29.004733-08:00 mx1 systemd[1]: fail2ban.service: Main
> process exited, code=exited, status=255/EXCEPTION
> 2024-02-25T02:27:29.004834-08:00 mx1 systemd[1]: fail2ban.service: Failed
> with result 'exit-code'.
>
> Seems 24.04 is missing a python 3.12 module 'asynchat'.
>
> This leaves my systems vulnerable to brute-force password guessing
> attacks.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 24.04
> Package: fail2ban 1.0.2-3
> Uname: Linux 6.7.6 x86_64
> ApportVersion: 2.28.0-0ubuntu1
> Architecture: amd64
> CasperMD5CheckResult: unknown
> CurrentDesktop: MATE
> Date: Mon Feb 26 20:33:12 2024
> InstallationDate: Installed on 2017-08-14 (2388 days ago)
> InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
> PackageArchitecture: all
> SourcePackage: fail2ban
>
[Bug 2055114] Re: fail2ban is broken in 24.04 Noble
I wish people wouldn't use languages like python which changes it's packages and syntax weekly, but since they do the obvious question, is anyone going to work on this? It is a rather important security tool. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055114 Title: fail2ban is broken in 24.04 Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/2055114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055782] [NEW] Installation of linux crashes installing grub to dedicated disk
Public bug reported: 4Tb SSD Disk was wiped for this install ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.20 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.2 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 08:52:40 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.20 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055782 Title: Installation of linux crashes installing grub to dedicated disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/2055782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
LP update: Mantic update: Due to lack of reproduction environment I have been performing following regression test: 1. Setup: nic: 2port E810-C both interfaces set up in bonding kernel: 6.5.0-25-generic 2. Test cases: 0) verified that code from the change is used during driver init a) stress traffic for 12h (multiple streams of iperf (tcp)) b) if up/down during stress traffic c) reload driver during stress traffic Look for any issues related to traffic processing, look for tx_hangs 3. Result: No issues have been detected during test execution -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036239] Re: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out
Hi Roxana, Mantic verification is still not finished. I did some touch tests without stress traffic. I'm trying to get my hands on E810 device to finish testing, I'll update ticket once it's done. Wishful ETA EOW 09. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036239 Title: Intel E810-XXV - NETDEV WATCHDOG: (ice): transmit queue timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2023322]
Bug driver 470, Nvidia GTX 650 W dniu 26.02.2024 o 04:06, Craig pisze: > (In reply to Michael Catanzaro from comment #62) >> Hi Craig and Thomas (and Emil if you're still around): if you're still >> encountering problems with NVIDIA graphics, please report new a bug and >> leave a comment here linking to the new bug. > My problem was on legacy nvidia driver, and newer versions wouldn't even > start. But I now know a workaround (GSK_RENDERER=cairo) and don't expect > there will be a fix for my old driver anyway. > https://gitlab.gnome.org/GNOME/gtk/-/issues/5858 > ** Attachment added: "Zrzut ekranu z 2024-02-26 14-51-55.png" https://bugs.launchpad.net/bugs/2023322/+attachment/5749476/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-51-55.png ** Attachment added: "Zrzut ekranu z 2024-02-26 14-52-37.png" https://bugs.launchpad.net/bugs/2023322/+attachment/5749477/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-52-37.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2023322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1978821] Re: libbrotli1 upgrade to 1.0.9 due to security
It's CVE-2020-8927 Apparently the earlier versions of Brotli have been patched, see https://usn.ubuntu.com/4568-1/ Still, it's confusing to see an earlier version and be unsure whether it was patched or not. I would think that a change from 1.0.3 or 1.0.7 to 1.0.9 would be safe. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-8927 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1978821 Title: libbrotli1 upgrade to 1.0.9 due to security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brotli/+bug/1978821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977621] [NEW] Transparency come and go
Public bug reported: Prior to upgrading to 22.04 everything worked as expected, after upgrading my panels are no longer transparent. The mate-tweak settings are not properly applied during login or reboot. If I after reboot set my panels transparent again, sometimes it will let me, sometimes it won't. If it lets me, the next time I logout and login again they are no longer transparent. I am not using Wayland, I use the Xorg Intel kernel server, this because I have Intel graphics and use virtualized GPU on a virtual machine, this does not work with Wayland and for that matter neither does Synaptic. Really I wish Wayland and Systemd and a bunch of the other modern atrocities that have transformed Ubuntu from a good reliable OS into an unstable difficult OS would just die. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mate-desktop 1.26.0-1 Uname: Linux 5.17.12 x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Jun 3 14:51:00 2022 SourcePackage: mate-desktop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977621 Title: Transparency come and go To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1977621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1975557] Re: blank screen does not turn off display backlight
** Reply to message from Daniel van Vugt <1975...@bugs.launchpad.net> on Wed, 25 May 2022 06:15:35 - I get an error running apport-collect. I am beginning to think that the last update to this system went wrong. There are other problems comming up which I did not have before. I have now tried the display with another 22.04 install and that works OK. So I think this problem report should be closed. bob1@Juptier:~$ apport-collect 1975557 ERROR: connecting to Launchpad failed: Unable to find the server at launchpad.net You can reset the credentials by removing the file "/home/bob1/.cache/apport/launchpad.credentials" bob1@Juptier:~$ > The difference between 21.10 and 22.04 might just be that we now default > to Wayland instead of Xorg. So the display subsystems are different. > > Please run this command to gather more information: > > apport-collect 1975557 > > And to save time in future please use the 'ubuntu-bug' command to report > new bugs. > > ** Tags added: jammy > > ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1975557 > > Title: > blank screen does not turn off display backlight > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > I updated a system from 21.10 to 22.04 and noticed that when the > screen is blanked by no keyboard or mouse activity that the backlight > in the VGA monitor is still on. The "settings->Displays" has "Unknown > Display" which I assume means the system does not know what commands > to send to the monitor to shut it off. I booted a live DVD of 21.10 > and the settings has the VGA display as 'AOC 22" ' which is correct > and the screen blanking works correctly. So it seems that the > definition for the AOC displays have been removed from 22.04. > > This behavior is different on Ubuntu 21.10, the VGA display is blank and the > backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the > VGA display manufacture name, on 22.04 the > VGA display manufacture name is "Unknown Display". > > I have discovered that the settings have the following options > > "settings->Power->Screen Blank" with a time value to be selected and the > following text on the next line "Turns the screen off after a period of > inactivity" > > "settings->Privacy->Screen->Blank Screen Display" with a time value to be > selected and the following text on the next line "Period of inactivity after > which the screen will go blank" > > The two options have different actions but seem to be connected because > changing the time on one changes the time on the other. > > My guess is that the update changed the action for Ubuntu 22.04. I > would like the 21.10 behavior, that is to turn off the VGA display not > just blank the display when selecting the "settings->Power->Screen > Blank" for 22.04. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+subscriptions -- Robert Blair Tell me and I forget. Teach me and I remember. Involve me and I learn. -- Xun Kuang (Confucian philosopher) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975557 Title: blank screen does not turn off display backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967013] Re: Bionic update: upstream stable patchset 2022-03-29
As stated in the bug ticket linked above, this commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b causes issues on hardware where the intel_lpss driver tries to load the intel idma driver, because this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel-lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 has not been backported to the 4.15 kernel. I propose backporting this commit to the 4.15 kernel ASAP to fix the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967013 Title: Bionic update: upstream stable patchset 2022-03-29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
FIXED IT! It is indeed the intel_lpss driver, at least in my case. This commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b will not work right when a module that is asynchronously loaded tries to synchronously load a module, which is not (or no longer?) allowed. It appears the intel_lpss driver did just that until this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel- lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 But this commit has not been backported to the 4.15 kernel, so the intel_lpss driver delivered with the 4.15.0-177 kernel package does not have it. Applying this commit to the 4.15.0-177 source tree, rebuilding and replacing (only!) the intel_lpss.ko module makes the kernel load without delays for me. I confirmed the same with kernel 4.15.0-180. So now we only need to convince the Ubuntu maintainers to backport https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mfd/intel- lpss.c?id=569fac74627cc332a2097a7a4bfdc654b8e7f273 to the 4.15 kernel... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967013] Re: Bionic update: upstream stable patchset 2022-03-29
This commit is suspected to cause issues for many users: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b Please see this bug ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967013 Title: Bionic update: upstream stable patchset 2022-03-29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
My "prime suspect" is this commit: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/kernel/module.c?h=Ubuntu-4.15.0-177.186=3879f4364139acb2bd3932e6a15994f109c49d6b Also see Linus' comments when this patch was submitted to the mainline kernel: https://www.spinics.net/lists/kernel/msg4223720.html "that might be a big deal slowing things down at boot time. [...] Comments? Maybe this is a "just apply it, see if somebody screams" situation?" From what I understand, other measures taken in the kernel and modules make this issue no longer occur, so my hypothesis is that this may not have caused issues in the current kernel. So the mistake was that Canonical backported this commit to a very old kernel version that kernel.org no longer maintains... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
I have found a change between 176 and 177 that looks suspicious:
diff -upr --color 176/linux-source-4.15.0/kernel/module.c
177/linux-source-4.15.0/kernel/module.c
--- 176/linux-source-4.15.0/kernel/module.c 2022-03-29 19:39:48.0
+0200
+++ 177/linux-source-4.15.0/kernel/module.c 2022-04-14 22:22:50.0
+0200
@@ -3520,22 +3514,13 @@ static noinline int do_init_module(struc
- /*
-* We need to finish all async code before the module init sequence
-* is done. This has potential to deadlock. For example, a newly
-* detected block device can trigger request_module() of the
-* default iosched from async probing task. Once userland helper
-* reaches here, async_synchronize_full() will wait on the async
-* task waiting on request_module() and deadlock.
-*
-* This deadlock is avoided by perfomring async_synchronize_full()
-* iff module init queued any async jobs. This isn't a full
-* solution as it will deadlock the same if module loading from
-* async jobs nests more than once; however, due to the various
-* constraints, this hack seems to be the best option for now.
-* Please refer to the following thread for details.
-*
-* http://thread.gmane.org/gmane.linux.kernel/1420814
-*/
- if (!mod->async_probe_requested && (current->flags & PF_USED_ASYNC))
+ /*
+* We need to finish all async code before the module init sequence
+* is done. This has potential to deadlock if synchronous module
+* loading is requested from async (which is not allowed!).
+*
+* See commit 0fdff3ec6d87 ("async, kmod: warn on synchronous
+* request_module() from async workers") for more details.
+*/
+ if (!mod->async_probe_requested)
async_synchronize_full();
Maybe this is the deadlock we're all running into...?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-177-generic freezes on the welcome screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1974203] Re: NO IRQ HANDLER FOR VECTOR
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974203 Title: NO IRQ HANDLER FOR VECTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975557] [NEW] blank screen does not turn off display backlight
Public bug reported: I updated a system from 21.10 to 22.04 and noticed that when the screen is blanked by no keyboard or mouse activity that the backlight in the VGA monitor is still on. The "settings->Displays" has "Unknown Display" which I assume means the system does not know what commands to send to the monitor to shut it off. I booted a live DVD of 21.10 and the settings has the VGA display as 'AOC 22" ' which is correct and the screen blanking works correctly. So it seems that the definition for the AOC displays have been removed from 22.04. This behavior is different on Ubuntu 21.10, the VGA display is blank and the backlight is off. A minor nit is on 21.10 the "settings->Displays" shows the VGA display manufacture name, on 22.04 the VGA display manufacture name is "Unknown Display". I have discovered that the settings have the following options "settings->Power->Screen Blank" with a time value to be selected and the following text on the next line "Turns the screen off after a period of inactivity" "settings->Privacy->Screen->Blank Screen Display" with a time value to be selected and the following text on the next line "Period of inactivity after which the screen will go blank" The two options have different actions but seem to be connected because changing the time on one changes the time on the other. My guess is that the update changed the action for Ubuntu 22.04. I would like the 21.10 behavior, that is to turn off the VGA display not just blank the display when selecting the "settings->Power->Screen Blank" for 22.04. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975557 Title: blank screen does not turn off display backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
Trying to isolate the issue, I: 1. Booted my portable Ubuntu 18.04.6 installation on a different machine (different CPU, chipset, but still Intel). On the other machine, kernel 4.15.0-177 booted without issues, so apparently it does not depend on the installation, but rather on the hardware or BIOS whether the freeze occurs or not. 2. Replaced the entire /lib/modules/4.15.0-177-generic/ with the contents from /lib/modules/4.15.0-176-generic/ and rebuilt initramfs. This did NOT cure the freezes (only caused a lot of module signature errors, confirming that the modules really were replaced). So whatever is causing the freezes is not in one of loadable modules, but rather within the kernel itself or the builtin modules. Still, the 176-to-177 diff over the builtin modules is HUGE... :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1974203] Re: NO IRQ HANDLER FOR VECTOR
Thanks for reply Daniel. When booting I can see this notification : "no irq handler ..." + "live patch cve-2013-1798 ... " in other words no update possible as no archive folder ... Doest it make any sense to you ? Le 20/05/2022 à 04:46, Daniel van Vugt a écrit : > Please explain in more detail what the problem is you are experiencing. > > ** Package changed: xorg (Ubuntu) => ubuntu > > ** Changed in: ubuntu > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974203 Title: NO IRQ HANDLER FOR VECTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1974102] Re: Sun4u emulation network does not work
Ok, I'll try to specify a lance interface, I think I specified hme, as the documentation said it had changed to that. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Fri, 20 May 2022, Paride Legovini wrote: > Date: Fri, 20 May 2022 13:54:13 - > From: Paride Legovini <1974...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1974102] Re: Sun4u emulation network does not work > > Hello Robert and thanks for this bug report. I checked what NICs are > supported on sparc, and: > > $ qemu-system-sparc -net nic,model='?' > Supported NIC models: > lance > > so apparently it's only lance. Now, is there any trace of this NIC on > the guest system? Does it show up in `ip addr` or `ip link`? Does it > show up in lspci / dmesg? Is there any trace of a lance kernel module > (this may be CONFIG_LANCE in the kernel config)? > > My guess here is that the guest system is lacking drivers for the lance > NIC, so it will show up in lspci but not no `ip link`, however I'm a bit > in the dark. Let us know your findings and we'll see if there's anything > we can do from the Ubuntu side. Thanks! > > ** Changed in: qemu (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1974102 > > Title: > Sun4u emulation network does not work > > Status in qemu package in Ubuntu: > Incomplete > > Bug description: > I've created a virtual machine using the following arguments: > > qemu-system-sparc -bios /opt/roms/ss5.bin -vga cg3 -hda > /var/lib/libvirt/images/ultra3.img -cdrom /opt/iso/redhat62.iso > > Where /opt/roms/ss5.bin are ROMS I obtained from a website for SS-5, > /var/lib/libvirt/images/ultra3.img is a qcow2 image file 4GB, and > /opt/iso/redhat62.iso is a redhat 6.2 image I copied using cp /dev/sr0 > /opt/iso/redhat62.iso. > > I was able to successfully install and boot the virtual machine with > Redhat 6.2, however the network interface does not talk. Can't even > ping the interface of the physical machine it is hosted on. > > virt-manager sparc is completely useless, no way to load from a CD > image and if I try to import the existing disk image I created this > way, the monitor blows up. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: qemu-system-sparc 1:6.2+dfsg-2ubuntu6 > Uname: Linux 5.17.7 x86_64 > ApportVersion: 2.20.11-0ubuntu82.1 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: MATE > Date: Wed May 18 16:38:57 2022 > InstallationDate: Installed on 2017-05-27 (1817 days ago) > InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) > Lsusb: > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: > /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M > /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M > /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M > /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M > MachineType: System manufacturer System Product Name > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7 > root=UUID=a5625ed7-127f-48e2-8430-167d139254ec ro quiet splash vt.handoff=7 > RebootRequiredPkgs: Error: path contained symlinks. > SourcePackage: qemu > UpgradeStatus: Upgraded to jammy on 2022-05-16 (2 days ago) > dmi.bios.date: 04/26/2017 > dmi.bios.release: 5.12 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 3402 > dmi.board.asset.tag: Default string > dmi.board.name: Z170 PRO GAMING > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr3402:bd04/26/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: System Product Name > dmi.product.sku: SKU > dmi.product.version: System Version > dmi.sys.vendor: System manuf
[Bug 1974203] [NEW] NO IRQ HANDLER FOR VECTOR
Public bug reported: CANNOT UPDATE ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_84_94_generic_85 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Thu May 19 16:30:38 2022 DistUpgraded: 2020-10-06 18:55:54,955 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: focal DistroVariant: ubuntu DpkgLog: GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller]) Subsystem: Lenovo Kabini [Radeon HD 8210] [17aa:3802] InstallationDate: Installed on 2018-11-18 (1277 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20240 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-84-generic root=UUID=1d6c2f9c-9ac1-47d3-8a0a-480bb5876f61 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-06 (589 days ago) dmi.bios.date: 12/04/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 82CN27WW(V3.00) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505 dmi.board.vendor: LENOVO dmi.board.version: 31900058Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505 dmi.modalias: dmi:bvnLENOVO:bvr82CN27WW(V3.00):bd12/04/2013:svnLENOVO:pn20240:pvrLenovoG505:rvnLENOVO:rnLenovoG505:rvr31900058Std:cvnLENOVO:ct10:cvrLenovoG505: dmi.product.family: IDEAPAD dmi.product.name: 20240 dmi.product.sku: LENOVO_MT_20240 dmi.product.version: Lenovo G505 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-31T16:07:37.548006 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Nov 18 18:23:05 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: radeon ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974203 Title: NO IRQ HANDLER FOR VECTOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974102] [NEW] Sun4u emulation network does not work
Public bug reported: I've created a virtual machine using the following arguments: qemu-system-sparc -bios /opt/roms/ss5.bin -vga cg3 -hda /var/lib/libvirt/images/ultra3.img -cdrom /opt/iso/redhat62.iso Where /opt/roms/ss5.bin are ROMS I obtained from a website for SS-5, /var/lib/libvirt/images/ultra3.img is a qcow2 image file 4GB, and /opt/iso/redhat62.iso is a redhat 6.2 image I copied using cp /dev/sr0 /opt/iso/redhat62.iso. I was able to successfully install and boot the virtual machine with Redhat 6.2, however the network interface does not talk. Can't even ping the interface of the physical machine it is hosted on. virt-manager sparc is completely useless, no way to load from a CD image and if I try to import the existing disk image I created this way, the monitor blows up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: qemu-system-sparc 1:6.2+dfsg-2ubuntu6 Uname: Linux 5.17.7 x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Wed May 18 16:38:57 2022 InstallationDate: Installed on 2017-05-27 (1817 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7 root=UUID=a5625ed7-127f-48e2-8430-167d139254ec ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: qemu UpgradeStatus: Upgraded to jammy on 2022-05-16 (2 days ago) dmi.bios.date: 04/26/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3402 dmi.board.asset.tag: Default string dmi.board.name: Z170 PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd04/26/2017:br5.12:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: qemu (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/1974102 Title: Sun4u emulation network does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1974102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973101] Re: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work
It was only partly successful, it failed to merge udp = y into the new conf. Also Ubuntu's decision to compile their kernels without UDP support is dumb. It does not make a huge difference in size or speed of the kernel and it does eliminate legacy support as the original NFS version 2 and version 3 specifications had no support for TCP. As it is I self compile a non-trivial portion of my server infrastructure because Ubuntu just does not provide the facilities that I need. I switched to Ubuntu from Redhat in 2012, when Redhat got to be this way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973101 Title: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973101] Re: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work
This is just plain WRONG. The issue is NOT the kernel, upstream or otherwise. I am using 5.17.7 compiled directly from kernel source off of kernel.org, and was using the SAME kernel under 20.04. The issue was your new configuration file, /etc/nfs.conf, that did not exist prior to 22.04, and thus I had no reason to look for it, having UDP disabled by default even for versions 2 and 3 of NFS which makes ZERO sense as version 2 and 3 of NFS did not support TCP. Once I was made aware of this conf file by you simply turning version 2 and UDP on resolved my issues. You can close this bug if you like but having udp = n by default in this conf file is dumb, the current upstream kernel supports it just fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973101 Title: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973645] [NEW] git-lfs migrte import painfully slow (3.0.2)
Public bug reported: Hello, git-lfs shipped with Ubuntu 22.04 (version 3.0.2) is very slow when doing "lfs migrate import". This is upstream bug/regression: https://github.com/git-lfs/git-lfs/issues/4750 Is there is any chance to backport/upgrade git-lfs package for Ubuntu 22.04? ** Affects: git-lfs (Ubuntu) Importance: Undecided Status: New ** Summary changed: - git-lfs migrte import painfuly slow (3.0.2) + git-lfs migrte import painfully slow (3.0.2) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973645 Title: git-lfs migrte import painfully slow (3.0.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git-lfs/+bug/1973645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Promotion from -proposed sure would be nice. I see verification has been done but a update excuses shows an netplan.io regression[1]. I'm not sure if the test is flaky but I see that seb retried it a few times[2] last week and it failed consistently, so maybe not. I'm just curious if there's any status on the test failure. (Also, I started writing this thinking it had been a month but it's been less than a week and I can't tell time. I know it wouldn't be promoted with less than a week in -proposed anyway.) [1] https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#wpa [2] https://autopkgtest.ubuntu.com/packages/netplan.io/jammy/arm64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962541] Re: PEAP wifi can't connect (ubuntu live/installer is also not working
Thank you Seb, I had the issue reported in this bug in a WeWork today (first time connecting since updating to Jammy) and the package in -proposed resolved the issue for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962541 Title: PEAP wifi can't connect (ubuntu live/installer is also not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1962541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1973101] Re: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work
Thank you very much. The disabling of udp by default is what broke version 2 and version 3, and since TCP were not part of the NFS specification for either of these versions, making it the default makes ZERO sense. On 5/12/22 11:44, Andreas Hasenack wrote: > rpcinfo -s j1-nfs-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973101 Title: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973358] [NEW] blinking app-indication area with Ubuntu 22.04
Public bug reported: After updating 21.10 to 22.04 the app-indicator starts "blinking" as if the positions of the indicators constantly have to be redrawn. Hovering the mouse over the multiload indicator shows a menu that is constantly changing size and position. Closing the app removes the indicator and the indicator area stays calm again. ** Affects: indicator-multiload (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Vido showing the problem" https://bugs.launchpad.net/bugs/1973358/+attachment/5589608/+files/simplescreenrecorder-2022-05-13_17.19.37.mkv ** Description changed: - After updating 21.09 to 22.04 the app-indicator starts "blinking" as if + After updating 21.10 to 22.04 the app-indicator starts "blinking" as if the positions of the indicators constantly have to be redrawn. Hovering the mouse over the multiload indicator shows a menu that is constantly changing size and position. Closing the app removes the indicator and the indicator area stays calm again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973358 Title: blinking app-indication area with Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/1973358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
Alas! I spoke to seen. The seeming "workaround" only lasted for one
boot, and after that, the ~180 seconds delay is back to stay, although
the Intel IOMMU is still disabled.
So this issue is "sporadic". Maybe even a race condition... :(
And maybe not even related to the intel-lpss driver: The line:
"intel-lpss :00:15.0: enabling device ( -> 0002)"
seems to come from drivers/pci/setup-res.c:
if (cmd != old_cmd) {
dev_info(>dev, "enabling device (%04x -> %04x)\n",
old_cmd, cmd);
pci_write_config_word(dev, PCI_COMMAND, cmd);
}
So it just enables the PCI device, which at some point leads to
drivers/mfd/intel-lpss.c#intel_lpss_probe() being called which requests
the DMA module leading to drivers/dma/idma64.c#idma64_probe() being
called which finally outputs:
dev_info(chip->dev, "Found Intel integrated DMA 64-bit\n");
So a lot of code between these two log lines:
[6.439056] intel-lpss :00:15.0: enabling device ( -> 0002)
[ 187.141427] idma64 idma64.0: Found Intel integrated DMA 64-bit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973167
Title:
linux-image-4.15.0-177-generic freezes on the welcome screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973234] Re: Slow Boot, No SOUND, No Ethernet
When the machine is booted, open a terminal and run "dmesg" to see on what the kernel was stuck so long. In my case, it was the intel-lpss PCI device initialization, and I fixed it by disabling the Intel IOMMU. If you get similar results, this issue might be a duplicate of mine which I reported here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973234 Title: Slow Boot, No SOUND, No Ethernet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
After grepping dmesg for all lines about the "00:15" devices, I found two lines starting with "DMAR:", which made me think of another machine running debian which had issues with DMAR: devices that were related to the Intel IOMMU. So I tried the workaround I knew from there: Edit /etc/default/grub and add "intel_iommu=off" to the GRUB_CMDLINE_LINUX_DEFAULT value, then run "sudo update-grub" to update the grub configuration and reboot. and voila, intel-lpss initializes within a few milliseconds again: [6.518592] intel-lpss :00:15.0: enabling device ( -> 0002) [6.560693] idma64 idma64.0: Found Intel integrated DMA 64-bit [6.569509] intel-lpss :00:15.1: enabling device ( -> 0002) [6.569691] idma64 idma64.1: Found Intel integrated DMA 64-bit [6.574164] mei_me :00:16.0: enabling device ( -> 0002) $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic root=UUID= ro intel_iommu=off So some change between 4.15.0-176 and 4.15.0-177 seemingly broke the Intel IOMMU. Question is whether it was a formerly "dormant" BIOS bug that was only unveiled by some change, or whether it is a newly introduced Linux bug that broke Intel IOMMU support... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
After finding someone reporting the same issue (https://forums.linuxmint.com/viewtopic.php?t=373747=2175201) and reading that the machine may come alive after a while, I found that indeed after 3 minutes the machine works. dmesg that reveals that it seemingly was the initialization of the intel_lpss driver that took 3 minutes: [6.889189] intel-lpss :00:15.0: enabling device ( -> 0002) [7.112397] input: PC Speaker as /devices/platform/pcspkr/input/input5 [7.220480] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer [7.220481] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules [7.220481] RAPL PMU: hw unit of domain package 2^-14 Joules [7.220482] RAPL PMU: hw unit of domain dram 2^-14 Joules [7.220482] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules [7.220483] RAPL PMU: hw unit of domain psys 2^-14 Joules [9.882380] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 10.068162] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready [ 10.070009] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready [ 10.115669] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready [ 10.117735] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 10.61] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready [ 14.114836] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx [ 14.114883] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready [ 15.14] atlantic: link change old 0 new 1000 [ 15.200150] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready [ 187.423062] intel-lpss :00:15.1: enabling device ( -> 0002) [ 187.432242] mei_me :00:16.0: enabling device ( -> 0002) [ 187.432264] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 187.441672] AVX2 version of gcm_enc/dec engaged. [ 187.441673] AES CTR mode by8 optimization enabled [ 187.445619] idma64 idma64.0: Found Intel integrated DMA 64-bit [ 187.452528] idma64 idma64.1: Found Intel integrated DMA 64-bit Note these lines: [6.889189] intel-lpss :00:15.0: enabling device ( -> 0002) [ 187.423062] intel-lpss :00:15.1: enabling device ( -> 0002) [ 187.432242] mei_me :00:16.0: enabling device ( -> 0002) [ 187.445619] idma64 idma64.0: Found Intel integrated DMA 64-bit [ 187.452528] idma64 idma64.1: Found Intel integrated DMA 64-bit For comparison, the same lines from the 4.15.0-176 dmesg: [6.321873] intel-lpss :00:15.0: enabling device ( -> 0002) [6.340549] idma64 idma64.0: Found Intel integrated DMA 64-bit [6.345409] intel-lpss :00:15.1: enabling device ( -> 0002) [6.345610] idma64 idma64.1: Found Intel integrated DMA 64-bit [6.350618] mei_me :00:16.0: enabling device ( -> 0002) So the initialization time increased from 30ms of 180s, i.e. by a factor of 6,000. This cannot be right. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973167] [NEW] linux-image-4.15.0-177-generic freezes on the welcome screen
Public bug reported: After updating to linux-image-4.15.0-177-generic, my machine completely freezes on the Ubuntu Welcome screen, i.e. right after switching to GUI mode. The mouse pointer is frozen, the keyboard does not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows no reaction. I cannot work with my machine at this point and have to hard reset it. Selecting advanced boot options in grub and selecting the previous linux kernel 4.15.0-176 makes it work again. So this bad bug was introduced with the 4.15.0-177 kernel release. I tried removing the nvidia-driver-510 package, presumably making Ubuntu use the "nouveau" driver, and with that, I could use the welcome screen and log in, but the machine still froze shortly afterwards. So maybe this is some sort of interference with my GeForce 1080 graphics card, but it is not specific to the driver used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18 Uname: Linux 4.15.0-176-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2082 F pulseaudio /dev/snd/controlC0: robert 2082 F pulseaudio /dev/snd/controlC2: robert 2082 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 12 13:36:28 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-29 (2386 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Supermicro Super Server ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-176-generic N/A linux-backports-modules-4.15.0-176-generic N/A linux-firmware 1.173.21 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago) dmi.bios.date: 09/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SAE dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973101] Re: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work
ubuntu-bug included mounts of other file systems on this machine, but it is the EXPORTS that aren't working NOT the mounts from other systems. Here is the content of /etc/exports: # /etc/exports: the access control list for filesystems which may be exported # to NFS clients. See exports(5). # # Example for NFSv2 and NFSv3: # /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check) # # Example for NFSv4: # /srv/nfs4gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check) # /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check) # /var/list 204.122.16.0/24(rw,async,no_root_squash,secure,subtree_check) /mail 204.122.16.4(rw,async,no_root_squash,insecure,subtree_check) /mail 204.122.16.0/24(rw,async,no_root_squash,secure,subtree_check) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973101 Title: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973101] [NEW] After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work
Public bug reported: I upgraded from 20.04 to 22.04 a server which has NFS clients that are version 2 (SunOS 4.1.4), version 3 (Redhat 6.2) and version 4.2 (other modern Linux systems). After upgrading the version 2 and version 3 clients no longer can mount the file systems. A check with rpcinfo -p showed version 2 no longer being advertised, I checked the conf and found the update had disabled it, I re-enabled it. Version 3 was still advertised, but the mount still fails, and after re- enabling version 2, the mount still fails. I am also not at all appreciative of the unauthorized changes that the upgrade made to my exports file. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nfs-kernel-server 1:2.6.1-1ubuntu1 Uname: Linux 5.17.6 x86_64 .etc.request-key.d.id_resolver.conf: create id_resolver * * /usr/sbin/nfsidmap -t 600 %k %d ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Wed May 11 18:44:54 2022 NFSMounts: NFSv4Mounts: /bu204.122.16.128:/mail.bu nfs4 rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=204.122.16.222,local_lock=none,addr=204.122.16.128 /misc 204.122.16.12:/misc nfs4 rw,nosuid,nodev,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=204.122.16.222,local_lock=none,addr=204.122.16.12 /home 204.122.16.12:/home nfs4 rw,nosuid,nodev,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=204.122.16.222,local_lock=none,addr=204.122.16.12 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nfs-utils UpgradeStatus: Upgraded to jammy on 2022-05-10 (1 days ago) ** Affects: nfs-utils (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/1973101 Title: After upgrade to 22.04 NFS exports for vers 2 and 3 no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972994] [NEW] package libssl3:amd64 3.0.2-0ubuntu1.1 failed to install/upgrade: package libssl3:amd64 is already installed and configured
Public bug reported: Updating software ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libssl3:amd64 3.0.2-0ubuntu1.1 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 AptdaemonVersion: 1.1.1+bzr982-0ubuntu39 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 600:0:124:262557:2022-05-11 08:49:58.565361738 -0400:2022-05-11 08:49:59.565361738 -0400:/var/crash/libssl3:amd64.0.crash Date: Wed May 11 08:49:59 2022 DpkgTerminalLog: dpkg: error processing package libssl3:amd64 (--configure): package libssl3:amd64 is already installed and configured ErrorMessage: package libssl3:amd64 is already installed and configured InstallationDate: Installed on 2022-05-02 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: dpkg Title: package libssl3:amd64 3.0.2-0ubuntu1.1 failed to install/upgrade: package libssl3:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972994 Title: package libssl3:amd64 3.0.2-0ubuntu1.1 failed to install/upgrade: package libssl3:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1972994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912190] Re: k4dirstat overriding default file manager in Firefox
k4dirstat declare it self has being able to open folders (this is in usr/share/applications/k4dirstat.desktop). There is no way to specify a MIME priority in a .desktop file. Users are expected to configure this priority them self. To do so edit/create $HOME/.config/mimeapps.list (user specific) or /etc/xdg/mimeapps.list (system wide) and add: [Default Applications] inode/directory=thunar.desktop <-- enter your prefered file manager here xfce4-mime-settings provide a GUI for that. I guess that KDE and Gnome have similar tools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912190 Title: k4dirstat overriding default file manager in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k4dirstat/+bug/1912190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970925] Re: K4dirstat installer registers incorrect inode/directory MIME type
> When K4Dirstat is installed, it adds following row to /etc/mailcap: No. k4dirstat just add /usr/share/applications/k4dirstat.desktop. An other package (maybe mailcap or mime-support) hook the installation process to regenerate /etc/mailcap. /etc/mailcap is a generated file so you'll have to redo this change every time you install a package. There is no way to specify a MIME priority in a .desktop file. Users are expected to configure this priority them self. To do so edit/create $HOME/.config/mimeapps.list (user specific) or /etc/xdg/mimeapps.list (system wide) and add: [Default Applications] inode/directory=thunar.desktop xfce4-mime-settings provide a GUI for that. I guess that KDE and Gnome have similar tools. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970925 Title: K4dirstat installer registers incorrect inode/directory MIME type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k4dirstat/+bug/1970925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972020] [NEW] Chromium splashscreen "ad" in Ubuntu Software shows "Sync with Google"
Public bug reported: Chromium hasn't had the ability to sync with Google since 2021-03-10. The ad / JPG that appears in Ubuntu Software shows "Take Chromium Everywhere", but that doesn't work any longer. Version: Ubuntu 22.04, loading from the Snap Store ** Affects: chromium (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2022-05-06 14-41-08.png" https://bugs.launchpad.net/bugs/1972020/+attachment/5587448/+files/Screenshot%20from%202022-05-06%2014-41-08.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972020 Title: Chromium splashscreen "ad" in Ubuntu Software shows "Sync with Google" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium/+bug/1972020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971162] [NEW] package libstdc++5 1:3.3.6-30ubuntu2 [modified: usr/share/doc/libstdc++5/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libstdc++5/chang
Public bug reported: Could not remove Boxes from my computer (Boxes does not work because my computer does not support visualization) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libstdc++5 1:3.3.6-30ubuntu2 [modified: usr/share/doc/libstdc++5/changelog.Debian.gz] ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 1 17:50:56 2022 DuplicateSignature: package:libstdc++5:1:3.3.6-30ubuntu2 [modified: usr/share/doc/libstdc++5/changelog.Debian.gz] Unpacking libstdc++5:i386 (1:3.3.6-30ubuntu2) over (1:3.3.6-30) ... dpkg: error processing archive /var/cache/apt/archives/libstdc++5_1%3a3.3.6-30ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libstdc++5/changelog.Debian.gz', which is different from other instances of package libstdc++5:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libstdc++5/changelog.Debian.gz', which is different from other instances of package libstdc++5:i386 InstallationDate: Installed on 2022-04-20 (11 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: gcc-3.3 Title: package libstdc++5 1:3.3.6-30ubuntu2 [modified: usr/share/doc/libstdc++5/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libstdc++5/changelog.Debian.gz', which is different from other instances of package libstdc++5:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gcc-3.3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971162 Title: package libstdc++5 1:3.3.6-30ubuntu2 [modified: usr/share/doc/libstdc++5/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libstdc++5/changelog.Debian.gz', which is different from other instances of package libstdc++5:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-3.3/+bug/1971162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964975] Re: can we update to 1.8.0 for Ubuntu 22.04
When using tpm2-pkcs11, in the current Ubuntu version 1.7.0, creating of
certificate signing requests (CSR) will not work correctly anymore which
renders tpm2-pkcs11 partially useless. Specially enviroments where a TLS
network (IEEE 802.1X) connection (over NetworkManager) or OpenConnect
VPN is required tpm2-pkcs11 will not work with the current 1.7.0
version.
This is because of the shift to openssl3. Openssl is required to create
the certificate signing requests while the method in tpm2-pkcs11 1.7.0
is using the deprecated "-engine" api, while openssl3 requires
"-provider" to be used.
The old openssl1 command for 1.7.0:
openssl req \
-new \
-engine pkcs11 \
-keyform engine \
-key
"pkcs11:token=$TOKEN_LABEL;object=$KEY_LABEL;type=private;pin-value=$USER_PIN" \
-subj "${SUBJ}" \
-out "$HOSTNAME".csr
The new openssl3 command for 1.8.0 (extracted, and tested as well, from
tpm2-pkcs11 integration tests, because of lack of updated documentation):
yaml_rsa0=$(tpm2_ptool export --label="${TOKEN_LABEL}"
--key-label="${KEY_LABEL}" --userpin="${USER_PIN}")
auth_rsa0=$(echo "$yaml_rsa0" | grep "object-auth" | cut -d' ' -f2-)
openssl req \
-new \
-provider tpm2 \
-provider base \
-key "${KEY_LABEL}".pem \ # created by the tpm2_ptool export above
-passin "pass:$auth_rsa0" \
-subj "${SUBJ}" \
-out "$HOSTNAME".csr
Be aware that tpm2-openssl now a dependency for creating CSR's and
tpm2-pytss is a dependency of tpm2-pkcs11.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964975
Title:
can we update to 1.8.0 for Ubuntu 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tpm2-pkcs11/+bug/1964975/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969303] Re: "No package to remove" error when attempting to uninstall
The snap-store beta channel currently contains the change and that will roll out to the stable channel soon (assuming no issues found). The fix will go into Debian for gnome-software (we are in sync with Debian for this), and that will be copied over to Ubuntu 22.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966849] Re: gzip exec format error under WSL1
Chiming in that it'd be great if this (gzip-1.10-4ubuntu4) continued to work in WSL1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966849 Title: gzip exec format error under WSL1 To manage notifications about this bug go to: https://bugs.launchpad.net/gzip/+bug/1966849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969303] Re: "No package to remove" error when attempting to uninstall
Pushed this change into the snap-store and snap-store-41 branches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969303] Re: "No package to remove" error when attempting to uninstall
** Changed in: snap-store-desktop Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: snap-store-desktop Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969303] Re: "No package to remove" error when attempting to uninstall
Fix is in https://gitlab.gnome.org/GNOME/gnome- software/-/merge_requests/1333 ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Critical ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) ** Changed in: snap-store-desktop Importance: Undecided => Critical ** Changed in: gnome-software (Ubuntu) Status: Confirmed => Triaged ** Changed in: snap-store-desktop Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970595] Re: The server installer double or triple fetches source ISO file
** Description changed:
- Hello,
+ Hello, hello,
I'm not sure if this is bug or expected behavior but here we go.
I was doing server reinstall from already installed linux OS via grub
bootstraping (to continue installation via SSH due to lacking access to
the server's physical console). I noticed that ISO file pointed by url
bootoption is fetched three times by Ubuntu installer. I did some
checking and this is my observation.
- ISO file: ubuntu-22.04-live-server-amd64.iso
+ ISO file: ubuntu-22.04-live-server-amd64.iso
(SHA256: 84aeaf7823c8c61baa0ae862d0a06b0340939480b3235854a6b38eb4856f)
IP used:
100.64.241.175 / local-install.vm - http server providing ISO and
{meta,user}-data files
100.64.100.100 - static IP for reinstalled server
100.64.0.1 - default gw
100.64.255.255 - DNS resolver
I tested two cases. One with DNS support and second one without DNS
resolver in place.
My grub.cfg looks like that:
menuentry 'Install with DNS support' {
- load_video
- gfxmode text
- insmod gzio
- insmod part_msdos
- insmod part_gpt
- insmod lvm
- insmod diskfilter
- insmod mdraid1x
- insmod ext2
- insmod xfs
- search --no-floppy --fs-uuid --set=root 2559c296-413a-4f82-9882-de741aca022f
- linux /boot/reinstall/vmlinuz root=/dev/ram0 ramdisk_size=150
ip=100.64.100.100::100.64.0.1:255.255.0.0::enp1s0:static:100.64.255.254
url=http://local-install.vm/ubuntu-22.04-live-server-amd64.iso
ds="nocloud-net;s=http://local-install.vm/;
- initrd /boot/reinstall/initrd
+ load_video
+ gfxmode text
+ insmod gzio
+ insmod part_msdos
+ insmod part_gpt
+ insmod lvm
+ insmod diskfilter
+ insmod mdraid1x
+ insmod ext2
+ insmod xfs
+ search --no-floppy --fs-uuid --set=root 2559c296-413a-4f82-9882-de741aca022f
+ linux /boot/reinstall/vmlinuz root=/dev/ram0 ramdisk_size=150
ip=100.64.100.100::100.64.0.1:255.255.0.0::enp1s0:static:100.64.255.254
url=http://local-install.vm/ubuntu-22.04-live-server-amd64.iso
ds="nocloud-net;s=http://local-install.vm/;
+ initrd /boot/reinstall/initrd
}
menuentry 'Install without DNS support' {
- load_video
- gfxmode text
- insmod gzio
- insmod part_msdos
- insmod part_gpt
- insmod lvm
- insmod diskfilter
- insmod mdraid1x
- insmod ext2
- insmod xfs
- search --no-floppy --fs-uuid --set=root 2559c296-413a-4f82-9882-de741aca022f
- linux /boot/reinstall/vmlinuz root=/dev/ram0 ramdisk_size=150
ip=100.64.100.100::100.64.0.1:255.255.0.0::enp1s0:static
url=http://100.64.241.175/ubuntu-22.04-live-server-amd64.iso
ds="nocloud-net;s=http://100.64.241.175/;
- initrd /boot/reinstall/initrd
+ load_video
+ gfxmode text
+ insmod gzio
+ insmod part_msdos
+ insmod part_gpt
+ insmod lvm
+ insmod diskfilter
+ insmod mdraid1x
+ insmod ext2
+ insmod xfs
+ search --no-floppy --fs-uuid --set=root 2559c296-413a-4f82-9882-de741aca022f
+ linux /boot/reinstall/vmlinuz root=/dev/ram0 ramdisk_size=150
ip=100.64.100.100::100.64.0.1:255.255.0.0::enp1s0:static
url=http://100.64.241.175/ubuntu-22.04-live-server-amd64.iso
ds="nocloud-net;s=http://100.64.241.175/;
+ initrd /boot/reinstall/initrd
}
user-data file:
#cloud-config
chpasswd:
- expire: false
- list:
- - installer:ubuntu-installer-22.04
+ expire: false
+ list:
+ - installer:ubuntu-installer-22.04
meta-data is empty.
When running from 'Install with DNS support' http server logs shows:
local-install.vm 100.64.100.100 - - [27/Apr/2022:11:09:10 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-" "Wget"
local-install.vm 100.64.100.100 - - [27/Apr/2022:11:09:18 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-"
"Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
local-install.vm 100.64.100.100 - - [27/Apr/2022:11:09:18 +0200] "GET
/meta-data HTTP/1.1" 200 0 "-" "Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
local-install.vm 100.64.100.100 - - [27/Apr/2022:11:09:19 +0200] "GET
/user-data HTTP/1.1" 200 87 "-" "Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
ubuntu-22.04-live-server-amd64.iso is fetched twice. Once by wget
(casper phase?) and secound one by cloud-init.
-
- But when running from 'Install without DNS support' I got this in the logs:
+ But when running from 'Install without DNS support' I got this in the
+ logs:
100.64.241.175 100.64.100.100 - - [27/Apr/2022:11:13:26 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-" "Wget"
100.64.241.175 100.64.100.100 - - [27/Apr/2022:11:13:33 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-"
"Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
100.64.241.175 100.64.100.100 - - [27/Apr/2022:11:13:36 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-"
"Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
100.64.241.175 100.64.100.100 - -
[Bug 1970599] [NEW] casper manual page improvement -> casper(7)
Public bug reported: Hello, hello, CASPER(7) manual page for ip options states: ip=IFACE,ADDRESS,NETMASK,GATEWAY[:IFACE,ADDRESS,NETMASK,GATEWAY]* Let you specify the name(s) and the options of the interface(s) that should be configured at boot time. Do not specify this if you want to use dhcp (default). But this syntax is not supported by Ubuntu Installer (I did not test this for generated live medium - sorry) What is supported for ip option (from klibc-2.0.10/usr/kinit/ipconfig/README.ipconfig) ::... For example for static IP config: ip=100.64.100.100::100.64.0.1:255.255.0.0::enp1s0:static:100.64.255.254 Best regards ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, CASPER(7) manual page for ip options states: ip=IFACE,ADDRESS,NETMASK,GATEWAY[:IFACE,ADDRESS,NETMASK,GATEWAY]* - Let you specify the name(s) and the options of the interface(s) that should be configured at boot time. Do not specify this if you - want to use dhcp (default). + Let you specify the name(s) and the options of the interface(s) that should be configured at boot time. Do not specify this if you + want to use dhcp (default). But this syntax is not supported by Ubuntu Installer (I did not test this for generated live medium - sorry) What is supported for ip option (from klibc-2.0.10/usr/kinit/ipconfig/README.ipconfig) ::... Best regards ** Description changed: Hello, CASPER(7) manual page for ip options states: ip=IFACE,ADDRESS,NETMASK,GATEWAY[:IFACE,ADDRESS,NETMASK,GATEWAY]* Let you specify the name(s) and the options of the interface(s) that should be configured at boot time. Do not specify this if you want to use dhcp (default). But this syntax is not supported by Ubuntu Installer (I did not test this for generated live medium - sorry) What is supported for ip option (from klibc-2.0.10/usr/kinit/ipconfig/README.ipconfig) ::... + For example for static IP config: + + ip=100.64.100.100::100.64.0.1:255.255.0.0::enp1s0:static:100.64.255.254 + Best regards ** Description changed: - Hello, + Hello, hello, CASPER(7) manual page for ip options states: ip=IFACE,ADDRESS,NETMASK,GATEWAY[:IFACE,ADDRESS,NETMASK,GATEWAY]* Let you specify the name(s) and the options of the interface(s) that should be configured at boot time. Do not specify this if you want to use dhcp (default). But this syntax is not supported by Ubuntu Installer (I did not test this for generated live medium - sorry) What is supported for ip option (from klibc-2.0.10/usr/kinit/ipconfig/README.ipconfig) ::... For example for static IP config: ip=100.64.100.100::100.64.0.1:255.255.0.0::enp1s0:static:100.64.255.254 Best regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970599 Title: casper manual page improvement -> casper(7) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1970599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970595] [NEW] The server installer double or triple fetches source ISO file
Public bug reported:
Hello,
I'm not sure if this is bug or expected behavior but here we go.
I was doing server reinstall from already installed linux OS via grub
bootstraping (to continue installation via SSH due to lacking access to
the server's physical console). I noticed that ISO file pointed by url
bootoption is fetched three times by Ubuntu installer. I did some
checking and this is my observation.
ISO file: ubuntu-22.04-live-server-amd64.iso
(SHA256: 84aeaf7823c8c61baa0ae862d0a06b0340939480b3235854a6b38eb4856f)
IP used:
100.64.241.175 / local-install.vm - http server providing ISO and
{meta,user}-data files
100.64.100.100 - static IP for reinstalled server
100.64.0.1 - default gw
100.64.255.255 - DNS resolver
I tested two cases. One with DNS support and second one without DNS
resolver in place.
My grub.cfg looks like that:
menuentry 'Install with DNS support' {
load_video
gfxmode text
insmod gzio
insmod part_msdos
insmod part_gpt
insmod lvm
insmod diskfilter
insmod mdraid1x
insmod ext2
insmod xfs
search --no-floppy --fs-uuid --set=root 2559c296-413a-4f82-9882-de741aca022f
linux /boot/reinstall/vmlinuz root=/dev/ram0 ramdisk_size=150
ip=100.64.100.100::100.64.0.1:255.255.0.0::enp1s0:static:100.64.255.254
url=http://local-install.vm/ubuntu-22.04-live-server-amd64.iso
ds="nocloud-net;s=http://local-install.vm/;
initrd /boot/reinstall/initrd
}
menuentry 'Install without DNS support' {
load_video
gfxmode text
insmod gzio
insmod part_msdos
insmod part_gpt
insmod lvm
insmod diskfilter
insmod mdraid1x
insmod ext2
insmod xfs
search --no-floppy --fs-uuid --set=root 2559c296-413a-4f82-9882-de741aca022f
linux /boot/reinstall/vmlinuz root=/dev/ram0 ramdisk_size=150
ip=100.64.100.100::100.64.0.1:255.255.0.0::enp1s0:static
url=http://100.64.241.175/ubuntu-22.04-live-server-amd64.iso
ds="nocloud-net;s=http://100.64.241.175/;
initrd /boot/reinstall/initrd
}
user-data file:
#cloud-config
chpasswd:
expire: false
list:
- installer:ubuntu-installer-22.04
meta-data is empty.
When running from 'Install with DNS support' http server logs shows:
local-install.vm 100.64.100.100 - - [27/Apr/2022:11:09:10 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-" "Wget"
local-install.vm 100.64.100.100 - - [27/Apr/2022:11:09:18 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-"
"Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
local-install.vm 100.64.100.100 - - [27/Apr/2022:11:09:18 +0200] "GET
/meta-data HTTP/1.1" 200 0 "-" "Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
local-install.vm 100.64.100.100 - - [27/Apr/2022:11:09:19 +0200] "GET
/user-data HTTP/1.1" 200 87 "-" "Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
ubuntu-22.04-live-server-amd64.iso is fetched twice. Once by wget
(casper phase?) and secound one by cloud-init.
But when running from 'Install without DNS support' I got this in the logs:
100.64.241.175 100.64.100.100 - - [27/Apr/2022:11:13:26 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-" "Wget"
100.64.241.175 100.64.100.100 - - [27/Apr/2022:11:13:33 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-"
"Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
100.64.241.175 100.64.100.100 - - [27/Apr/2022:11:13:36 +0200] "GET
/ubuntu-22.04-live-server-amd64.iso HTTP/1.1" 200 1466714112 "-"
"Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
100.64.241.175 100.64.100.100 - - [27/Apr/2022:11:13:37 +0200] "GET /meta-data
HTTP/1.1" 200 0 "-" "Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
100.64.241.175 100.64.100.100 - - [27/Apr/2022:11:13:37 +0200] "GET /user-data
HTTP/1.1" 200 87 "-" "Cloud-Init/22.1-14-g2e17a0d6-0ubuntu1~22.04.5"
ubuntu-22.04-live-server-amd64.iso is fetched tree times (once by wget,
and two times by cloud-init).
I additonaly checked this with ubuntu-20.04.3-live-server-amd64.iso
(f8e3086f3cea0fb3fefb29937ab5ed9d19e767079633960ccb50e76153effc98) and
results are the same.
It's not big problem in LAN - but this is slow for insalling from remote
(Internet) location.
Best regards
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970595
Title:
The server installer double or triple fetches source ISO file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1970595/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969303] Re: "No package to remove" error when attempting to uninstall
** Changed in: snap-store-desktop Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969303 Title: "No package to remove" error when attempting to uninstall To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968391] Re: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS
This is affecting me as well after an upgrade to 22.04 (Ubuntu Mate.) Previous install, fully-patched 20.04, was rock solid. Now I am lucky if I get 90seconds of internet access without a disconnection. My whole house runs on wifi -- sadly, no hardwired options. All other computers/phones have no issues with wireless access. wireless adapter: 01:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01) current kernel: Linux robertm-desktop 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Tried the powersave trick with no success. Happy to provide any logs if someone can point me in the right direction. tail -f /var/log/syslog is currently an impressive flood of connect/disconnect, CTRL-EVENT-* messages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968391 Title: Unreliable wifi with loads of CTRL-EVENT-BEACON-LOSS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1968391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969633] Re: Continuous Bluetooth timeouts [Broadcom BCM20702A]
So how do I get Canonical to fix the kernel bug? How do I notify them of the bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Continuous Bluetooth timeouts [Broadcom BCM20702A] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1969633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969633] [NEW] Bluetooth not connecting
Public bug reported: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Bluetooth not connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1969633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969310] [NEW] Grub Update Issue on Fresh Install of 20.04 LTS
Public bug reported: Grub Update Issue on Fresh Install of 20.04 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.17 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 17 14:09:17 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969310 Title: Grub Update Issue on Fresh Install of 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1969310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969190] Re: package libpython3.10-minimal 3.10.4-1+focal1 failed to install/upgrade: trying to overwrite '/usr/lib/python3.10/typing', which is also in package libpython3.10-stdlib:amd64 3.10.4-
I got a similar error while running an update: Preparing to unpack .../libpython3.10-stdlib_3.10.4-3~20.04.sav0_amd64.deb ... Unpacking libpython3.10-stdlib:amd64 (3.10.4-3~20.04.sav0) over (3.10.4-1+focal1) ... dpkg: error processing archive /var/cache/apt/archives/libpython3.10-stdlib_3.10.4-3~20.04.sav0_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3.10/_sysconfigdata__linux_x86_64-linux-gnu.py', which is also in package libpython3.10-minimal:amd64 3.10.4-1+focal1 Preparing to unpack .../libpython3.10-minimal_3.10.4-3~20.04.sav0_amd64.deb ... Unpacking libpython3.10-minimal:amd64 (3.10.4-3~20.04.sav0) over (3.10.4-1+focal1) ... dpkg: error processing archive /var/cache/apt/archives/libpython3.10-minimal_3.10.4-3~20.04.sav0_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3.10/typing.py', which is also in package libpython3.10-stdlib:amd64 3.10.4-1+focal1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libpython3.10-stdlib_3.10.4-3~20.04.sav0_amd64.deb /var/cache/apt/archives/libpython3.10-minimal_3.10.4-3~20.04.sav0_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) this while doing a sudo apt update && sudo apt upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969190 Title: package libpython3.10-minimal 3.10.4-1+focal1 failed to install/upgrade: trying to overwrite '/usr/lib/python3.10/typing', which is also in package libpython3.10-stdlib:amd64 3.10.4-1+focal3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1969190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
Uploaded as 1:41.4-1ubuntu11 ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: FFe: Backport new RDP settings
Łukasz - PPA here https://launchpad.net/~robert- ancell/+archive/ubuntu/gnome-control-center -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: Backport new RDP settings
Proposed changes are in https://salsa.debian.org/gnome-team/gnome- control-center/-/tree/ubuntu/sharing-rdp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: Backport new RDP settings
Freeze exception emails: https://lists.ubuntu.com/archives/ubuntu-doc/2022-April/020825.html https://lists.ubuntu.com/archives/ubuntu-translators/2022-April/007830.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: Backport new RDP settings
** Attachment added: "Backported sharing panel" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+attachment/5579134/+files/Screenshot%20from%202022-04-11%2016-06-52.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: Backport new RDP settings
** Attachment added: "Backported sharing dialog" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+attachment/5579135/+files/Screenshot%20from%202022-04-11%2016-06-56.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: Backport new RDP settings
** Attachment added: "Current sharing dialog in jammy" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+attachment/5579133/+files/Screenshot%20from%202022-04-11%2016-01-10.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] Re: Backport new RDP settings
** Attachment added: "Current sharing panel in jammy" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+attachment/5579132/+files/Screenshot%20from%202022-04-11%2016-01-00.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968518 Title: FFe: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968518] [NEW] Backport new RDP settings
Public bug reported: We are shipping some GNOME 41 and some GNOME 42 components in jammy. In GNOME 42 the remote desktop support moved from VNC to RDP. We have the updated gnome-remote-desktop in jammy, but not the settings changes in gnome-control-center 41. The proposal is to backport these settings. ** Affects: gnome-control-center (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/1968518 Title: Backport new RDP settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1968518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802821] Re: Serious design flaw using large external drives.
I read that Paragon Software NTFS drivers will be part of the 3.5 kernel. I would like to use NTFS so that other computers can actually read my data. The current drives I'm using are 8 TB Seagate external drives with a 2 year warranty. Their price went up to $150 when on sale. I will probably get a Seagate Exos x18 18 TB drive for 2 times the cost and 2.25 times the capacity and 2.5 times the warranty period. (Also greater MTBF and annual data usage.) It would be nice if Ubuntu could access an 18 TB drive with an NTFS at greater than continental drift speeds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802821 Title: Serious design flaw using large external drives. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
