[Bug 1977642] Re: mailfromd.service: State 'stop-sigterm' timed out. Killing.
> To say the truth, I fear that I simply missed a > Type=forking > in the mailfromd.service. I did not even try this ;-) But please check also https://bugs.launchpad.net/ubuntu/+source/mailfromd/+bug/1977641 mailfromd does not work. There seems to be a problem with the symbols. mu_stream_getline and other functions have become inline and moved into header files. But mailfromd was not compiled against these new headers, so it still believes they are in the libs. Resulting in undefined symbol: mu_stream_getline -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977642 Title: mailfromd.service: State 'stop-sigterm' timed out. Killing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailfromd/+bug/1977642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841666] Re: mate-menu.py crashed with AttributeError in onMotion(): 'MenuApplicationLauncher' object has no attribute 'mouse_entered'
[Expired for mate-menu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-menu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841666 Title: mate-menu.py crashed with AttributeError in onMotion(): 'MenuApplicationLauncher' object has no attribute 'mouse_entered' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-menu/+bug/1841666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872340] Re: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()
[Expired for brisk-menu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: brisk-menu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872340 Title: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1872340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874002] Re: brisk menu crash
[Expired for brisk-menu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: brisk-menu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874002 Title: brisk menu crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1874002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895462] Re: ayatana-indicator-sound-WARNING **: 16:02:42.061: volume-control-pulse.vala:745: Unable to connect to dbus server at 'unix:path=/run/user/999/pulse/dbus-socket': Could not connect: N
[Expired for ayatana-indicator-sound (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ayatana-indicator-sound (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895462 Title: ayatana-indicator-sound-WARNING **: 16:02:42.061: volume-control- pulse.vala:745: Unable to connect to dbus server at 'unix:path=/run/user/999/pulse/dbus-socket': Could not connect: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-sound/+bug/1895462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961750] Re: ubuntu mate focal.4 adjusting display config causes part of screen to become unusable
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961750 Title: ubuntu mate focal.4 adjusting display config causes part of screen to become unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977491] Re: Update Samba in 22.04LTS to 4.15.7 so macOS clients can connect and transfer.
** Summary changed: - Update Samba in 22.04LTS to 4.15.7 + Update Samba in 22.04LTS to 4.15.7 so macOS clients can connect and transfer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977491 Title: Update Samba in 22.04LTS to 4.15.7 so macOS clients can connect and transfer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1977491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969326] Re: Enable hotspot feature for Realtek 8821CE
** 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/1969326 Title: Enable hotspot feature for Realtek 8821CE To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1969326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977669] [NEW] Metadata broken for SR-IOV external ports
Public bug reported: OpenStack Usurri/OVN SR-IOV instances are unable to connect to the metadata service despite DHCP and normal traffic work. The 169.254.169.254 metadata route is directed at the DHCP port IP, and no arp reply is received by the VM for this IP. Diagnosis finds that the ARP reply returns from the ovnmeta namespace on the chassis hosting the external port but is dropped inside OVS. 20.03.2-0ubuntu0.20.04.2 backported the following patch: Do not forward traffic from localport to localnet ports (LP: #1943266) (d/p/lp-1943266-physical-do-not-forward-traffic-from-localport-to-a-.patch) This patch broke metadata for SR-IOV external prots and was fixed in 1148580290d0ace803f20aeaa0241dd51c100630 "Don't suppress localport traffic directed to external port": https://github.com/ovn-org/ovn/commit/1148580290d0ace803f20aeaa0241dd51c100630 ** Affects: ovn (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/1977669 Title: Metadata broken for SR-IOV external ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/1977669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976110] Re: `tmux -d -x ... -y ...` does not respect sizing
This bug was fixed in the package tmux - 3.3-2 --- tmux (3.3-2) unstable; urgency=medium * Cherry-pick fixes from upstream Git: + 0f6227f46b: don't silently delete or rename the most recent buffer + 18838fbc87: fix crash when using `run-shell' in config file + 3edda3c5e7: do not unintentionally turn off all mouse mode * Remove obsolete field Name from debian/upstream/metadata. * Upload to unstable. -- Romain Francoise Sat, 04 Jun 2022 17:08:29 +0200 ** Changed in: tmux (Ubuntu) Status: Triaged => 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/1976110 Title: `tmux -d -x ... -y ...` does not respect sizing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1976110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862764] Re: add-apt-repository should use signed-by
I started using Ubuntu 22.04 and this issue started to occour. The 'add-apt-repository' command adds the gpg key of the PPA repository in the trusted.gpg file (/etc/apt/trusted.gpg) As commented above, the PPA repositories are not being included in the sources.list file (/etc/apt/sources.list) or in the directory /etc/apt/sources.list.d/ with the parameter [signed-by=] Workaround: While the fix doesn't come, the way is to adapt the repository in this way: 1- $ sudo add-apt-repository ppa:author/project 2- $ apt-key list 3- $ gpg --export | sudo tee /etc/apt/trusted.gpg.d/.gpg 4- $ sudo nano /etc/apt/sources.list.d/repository-name.list 5- Find & Replace: deb http://ppa.launchpad.net/author/project/ubuntu jammy main by deb [signed-by=/etc/apt/trusted.gpg.d/.gpg http://ppa.launchpad.net/author/project/ubuntu jammy main 6- Save the changes and run 'sudo apt update' again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use signed-by To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847582] Re: checkinstall leaves root filesystem unusable if interrupted
Thank you @hjwp2! Your fix is so much faster than reinstalling 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/1847582 Title: checkinstall leaves root filesystem unusable if interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/1847582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214]
The fix commit included a testcase. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974214 Title: Segfaults on verify callout, in _gnutls_trust_list_get_issuer To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/1974214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977667] Re: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1
Unfortunately I think the log is gone now because I "completed" the installation, made sure all packages completed installation with `sudo dpkg --configure -a` and then rebooted. So what we've got above is all we've got. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977667 Title: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977667] Re: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1
"failed to install/upgrade" also means that a package failed to configure. If as Simon says the packages were left unconfigured, then that means the package is "Installed but failed to restart on upgrade" which is an action the postinst scripts execute. So it may not be an 'installer' failure but the configuration failure which led to a false 'installer failed' situation because postinst is configured to reload/restart the NGINX processes on an upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977667 Title: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977667] Re: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1
@kip, it should in theory not have crashed the installer. Only the nginx(-*) package(s) should be left unconfigured. You can check that with "dpkg -l | grep -v ^ii", it should show you which packages need attention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977667 Title: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977667] Re: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1
Not quite. It's true that the certificates nginx was looking for weren't present, but that should not have crashed the installer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977667 Title: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947115] Re: VAAPI / HW-acceleration not working Snap-packaged Firefox
Hey there, I am facing the same issue. However, for me if I use MOZ_DISABLE_RDD_SANDBOX=1 firefox, it works as expected. Is there a way to use it while not disabling the sandbox? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947115 Title: VAAPI / HW-acceleration not working Snap-packaged Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977667] Re: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1
Looks like during your upgrade a certificate went awry, but this isn't an NGINX issue, it's the maintenance of your system on your end. From the journalctl data: Jun 04 14:21:05 heliopolis-aws nginx[44002]: nginx: [emerg] cannot load certificate "/etc/ssl/certs/heliosd.crt": BIO_new_file() failed (SSL: error:8002:system library::No such file or directory:calling fopen(/etc/ssl/certs/heliosd.crt, r) error:1080:BIO routines::no such file) Jun 04 14:21:05 heliopolis-aws nginx[44002]: nginx: configuration file /etc/nginx/nginx.conf test failed The required certificate file is missing and can't be found. ** Changed in: nginx (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977667 Title: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970674] Re: New bug fix releases 3.4.11, 4.2.7 and 4.4.2
The tests did not finish in 24 minutes and one test (sub2video) is taking 15 minutes. I will retest on 18.04 now and publish results tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970674 Title: New bug fix releases 3.4.11, 4.2.7 and 4.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977667] [NEW] package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1
Public bug reported: I was upgrading from Impish to Jammy when this occurred. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nginx-core 1.18.0-6ubuntu14.1 ProcVersionSignature: Ubuntu 5.13.0-1026.28-aws 5.13.19 Uname: Linux 5.13.0-1026-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jun 4 14:21:05 2022 Ec2AMI: ami-001c0c48bd293d6cd Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ca-central-1b Ec2InstanceType: c6i.metal Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: installed nginx-core package post-installation script subprocess returned error exit status 1 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.1 apt 2.4.5 SourcePackage: nginx Title: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-06-04 (0 days ago) ** Affects: nginx (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977667 Title: package nginx-core 1.18.0-6ubuntu14.1 failed to install/upgrade: installed nginx-core package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977666] [NEW] gnome-shell crash when a monitor is connected
Public bug reported: Hi, I have just installed Ubuntu 22.04, and I have found a bug when I connect an external monitor to my laptop. Gnome-shell crash, and it seems to be linked with Wayland, the problem doesn't appear with Xorg. Here is my syslog when the crash occurs : Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failed Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: GNOME Shell crashed with signal 11 Jun 4 23:23:02 Ubuntu-Principal gnome-shell[29275]: == Stack trace for context 0x562d4c9ca4b0 == Jun 4 23:23:04 Ubuntu-Principal psensor[31395]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal xdg-desktop-por[29992]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal evolution-alarm[29692]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal xdg-desktop-por[30039]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-media-keys[29633]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-wacom[29665]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-keyboard[29631]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal gsd-power[29638]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal nautilus[29574]: Error reading events from display: Connexion ré-initialisée par le correspondant Jun 4 23:23:04 Ubuntu-Principal xpad[29711]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal update-notifier[31948]: Error reading events from display: Relais brisé (pipe) Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal gnome-shell[29781]: (EE) failed to write to Xwayland fd: Broken pipe Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.Shell@wayland.service: Main process exited, code=dumped, status=11/SEGV Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'. Jun 4 23:23:04 Ubuntu-Principal systemd[26548]: org.gnome.SettingsDaemon.Wacom.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 23:31:50 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-06 (363 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-04 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977666 Title: gnome-shell crash when a monitor is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970056] Re: Ubuntu 22.04 unable to mount root partition
After testing kernel 5.18.0 from mainline, the issue does appear resolved -- the system will boot with "pci=nocrs" and the touchpad, touchscreen function. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970056 Title: Ubuntu 22.04 unable to mount root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977665] [NEW] The launcher is a symlink that points to the wrong file
Public bug reported: The launcher '/usr/share/applications/guake.desktop' points to '/usr/share/guake/DATA/autostart-guake.desktop'* while it should point to '/usr/share/guake/autostart-guake.desktop' *Capital letters on purpose. user@host:~$ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 user@host:~$ apt-cache policy guake guake: Instalados: 3.8.5-1 Candidato: 3.8.5-1 Tabla de versión: *** 3.8.5-1 500 500 http://es.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu jammy/universe i386 Packages 100 /var/lib/dpkg/status ** Affects: guake (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/1977665 Title: The launcher is a symlink that points to the wrong file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/guake/+bug/1977665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970674] Re: New bug fix releases 3.4.11, 4.2.7 and 4.4.2
The test failed on 18.04 due to an integrity issue when receiving the input file for the failed test. I will re-run the test suite now, but with the following commands (I only added the -k option to the last command): $ debuild -us -uc $ export LD_LIBRARY_PATH="libavcodec:libavdevice:libavfilter:libavformat:libavresample:libavutil:libpostproc:libswresample:libswscale" $ cd debian/standard $ make -j1 fate-rsync SAMPLES=fate-suite/ $ make -k -j1 fate SAMPLES=fate-suite/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970674 Title: New bug fix releases 3.4.11, 4.2.7 and 4.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1970674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977663] [NEW] Remote Control under Remote Desktop sharing option only works for VNC
Public bug reported: Toggling "Remote Control" doesn't apply the value to the RDP service ** Affects: gnome-control-center (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) 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/1977663 Title: Remote Control under Remote Desktop sharing option only works for VNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1977663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710373] Re: Desktop shortcut missing for Vino GUI in Ubuntu 17.10
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710373 Title: Desktop shortcut missing for Vino GUI in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1710373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964709] Re: 1.24.0-1ubuntu1 FTBFS: PHP 8.1 and libicu changes
** Changed in: php-symfony-polyfill (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964709 Title: 1.24.0-1ubuntu1 FTBFS: PHP 8.1 and libicu changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-symfony-polyfill/+bug/1964709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976627] Re: New upstream
** Changed in: timeshift (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976627 Title: New upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timeshift/+bug/1976627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
** Description changed: My network has both DHCPv6 and SLAAC for IPv6. From both a privacy perspective and readability reasons, DHCPv6 should *always* be preferred over SLAAC addresses when available. NetworkManager has always been able to adhere to that by simply setting - ip6.privacy=0 for the connection. + ip6.privacy=0 for the connection. Then it would not generate temporary + addresses and use the DHCPv6 address as the source for outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 - address would be used to connect to the outside world. + address would be used to connect to the outside world and be echoed + back. Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Setting net.ipv6.conf.all.use_tempaddr=0 and net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has any effect. Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's altogether is the only way to stop NetworkManager from preferring SLAAC over DHCPv6 now. Looking at the changelog of NetworkManager 1.36.6, things regarding IP address order and temporary addresses have been changed in that release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 this was not the case. (The Linux kernel uses the address highest in the list as preferred.) This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. So this update introduces a very breaking change in IPv6 source address selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. /etc/os-release: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy 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=jammy nmcli -v: nmcli tool, version 1.36.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 orders IPv6 addresses incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970957] Re: suspend problem
Tested 5.18.0-051800-generic on my Lenovo Yoga L13 Gen2, after 90 minutes with lid closed, the battery lost 50% of its charge. Checked log, it never entered in suspend mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975621] Re: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off
The problem does not happen frequently : Jun 2 22:01:46 pluton kernel: [3.544530] systemd[1]: Listening on Device-mapper event daemon FIFOs. Jun 2 22:14:51 pluton kernel: [ 790.744064] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Jun 3 00:00:15 pluton kernel: [3.540836] systemd[1]: Listening on Device-mapper event daemon FIFOs. Jun 3 00:03:34 pluton kernel: [ 205.129238] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun Jun 4 01:06:08 pluton kernel: [3.117861] systemd[1]: Listening on Device-mapper event daemon FIFOs. Jun 4 02:22:42 pluton kernel: [ 4008.227038] i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun It happened once yesterday after reboot (kernel upgrade) Then it happened 4000 sec after the reboot And since, it did not happen. Not using the xserver-xorg-video-intel might help... But i'm not sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975621 Title: [Star Labs Lite IV] screen flashes on-off unless PSR is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 orders IPv6 addresses incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975454] Re: Cannot resume after suspend
I got the exact same bug as described in this ticket. Today I upgraded from 20.04.4 to 22.04. Before I never got this bug but first time opening the lid after upgrade I got this and had to reboot the system. Attached is the prevboot.txt as requested in the above comment. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+bug/1975454/+attachment/5594897/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975454 Title: Cannot resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1975454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977660] [NEW] Power settings have no effect and offer nonexisting options
Public bug reported: The "power" area of the settings offer three options: powersave, balanced, and performance. As per cpufreq-info "balanced" is not a valid option. Also changing to any of the two really existing options does not change cpu frequency in a visible way. Maybe there is a connection between this and the bug i reported about the matching indicator: https://bugs.launchpad.net/ubuntu/+source/indicator-cpufreq/+bug/1977659 I *can* actually switch between the values using the studio-controls application. changing values there leads to visible changes in cpufreq- info output and /proc/cpuinfo data shown. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-35.36-lowlatency 5.15.35 Uname: Linux 5.15.0-35-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 20:36:14 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-12 (782 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-28 (36 days ago) ** Affects: gnome-control-center (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/1977660 Title: Power settings have no effect and offer nonexisting options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1977660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977659] Re: indicator neither shows nor sets cpu governer correctly
additional info: I *can* actually switch between the values using the studio-controls application. changing values there leads to visible changes in cpufreq- info output and /proc/cpuinfo data shown. Maybe this is related to or the actual root is in https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1977660 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977659 Title: indicator neither shows nor sets cpu governer correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-cpufreq/+bug/1977659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975642] Re: package firefox 100.0.2+build1-0ubuntu0.21.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess was killed by signal (Killed)
Upgrade succeeded after killing the dialog. Since then I switched to Firefox deb https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt- 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/1975642 Title: package firefox 100.0.2+build1-0ubuntu0.21.10.1 failed to install/upgrade: new firefox package pre-installation script subprocess was killed by signal (Killed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1975642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977659] [NEW] indicator neither shows nor sets cpu governer correctly
Public bug reported: when changing values in the indicator menu between performance/balanced/powersave these values are not reflected when checking the settings with cpufreq-info, or manually looking at /proc/cpuinfo. Furthermore the option "Balanced" that its offering for selection seems not to really exist, as per cpufreq-info. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: indicator-cpufreq 0.2.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-35.36-lowlatency 5.15.35 Uname: Linux 5.15.0-35-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 20:27:35 2022 InstallationDate: Installed on 2020-04-12 (782 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: indicator-cpufreq UpgradeStatus: Upgraded to jammy on 2022-04-28 (36 days ago) ** Affects: indicator-cpufreq (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/1977659 Title: indicator neither shows nor sets cpu governer correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-cpufreq/+bug/1977659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977657] [NEW] install fatal error grub not installed nvme0
Public bug reported: ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Sat Jun 4 14:23:31 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977657 Title: install fatal error grub not installed nvme0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1977657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976622] Re: libisal: FTBFS on big-endian architectures
** Changed in: libisal (Debian) Status: New => Fix Released ** Changed in: libisal (Debian) Importance: Undecided => Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976622 Title: libisal: FTBFS on big-endian architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fastp/+bug/1976622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977656] [NEW] Visual corruption in main window
Public bug reported: There are green and purple blocks in several areas of the main window. Some of them flicker when you move your mouse over the location bar, section dividers, or typeahead input. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pcmanfm 1.3.2-1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Config_pcmanfm_System_ubuntu: Error: [Errno 2] No such file or directory: '/etc/xdg/pcmanfm/ubuntu/pcmanfm.conf' CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 10:33:43 2022 InstallationDate: Installed on 2022-05-01 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pcmanfm Udisks_dump: Error: [Errno 2] No such file or directory: 'udisks' UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcmanfm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Visual corruption in main window" https://bugs.launchpad.net/bugs/1977656/+attachment/5594876/+files/Screenshot%20from%202022-06-04%2010-33-18.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977656 Title: Visual corruption in main window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1977656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it
Can confirm that removing the .service files in /etc/systemd/system/systemd-suspend.service.requires works. The reason this occurred to me is because i switched GPU from nvidia to AMD, and some programs thought I have nvenc (because the library is installed) when i don't, which necessitates the removal of the nvidia- driver packages. This seem like an issue with one of the nvidia package's postrm debian package scripts as opposed to systemd, tho. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933880 Title: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977655] [NEW] Nautilus Open Files and Save File... dialogs keep growing
Public bug reported: In Firefox and Chrome, each time the Open File(s) or Save File... dialog opens, it grows in size. Eventually, it fills the whole screen. See attached screen recording taken from Firefox 101.0 (Mozilla Firefox Snap for Ubuntu canonical-002 - 1.0). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 10:00:40 2022 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true' InstallationDate: Installed on 2022-05-01 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-dropbox 2019.02.14-1ubuntu1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Firefox save file dialog growing" https://bugs.launchpad.net/bugs/1977655/+attachment/5594873/+files/Screencast%20from%2006-04-2022%2010%3A03%3A41%20AM.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977655 Title: Nautilus Open Files and Save File... dialogs keep growing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1977655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977654] [NEW] installation failed
Public bug reported: Installation failed at 1st attempt in Try Ubuntu mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Sat Jun 4 12:45:57 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977654 Title: installation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1977654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
The same is with v5.18 from Mainline Kernel PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955704] Re: systemd/plymouth preventing reboot/shutdown
Hi [~phm2f1alcw69] is this possibly related to #1977652 ? Depends on: - your version of systemd / ubuntu (I don't see any versions in this report) - whether you also saw items looped in the logs (journald -b -1 | tail) Cheers, Walter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955704 Title: systemd/plymouth preventing reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1955704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977649] Re: my system is not showing me 1080p resolution
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977649 Title: my system is not showing me 1080p resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1977649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977642] Re: mailfromd.service: State 'stop-sigterm' timed out. Killing.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mailfromd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977642 Title: mailfromd.service: State 'stop-sigterm' timed out. Killing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailfromd/+bug/1977642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977642] Re: mailfromd.service: State 'stop-sigterm' timed out. Killing.
To say the truth, I fear that I simply missed a Type=forking in the mailfromd.service. I'm just preparing a new version 8.13-2, that fixes this, it will be available in Debian soon (and somewhat later in Ubuntu...). Thanks for finding and reporting this issue! Roland (Debian maintainer of the mailfromd package) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977642 Title: mailfromd.service: State 'stop-sigterm' timed out. Killing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailfromd/+bug/1977642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977652] [NEW] systemd loops trying to start systemd-ask-password-plymouth
Public bug reported: Short story: - after boot - when a systemd service wants a password - systemd-ask-password is invoked - systemd-ask-password-plymouth.path is reached - systemd-ask-password-plymouth.service is started Except: - the conditions for the latter are (apparently) not met End result: - 40.000x "Condition check resulted in Forward Password Requests to Plymouth being skipped." - 1.5 minutes of 100% cpu usage AFFECTED VERSION systemd 249.11-0ubuntu3.1 on Ubuntu/Jammy 22.04 HOW TO REPRODUCE If I leave the `systemd-ask-password-plymouth.path` unmasked/enabled and reboot. OpenVPN (calling systemd-ask-password) will trigger the condition. This causes high CPU usage for 1.5 minutes. It looks like /run/plymouth/pid exists (for the .path file) at first, when that is invoked, but then the resultant target (the .service file) checks again, and finds that it is gone. Manually reproducing: # ls /run/systemd/ask-password ask.5hW6rb sck.79cfe1203518610 # mkdir /run/plymouth/pid # systemctl start systemd-ask-password-plymouth.service systemd-ask-password-plymouth.path # systemctl show --value --property=MainPID systemd-ask-password-plymouth.service 24777 # rmdir /run/plymouth/pid ; kill 24777 Result: systemd going into a loop. Stop the loop with: # systemctl stop systemd-ask-password-plymouth.path ANALYSIS It looks like this: https://github.com/systemd/systemd/issues/21025 which is fixed by: https://github.com/systemd/systemd/pull/21030 Alternative bug reports: https://bugzilla.redhat.com/show_bug.cgi?id=1919538 Systemd's own analysis of the situation: # systemd-analyze critical-chain systemd-ask-password-plymouth.service ... systemd-ask-password-plymouth.service @1min 35.823s └─systemd-ask-password-plymouth.path @593ms └─plymouth-start.service @571ms +21ms └─systemd-udevd.service @450ms +119ms └─systemd-tmpfiles-setup-dev.service @429ms +18ms └─systemd-sysusers.service @382ms +46ms └─systemd-remount-fs.service @353ms +22ms └─systemd-journald.socket @318ms └─system.slice @264ms └─-.slice @264ms --- WORKAROUNDS --- This works as long as you don't need the plymouth-ask-password: # systemctl disable systemd-ask-password-plymouth.path # systemctl mask systemd-ask-password-plymouth.path Could you get the relevant patches from upstream sorted in Jammy? Thanks! Walter Doekes OSSO B.V. ** Affects: systemd (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/1977652 Title: systemd loops trying to start systemd-ask-password-plymouth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973434] Re: massive performance issues since 22.04 upgrade
BTW: also, as I have an nvidia graphics card in that machine, one could think something is wrong with the graphics drivers... But I tried the nvidia drivers as recommended by the driver GUI tool as well as nouveau. It "feels" like the nvidia drivers are even slightly worse. On the Ubuntu live USB sticks, where perfromance is better, nouveau is used, on Poop OS the nividia driver - they seem all work similarly good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973434 Title: massive performance issues since 22.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973434] Re: massive performance issues since 22.04 upgrade
I have an update on this and quite a bit of more information, even though not very clear what it means and how to further go on fully fixing it: After some more usage i realized that the performance is still pretty weak when using my desktop system for slightly more "real" work. I kept getting stutter in Video playback and Web browsers when using web applications with the slightest bit of JavaScript functionality, and a Virtualbox virtual machine. I first suspected gnome-shell to be a culprit and had the impressions things where sligthly better when using LXDE as a desktop environment, but still I never got real good performance. it's a real hard to get a grip on problem, as I dont know how to instantly produce the problem and measure it as with normal bugs. The easiest thing I can do is open a web browser, got to youtube, and open a few videos in new tabs and try to play them, and skip back and forth to different points, and "pretty soon" I get a stuttering in the video, a mouse pointer not moving fluently, switching tabs taking multiple seconds that usually works in an instant, a browser process with multiple 100s of % of CPU and a RRD* process. these are things that work without a problem on a very old Lenovo x1 tablet with a mobile processor, and that i would expect to work equally easy on a pretty new X1 extreme with i9 processor and 32G Ram... I did some more testing ( I cannot call it real debugging as I dont know how to use proper tooling and stuff for these kind of analysis) and checked how other Distributions and other Ubuntu versions perform from USB Live systems and found that not only PopOS, but also Ubuntu 21.10, BUT to my surprise also 22.04 from USB Live system behave much better. So I thought i must have some setting wrong, but I didn't know which, until i tried to turn off Intel Boost because I remembered in Ubuntu Studio it is recommended to be turned off for good audio performance. This helps a lot! But, this is not what is different between 22.04 live - because there, Intel boost is ON and it still behaves good. I tried this with several browsers with always the same result, so it seems to be a generic graphics system/library, or kernel problem. It actually "feels" like some scheduling issue - which was the reason I tried the boost setting. I also tried with a new test user, to make sure it's not a userspace local setting, or any browser plugin. But the same problems with a new, "clean" user. The system I experience all this with has been installed first with 20.10, so it has multiple upgrades - it *could* be there is some other setting from previous software versions thats broken - but I have no idea what setting this could be and how I can search for it. It could also be some old version of some gnome, X11 ( I also tried Xorg as well as wayland, no noticeable difference) or graphics library, and the kernel package is the wrong place for this bug, but I dont know where to start with that then... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973434 Title: massive performance issues since 22.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977651] [NEW] Support for removal of snaps from inside a chroot
Public bug reported: It would be great if support for removal of packages was supported in chroots, like installation is supported through seeds. This is going to prevent us from releasing Ubuntu Web 22.04's Brave edition. We want to remove the Firefox snap from it, but looks like packages can't be removed from a seed.yaml file (to replace it with the Brave snap). This doesn't only affect flavors and remixes like Ubuntu Unity, Ubuntu Web, Ubuntu Cinnamon etc, but also affects people who 1) build ISOs with tools like the Ubuntu Remix Builder (https://gitlab.com/ubuntu-unity/ubuntu-remixes) and @PJSingh5000's Cubic project for their regular setups 2) develop downstream distros which remove snap packages when building inside a chroot 3) build images for their embedded devices using their own builders (not Ubuntu's builder) which build inside a chroot I think this issue is really important and should be re-opened. (seed.yaml is only a temporary workaround for very few usecases) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Description changed: It would be great if support for removal of packages was supported in chroots, like installation is supported through seeds. This is going to prevent us from releasing Ubuntu Web 22.04's Brave edition. We want to remove the Firefox snap from it, but looks like packages can't be removed from a seed.yaml file (to replace it with the - Brave snap). Are there any plans to implement option 2? (basic support - for installation and removal of snap packages inside a chroot, other - operations don't need to be supported for most usecases inside a chroot, - like mounting and running snaps). + Brave snap). This doesn't only affect flavors and remixes like Ubuntu Unity, Ubuntu Web, Ubuntu Cinnamon etc, but also affects people who 1) build ISOs with tools like the Ubuntu Remix Builder (https://gitlab.com/ubuntu-unity/ubuntu-remixes) and @PJSingh5000's Cubic project for their regular setups 2) develop downstream distros which remove snap packages when building inside a chroot 3) build images for their embedded devices using their own builders (not Ubuntu's builder) which build inside a chroot I think this issue is really important and should be re-opened. (seed.yaml is only a temporary workaround for very few usecases) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977651 Title: Support for removal of snaps from inside a chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1977651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976534] Re: /dev/ttyUSB0 doesn't appear for an FTDI on fresh Ubuntu 22.04
** Description changed: Hi all, This problem appeared on a freshly installed Ubuntu 22.04 desktop. When I'm attaching a ftdi device into usb everything looks great but there's no /dev/ttyUSB0 file. Looks like it's created and then disappears immediately. I tried to remove brltty package (as some recommends https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224) but it didn't help. The same ftdi device works on older Ubuntu version w/o any problems. So hardware is ok. I'm having this in syslog: Jun 1 16:58:09 qgs-comp kernel: [ 538.642086] usb 2-1.5: new full-speed USB device number 5 using ehci-pci Jun 1 16:58:10 qgs-comp kernel: [ 538.756437] usb 2-1.5: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 Jun 1 16:58:10 qgs-comp kernel: [ 538.756445] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 1 16:58:10 qgs-comp kernel: [ 538.756448] usb 2-1.5: Product: USB Serial Jun 1 16:58:10 qgs-comp kernel: [ 538.756450] usb 2-1.5: Manufacturer: FTDI Jun 1 16:58:10 qgs-comp kernel: [ 538.756452] usb 2-1.5: SerialNumber: FT0KKBIF Jun 1 16:58:10 qgs-comp kernel: [ 538.759677] ftdi_sio 2-1.5:1.0: FTDI USB Serial Device converter detected Jun 1 16:58:10 qgs-comp kernel: [ 538.759713] usb 2-1.5: Detected FT232RL Jun 1 16:58:10 qgs-comp kernel: [ 538.760546] usb 2-1.5: FTDI USB Serial Device converter now attached to ttyUSB0 Jun 1 16:58:01 qgs-comp colord-sane: message repeated 2 times: [ io/hpmud/musb.c 2101: Invalid usb_open: Permission denied] Jun 1 16:58:10 qgs-comp mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5" Jun 1 16:58:10 qgs-comp mtp-probe: bus: 2, device: 5 was not an MTP device Jun 1 16:58:10 qgs-comp systemd-udevd[5394]: 2-1.5: Failed to create/update device symlink '/dev/ttyUSB0', ignoring: File exists Jun 1 16:58:10 qgs-comp snapd[942]: hotplug.go:199: hotplug device add event ignored, enable experimental.hotplug Jun 1 16:58:10 qgs-comp mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5" Jun 1 16:58:10 qgs-comp mtp-probe: bus: 2, device: 5 was not an MTP device Jun 1 16:58:10 qgs-comp colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied I noticed this line: Jun 1 16:58:10 qgs-comp systemd-udevd[5394]: 2-1.5: Failed to create/update device symlink '/dev/ttyUSB0', ignoring: File exists Why is it happening? There's no /dev/ttyUSB0 neither before nor after I attach ftdi device to a USB port. + + + Let's take a look in /dev/serial folder: + + cd /dev/serial ; ls -LR + + .: + by-id + by-path + + ./by-id: + ls: cannot access './by-id/usb-FTDI_USB_Serial_FT0KKBIF-if00-port0': No such file or directory + usb-FTDI_USB_Serial_FT0KKBIF-if00-port0 + + ./by-path: + ls: cannot access './by-path/pci-:00:1d.0-usb-0:1.5:1.0-port0': No such file or directory + pci-:00:1d.0-usb-0:1.5:1.0-port0 + + So the folders and links are there but there's no /dev/ttyUSB0 file the + links point to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976534 Title: /dev/ttyUSB0 doesn't appear for an FTDI on fresh Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1976534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977650] [NEW] gjs is running always on my system. but it has a icon at the bar. cannot exit from that
Public bug reported: gjs is running always on my system. but it has a icon at the bar. cannot exit from that ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 17:52:11 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-09-05 (272 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-07 (27 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1977650 Title: gjs is running always on my system. but it has a icon at the bar. cannot exit from that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977642] Re: mailfromd.service: State 'stop-sigterm' timed out. Killing.
did use type=exec in unit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977642 Title: mailfromd.service: State 'stop-sigterm' timed out. Killing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailfromd/+bug/1977642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969509] Re: [snap] Unmaximized but not unfullscreened
Launchpad has imported 2 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1772693. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2022-06-04T13:39:24+00:00 vasdi wrote: Created attachment 9279747 firefoxbug.png User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:101.0) Gecko/20100101 Firefox/101.0 Steps to reproduce: Ubuntu 21.10 Gnome 42.1, X11 Firefox from snap, reproducible in Nightly build 20220604092742 With title bar hidden: maximize Firefox window (by double-click on top bar) set it full-screen (by pressing F11 key) move cursor to the upper edge of the screen double-click the bar Actual results: The window ends up in unexpected state. It behaves as fullscreen window but it's not one. Expected results: I expect window to stay maximized. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969509/comments/3 On 2022-06-04T14:17:34+00:00 Release-mgmt-account-bot wrote: The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1969509/comments/4 ** Changed in: firefox Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969509 Title: [snap] Unmaximized but not unfullscreened To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1969509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969509] Re: [snap] Unmaximized but not unfullscreened
** Bug watch added: Mozilla Bugzilla #1772693 https://bugzilla.mozilla.org/show_bug.cgi?id=1772693 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1772693 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969509 Title: [snap] Unmaximized but not unfullscreened To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1969509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977649] [NEW] my system is not showing me 1080p resolution
Public bug reported: After ubuntu 20 install I am not able to increase my screen resolution. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 4 19:16:39 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor Family Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2022-06-04 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Gigabyte Technology Co., Ltd. H81M-S1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-44-generic root=UUID=fc58eb01-ce48-4d0e-ac05-443d37948ed0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-S1 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd01/17/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S1:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-S1 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977649 Title: my system is not showing me 1080p resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977626] Re: Kubuntu 22.04 screen lock would not type a password to unlock
** Description changed: Kubuntu 22.04 LTS Screen lock would not type a password to unlock. Tried 3 times to enter a password to unlock screen. Clicked the password bar and typed. It will not accept any letter or number for a password. This is a new install and completed the first updates. Manually shutdown computer to make bug report. KDE Frameworks 5.92.0 Qt 5.15.3 using X-11 lsb_release -a; uname -a;python3 --version No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy Linux b3-VirtualBox 5.15.0-35-generic #36-Ubuntu SMP Sat May 21 02:24:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Python 3.10.4 + Unable to reproduce the bug. + This only happened after initial install and first updates. + Kscreenlocker works according to expectations. + I am marking as invalid bug. + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libkscreenlocker5 5.24.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 3 18:09:52 2022 InstallationDate: Installed on 2022-06-03 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: kscreenlocker UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: kscreenlocker (Ubuntu) Status: New => Invalid ** Description changed: Kubuntu 22.04 LTS Screen lock would not type a password to unlock. Tried 3 times to enter a password to unlock screen. Clicked the password bar and typed. It will not accept any letter or number for a password. This is a new install and completed the first updates. Manually shutdown computer to make bug report. KDE Frameworks 5.92.0 Qt 5.15.3 using X-11 lsb_release -a; uname -a;python3 --version No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy Linux b3-VirtualBox 5.15.0-35-generic #36-Ubuntu SMP Sat May 21 02:24:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Python 3.10.4 - Unable to reproduce the bug. + * Unable to reproduce the bug. This only happened after initial install and first updates. Kscreenlocker works according to expectations. - I am marking as invalid bug. + I am marking as invalid bug.* ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libkscreenlocker5 5.24.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 3 18:09:52 2022 InstallationDate: Installed on 2022-06-03 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: kscreenlocker UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977626 Title: Kubuntu 22.04 screen lock would not type a password to unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kscreenlocker/+bug/1977626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977648] [NEW] GLX is rendered by Intel GPU only in Wayland
Public bug reported: I'm using Nvidia driver and PRIME profile is set to performance, however in Wayland only, GLX is rendered by Intel GPU and can't have Nvidia as default renderer. This is a problem because not all OpenGL applications can work with XWayland or by setting the ENV variables to use Nvidia. In Xorg Nvidia can be the default renderer with the same configuration. $ prime-select query nvidia $ glxinfo -B name of display: :1 display: :1 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel (0x8086) Device: Mesa Intel(R) Xe Graphics (TGL GT2) (0x9a49) Version: 22.0.1 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.1 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.0.1 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 4 15:15:50 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Also affects: wayland (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/1977648 Title: GLX is rendered by Intel GPU only in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977647] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: I didn't perform any action to get this crash. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.15.0-33.34-lowlatency 5.15.30 Uname: Linux 5.15.0-33-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marqrdt 676730 F pulseaudio /dev/snd/controlC0: marqrdt 676730 F pulseaudio /dev/snd/controlC1: marqrdt 676730 F pulseaudio CasperMD5CheckResult: pass Date: Tue May 31 11:25:55 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu3 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-07-09 (330 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-lowlatency root=/dev/mapper/vgubuntu-root ro threadirqs quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: /usr/bin/python3.10, Python 3.10.4, python-is-python3, 3.9.2-2 RelatedPackageVersions: grub-pc 2.06-2ubuntu7 SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) dmi.bios.date: 06/13/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/13/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977647 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977643] Re: gdm crash when unlocking screen if using Nouveau driver
Another update, also it happens with Nviida driver but when PRIME profile is set to on-demand. But performance mode is fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977643 Title: gdm crash when unlocking screen if using Nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1977643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Happens on every boot with this kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977646] [NEW] Snap apps launch time are EXTREMELY slow
Public bug reported: Snap apps launch time are EXTREMELY slow for all applications. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snapd 2.55.3+22.04ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 4 14:42:53 2022 InstallationDate: Installed on 2022-02-03 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: snapd UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) ** Affects: snapd (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/1977646 Title: Snap apps launch time are EXTREMELY slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1977646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974428] Re: Update to the current 1.36 stable version
@seb128 I have created a new bug report with links to the upstream commits. The core of the issue is that IPv6 addresses are now being added in the wrong order, so the kernel prefers SLAAC addresses over DHCPv6 addresses, which should be the other way around. As this is a breaking change in source-based IPv6 routing in an LTS release, I think the impact is severe. In my opinion, this update should never have reached stable, especially because this bug is known upstream and fixed in a later version. I'm already quite stressed how this will turn out at work after the weekend. We use source-based ACL's on all of our firewalls, giving static DHCPv6 leases to our client devices. Now all of a sudden those addresses are no longer being used for outgoing traffic, but instead the non-controllable SLAAC-addresses are. This will lock everyone out of all servers. The only way to get the proper addresses to be preferred again seems to be to disable SLAAC on the router, because any local setting in NetworkManager no longer works. I can disable SLAAC without issues at home, because everything is 100% Ubuntu and Debian there. But in environments with other OS'es that don't support DHCPv6 (like Android), disabling SLAAC will break IPv6 on all such devices. Moreover, not everybody controls their own routers, so this really isn't much of a solution. Other options would be to downgrade and apt-mark hold network-manager on all Ubuntu 22.04 devices, or to completely change server firewall infrastructure by whitelisting prefixes. As you can see, none of these options sound appealing. So regarding the regression potential: it has severely regressed IPv6 handling, and definitely *not* fixed things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974428 Title: Update to the current 1.36 stable version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975597] Re: Python files are still packaged for Python 3.8
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-keyboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975597 Title: Python files are still packaged for Python 3.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1975597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977645] Re: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail
The attachment "0001-avoid-identifying-as-beta-FIXED.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977645 Title: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969220]
(In reply to Olivier Tilloy from comment #4) > It looks like the difference might be in using the Wayland backend (default > in the beta and edge channels), versus being an XWayland client (default in > the stable channel). > > Can you switch back to the stable channel, and test again with > `MOZ_ENABLE_WAYLAND=1` ? The snap was previously failing to recognise the gesture with the Wayland backend on the beta channel a few weeks back (switched to beta roughly around the time stable was made to default to XWayland). Running `MOZ_ENABLE_WAYLAND=1 firefox` when using the stable channel version now recognises the gesture. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969220 Title: Pinch to zoom not working on Wayland on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1969220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969220]
It looks like the difference might be in using the Wayland backend (default in the beta and edge channels), versus being an XWayland client (default in the stable channel). Can you switch back to the stable channel, and test again with `MOZ_ENABLE_WAYLAND=1` ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969220 Title: Pinch to zoom not working on Wayland on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1969220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976585] Re: Ubiquity Installer Crash (Consistently Repeatable)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976585 Title: Ubiquity Installer Crash (Consistently Repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977499] Re: BUG IN UBUNTU 22.10 KINETIC KUDU: Audio Does Not Work Properly And Video Playback Is Very Laggy
When i made the same dist-upgrade, Ubuntu was moving from pulseaudio to pipewire. The result was: no sound hardware detected. So into a terminal i have ran: sudo touch /usr/share/pipewire/media-session.d/with-pulseaudio systemctl --user restart pipewire-session-manager After a reboot, the sound hardware was found and set to work as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977499 Title: BUG IN UBUNTU 22.10 KINETIC KUDU: Audio Does Not Work Properly And Video Playback Is Very Laggy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1977499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Another occurrence: [4.410322] = [4.410323] UBSAN: array-index-out-of-bounds in /build/linux-hwe-5.15-scdIe0/linux-hwe-5.15-5.15.0/drivers/ata/libahci.c:968:41 [4.410326] index 15 is out of range for type 'ahci_em_priv [8]' [4.410327] CPU: 1 PID: 434 Comm: scsi_eh_6 Tainted: G OE 5.15.0-33-generic #34~20.04.1-Ubuntu [4.410330] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B550M-HDV, BIOS P2.10 02/24/2022 [4.410331] Call Trace: [4.410332] [4.410334] dump_stack_lvl+0x4a/0x5f [4.410339] dump_stack+0x10/0x12 [4.410340] ubsan_epilogue+0x9/0x45 [4.410342] __ubsan_handle_out_of_bounds.cold+0x44/0x49 [4.410344] ahci_qc_issue+0x15e/0x160 [libahci] [4.410348] ata_qc_issue+0x132/0x240 [4.410351] ata_exec_internal_sg+0x2c6/0x580 [4.410353] ? vprintk_default+0x1d/0x20 [4.410356] ata_exec_internal+0x67/0xa0 [4.410358] ? sata_scr_read+0x45/0x60 [4.410360] sata_pmp_read.isra.0+0x8a/0xb0 [4.410363] sata_pmp_read_gscr+0x40/0xa0 [4.410365] sata_pmp_attach+0x8b/0x530 [4.410367] ata_eh_revalidate_and_attach+0x249/0x490 [4.410369] ata_eh_recover+0x6d5/0x1370 [4.410371] ? ahci_stop_engine+0xb0/0xb0 [libahci] [4.410373] ? ahci_do_hardreset+0x150/0x150 [libahci] [4.410376] ? ahci_do_softreset+0x260/0x260 [libahci] [4.410378] ? ata_phys_link_offline+0x60/0x60 [4.410381] ? ata_phys_link_offline+0x60/0x60 [4.410382] sata_pmp_eh_recover+0x61c/0xa80 [4.410385] ? ahci_stop_engine+0xb0/0xb0 [libahci] [4.410387] ? ata_phys_link_offline+0x60/0x60 [4.410389] ? ahci_do_softreset+0x260/0x260 [libahci] [4.410391] ? ahci_do_hardreset+0x150/0x150 [libahci] [4.410394] sata_pmp_error_handler+0x23/0x30 [4.410396] ahci_error_handler+0x43/0x80 [libahci] [4.410398] ata_scsi_port_error_handler+0x3a0/0x850 [4.410400] ata_scsi_error+0x9c/0xd0 [4.410402] scsi_error_handler+0xc3/0x520 [4.410404] ? scsi_eh_get_sense+0x250/0x250 [4.410406] kthread+0x127/0x150 [4.410408] ? set_kthread_struct+0x40/0x40 [4.410410] ret_from_fork+0x1f/0x30 [4.410413] [4.410414] = -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977645] Re: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail
Created PR at Debian: https://salsa.debian.org/debian/gpgme/-/merge_requests/4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977645 Title: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967572] Re: torbrowser-launcher crashed with move(self, int, int) in main(): argument 1 has unexpected type 'float'
Bug (Debian Bug #1010441) is fixed in Debian's torbrowser-launcher 0.3.5-3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967572 Title: torbrowser-launcher crashed with move(self, int, int) in main(): argument 1 has unexpected type 'float' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1967572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976272] Re: torbrowser-launcher crashes with Python error in __init__.py
*** This bug is a duplicate of bug 1967572 *** https://bugs.launchpad.net/bugs/1967572 ** This bug has been marked a duplicate of bug 1967572 torbrowser-launcher crashed with move(self, int, int) in main(): argument 1 has unexpected type 'float' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976272 Title: torbrowser-launcher crashes with Python error in __init__.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1976272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems
Hi, i opened a separate bug with my wish for not needing a second zeroizing dd run when the ISO is already on the USB stick: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1977644 "Please preserve MBR partition entries 2 to 4 when creating persistent partition" Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922342 Title: Impish live session takes ages to boot on BIOS systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976272] Re: torbrowser-launcher crashes with Python error in __init__.py
*** This bug is a duplicate of bug 1967572 *** https://bugs.launchpad.net/bugs/1967572 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: torbrowser-launcher (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976272 Title: torbrowser-launcher crashes with Python error in __init__.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1976272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977645] [NEW] python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail
Public bug reported: The python version of the gpgme version contains "unknown" and is therefore not PEP440 order compatible. See this example: # pip3 freeze | grep gpg gpg===1.16.0-unknown # pip3 install pstore ... Successfully installed gpg-1.10.0 Successfully installed pstore-2.0.0 # pip3 freeze | grep gpg gpg==1.10.0 Key takeways from that example: - pstore depends on gpg>=1.10 - 1.16 SHOULD be higher than 1.10 - pip installs 1.10 even though 1.16 exists - the triple-= (gpg===1.16.0-unknown) means that the version exists, but cannot be version compared: https://peps.python.org/pep-0440/#arbitrary- equality Suggested fix: - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with a '+'; that will compare as expected; - fix so "-unknown" isn't appended. Apparently, this is caused by insufficient fixes in 0001-avoid-identifying-as-beta.patch I've attached a FIXED version, which should fix things. Before: $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown. After: $ quilt push Applying patch 0001-avoid-identifying-as-beta-FIXED.patch $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0. Versions: $ lsb_release -a 2>/dev/null| grep Codename Codename: jammy $ apt-cache policy python3-gpg | grep Installed Installed: 1.16.0-1.2ubuntu4 Cheers, Walter Doekes OSSO B.V. ** Affects: gpgme1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "0001-avoid-identifying-as-beta-FIXED.patch" https://bugs.launchpad.net/bugs/1977645/+attachment/5594802/+files/0001-avoid-identifying-as-beta-FIXED.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977645 Title: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977644] [NEW] Please preserve MBR partition entries 2 to 4 when creating persistent partition
Public bug reported: Hi, i propose to let function find_or_create_persistent_partition in scripts/casper-helpers preserve the MBR partition entries 2 to 4 when it applies sfdisk to create the persistent partition. Currently it writes an MBR partition entry 2 with start LBA 0, size 1, and boot flag if it detects GPT after the persistent partition was created. (sfdisk had overwritten it by zeros but normally the ISO shall have it.) My idea for casper-helpers is to record the three entries in a file: MBR_STASH=/tmp/mbr_stash_$$ dd if="$DEVICE" bs=1 skip=462 count=48 of="$MBR_STASH" and to restore them after creation of the new partition dd if="$MBR_STASH" bs=1 seek=462 conv=notrunc count=48 of="$DEVICE" instead of writing a newly composed entry 2, as is done now: echo $escape_arg -n '\0200\00\01\00\00\00\01\00\00\00\00\00\01\00\00\00' \ | dd of=$DEVICE bs=1 seek=462 conv=notrunc count=16 --- Reasoning: In the course of https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342 we found out that some rare old machines need 10 minutes or longer to boot the current Ubuntu ISOs from USB stick. The trigger is the presence of the MBR partition 2 with boot flag. This partition exists for some old but not so rare machines. It is a mild violation of UEFI/GPT specs which don't offer a clear way to equip a GPT partitioned device with an MBR boot flag. If MBR partition entry 2 of the ISO image is overwritten by zero bytes before the image is put onto the USB stick, then it boots substantially faster. E.g. 3 minutes rather than 10 minutes. But casper re-installs MBR partition 2 when starting the first Live session. So after one swift boot, the problem is back and the USB stick needs the removal of MBR partition 2 again. This time the remedy is permanent. But it has to be applied to the USB stick with superuser authority. Given that the Ubuntu tutorial proposes to put the ISO image onto the USB stick by Balena Etcher rather than by cp or dd, i deem it not safe to propose a dd run as superuser. I make this change proposal so that it is possible to apply the remedy as normal user to the ISO image file rather than as superuser to the stick. --- Additional details: Affected are: - a tablet computer "motion computing j3400" of Chris Guiver, - a Gigabyte H61M-D2H-USB3 mainboard of José Marinho (see also https://launchpadlibrarian.net/531427797/lshw.txt), - (a Gigabyte GA-970A-DS3, BIOS F7a 01/24/2013 of tlk, of which we have no confirmation that removing MBR partition 2 really helps). The long delay happens after the GRUB boot menu, probably still in GRUB. I lack of ideas how to even find out whether vmlinuz hasn't started yet, not to speak of diagnosing why it only happens with particular firmwares. Bug 1922342 mentions an error message "Error can't find grub_platform" which is related to a few lines grub.cfg. In the end it turned out that disabling these lines silences the message but does not speed up booting. Have a nice day :) Thomas ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, i propose to let function find_or_create_persistent_partition in scripts/casper-helpers preserve the MBR partition entries 2 to 4 when it applies sfdisk to create the persistent partition. Currently it writes an MBR partition entry 2 with start LBA 0, size 1, and boot flag if it detects GPT after the persistent partition was created. (sfdisk had overwritten it by zeros but normally the ISO shall have it.) My idea for casper-helpers is to record the three entries in a file: MBR_STASH=/tmp/mbr_stash_$$ dd if="$DEVICE" bs=1 skip=462 count=48 of="$MBR_STASH" and to restore them after creation of the new partition - dd if="$MBR_STASH" bs=1 seek=462 conv=notrunc count=48 + dd if="$MBR_STASH" bs=1 seek=462 conv=notrunc count=48 of="$DEVICE" instead of writing a newly composed entry 2, as is done now: echo $escape_arg -n '\0200\00\01\00\00\00\01\00\00\00\00\00\01\00\00\00' \ | dd of=$DEVICE bs=1 seek=462 conv=notrunc count=16 --- Reasoning: In the course of https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342 we found out that some rare old machines need 10 minutes or longer to boot the current Ubuntu ISOs from USB stick. The trigger is the presence of the MBR partition 2 with boot flag. This partition exists for some old but not so rare machines. It is a mild violation of UEFI/GPT specs which don't offer a clear way to equip a GPT partitioned device with an MBR boot flag. If MBR partition entry 2 of the ISO image is overwritten by zero bytes before the image is put onto the USB stick, then it boots substantially faster. E.g. 3 minutes rather
[Bug 1947588] Re: Infinite Loop in OpenSSL s_server
This bug was fixed in the package openssl - 3.0.3-5ubuntu2 --- openssl (3.0.3-5ubuntu2) kinetic; urgency=medium * d/p/Set-systemwide-default-settings-for-libssl-users: don't comment out the CipherString string to avoid an empty section. -- Simon Chopin Tue, 31 May 2022 13:02:15 +0200 ** Changed in: openssl (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947588 Title: Infinite Loop in OpenSSL s_server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974035] Re: openssl: Merge 3.0.3-4 from Debian unstable
This bug was fixed in the package openssl - 3.0.3-5ubuntu2 --- openssl (3.0.3-5ubuntu2) kinetic; urgency=medium * d/p/Set-systemwide-default-settings-for-libssl-users: don't comment out the CipherString string to avoid an empty section. -- Simon Chopin Tue, 31 May 2022 13:02:15 +0200 ** Changed in: openssl (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974035 Title: openssl: Merge 3.0.3-4 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level
This bug was fixed in the package openssl - 3.0.3-5ubuntu2 --- openssl (3.0.3-5ubuntu2) kinetic; urgency=medium * d/p/Set-systemwide-default-settings-for-libssl-users: don't comment out the CipherString string to avoid an empty section. -- Simon Chopin Tue, 31 May 2022 13:02:15 +0200 ** Changed in: openssl (Ubuntu Kinetic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972056 Title: [openssl3] please sync openssl.cnf to ease changing security level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974037] Re: openssl: EVP_EC_gen() segfault without init
This bug was fixed in the package openssl - 3.0.3-5ubuntu2 --- openssl (3.0.3-5ubuntu2) kinetic; urgency=medium * d/p/Set-systemwide-default-settings-for-libssl-users: don't comment out the CipherString string to avoid an empty section. -- Simon Chopin Tue, 31 May 2022 13:02:15 +0200 ** Changed in: openssl (Ubuntu Kinetic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974037 Title: openssl: EVP_EC_gen() segfault without init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720717] Re: Add multiarch metadata to tessaract lib/dev
** Changed in: tesseract (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720717 Title: Add multiarch metadata to tessaract lib/dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tesseract/+bug/1720717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977643] [NEW] gdm crash when unlocking screen if using Nouveau driver
Public bug reported: Randomly but frequently when trying to unlock screen, it either becomes very slow (like when typing the password, characters are reflected very slowly) or it totally freeze and crash. Also switching TTY's doesn't work and have to hard reset. This was happening for me before while using Nvidia's driver but it has been working fine, now when I switched to the Nouveau driver, it constantly happens. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 4 13:06:05 2022 InstallationDate: Installed on 2022-02-03 (120 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago) mtime.conffile..etc.pam.d.gdm-password: 2022-02-19T02:26:10.814729 ** Affects: gdm3 (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/1977643 Title: gdm crash when unlocking screen if using Nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1977643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548250] Re: package libtesseract4 not installed failed to install/upgrade: trying to overWRITE /usr/lib/libtesseract.so.3.0.4 , which is also in package libtesseract3v5 3.04.00-5ubuntu1
** Changed in: tesseract (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548250 Title: package libtesseract4 not installed failed to install/upgrade: trying to overWRITE /usr/lib/libtesseract.so.3.0.4 , which is also in package libtesseract3v5 3.04.00-5ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tesseract/+bug/1548250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548481] Re: package libtesseract4 (not installed) failed to install/upgrade: Versuch, »/usr/lib/libtesseract.so.3.0.4« zu überschreiben, welches auch in Paket libtesseract3v5 3.04.00-5ubuntu1 is
*** This bug is a duplicate of bug 1548250 *** https://bugs.launchpad.net/bugs/1548250 ** This bug has been marked a duplicate of bug 1548250 package libtesseract4 not installed failed to install/upgrade: trying to overWRITE /usr/lib/libtesseract.so.3.0.4 , which is also in package libtesseract3v5 3.04.00-5ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548481 Title: package libtesseract4 (not installed) failed to install/upgrade: Versuch, »/usr/lib/libtesseract.so.3.0.4« zu überschreiben, welches auch in Paket libtesseract3v5 3.04.00-5ubuntu1 ist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tesseract/+bug/1548481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548796] Re: package libtesseract4 3.04.01-2 failed to install/upgrade: a tentar sobre-escrever '/usr/lib/libtesseract.so.3.0.4', que também está no pacote libtesseract3v5 3.04.00-5ubuntu1
*** This bug is a duplicate of bug 1548250 *** https://bugs.launchpad.net/bugs/1548250 ** This bug has been marked a duplicate of bug 1548250 package libtesseract4 not installed failed to install/upgrade: trying to overWRITE /usr/lib/libtesseract.so.3.0.4 , which is also in package libtesseract3v5 3.04.00-5ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548796 Title: package libtesseract4 3.04.01-2 failed to install/upgrade: a tentar sobre-escrever '/usr/lib/libtesseract.so.3.0.4', que também está no pacote libtesseract3v5 3.04.00-5ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tesseract/+bug/1548796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1555857] Re: package libtesseract4 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libtesseract.so.3.0.4', which is also in package libtesseract3v5 3.04.00-5ubuntu1
*** This bug is a duplicate of bug 1548250 *** https://bugs.launchpad.net/bugs/1548250 ** This bug has been marked a duplicate of bug 1548250 package libtesseract4 not installed failed to install/upgrade: trying to overWRITE /usr/lib/libtesseract.so.3.0.4 , which is also in package libtesseract3v5 3.04.00-5ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1555857 Title: package libtesseract4 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libtesseract.so.3.0.4', which is also in package libtesseract3v5 3.04.00-5ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tesseract/+bug/1555857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802334] Re: update tesseract-ocr to 4.0.0 stable
** Changed in: tesseract (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802334 Title: update tesseract-ocr to 4.0.0 stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tesseract/+bug/1802334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816304] Re: Several issues due to version 4 beta while the final 4.0.0 has been released
** Changed in: tesseract (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816304 Title: Several issues due to version 4 beta while the final 4.0.0 has been released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openalpr/+bug/1816304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977642] [NEW] mailfromd.service: State 'stop-sigterm' timed out. Killing.
Public bug reported: EXPECTED mailfromd should stay running WHAT HAPPENS Jun 04 12:19:13 base-generic-a mailfromd[180100]: mailfromd started Jun 04 12:20:43 base-generic-a systemd[1]: mailfromd.service: State 'stop-sigterm' timed out. Killing. Jun 04 12:20:43 base-generic-a systemd[1]: mailfromd.service: Killing process 180100 (mailfromd) with signal SIGKILL. Jun 04 12:20:43 base-generic-a systemd[1]: mailfromd.service: Failed with result 'timeout'. This happens after each 90 secs. WHAT I DID ...but this is definitely not the way it should be: changed mailfromd.service to be like this: [Service] Type=simple ExecStartPre=/usr/bin/install -m 755 -o mailfromd -g mailfromd -d /run/mailfromd ExecStart=/usr/sbin/mailfromd --pidfile /run/mailfromd/mailfromd.pid --user mailfromd --foreground Set Type to "simple" Changed mailfromd to run in foreground Now it seems to work. Btw, running within the 90 secs timeframe I was unable to stop the service. Now, I can. VERSIONS lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04 LTS Release: 22.04 Codename: jammy ii mailfromd 8.13-1 amd64 General-Purpose Mail Filter ii libmailutils-dev 1:3.14-1 amd64 development files for GNU mailutils ii libmailutils8:amd64 1:3.14-1 amd64 GNU Mail abstraction library ii mailutils-common 1:3.14-1 all common files for GNU mailutils ** Affects: mailfromd (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/1977642 Title: mailfromd.service: State 'stop-sigterm' timed out. Killing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailfromd/+bug/1977642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing
The pipewire-media-session postrm is:
#!/bin/sh
set -e
# Automatically added by dh_installsystemduser/13.7.1ubuntu1
if [ "$1" = "remove" ]; then
if [ -z "${DPKG_ROOT:-}" ] && [ -x "/usr/bin/deb-systemd-helper" ] ;
then
deb-systemd-helper --user mask 'pipewire-media-session.service'
>/dev/null || true
fi
fi
if [ "$1" = "purge" ]; then
if [ -z "${DPKG_ROOT:-}" ] && [ -x "/usr/bin/deb-systemd-helper" ] ;
then
deb-systemd-helper --user purge
'pipewire-media-session.service' >/dev/null || true
deb-systemd-helper --user unmask
'pipewire-media-session.service' >/dev/null || true
fi
fi
# End automatically added section
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977564
Title:
wireplumber conflicts with pipewire-media-session & needs fixing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
** Description changed: My network has both DHCPv6 and SLAAC for IPv6. From both a privacy perspective and readability reasons, DHCPv6 should *always* be preferred over SLAAC addresses when available. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world. Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Setting net.ipv6.conf.all.use_tempaddr=0 and net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has any effect. Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's altogether is the only way to stop NetworkManager from preferring SLAAC over DHCPv6 now. Looking at the changelog of NetworkManager 1.36.6, things regarding IP address order and temporary addresses have been changed in that release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 this was not the case. (The Linux kernel uses the address highest in the list as preferred.) This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. - So this update introduces a very breaking change to an LTS release, - while LTS releases should be stable. + So this update introduces a very breaking change in IPv6 source address + selection to an LTS release, while LTS releases should be stable. I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. /etc/os-release: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy 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=jammy nmcli -v: nmcli tool, version 1.36.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 orders IPv6 addresses incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977641] Re: mailfromd: undefined symbol: mu_stream_getline
mu_stream_getline and others have changed to inline (changelog). It seems as if not all dependent packages have been recompiled after this change. Simple recompilation of mailfromd with the new headers did the job. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977641 Title: mailfromd: undefined symbol: mu_stream_getline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailfromd/+bug/1977641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hi Daniel! #20 works for me! Thanks! Do you have any explanation for this? How come this was not a problem back when I was running Fedora? Is Ubuntu 22.04 using an older, unfixed version of some package? Was this bug introduced downstream in the Ubuntu release? Are there any plans of fixing this for 22.04.1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977630] Re: machinectl pull-tar/pull-raw Operation not permitted
To add to that, this is the error when trying to pull an image $ machinectl pull-tar --verify=no https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz test ... Got 98% of https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz. 1s left at 3.6M/s. Got 99% of https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz. 200ms left at 3.6M/s. Download of https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-amd64-root.tar.xz complete. Failed to rename to final image name to /var/lib/machines/.tar-https:\x2f\x2fcloud-images\x2eubuntu\x2ecom\x2fjammy\x2fcurrent\x2fjammy-server-cloudimg-amd64-root\x2etar\x2exz.\x2216765cac-5e045b7e29b80\x22: Operation not permitted Exiting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977630 Title: machinectl pull-tar/pull-raw Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly
** Description changed: My network has both DHCPv6 and SLAAC for IPv6. From both a privacy perspective and readability reasons, DHCPv6 should *always* be preferred over SLAAC addresses when available. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world. Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Setting net.ipv6.conf.all.use_tempaddr=0 and net.ipv6.conf..use_tempaddr=0 with sysctl also no longer has any effect. Removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's altogether is the only way to stop NetworkManager from preferring SLAAC over DHCPv6 now. Looking at the changelog of NetworkManager 1.36.6, things regarding IP address order and temporary addresses have been changed in that release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 this was not the case. (The Linux kernel uses the address highest in the list as preferred.) This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have no influence on), I am being locked out of the servers in question unless I forcefully remove the addresses or disable SLAAC on my router, so my outgoing traffic is being routed through the DHCPv6 address again. + So this update introduces a very breaking change to an LTS release, + while LTS releases should be stable. + I should note that the bug is not present in NetworkManager 1.38.0 on Debian sid. That just prefers DHCPv6 addresses when available, like it should. /etc/os-release: PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy 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=jammy nmcli -v: nmcli tool, version 1.36.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977619 Title: NetworkManager 1.36.6 orders IPv6 addresses incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977641] [NEW] mailfromd: undefined symbol: mu_stream_getline
Public bug reported: EXPECTED mailfromd works WHAT HAPPENS systemctl start mailfromd gives the following error: Jun 04 09:53:06 base-generic-a mailfromd[2515]: /usr/sbin/mailfromd: symbol lookup error: /usr/sbin/mailfromd: undefined symbol: mu_stream_getline Jun 04 09:53:06 base-generic-a systemd[1]: mailfromd.service: Main process exited, code=exited, status=127/n/a Jun 04 09:53:06 base-generic-a systemd[1]: mailfromd.service: Failed with result 'exit-code'. VERSIONS lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy ii mailfromd 8.13-1 amd64General-Purpose Mail Filter ii libmailutils-dev 1:3.14-1 amd64development files for GNU mailutils ii libmailutils8:amd64 1:3.14-1 amd64GNU Mail abstraction library ii mailutils-common 1:3.14-1 all common files for GNU mailutils ** Affects: mailfromd (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/1977641 Title: mailfromd: undefined symbol: mu_stream_getline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailfromd/+bug/1977641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
