[Desktop-packages] [Bug 2049515] Re: Import iwd 2.13-1 (universe) from Debian unstable/testing (main)
This bug was fixed in the package iwd - 2.13-1ubuntu1 --- iwd (2.13-1ubuntu1) noble; urgency=medium * Merge with Debian unstable. Remaining changes: (LP: #2049515) - debian/iwd.conf, debian/rules: - provide a network-manager configuration to make iwd the default backend when installed - debian/rules: - build with --enable-wired to avoid functional compared to wpa - disable lto, it's leading to a build issue iwd (2.13-1) unstable; urgency=medium [ upstream ] * new release [ Jonas Smedegaard ] * build-depend on systemd-dev (not systemd); closes: bug#1060583, thanks to Michael Biebl * update copyright info: update coverage iwd (2.12-1) unstable; urgency=medium [ upstream ] * new release iwd (2.11-1) unstable; urgency=medium [ upstream ] * new release iwd (2.10-1) unstable; urgency=medium [ upstream ] * new release(s) [ Jonas Smedegaard ] * tighten build-dependency on libell-dev * unfuzz patches -- Sudip Mukherjee Tue, 16 Jan 2024 18:45:49 + ** Changed in: iwd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iwd in Ubuntu. https://bugs.launchpad.net/bugs/2049515 Title: Import iwd 2.13-1 (universe) from Debian unstable/testing (main) Status in iwd package in Ubuntu: Fix Released Bug description: Please merge iwd 2.13-1 (universe) from Debian unstable (main) Explanation of the Ubuntu delta: Carry forward previous Ubuntu specific changes. 1. provide a network-manager configuration to make iwd the default backend when installed 2. build with --enable-wired to avoid functional compared to wpa 3. disable lto, it's leading to a build issue [ Original Bug Description ] A few versions have been released and Ubuntu Noble still has the 2.8 version (2.8-1ubuntu1). Could it be possible to import the latest version from Debian testing fixing a bunch of issues? Debian Changelog: iwd (2.13-1) unstable; urgency=medium [ upstream ] * new release [ Jonas Smedegaard ] * build-depend on systemd-dev (not systemd); closes: bug#1060583, thanks to Michael Biebl * update copyright info: update coverage -- Jonas Smedegaard <> Sun, 14 Jan 2024 09:22:07 +0100 iwd (2.12-1) unstable; urgency=medium [ upstream ] * new release -- Jonas Smedegaard <> Sat, 30 Dec 2023 03:44:28 +0100 iwd (2.11-1) unstable; urgency=medium [ upstream ] * new release -- Jonas Smedegaard <> Fri, 15 Dec 2023 22:28:36 +0100 iwd (2.10-1) unstable; urgency=medium [ upstream ] * new release(s) [ Jonas Smedegaard ] * tighten build-dependency on libell-dev * unfuzz patches -- Jonas Smedegaard <> Thu, 30 Nov 2023 12:08:59 +0100 IWD ChangeLog: ver 2.13: Fix issue with handling netconfig and roaming conditions. Fix issue with logging requirement for CMD_EXTERNAL_AUTH. Fix issue with using OpenSSL 3.2 installations. ver 2.12: Fix issue with DPP extra settings not being used. Fix issue with DPP and PRF+ handling on AARCH64. Add support for SAE password identifiers. ver 2.11: Fix issue with handling iovecs with multiple IEs. Fix issue with handling SAE password identifiers. Fix issue with handling agent release method call. ver 2.10: Fix issue with buffer overflow for 32 byte SSIDs. Fix issue with deauthentication before FT work completes. Fix issue with power save disabling procedure. ver 2.9: Fix issue with handling certain FT failures. Fix issue with handling user-disabled bands. Fix issue with handling roam on beacon loss event. Add support for PKEX configurator. Add support for PKEX enrollee. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/2049515/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049352] Re: Package BlueZ 5.72 for Noble
This bug was fixed in the package bluez - 5.72-0ubuntu1 --- bluez (5.72-0ubuntu1) noble; urgency=medium * New upstream release 5.72 (LP: #2049352): - Fix issue with BAP and handling stream IO linking. - Fix issue with BAP and setup of multiple streams per endpoint. - Fix issue with AVDTP and potential incorrect transaction label. - Fix issue with A2DP and handling crash on suspend. - Fix issue with GATT database and an invalid pointer. - Add support for AICS service. * Add bluetoothctl.1 man page to bluez package. -- Daniel van Vugt Tue, 16 Jan 2024 15:15:23 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049352 Title: Package BlueZ 5.72 for Noble Status in bluez package in Ubuntu: Fix Released Bug description: ver 5.72: Fix issue with BAP and handling stream IO linking. Fix issue with BAP and setup of multiple streams per endpoint. Fix issue with AVDTP and potential incorrect transaction label. Fix issue with A2DP and handling crash on suspend. Fix issue with GATT database and an invalid pointer. Add support for AICS service. https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.72.tar.xz https://git.kernel.org/pub/scm/bluetooth/bluez.git/tag/?h=5.72 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028172] Re: Cups-browsed cannot bind to port 631 as non-root user on Ubuntu 23.04
This bug was fixed in the package cups-browsed - 2.0.0-0ubuntu3 --- cups-browsed (2.0.0-0ubuntu3) noble; urgency=medium * Added dependencies on pkgconf and cups >= 2.4.6-0ubuntu3 to to the cups-browsed-tests binary package, to make the autopkgtest work (LP: #2028172). -- Till Kamppeter Tue, 16 jan 2024 12:16:33 -0300 ** Changed in: cups-browsed (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2028172 Title: Cups-browsed cannot bind to port 631 as non-root user on Ubuntu 23.04 Status in cups-browsed package in Ubuntu: Fix Released Bug description: After upgrading to Ubuntu 23.04, my laptop failed to discover our print server. The problem seems to have been caused by a new change in cups-browsed that was added to Ubuntu 23.04. I looked into it and found a small fix that seems to solve my issue. Using the debug configuration for cupsd and cups-browsed, I looked through the logs and noticed the following line: failed to bind CUPS Browsing socket: Permission denied After reading more about printer advertisement and cups-browsed, I concluded that the printer is shared to my Ubuntu 23.04 laptop via CUPS on port 631. When I connected an Ubuntu 22.04 laptop to the WIFI network, I saw the printer really was being shared with CUPS on port 631. Cups-browsed was running as root on 22.04 while on 23.04 it is running as a new user - cups-browsed, but this new user didn't seem to have the necessary permissions to open a listening socket on port 631. The solution I tried was granting the relevant binding permissions to the binary with this command (on the 23.04): setcap cap_net_bind_service+ep /usr/sbin/cups-browsed After giving the permissions, my computer successfully discovered the printer, just like it used to on 22.04! I think the command should be added to the post install script or maybe the capability should be granted to the new cups-browsed user. I posted it as an issue in the CUPS project on github. They told me to post it here because its an Ubuntu issue: https://github.com/OpenPrinting/cups-browsed/issues/17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2028172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048931] Re: [noble] extension pref dialog turns hidden
** Changed in: gjs (Ubuntu) Status: Triaged => Fix Committed ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Invalid ** Tags added: fixed-in-gjs-1.79.2 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2048931 Title: [noble] extension pref dialog turns hidden Status in gjs: Fix Released Status in GNOME Shell: New Status in gjs package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Invalid Bug description: Hi, I get this after: 1) open Extensions app 2) open a pref 3) prefs window after a quarter of second gets hidden 4) no way to access this window JS ERROR: Gio.IOErrorEnum: GDBus.Error:org.gnome.gjs.JSError.Error: Already showing a prefs dialog asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 _init/GLib.MainLoop.prototype.runAsync/https://bugs.launchpad.net/gjs/+bug/2048931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048931] Re: [noble] extension pref dialog turns hidden
** Changed in: gjs Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2048931 Title: [noble] extension pref dialog turns hidden Status in gjs: Fix Released Status in GNOME Shell: New Status in gjs package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, I get this after: 1) open Extensions app 2) open a pref 3) prefs window after a quarter of second gets hidden 4) no way to access this window JS ERROR: Gio.IOErrorEnum: GDBus.Error:org.gnome.gjs.JSError.Error: Already showing a prefs dialog asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 _init/GLib.MainLoop.prototype.runAsync/https://bugs.launchpad.net/gjs/+bug/2048931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988754] Re: libreoffice writer crashes when edit the page break
** Changed in: df-libreoffice Importance: Medium => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1988754 Title: libreoffice writer crashes when edit the page break Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 22.04.1 and also in LinuxMint 21. I have tried also using LibreOffice from ppa and it still crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729433]
*** Bug 158964 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1729433 Title: LibreOffice doesn't remember window size when running under Wayland Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice package in Fedora: Confirmed Bug description: 1. Open any LibreOffice document, e.g., a Writer or Calc document. 2. Make the window a reasonable, non-maximized size. 3. Maximize the window. 4. Close LibreOffice. 5. Open the document again; it will open maximized. 6. Un-maximize the window. 7. Observe how the window has a ridiculously small size, not its previously unmaximized size. LibreOffice or gnome-shell bug? Not sure. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-core 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 16:21:29 2017 InstallationDate: Installed on 2017-05-19 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806385]
Dear Rüdiger Kupper, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1806385 Title: [upstream] Creating a new slide by double click not working correctly Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Version: 6.1.3.2 Build-ID: libreoffice-6.1.3.2-snap1 You can create new slides in impress by double clicking on the empty part of the slides pane (below the existing slide). However, this works only as expected while the slides pane actually has empty space at the bottom. As soon as I have created a few slides, the slides pane is completely filled, and two things happen: (1) Improvement: It is very hard to double click on the thin white space at the bottom of the filled slides pane. This could be improved by always letting a few pixels at the bottom to click on. (2) Bug: You can actually manage to double click there and this creates a new slide. However, this new slide is not filed at the end of slides (as it should) but appears at a strange location somewhere in the middle of slides. This is definitely wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1806385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988754]
Still reproducible in Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ef6083200a4f28e43198c7a0878da6f4b880725f CPU threads: 8; OS: Linux 6.1; UI render: default; VCL: x11 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1988754 Title: libreoffice writer crashes when edit the page break Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 22.04.1 and also in LinuxMint 21. I have tried also using LibreOffice from ppa and it still crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043958] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("FONTCONFIG_SYSROOT") from IA__FcConfigCreate() from FcInitLoadOwnConfig() from FcInitLoadOwnConfigAndFonts() from
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2043958
Title:
gnome-shell crashed with SIGSEGV in __GI_getenv("FONTCONFIG_SYSROOT")
from IA__FcConfigCreate() from FcInitLoadOwnConfig() from
FcInitLoadOwnConfigAndFonts() from IA__FcInitLoadConfigAndFonts()
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
45.1-1ubuntu1, the problem page at
https://errors.ubuntu.com/problem/c4d852b67163763f6ebf416e212eb366999c17b8
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043958/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049752] Re: gnome-shell crashed with SIGSEGV in __GI_getenv()
*** This bug is a duplicate of bug 2043958 ***
https://bugs.launchpad.net/bugs/2043958
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2043958, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 2043958
gnome-shell crashed with SIGSEGV in __GI_getenv("FONTCONFIG_SYSROOT") from
IA__FcConfigCreate() from FcInitLoadOwnConfig() from
FcInitLoadOwnConfigAndFonts() from IA__FcInitLoadConfigAndFonts()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2049752
Title:
gnome-shell crashed with SIGSEGV in __GI_getenv()
Status in gnome-shell package in Ubuntu:
New
Bug description:
New noble version
ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: gnome-shell 45.3-1ubuntu1
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Greeter:GNOME
Date: Thu Jan 18 12:22:32 2024
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2024-01-18 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/false
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45.3-1ubuntu1
SegvAnalysis:
Segfault happened at: 0x7e9568201e5d <__GI_getenv+77>: cmp
(%rbx),%r12b
PC (0x7e9568201e5d) ok
source "(%rbx)" (0x621392096246) not located in a known VMA region (needed
readable region)!
destination "%r12b" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
__GI_getenv (name=0x7e956533813e "FONTCONFIG_SYSROOT") at
./stdlib/getenv.c:31
FcConfigCreate () from /lib/x86_64-linux-gnu/libfontconfig.so.1
?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1
FcInit () from /lib/x86_64-linux-gnu/libfontconfig.so.1
Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2049752/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047008] Re: [SRU] Add Telit FN990 compositions
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Released Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
> Normally, it is not. Rust compilers, even in the stable channel, include > the complete logic of a nightly compiler. The logic is disabled by > default during the runtime when the compiler is in the stable channel. It is reassuring to learn that. > I hope my explanation makes sense. It does, and thanks again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
> I.e., is there an increased risk in using RUSTC_BOOTSTRAP in a non-nightly compiler (the proposed case for us downstream) in comparison to using the unstable options in a nightly compiler (what upstream does)? Normally, it is not. Rust compilers, even in the stable channel, include the complete logic of a nightly compiler. The logic is disabled by default during the runtime when the compiler is in the stable channel. The reason why the variable is called "RUSTC_BOOTSTRAP" is that this functionality is usually required when building the next version of the Rust compiler. In this case, the Rust compiler needs to understand newer syntax unavailable in the previous version. I hope my explanation makes sense. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
Verified on a few different reference boards internally by running a set of 3 Unigine benchmarks with the updated mesa on the following: Stormpeak W/Radeon 7900 XTX Stormpeak W/Radeon Pro W7500 Stormpeak W/Radeon Pro W7900 Phoenix AMD Ryzen 7 7840U W/AMD Radeon™ 780M Phoenix2 AMD Ryzen 5 7545U W/AMD Radeon™ 740M verified also on a couple different pre-production platforms. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
Thanks for that suggestion, looks like just what I needed. I looked it up and found this: > The build system sets RUSTC_BOOTSTRAP=1. This special variable means to break the stability guarantees of rust: Allow using #![feature(...)] with a compiler that's not nightly. This should never be used except when bootstrapping the compiler. Is it reasonable to dismiss that foreboding statament on the premise that we, as downstream, are not the ones introducing the usage of those unstable features and as such trust upstream to know what they are doing? I.e., is there an increased risk in using RUSTC_BOOTSTRAP in a non-nightly compiler (the proposed case for us downstream) in comparison to using the unstable options in a nightly compiler (what upstream does)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049434] Re: Nautilus crashes when trying to open file options in administrator mode
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2049434/+attachment/5740512/+files/prevjournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2049434 Title: Nautilus crashes when trying to open file options in administrator mode Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 23.10 nautilus 1:45~rc-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 16 00:46:25 2024 InstallationDate: Installed on 2024-01-11 (4 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2049434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049434] Re: Nautilus crashes when trying to open file options in administrator mode
https://errors.ubuntu.com/oops/f6fd9128-b646-11ee-b9e5-fa163e171f02 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2049434/+attachment/5740511/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2049434 Title: Nautilus crashes when trying to open file options in administrator mode Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 23.10 nautilus 1:45~rc-1ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 16 00:46:25 2024 InstallationDate: Installed on 2024-01-11 (4 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=ru_RU.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2049434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2029010] Re: dummy sound on huawei mate d15 laptop
** Changed in: linux Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2029010 Title: dummy sound on huawei mate d15 laptop Status in Linux: New Status in alsa-driver package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried different options, but I couldn't raise the sound. saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd03c irq 80 1 [acp]: acp - acp HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2 saber716rus@saber716rus-BOM-WXX9 ~> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2029010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047008] Update Released
The verification of the Stable Release Update for modemmanager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Released Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047008] Re: [SRU] Add Telit FN990 compositions
This bug was fixed in the package modemmanager - 1.20.0-1~ubuntu22.04.3 --- modemmanager (1.20.0-1~ubuntu22.04.3) jammy; urgency=medium * Backport the newer modemmanager commits from 1.20.6 to the LTS as part of new hardware enablement including Telit FN990 modem (lp: #2047008) -- Laider Lai Wed, 20 Dec 2023 05:35:16 + ** Changed in: modemmanager (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Released Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047008] Re: [SRU] Add Telit FN990 compositions
Thank you for the detailed and unambiguous verification! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/2047008 Title: [SRU] Add Telit FN990 compositions Status in OEM Priority Project: Fix Committed Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Jammy: Fix Released Bug description: [SRU] Add Telit FN990 compositions [ Impact ] The modemmanager v1.20.0 doesn't have Telit FN990 compositions. It works with compatibility mode. (lp: #2046699) [ Test Plan ] Under Jammy environment, check modemmanager can identify Telit FN990 modem correctly. [ Where problems could occur ] The Telit FN990 compositions is upstreamed to modemmanager v1.20.6 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/b68a1bb8474991a72cf988e8e24ba6549f1cf9c2 Noble and Mantic already working with modemmanager v1.20.6. The target platform modem function works well on Mantic. The change parts just only add VID/PIDs for Telit's FN990 modems under the Telit plugin. [ Other Info ] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2029010] Re: dummy sound on huawei mate d15 laptop
we found a solution for my problem together with Marian Postevca. He made a patch, and there is also an alsa regression. A temporary solution is described here. https://github.com/codepayne/linux-sound-huawei/issues/26#issuecomment-1837502247 ** Bug watch added: github.com/codepayne/linux-sound-huawei/issues #28 https://github.com/codepayne/linux-sound-huawei/issues/28 ** Changed in: linux Importance: High => Unknown ** Changed in: linux Status: Confirmed => Unknown ** Changed in: linux Remote watch: Linux Kernel Bug Tracker #215119 => github.com/codepayne/linux-sound-huawei/issues #28 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2029010 Title: dummy sound on huawei mate d15 laptop Status in Linux: Unknown Status in alsa-driver package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: I tried different options, but I couldn't raise the sound. saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)" VERSION_ID="21" HOME_URL="https://greenlinux.ru/; SUPPORT_URL="https://forum.linuxmint.su/; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/; PRIVACY_POLICY_URL="https://greenlinux.ru/; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xd03c irq 80 1 [acp]: acp - acp HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2 saber716rus@saber716rus-BOM-WXX9 ~> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2029010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
> Since I encountered the same error before and was able to overcome it by manually removing all instances of that unstable option from the build files, I'll try that strategy again. It is in general a boring process because those options are generated during build and I couldn't track down their originators; they are not to be found literally in the source files, and so I removed them iteratively with a ad-hoc (and rather embarrassing :p) You have an easy option here: There is a somewhat undocumented rustc feature where you could trick it into thinking it is a nightly compiler: just add `RUSTC_BOOTSTRAP: 1` under the `environment` section in your YAML file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2049493 Title: Newer rustc version needed in jammy to build chromium updates Status in chromium-browser package in Ubuntu: New Status in rustc package in Ubuntu: New Bug description: The next chromium version is making rustc mandatory to build. Chromium is a snap built from core22 so using the jammy packages, the build is currently failing because it needs libprofiler_builtins.rlib which isn't available. Upstream provides toolchain builds that can be used but only for amd64 so currently the snap is failing to build on arm https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta The version upstream is using is 1.75 but it's possible that a lower version would be enough for now if libprofiler was enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x
IMO the wpasupplicant trigger is a red herring, as we see the same
failure on a trigger=system/255... test case:
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/n/netplan.io/20240104_111341_511f7@/log.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails with "systemd units changed without reload" on
s390x
Status in netplan:
Invalid
Status in netplan.io package in Ubuntu:
Triaged
Status in wpa package in Ubuntu:
New
Bug description:
The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
often fails with
AssertionError: systemd units changed without reload
Looking at the history of autopkgtest runs, it looks like that the
error does not always occur during execution of a specific test. I've
seen occurrences of this error during the following test-cases:
test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL
Example [1]:
781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
781s --
781s Traceback (most recent call last):
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line
189, in test_dhcp6
781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in
generate_and_settle
781s self.fail('systemd units changed without reload')
781s AssertionError: systemd units changed without reload
[1] https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049708] Re: bluez bluetoothd unable to locate executable
Found a rouge service (not from the ubuntu distro but instead my custom nvidia tegra BSP) that had the `/usr/lib/bluetooth/bluetoothd` path in it. Closing as removing or altering that service fixes it. ** Changed in: bluez (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2049708 Title: bluez bluetoothd unable to locate executable Status in bluez package in Ubuntu: Invalid Bug description: Release: Ubuntu Noble Dev Branch the location of bluetoothd was just changed to /usr/libexec/bluetooth/bluetoothd this causes bluetooth to fail to start since something is still looking for the old location Jan 17 21:23:26 switch systemd[1]: Starting bluetooth.service - Bluetooth service... ░░ Subject: A start job for unit bluetooth.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit bluetooth.service has begun execution. ░░ ░░ The job identifier is 2843. Jan 17 21:23:26 switch (uetoothd)[3245]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDire> Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory ░░ Subject: Process /usr/lib/bluetooth/bluetoothd could not be executed ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ The process /usr/lib/bluetooth/bluetoothd could not be executed and failed. ░░ ░░ The error number returned by this process is ERRNO. Jan 17 21:23:26 switch (uetoothd)[3245]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory the system service ExecStart location was correctly updated so not sure what still has the old location cat /lib/systemd/system/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049708/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049236] Re: Chromium queuing my application requests
OK, feel free to reset the bug if the problem re-appears. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2049236 Title: Chromium queuing my application requests Status in chromium-browser package in Ubuntu: Incomplete Bug description: I have web application with frontend and backend served behind nginx proxy with HTTP 2 enabled. My application is loading very slow, because some requests are put into queue for 1s. This only happening with chromium. I tested with Newest Edge, Firefox and Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails with "systemd units changed without reload" on
s390x
Status in netplan:
Invalid
Status in netplan.io package in Ubuntu:
Triaged
Status in wpa package in Ubuntu:
New
Bug description:
The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
often fails with
AssertionError: systemd units changed without reload
Looking at the history of autopkgtest runs, it looks like that the
error does not always occur during execution of a specific test. I've
seen occurrences of this error during the following test-cases:
test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL
Example [1]:
781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
781s --
781s Traceback (most recent call last):
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line
189, in test_dhcp6
781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
781s File
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in
generate_and_settle
781s self.fail('systemd units changed without reload')
781s AssertionError: systemd units changed without reload
[1] https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049670] Re: noble: gnome-initial-setup 20 second delay & error popup
Yes I think this bug is the same as my https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2049596 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2049670 Title: noble: gnome-initial-setup 20 second delay & error popup Status in gnome-initial-setup package in Ubuntu: Confirmed Status in ubuntu-report package in Ubuntu: Confirmed Bug description: When GNOME Initial Setup is run in Ubuntu 24.04 LTS (the current development release), when clicking Next on the "Help improve Ubuntu" screen, the Initial Setup pauses for 20 seconds then shows a popup dialog (screenshot attached). This happens regardless of whether Yes or No is chosen on that screen. Sometimes, the app might go to the next screen and close the popup dialog itself. Logs GNOME Initial Setup can be run from the command line by running /usr/libexec/gnome-initial-setup --existing-user When run from the command line, these warnings are emitted: InitialSetup-Message: Starting gnome-initial-setup InitialSetup-Message: Production mode: changes will be saved to disk INFO[0003] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open /var/lib/ubuntu_dist_channel: no such file or directory (gnome-initial-setup): InitialSetup-WARNING **: Failed to send report information: data were not delivered successfully to metrics server, saving for a later automated report: couldn't send post http request: Post "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded (Client.Timeout exceeded while awaiting headers) INFO[0107] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open /var/lib/ubuntu_dist_channel: no such file or directory Logs 2 == If No is selected, the command-line warning is slightly different. Failed to send report decline: data were not delivered successfully to metrics server, saving for a later automated report: couldn't send post http request: Post "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Other Info == Perhaps the metrics server is not set up for Ubuntu 24.04 LTS yet? This bug is related to bug 1761742 and I agree with comment #3 there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2049670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049670] Re: noble: gnome-initial-setup 20 second delay & error popup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-report (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2049670 Title: noble: gnome-initial-setup 20 second delay & error popup Status in gnome-initial-setup package in Ubuntu: Confirmed Status in ubuntu-report package in Ubuntu: Confirmed Bug description: When GNOME Initial Setup is run in Ubuntu 24.04 LTS (the current development release), when clicking Next on the "Help improve Ubuntu" screen, the Initial Setup pauses for 20 seconds then shows a popup dialog (screenshot attached). This happens regardless of whether Yes or No is chosen on that screen. Sometimes, the app might go to the next screen and close the popup dialog itself. Logs GNOME Initial Setup can be run from the command line by running /usr/libexec/gnome-initial-setup --existing-user When run from the command line, these warnings are emitted: InitialSetup-Message: Starting gnome-initial-setup InitialSetup-Message: Production mode: changes will be saved to disk INFO[0003] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open /var/lib/ubuntu_dist_channel: no such file or directory (gnome-initial-setup): InitialSetup-WARNING **: Failed to send report information: data were not delivered successfully to metrics server, saving for a later automated report: couldn't send post http request: Post "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded (Client.Timeout exceeded while awaiting headers) INFO[0107] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open /var/lib/ubuntu_dist_channel: no such file or directory Logs 2 == If No is selected, the command-line warning is slightly different. Failed to send report decline: data were not delivered successfully to metrics server, saving for a later automated report: couldn't send post http request: Post "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Other Info == Perhaps the metrics server is not set up for Ubuntu 24.04 LTS yet? This bug is related to bug 1761742 and I agree with comment #3 there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2049670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046162] Re: RDP Remote Desktop automatically closes abnormally and refuses to connect.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-remote-desktop (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2046162 Title: RDP Remote Desktop automatically closes abnormally and refuses to connect. Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: taichu@taichu-System:~$ journalctl --user-unit=gnome-remote-desktop -f 12月 11 22:39:56 taichu-System gnome-remote-de[2789012]: Unable to check file descriptor, closing connection 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: onnection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:38:43:794] [2789012:2873403] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:38:43:794] [2789012:2873403] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:38:43:794] [2789012:2873403] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:06:840] [2789012:2873497] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:06:840] [2789012:2873497] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:06:840] [2789012:2873497] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:15:892] [2789012:2873568] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:15:892] [2789012:2873568] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:15:892] [2789012:2873568] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:33:078] [2789012:2874536] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:33:078] [2789012:2874536] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:33:078] [2789012:2874536] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:55:567] [2789012:2874729] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:55:567] [2789012:2874729] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:55:567] [2789012:2874729] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:19:945] [2789012:2874839] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:19:945] [2789012:2874839] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:19:945] [2789012:2874839] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:27:704] [2789012:2874906] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:27:704] [2789012:2874906] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:27:704] [2789012:2874906] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:45:512] [2789012:2875009] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:45:512] [2789012:2875009] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]:
[Desktop-packages] [Bug 2046162] Re: RDP Remote Desktop automatically closes abnormally and refuses to connect.
Same issue here. 1月 18 21:28:00 hostname gnome-remote-desktop-daemon[23759]: [21:28:00:899] [23759:47299] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 1月 18 21:28:00 hostname gnome-remote-desktop-daemon[23759]: [21:28:00:899] [23759:47299] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 1月 18 21:28:08 hostname gnome-remote-desktop-daemon[23759]: [21:28:00:899][21:28:08:847] [23759:47299] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] 1月 18 21:28:08 hostname gnome-remote-desktop-daemon[23759]: [21:28:08:929] [23759:47299] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] 1月 18 21:28:09 hostname gnome-remote-desktop-daemon[23759]: [21:28:09:011] [23759:47299] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer 1月 18 21:28:09 hostname gnome-remote-desktop-daemon[23759]: [21:28:09:011] [23759:47299] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D] 1月 18 21:28:09 hostname gnome-remote-desktop-daemon[23759]: [21:28:09:011] [23759:47299] [ERROR][com.freerdp.core.nla] - [nla_recv] error: -1 1月 18 21:28:09 hostname gnome-remote-desktop-daemon[23759]: [21:28:09:011] [23759:47299] [ERROR][com.freerdp.core.transport] - client authentication failure 1月 18 21:28:09 hostname gnome-remote-desktop-daemon[23759]: [21:28:09:011] [23759:47299] [ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_INITIAL - rdp_server_accept_nego() fail 1月 18 21:28:09 hostname gnome-remote-desktop-daemon[23759]: [21:28:09:011] [23759:47299] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -1 1月 18 21:28:09 hostname gnome-remote-de[23759]: Unable to check file descriptor, closing connection 1月 18 21:28:09 hostname gnome-remote-desktop-daemon[23759]: [21:28:09:011] [23759:23759] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe 1月 18 21:28:09 hostname gnome-remote-desktop-daemon[23759]: [21:28:09:364] [23759:47321] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312] 1月 18 21:28:09 hostname gnome-remote-desktop-daemon[23759]: [21:28:09:447] [23759:47321] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313] 1月 18 21:28:10 hostname gnome-remote-de[23759]: Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Session creation inhibited 1月 18 21:28:10 hostname gnome-remote-desktop-daemon[23759]: [21:28:10:461] [23759:23759] [ERROR][com.freerdp.core] - rdp_set_error_info:freerdp_set_last_error_ex ERRINFO_RPC_INITIATED_DISCONNECT [0x00010001] Distributor ID: Ubuntu Description:Ubuntu 22.04.3 LTS Release:22.04 Codename: jammy Package: gnome-remote-desktop Version: 42.9-0ubuntu0.22.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2046162 Title: RDP Remote Desktop automatically closes abnormally and refuses to connect. Status in gnome-remote-desktop package in Ubuntu: Confirmed Bug description: taichu@taichu-System:~$ journalctl --user-unit=gnome-remote-desktop -f 12月 11 22:39:56 taichu-System gnome-remote-de[2789012]: Unable to check file descriptor, closing connection 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: onnection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:38:43:794] [2789012:2873403] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:38:43:794] [2789012:2873403] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:38:43:794] [2789012:2873403] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:06:840] [2789012:2873497] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:06:840] [2789012:2873497] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:06:840] [2789012:2873497] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:15:892] [2789012:2873568] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System
[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written
** Changed in: firefox Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168]
Thanks, do you know what ubuntu release currently has that out of `-proposed` ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168]
(In reply to :gerard-majax from comment #56) > Thanks, do you know what ubuntu release currently has that out of `-proposed` > ? Tested on 22.04 it's not yet backported, but it looks to be working on uptodate 23.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168]
For 23.10, as soon as version 45.1 enters, it will be fixed. For 22.04 I prepared a SRU, but since it's a LTS version, it's a slow process. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168]
Yes, this can be considered as fixed. It was merged in upstream (gnome 46), and also backported to Gnome 45. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971168]
Thanks! What is the status, can we considered this as fixed? assuming we have to wait for backports? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046150] Re: [BPO] libreoffice 7.5.9 for jammy
** Changed in: libreoffice (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2046150 Title: [BPO] libreoffice 7.5.9 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Released Bug description: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/4:7.5.9-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1776/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15416837/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231208_123108_1b879@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231208_175608_c3b14@/log.gz * [armhf] ... (autopkgtests infra problems on this arch) * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231208_135706_f6680@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231208_150850_45529@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2046150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Actually, not that scary. I think I can implement a complete solution as a single kernel patch. Just extend fbcon's deferred takeover feature to wait until a certain timeout has passed. And if "splash" is present then you can assume that should be a default of 10 seconds to wait for Plymouth's 8 second device timeout. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049596] Re: Failed to send report information: data not delivered
*** This bug is a duplicate of bug 2049670 *** https://bugs.launchpad.net/bugs/2049670 I'm going to mark this a duplicate of bug 2049670 since there's more engagement there. Thank you for reporting this bug and helping to make Ubuntu better! ** This bug has been marked a duplicate of bug 2049670 noble: gnome-initial-setup 20 second delay & error popup -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2049596 Title: Failed to send report information: data not delivered Status in ubuntu-report package in Ubuntu: New Bug description: After install click to 'send info to canonical' 'help to improve Ubuntu' fails with msg: Failed to send report information... see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-report 1.7.2 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 10:06:35 2024 InstallationDate: Installed on 2024-01-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240117) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-report UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2049596/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049670] Re: noble: gnome-initial-setup 20 second delay & error popup
I'm adding a ubuntu-report task because it appears like there is backend work that needs to be done here too. This is inspired by bug 2049596 which I've marked as a duplicate of this bug, but we could unduplicate it if we want to handle that issue separately. ** Also affects: ubuntu-report (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2049670 Title: noble: gnome-initial-setup 20 second delay & error popup Status in gnome-initial-setup package in Ubuntu: Confirmed Status in ubuntu-report package in Ubuntu: New Bug description: When GNOME Initial Setup is run in Ubuntu 24.04 LTS (the current development release), when clicking Next on the "Help improve Ubuntu" screen, the Initial Setup pauses for 20 seconds then shows a popup dialog (screenshot attached). This happens regardless of whether Yes or No is chosen on that screen. Sometimes, the app might go to the next screen and close the popup dialog itself. Logs GNOME Initial Setup can be run from the command line by running /usr/libexec/gnome-initial-setup --existing-user When run from the command line, these warnings are emitted: InitialSetup-Message: Starting gnome-initial-setup InitialSetup-Message: Production mode: changes will be saved to disk INFO[0003] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open /var/lib/ubuntu_dist_channel: no such file or directory (gnome-initial-setup): InitialSetup-WARNING **: Failed to send report information: data were not delivered successfully to metrics server, saving for a later automated report: couldn't send post http request: Post "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded (Client.Timeout exceeded while awaiting headers) INFO[0107] no DCD information: couldn't open /var/lib/ubuntu_dist_channel: open /var/lib/ubuntu_dist_channel: no such file or directory Logs 2 == If No is selected, the command-line warning is slightly different. Failed to send report decline: data were not delivered successfully to metrics server, saving for a later automated report: couldn't send post http request: Post "https://metrics.ubuntu.com/ubuntu/desktop/24.04": context deadline exceeded (Client.Timeout exceeded while awaiting headers) Other Info == Perhaps the metrics server is not set up for Ubuntu 24.04 LTS yet? This bug is related to bug 1761742 and I agree with comment #3 there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/2049670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049493] Re: Newer rustc version needed in jammy to build chromium updates
The build failed[1] with
error: the option `Z` is only accepted on the nightly compiler
In the ideal world that nightly Rustc would be used, but given the
nature of deb packaging I suppose it is not doable.
Since I encountered the same error before and was able to overcome it by
manually removing all instances of that unstable option from the build
files, I'll try that strategy again. It is in general a boring process
because those options are generated during build and I couldn't track
down their originators; they are not to be found literally in the source
files, and so I removed them iteratively with a ad-hoc (and rather
embarrassing :p)
--->
find / -type f -name '*.ninja' -exec grep -Fq Zmacro-backtrace {} \; \
-exec sed -i \
's/-Zdep-info-omit-d-target//g;s/-Zmacro-backtrace//g;s/-Zremap-cwd-prefix=.//g'
\
{} +
<---
Additionally, near the end of the build (the one with the old Rustc to
be clear) things there were multiple undefined references[2], but I
reckon that was because the libprofiler_builtins.rlib was not available
and not because of the removal of the -Z options.
I'm submitting another build with the -Z options again removed and will
report back with the results once available.
[1]
https://launchpadlibrarian.net/709883798/buildlog_snap_ubuntu_jammy_arm64_chromium-rust_BUILDING.txt.gz
[2]
https://launchpadlibrarian.net/708915623/buildlog_snap_ubuntu_jammy_armhf_chromium-rust_BUILDING.txt.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2049493
Title:
Newer rustc version needed in jammy to build chromium updates
Status in chromium-browser package in Ubuntu:
New
Status in rustc package in Ubuntu:
New
Bug description:
The next chromium version is making rustc mandatory to build. Chromium
is a snap built from core22 so using the jammy packages, the build is
currently failing because it needs libprofiler_builtins.rlib which
isn't available.
Upstream provides toolchain builds that can be used but only for amd64 so
currently the snap is failing to build on arm
https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-beta
The version upstream is using is 1.75 but it's possible that a lower
version would be enough for now if libprofiler was enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2049493/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049752] Re: gnome-shell crashed with SIGSEGV in __GI_getenv()
** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2049752 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() Status in gnome-shell package in Ubuntu: New Bug description: New noble version ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 18 12:22:32 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2024-01-18 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7e9568201e5d <__GI_getenv+77>: cmp (%rbx),%r12b PC (0x7e9568201e5d) ok source "(%rbx)" (0x621392096246) not located in a known VMA region (needed readable region)! destination "%r12b" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7e956533813e "FONTCONFIG_SYSROOT") at ./stdlib/getenv.c:31 FcConfigCreate () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 FcInit () from /lib/x86_64-linux-gnu/libfontconfig.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2049752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049752] [NEW] gnome-shell crashed with SIGSEGV in __GI_getenv()
Public bug reported: New noble version ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 18 12:22:32 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2024-01-18 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7e9568201e5d <__GI_getenv+77>: cmp(%rbx),%r12b PC (0x7e9568201e5d) ok source "(%rbx)" (0x621392096246) not located in a known VMA region (needed readable region)! destination "%r12b" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7e956533813e "FONTCONFIG_SYSROOT") at ./stdlib/getenv.c:31 FcConfigCreate () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 FcInit () from /lib/x86_64-linux-gnu/libfontconfig.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace noble ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2049752 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() Status in gnome-shell package in Ubuntu: New Bug description: New noble version ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 18 12:22:32 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2024-01-18 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7e9568201e5d <__GI_getenv+77>: cmp (%rbx),%r12b PC (0x7e9568201e5d) ok source "(%rbx)" (0x621392096246) not located in a known VMA region (needed readable region)! destination "%r12b" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7e956533813e "FONTCONFIG_SYSROOT") at ./stdlib/getenv.c:31 FcConfigCreate () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 ?? () from /lib/x86_64-linux-gnu/libfontconfig.so.1 FcInit () from /lib/x86_64-linux-gnu/libfontconfig.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2049752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049596] Re: Failed to send report information: data not delivered
attaching journalctl of the 1st boot ** Attachment added: "boo.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2049596/+attachment/5740448/+files/boo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2049596 Title: Failed to send report information: data not delivered Status in ubuntu-report package in Ubuntu: New Bug description: After install click to 'send info to canonical' 'help to improve Ubuntu' fails with msg: Failed to send report information... see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-report 1.7.2 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 10:06:35 2024 InstallationDate: Installed on 2024-01-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240117) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-report UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2049596/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049596] Re: Failed to send report information: data not delivered
Again on system installed from ISO dated 24-01-18 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2049596 Title: Failed to send report information: data not delivered Status in ubuntu-report package in Ubuntu: New Bug description: After install click to 'send info to canonical' 'help to improve Ubuntu' fails with msg: Failed to send report information... see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-report 1.7.2 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 10:06:35 2024 InstallationDate: Installed on 2024-01-17 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240117) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-report UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2049596/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
Verified this new mesa proposed on my end with oem-6.5, looks positive to launch Firefox with multiple tabs to play videos on YouTube. [Verification]: HP platform(Under development phase) AMD R9 PRO 8945HS w/ Radeon 780M Graphics -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in rust-bindgen package in Ubuntu: Invalid Status in rust-clang-sys package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in rust-bindgen source package in Jammy: Invalid Status in rust-clang-sys source package in Jammy: Invalid Bug description: [Impact] The graphics HWE stack from mantic needs to be backported for 22.04.4 directx-headers - build-dep of the new Mesa mesa - new major release (23.2.x) - new HW support, Meteor Lake.. [Test case] We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA blob after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point. - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*) - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2) Install the new packages and run some tests: - check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe - run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition) - run some games from Steam if possible and in each case check that there is no gfx corruption happening or worse. Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with mantic, we'd already know if there are serious issues. We will backport the final 23.2.x at a later stage, the first backport is needed for enabling Intel Meteor Lake. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
