[Touch-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server * Test case try to connect to a TLS <= 1.1 access point * Regression potential the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files
Further analysis by Milan Crha shows that the issue under Xorg seems to be caused by Ubuntu's gtk3, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972#note_1524307. ** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #1972 https://gitlab.gnome.org/GNOME/evolution/-/issues/1972 ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1983794 Title: Evolution not deleting autosave files Status in evolution package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1983794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.
I installed libgdk-pixbuf2.0-common (2.42.9+dfsg-1ubuntu1) and libgdk- pixbuf-2.0-0 (2.42.9+dfsg-1ubuntu1) from the proposed repository on 22.10. I can confirm that I'm now able to open large images in eog that I wasn't able to open before, so this looks good to me. ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1998263 Title: JPEG ( backing store not supported ) : many pictures won't open. Status in Eye of GNOME: Fix Released Status in gdk-pixbuf: Fix Released Status in gdk-pixbuf package in Ubuntu: Fix Released Status in gdk-pixbuf source package in Jammy: Invalid Status in gdk-pixbuf source package in Kinetic: Fix Committed Status in gdk-pixbuf source package in Lunar: Fix Released Bug description: * Impact Eog can't open high resolution jpg files * Test Case - download https://gitlab.gnome.org/GNOME/gdk-pixbuf/uploads/fcda5bc359fbf55a1b9755ba92c3303d/kwiatek.jpg - try to open the image in eog * Regression potential The change increase the memory usage limit for loading jpg, it could lead to put the system under memory pressure. The limit has been added in 22.10 though so it isn't a regression compared to the previous version of Ubuntu - Hi, 22.10. Just try to open some .jpg files from my usual storage. Error interpreting jpeg file ( Backing store not supported. ) Those same pictures open in other OSes ( 22.04, 20.04 and else. ) Can't use those pictures as backgrounds. But able to open them in Gimp or Shotwell. Maybe related to : https://gitlab.gnome.org/GNOME/gdk- pixbuf/-/issues/216 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: eog 43.0-1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 29 23:31:36 2022 InstallationDate: Installed on 2022-10-27 (33 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1998263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925745] [NEW] Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Public bug reported: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: 21.04 hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
A workaround is to manually force installation of the dependencies with the newer "phased" versions: apt install ubuntu-release-upgrader-core=1:21.04.11 python3-distupgrade=1:21.04.11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Manfred: Thanks! (Offtopic: I googled "apt phased 20%". The "20%" seems to throw Google off completely, it didn't show ANY results related to Linux. Leaving off the 20% yields much better results ;)) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Hi, when will this bug be fixed in 21.04/Hirsute? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
Thank you Brian for following up on this! Is there any news regarding the fix in Hirsute yet? Two months of not being able to access iCloud mails in a core component of the current supported Ubuntu release is a really long time ... :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Triaged Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
I tested evolution-data-server version 3.40.0-1ubuntu1.1 from proposed in Hirsute. I can confirm that iCloud accounts can be accessed again. Thanks for your work, Brian, Sebastien and Iain! ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Similar to what Dan wrote in comment #10, my original test case of installing ubuntu-desktop now works even without enabling the proposed repository. So unfortunately I cannot verify the fix now since I cannot reproduce the original error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in apt package in Ubuntu: Fix Released Status in apt source package in Hirsute: Fix Committed Status in apt source package in Impish: Fix Released Bug description: [Impact] Phased upgrades were only applied to already installed packages, so if we had a source package foo building foo-core and foo-extra, and foo-core=1 was installed, and we tried to install foo-extra, it would fail because it would try to install 0% foo-extra=2 while blocking foo-core as it's "not for us". [Test Plan] The autopkgtests ensure we don't regress and they kind of check this by checking the policy output to see that "foo-extra=2" above is also not the candidate, but foo-extra=1 is (so installing it alongside foo-core=1 would work fine) but they don't install it, so it might be nice to verify this too: Find a package that is phased, but not for us (maybe just setting the never-include-phased flag?), install one binary from it from the release pocket, and then try to install another from the updates pocket. At the moment, installing libsystemd-dev would trigger it. [Where problems could occur] This is a change in behavior when installing new packages that might cause regression in image building tools for example, if those don't use a chroot (chroots being detected). Apart from that risk, the change is just removing a flag check inside an if, so not much else. [Original bug report] I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1966418] Re: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc)
While this bug is fixed for displaying emails in Evolution, the same problem still occurs when editing emails. I created bug #1969584 for this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] webkit apps do not display content (yelp, epiphany, gnome-online-accounts etc) Status in Gnome DevHelp: Invalid Status in Mesa: Unknown Status in Webkit: Confirmed Status in epiphany-browser package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnome-control-center package in Ubuntu: Invalid Status in liferea package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in webkit2gtk package in Ubuntu: Invalid Bug description: Impact -- All webkit using apps for affected users display a blank screen. Original Bug Report --- Evolution has suddenly stopped displaying message contents on the last 24h. Starting it up from the command line shows this output: ``` EGLDisplay Initialization failed: EGL_NOT_INITIALIZED Cannot create EGL context: invalid display (last error: EGL_SUCCESS) ``` I don't know if it's related, but googling around shows some webkitgtk hits on this error. The email contents are however clickable. They're just not rendered to screen (see attached file). Deleting the evolution folders from `~/.config`, `~/.cache` and `~/.local/share` does not help. Email accounts are all google, configured through gnome online accounts. Workaround #1 - You can run the app from the command line with WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution (Replace evolution with the name of the webkit app you are trying to use) Workaround #2 - Log out. Select your name on the login screen. Click the gear button and choose Ubuntu on Xorg. Enter your password to finish logging in. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evolution 3.44.0-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: sway Date: Fri Mar 25 10:55:49 2022 SourcePackage: evolution UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/devhelp/+bug/1966418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017420] [NEW] Cannot open HEIF/HEIC images in 23.04/lunar anymore
Public bug reported: In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Affects: libheif (Ubuntu) Importance: Undecided Status: New ** Tags: lunar ** Tags added: lunar ** Also affects: libheif (Ubuntu) Importance: Undecided Status: New ** Also affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: New Status in libheif package in Ubuntu: New Bug description: In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore
Dirk is correct: The library tries to open /usr/lib/x86_64-linux- gnu/libheif/plugins, which doesn't exist, but seems to be required in the libheif version in 23.04. After creating the path, both eog and gpicview can show HEIF/HEIC files again, so this is an easy workaround. According to Dirk, newer versions of libheif do _not_ require the plugins directory to exist anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Confirmed Status in gdk-pixbuf package in Ubuntu: Confirmed Status in libheif package in Ubuntu: Confirmed Bug description: In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore
I tested the package from proposed after deleting the manually created plugins directory first. The new package correctly creates the directory and HEIF files can be opened. Thanks! ** Tags removed: verification-needed verification-needed-lunar ** Tags added: verification-done verification-done-lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/2017420 Title: Cannot open HEIF/HEIC images in 23.04/lunar anymore Status in eog package in Ubuntu: Invalid Status in gdk-pixbuf package in Ubuntu: Invalid Status in libheif package in Ubuntu: Fix Released Status in eog source package in Lunar: Invalid Status in gdk-pixbuf source package in Lunar: Invalid Status in libheif source package in Lunar: Fix Committed Bug description: * Impact The libheif loader is bailing out due to a missing plugin directory which leads to image viewer as eog not being able to open pictures in that format anymore * Testcase Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in eog * Where problems could occur The package build is using the option to not split the codec in separate plugins but the version of Lunar doesn't handle the missing plugins directory and bails out. The code of the version in mantic has been refactored in a way which fixes this problem. For lunar it's easier to just create the directory. The directory is included in the libheif1 binary but that should not create any conflict, it's a temporary situation for lunar only and even if the soname changed dpkg allows for several deb packages to provide the same directory. -- In previous Ubuntu versions, including 22.10, I was able to open HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does not work anymore in 23.04. Running eog in a terminal displays: $ eog IMG_9996.HEIC ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin directory. (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_is_static_image: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION (animation)' failed (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543: gdk_pixbuf_animation_iter_get_pixbuf: assertion 'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed eog then shows "Could not load image “IMG_9996.HEIC”. Image loading failed." gpicview even crashes immediately: $ gpicview IMG_9996.HEIC Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module" ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin directory. ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory. Segmentation fault (core dumped) The problem concerns all HEIF/HEIC images I tested. The installed versions of the (possibly) relevant packages are: libheif1: 1.14.2-1 heif-gdk-pixbuf: 1.14.2-1 libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1 eog: 44.0-1 gpicview: 0.2.5-3build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1895664] Re: evince can't start local installation of vivaldi browser
@seb128: Vivaldi is the spiritual successor of Opera. Opera _is_ included in /etc/apparmor.d/abstractions/ubuntu-browsers, so Vivaldi should be as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1895664 Title: evince can't start local installation of vivaldi browser Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Invalid Bug description: evince 3.28.4-0ubuntu1.2 running on bionic. I cannot call the vivaldi-browser by clicking on a link. Instead an error is shown "Failed to execute child process “/usr/bin/vivaldi-stable” (Permission denied)". Some lines from syslog: Sep 15 14:28:28 work kernel: [46945.893234] audit: type=1400 audit(1600172908.761:241): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.523153] audit: type=1400 audit(1600172909.393:242): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.716721] audit: type=1400 audit(1600172909.585:243): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:29 work kernel: [46946.748450] audit: type=1400 audit(1600172909.617:244): apparmor="DENIED" operation="create" profile="/usr/bin/evince//sanitized_helper" pid=4709 comm="pool" family="netlink" sock_type="raw" protocol=0 requested_mask="create" denied_mask="create" Sep 15 14:28:53 work kernel: [46970.973331] audit: type=1400 audit(1600172933.841:256): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/opt/vivaldi/vivaldi" pid=5390 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988488] Re: Screen freeze before the login screen on VirtualBox (if the third party software option was selected)
I'm using VirtualBox to test upcoming Ubuntu versions using the exact same config and packages that will later be used on several physical machines. So it's pretty important to me to install the third-party packages in VMs as well. But yes, I can live with the workaround for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1988488 Title: Screen freeze before the login screen on VirtualBox (if the third party software option was selected) Status in gnome-shell package in Ubuntu: Confirmed Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Status in libxcb package in Ubuntu: Confirmed Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037202] [NEW] Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
Public bug reported: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
** Tags added: mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
** Description changed: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: - dhcpd-10.0.2 starting + dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot - dhcpd exited + dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. - Executing dhcpd now correctly gets IP addresses, but I don't know how to - continue the boot from there. + Executing dhcpcd now correctly gets IP addresses, but I don't know how + to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
As a workaround, I added a `sleep 1` at the end of `_set_available_devices_to_up()` in `scripts/functions` in the Mantic initrd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
If I understand the process correctly, dhcpcd is already run in a loop. But the loop is over too quickly if the interface takes a few seconds to come up. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: New Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037202] Re: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up
I tested on two machines where the boot failed previously. With the new `scripts/functions`, the boot now works properly. Thanks you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2037202 Title: Mantic/23.10: PXE boot tries to initialize DHCP before network link is up Status in initramfs-tools package in Ubuntu: Fix Released Bug description: I'm not sure whether this is the correct package for this bug, please reassign if not. I'm booting the Ubuntu Mantic/23.10 desktop beta image via PXE in order to perform an unattended installation. The kernel command line looks like that: iso/casper/vmlinuz --- ip=dhcp netboot=nfs nfsroot=192.168.1.1:/export/ubuntu autoinstall ds=nocloud\;s= This has worked perfectly before. However, in 23.10, the kernel tries to intialize DHCP before a network link is up. I can see a few instances of messages like the following: dhcpcd-10.0.2 starting dev: loaded udev no interfaces have a carrier exiting due to oneshot dhcpcd exited Then, the kernel tries to mount NFS, even though neither an IP address nor even a link is available: connect: Network is unreachable NFS over TCP not available from 192.168.1.1 This is repeated for a while. In between, a message tells that now the link is up: [10.0002805] e1000e :00:19.0 enp0s25: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx The NFS messages repeat for a while, until the system gives up and I'm dropped into a busybox prompt. Executing dhcpcd now correctly gets IP addresses, but I don't know how to continue the boot from there. The problem occurs on most physical machines that I tried, but not in VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781699] Re: DHCPv6 server crashes regularly (bionic)
To those waiting for a fix: I'm using a workaround by setting systemd to restart the service when it crashes. This works well for me: $ cat /etc/systemd/system/isc-dhcp-server6.service.d/override.conf [Service] Restart=on-abort RestartSec=1 Run systemctl daemon-reload after creating/changing the file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) Status in isc-dhcp package in Ubuntu: Confirmed Status in isc-dhcp package in Debian: New Status in isc-dhcp package in Fedora: Unknown Bug description: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ?? Jul 14 09:35:53 sh[1543]: #9 0x55d9ee667463 in ?? Jul 14 09:35:53 sh[1543]: #10 0x55d9ee696476 in ?? Jul 14 09:35:53 sh[1543]: #11 0x7efc458dd73b in ?? Jul 14 09:35:53 sh[1543]: #12 0x7efc458ccf9e in ?? Jul 14 09:35:53 sh[1543]: #13 0x7efc458d1e60 in ?? Jul 14 09:35:53 sh[1543]: #14 0x7efc458d2325 in ?? Jul 14 09:35:53 sh[1543]: #15 0x55d9ee6696b0 in ?? Jul 14 09:35:53 sh[1543]: #16 0x55d9ee61d519 in ?? Jul 14 09:35:53 sh[1543]: #17 0x7efc454c6b97 in ?? Jul 14 09:35:53 sh[1543]: #18 0x55d9ee61de0a in ?? Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Main process exited, code=dumped, status=6/ABRT Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Failed with result 'core-dump'. The bug was reported to Debian independently, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=896122. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1781699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781699] [NEW] DHCPv6 server crashes regularly (bionic)
Public bug reported: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ?? Jul 14 09:35:53 sh[1543]: #9 0x55d9ee667463 in ?? Jul 14 09:35:53 sh[1543]: #10 0x55d9ee696476 in ?? Jul 14 09:35:53 sh[1543]: #11 0x7efc458dd73b in ?? Jul 14 09:35:53 sh[1543]: #12 0x7efc458ccf9e in ?? Jul 14 09:35:53 sh[1543]: #13 0x7efc458d1e60 in ?? Jul 14 09:35:53 sh[1543]: #14 0x7efc458d2325 in ?? Jul 14 09:35:53 sh[1543]: #15 0x55d9ee6696b0 in ?? Jul 14 09:35:53 sh[1543]: #16 0x55d9ee61d519 in ?? Jul 14 09:35:53 sh[1543]: #17 0x7efc454c6b97 in ?? Jul 14 09:35:53 sh[1543]: #18 0x55d9ee61de0a in ?? Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Main process exited, code=dumped, status=6/ABRT Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Failed with result 'core-dump'. The bug was reported to Debian independently, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=896122. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) Status in isc-dhcp package in Ubuntu: New Bug description: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ??
[Touch-packages] [Bug 1781699] Re: DHCPv6 server crashes regularly (bionic)
Thanks for your work, Alex, Andreas and Marc! I can confirm that isc- dhcp-server 4.3.5-3ubuntu7.1 has been running for two days while the previous version crashed every few hours in my environment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) Status in DHCP: Unknown Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Bionic: In Progress Status in isc-dhcp source package in Cosmic: In Progress Status in isc-dhcp source package in Disco: Fix Released Status in isc-dhcp source package in Eoan: Fix Released Status in isc-dhcp package in Debian: New Status in isc-dhcp package in Fedora: Unknown Bug description: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ?? Jul 14 09:35:53 sh[1543]: #9 0x55d9ee667463 in ?? Jul 14 09:35:53 sh[1543]: #10 0x55d9ee696476 in ?? Jul 14 09:35:53 sh[1543]: #11 0x7efc458dd73b in ?? Jul 14 09:35:53 sh[1543]: #12 0x7efc458ccf9e in ?? Jul 14 09:35:53 sh[1543]: #13 0x7efc458d1e60 in ?? Jul 14 09:35:53 sh[1543]: #14 0x7efc458d2325 in ?? Jul 14 09:35:53 sh[1543]: #15 0x55d9ee6696b0 in ?? Jul 14 09:35:53 sh[1543]: #16 0x55d9ee61d519 in ?? Jul 14 09:35:53 sh[1543]: #17 0x7efc454c6b97 in ?? Jul 14 09:35:53 sh[1543]: #18 0x55d9ee61de0a in ?? Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Main process exited, code=dumped, status=6/ABRT Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Failed with result 'core-dump'. The bug was reported to Debian independently, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=896122. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1781699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Sebastien, I can confirm that the updated package fixes the problem. Thanks for your work! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts: Unknown Status in evolution-data-server package in Ubuntu: Fix Released Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
Still occurs in 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1557157 Title: apparmor profile denied for saslauthd: /run/saslauthd/mux Status in openldap package in Ubuntu: Confirmed Bug description: When using slapd with saslauthd the processes communicate via the {,/var}/run/saslauthd/mux socket (this is the default location for the saslauthd server from the sasl2-bin package in the /etc/default/saslauthd config), but the apparmor profile for usr.sbin.slapd does not allow access to this socket/file. Syslog message: apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" name="/run/saslauthd/mux" pid=1880 4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0 Please add the following line to /etc/apparmor.d/usr.sbin.slapd: /{,var/}run/saslauthd/mux rw, Ubuntu version: Ubuntu 14.04.4 LTS slapd version: 2.4.31-1+nmu2ubu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
My configs are: /etc/default/saslauthd: # # Settings for saslauthd daemon # Please read /usr/share/doc/sasl2-bin/README.Debian for details. # # Should saslauthd run automatically on startup? (default: no) START=yes # Description of this saslauthd instance. Recommended. # (suggestion: SASL Authentication Daemon) DESC="SASL Authentication Daemon" # Short name of this saslauthd instance. Strongly recommended. # (suggestion: saslauthd) NAME="saslauthd" # Which authentication mechanisms should saslauthd use? (default: pam) # # Available options in this Debian package: # getpwent -- use the getpwent() library function # kerberos5 -- use Kerberos 5 # pam -- use PAM # rimap -- use a remote IMAP server # shadow-- use the local shadow password file # sasldb-- use the local sasldb database file # ldap -- use LDAP (configuration is in /etc/saslauthd.conf) # # Only one option may be used at a time. See the saslauthd man page # for more information. # # Example: MECHANISMS="pam" MECHANISMS="kerberos5" # Additional options for this mechanism. (default: none) # See the saslauthd man page for information about mech-specific options. MECH_OPTIONS="" # How many saslauthd processes should we run? (default: 5) # A value of 0 will fork a new process for each connection. THREADS=5 # Other options (default: -c -m /var/run/saslauthd) # Note: You MUST specify the -m option or saslauthd won't run! # # WARNING: DO NOT SPECIFY THE -d OPTION. # The -d option will cause saslauthd to run in the foreground instead of as # a daemon. This will PREVENT YOUR SYSTEM FROM BOOTING PROPERLY. If you wish # to run saslauthd in debug mode, please run it by hand to be safe. # # See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information. # See the saslauthd man page and the output of 'saslauthd -h' for general # information about these options. # # Example for chroot Postfix users: "-c -m /var/spool/postfix/var/run/saslauthd" # Example for non-chroot Postfix users: "-c -m /var/run/saslauthd" # # To know if your Postfix is running chroot, check /etc/postfix/master.cf. # If it has the line "smtp inet n - y - - smtpd" or "smtp inet n - - - - smtpd" # then your Postfix is running in a chroot. # If it has the line "smtp inet n - n - - smtpd" then your Postfix is NOT # running in a chroot. OPTIONS="-c -m /var/run/saslauthd" /etc/ldap/sasl2/slapd.conf: mech_list: plain pwcheck_method: saslauthd As the reporter of this bug stated, AppArmor denies slapd access to the saslauthd socket /run/saslauthd/mux. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1557157 Title: apparmor profile denied for saslauthd: /run/saslauthd/mux Status in openldap package in Ubuntu: Incomplete Bug description: When using slapd with saslauthd the processes communicate via the {,/var}/run/saslauthd/mux socket (this is the default location for the saslauthd server from the sasl2-bin package in the /etc/default/saslauthd config), but the apparmor profile for usr.sbin.slapd does not allow access to this socket/file. Syslog message: apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" name="/run/saslauthd/mux" pid=1880 4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0 Please add the following line to /etc/apparmor.d/usr.sbin.slapd: /{,var/}run/saslauthd/mux rw, Ubuntu version: Ubuntu 14.04.4 LTS slapd version: 2.4.31-1+nmu2ubu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp