[Desktop-packages] [Bug 2037228] Re: Firefox doesn't work after 23.10 upgrade
[Expired for snapd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: snapd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037228 Title: Firefox doesn't work after 23.10 upgrade Status in firefox package in Ubuntu: Expired Status in snapd package in Ubuntu: Expired Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Firefox doesn’t work after upgrading from 23.04 to 23.10 beta. The Firefox icon disappeared from my sidebar during the upgrade process. 'snap list' shows firefox stable is installed, trying to run the command firefox says: Command '/usr/bin/firefox' requires the firefox snap to be installed. Please install it with: snap install firefox $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu3 Candidate: 1:1snap1-0ubuntu3 Version table: *** 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+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 2037228] Re: Firefox doesn't work after 23.10 upgrade
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037228 Title: Firefox doesn't work after 23.10 upgrade Status in firefox package in Ubuntu: Expired Status in snapd package in Ubuntu: Expired Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Firefox doesn’t work after upgrading from 23.04 to 23.10 beta. The Firefox icon disappeared from my sidebar during the upgrade process. 'snap list' shows firefox stable is installed, trying to run the command firefox says: Command '/usr/bin/firefox' requires the firefox snap to be installed. Please install it with: snap install firefox $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu3 Candidate: 1:1snap1-0ubuntu3 Version table: *** 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+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 2044718] Re: mantic on raspberry5: x and/or lightdm problems
Reassigning to xorg-server initially. Ubuntu doesn't have gldriver-test to enable xorg desktops to work on a raspi5. So is there an equivalent package for Ubuntu or should gldriver-test be added to the ubuntu repo? ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2044718 Title: mantic on raspberry5: x and/or lightdm problems Status in linux-raspi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: New Bug description: running mantic on raspberry5, graphical sessions doesn't start unless on gdm3; while performing installation, Ubuntu Budgie graphical session goes on without problems but at reboot DE doesn't start. Tried installing "classical" ubuntu and DE came on w/o problems; installed budgie-desktop and lightdm side by side and budgie didn't start; installed sddm with same results. Only gdm3 works See attached logs collection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2044718/+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 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set
** No longer affects: tracker-miners (Ubuntu Noble) ** Changed in: tracker-miners (Ubuntu) Status: In Progress => Fix Committed ** No longer affects: gvfs (Ubuntu) ** No longer affects: gvfs (Ubuntu Bionic) ** No longer affects: gvfs (Ubuntu Jammy) ** No longer affects: gvfs (Ubuntu Focal) ** No longer affects: gvfs (Ubuntu Noble) ** No longer affects: gvfs (Ubuntu Mantic) ** No longer affects: gvfs (Ubuntu Lunar) ** No longer affects: gvfs (Ubuntu Kinetic) ** No longer affects: tracker-miners (Ubuntu Kinetic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1779890 Title: gvfsd process does not have the KRB5CCNAME environment set Status in tracker-miners package in Ubuntu: Fix Committed Status in tracker-miners source package in Bionic: Won't Fix Status in tracker-miners source package in Focal: In Progress Status in tracker-miners source package in Jammy: In Progress Status in tracker-miners source package in Lunar: In Progress Status in tracker-miners source package in Mantic: In Progress Bug description: [ Impact ] The KRB5CCNAME environment variable points to the Kerberos ticket of the current machine and this ticket is used for authentication in Active Directory servers. This variable is set by pam_sss when the user authenticates and can be used by other processes, such as gio, to skip the credentials input when accessing network shares, for example. Some services rely on gvfs-daemon in order to properly function, such as tracker-extract-3.service and tracker-miner-fs-3.service, which means they will ask for the gvfs-daemon to be initialized when they are executed by systemd. This creates problems if one service that relies on gvfsd is started too early, as it would result in gvfsd being started too early as well. As of version 3.1 of tracker-miners, the install target of tracker- miners-fs-3.service was set to gnome-session.target: https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/283 However, the tracker-extract-3.service was not updated and its target is still default.target, which is too early for the service to start. Starting tracker-extract too early is also starting gvfsd too early, before the session environment gets fully updated. Which means that gvfsd does not have the KRB5CCNAME variable and can not do any operations with it. Tracker-extract is supposed to be a helper service managed by tracker- miner-fs-3.service. By using a [Install] section, we are actually telling systemd that it should manage this service as well, when it shouldn't. So, by removing the [Install] section and having tracker-miner- fs-3.service being tied to gnome-session.target, we fix the issue of gvfsd starting too early without the updated session environment. [ Test Plan ] In order to test this issue, it's required to have an Active Directory server running. 1) Authenticate with an AD user (as this would set the KRB5CCNAME env); 2) Check gvfsd environment. This can be done by running: cat /proc/$(pidof gvfsd)/environ | xargs --null -n1 You will be able to see that it does not have the variable listed. 3) Check that the information mentioned above about tracker-miner-fs- 3.service is true. 4) Disable tracker-extract-3.service (This is a bit tricky, since its target was default.target. The easiest way is to remove the symlink that systemd created when enabling the unit, located under /etc/systemd/user/default.target.wants/tracker-extract-3.service 5) Reboot the machine; 6) Repeat steps 1 and 2. This will show that gvfsd is now started with the proper environment. Is not enough to look at ptree and the pids of the processes, instead it's better to look into the session logs with: journalctl --user -b And check the order in which the services were started and when they were triggered. Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf320070-test After installing test packages of tracker-miners, KRB5CCNAME should be set in gvfs environment upon login to gnome. [ Where problems could occur ] The tracker project is a search engine that speeds up search operations in Gnome. The tracker-miners is the indexing daemon that populates the database with information, so changing its start does not affect the system behavior. This changes fix the startup of gvfs-daemon.service, which could delay services that relied on it running to be executed. [ Other info ] This was fixed upstream by the following commit: commit 29a2320c1e4f0f7ced3c3e9d4d1c06c51518c1f3 From: Denison Barbosa Date: Tue, 21 Mar 2023 15:04:28 + Subject: Removing [Install] section from tracker-extract-3.service Link:
[Desktop-packages] [Bug 2045420] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build : Paramétrage de nvidia-340 (340.108-0ubuntu5.20.04.2) ... dpkg: erreur: mauvaise s
Public bug reported: mzt@mzt-R610:~$ sudo apt-get install -f E: dpkg a été interrompu. Il est nécessaire d'utiliser « sudo dpkg --configure -a » pour corriger le problème. mzt@mzt-R610:~$ sudo dpkg --configure -a Paramétrage de nvidia-340 (340.108-0ubuntu5.20.04.2) ... dpkg: erreur: mauvaise syntaxe de la version « - »: revision number is empty dpkg: erreur: mauvaise syntaxe de la version « - »: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Removing old nvidia-340-340.108 DKMS files... Uninstall Beginning Module: nvidia-340 Version: 340.108 Kernel: 5.4.0-42-generic (x86_64) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.15.0-89-generic Date: Fri Dec 1 17:13:40 2023 PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/2045420 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build : Paramétrage de nvidia-340 (340.108-0ubuntu5.20.04.2) ... dpkg: erreur: mauvaise syntaxe de la version « - »: revision number is empty Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: mzt@mzt-R610:~$ sudo apt-get install -f E: dpkg a été interrompu. Il est nécessaire d'utiliser « sudo dpkg --configure -a » pour corriger le problème. mzt@mzt-R610:~$ sudo dpkg --configure -a Paramétrage de nvidia-340 (340.108-0ubuntu5.20.04.2) ... dpkg: erreur: mauvaise syntaxe de la version « - »: revision number is empty dpkg: erreur: mauvaise syntaxe de la version « - »: revision number is empty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Removing old nvidia-340-340.108 DKMS files... Uninstall Beginning Module: nvidia-340 Version: 340.108 Kernel: 5.4.0-42-generic (x86_64) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.15.0-89-generic Date: Fri Dec 1 17:13:40 2023 PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2045420/+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 2044019] Re: [SRU] libreoffice 7.6.3 for mantic
For reference https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/log/?h=wip/mantic-7.6 -- 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/2044019 Title: [SRU] libreoffice 7.6.3 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Incomplete Bug description: [Impact] * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 (that's a total of 116 bugs): https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs 7.6.3 RC2 is identical to the 7.6.3 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_76/1459/ * 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. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15393176/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/amd64/libr/libreoffice/20231123_103407_283ac@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/arm64/libr/libreoffice/20231124_182414_cb6a2@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/armhf/libr/libreoffice/20231123_114914_bf535@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/ppc64el/libr/libreoffice/20231123_150619_c4055@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/s390x/libr/libreoffice/20231123_122430_41ff2@/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 minor release with a total of 116 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * 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/2044019/+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 2044019] Re: [SRU] libreoffice 7.6.3 for mantic
Hello, thank you for the detailed review. The packaging changes are addressing packaging errors and required changes for CMIS support. 4) 5) follow the upstream CMIS changes Upstream bumped the internal requirement of libcmis which finally allows the proper CMIS service support. Unfortunately it had to be disabled before because it was broken. Upstream chose Openssl as official choice for this feature/combination which was followed here. But it would be possible to continue using gnutls if the SRU requires it. 1) 2) 3) 6) are packaging bugs regarding Java support Those are needed to allow Java support to be disabled on specific archs if needed. Fortunately this wasn't required yet while the already applied mitigations to the bridgetests still are sufficient. (This would affect armhf, ppc64el and s390x. Those are not supported by upstream) -- 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/2044019 Title: [SRU] libreoffice 7.6.3 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Incomplete Bug description: [Impact] * LibreOffice 7.6.3 is in its third bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.3_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.3 (that's a total of 116 bugs): https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs 7.6.3 RC2 is identical to the 7.6.3 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_76/1459/ * 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. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15393176/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/amd64/libr/libreoffice/20231123_103407_283ac@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/arm64/libr/libreoffice/20231124_182414_cb6a2@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/armhf/libr/libreoffice/20231123_114914_bf535@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/ppc64el/libr/libreoffice/20231123_150619_c4055@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-libreoffice-libreoffice-prereleases/mantic/s390x/libr/libreoffice/20231123_122430_41ff2@/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 minor release with a total of 116 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * 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/2044019/+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 2044019] Re: [SRU] libreoffice 7.6.3 for mantic
Hi Rico,
Thanks for the nice and detailed SRU template, and all the testing.
While looking at this, particularly the changes in the packaging,
there are a few points that seem to warrant clarification, since
are apparently not related/supporting the upstream bug fixes, or
are not justified as to why included in a SRU (ie, which issues
or bugs are being addressed).
I checked most of these points with Andreas yesterday, and he too
agreed more details would be required before proceeding with this.
Could please address the points below? That's very appreciated.
Thanks again for all the effort on this!
cheers,
Mauricio
...
Changes:
$ debdiff libreoffice_7.6.2-0ubuntu1.dsc
libreoffice_7.6.3-0ubuntu0.23.10.1.dsc | filterdiff -i '*/debian/*'
There are some changes in debian/ that may warrant some clarification
as they do not fit into the SRU policy for minor release updates
(ie, bug-fix only) or to be related to the bugs fixed by upstream
(ie, to support a bug-fix).
I've looked for similarities in the changelog of previous releases,
but apparently haven't found them as precedents. This is the first
time I'm looking at this package, so I might be missing something.
I'll note specific changes in changelog/rules below, for clarity.
1)
d/changelog
18 +- don't try to install dbreport config modules into
19 + -uiconfig-report-builder if the report builder is disabled
d/rules
413 +ifeq "$(ENABLE_REPORTBUILDER)" "y"
414 mv
$(PKGDIR)-common/$(OODIR)/share/config/soffice.cfg/modules/dbreport \
415
$(PKGDIR)-uiconfig-report-builder/$(OODIR)/share/config/soffice.cfg/modules
416 +else
417 + rm -rf
$(PKGDIR)-common/$(OODIR)/share/config/soffice.cfg/modules/dbreport
418 +endif
Is this possibly a separate bug, as apparently it's not related to
an upstream bug fix; it would be nice to have some clarification.
Maybe this is covered in the SRU policy under "it is also acceptable to
upload new microreleases with many bug fixes without individual
Launchpad bugs for each of them", but I considered such 'many bug fixes'
to be related to the upstream bugs, and this change is on packaging.
2)
d/changelog
20 +- switch OOO_BASE_ARCHS/OOO_REPORTBUILDER_ARCHS variables
21 + (build base on all architectures instead of Java architectures
22 + and report-builder-* only on archs where Java is enabled, not on
23 + "all base archs"); there's -sdbc-{mysql,postgresql,firebird} anyway
d/rules
356 -OOO_BASE_ARCHS := $(OOO_JAVA_ARCHS)
357 +OOO_BASE_ARCHS := $(OOO_ARCHS)
358 $(eval $(call gen_no_archs,OOO_BASE_ARCHS))
359 -OOO_REPORTBUILDER_ARCHS := $(OOO_BASE_ARCHS)
360 +OOO_REPORTBUILDER_ARCHS := $(OOO_JAVA_ARCHS)
Similarly; it would be nice to have some clarification,
and perhaps explain the trailing note about '-sdbc-* anyway'.
3)
d/changelog
24 +- don't try to build Jar_{OOoRunner,test,ConnectivityTools} if Java is
25 + disabled as an extra safety net (instead of checking for junit only)
Similary, it would be nice to have some clarification.
d/rules
399 -ifeq "$(BUILD_TEST_PACKAGES)" "y"
400 - ifeq "$(ENABLE_JUNIT4)" "y"
401 +ifeq "$(ENABLE_JAVA)" "y"
402 + ifeq "$(BUILD_TEST_PACKAGES)" "y"
403 +ifeq "$(ENABLE_JUNIT4)" "y"
404 PATH=$(BUILD_PATH) LD_LIBRARY_PATH=$(BUILD_LD_LIBRARY_PATH)
ARCH_FLAGS=$(ARCH_FLAGS) TMP=`mktemp -q -d` $(MAKE) Jar_{OOoRunner,tes
t,ConnectivityTools}
405 +endif
4)
d/changelog
26 +- re-enable cmis; bump libcmis build-dep to >= 0.6.1
Similarly; it would be nice to have some clarification.
And also the reason to enable it in an SRU? Maybe some relation to
an upstream bug or ubuntu bug? Any changes at behavior/runtime?
(apparently just an internal build dep; why is this needed, and
isn't the archive version (older) sufficient?)
d/rules
343 @@ -356,7 +356,7 @@
344 DICT_DIR=/usr/share/hunspell
345 HYPH_DIR=/usr/share/hyphen
346 THES_DIR=/usr/share/mythes
347 -ENABLE_LIBCMIS=n
348 +ENABLE_LIBCMIS=y
386 @@ -1423,7 +1429,7 @@
387endif
388ifeq "$(ENABLE_LIBCMIS)" "y"
389 ifneq (,$(filter libcmis, $(SYSTEM_STUFF)))
390 - BUILD_DEPS += , libcmis-dev (>= 0.5.2~), libcmis-dev (<< 0.6~)
391 + BUILD_DEPS += , libcmis-dev (>= 0.6.1~), libcmis-dev (<< 0.7~)
392 endif
393else
394 CONFIGURE_FLAGS += --disable-libcmis
5)
27 +- build against libcurl4-openssl-dev instead of gnutls
334 @@ -271,7 +271,7 @@
335 USE_GSTREAMER=y
336 endif
337 ENABLE_CURL=y
338 -CURL_SECTYPE=gnutls
339 +CURL_SECTYPE=openssl
Similarly; it would be nice to have some clarification on its reason,
and potential changes to runtime behavior or functionality.
This is a significant change.
6)
30 + * debian/control.ure.in:
31 +- make ure-java actutally Architecture: %OOO_JAVA_ARCHS%
Similarly, it would be nice to have some clarification.
** Changed in: libreoffice (Ubuntu Mantic)
Status: In Progress => Incomplete
--
You received this bug notification
[Desktop-packages] [Bug 2038834] Re: GPU acceleration via VirGL is broken in qemu
The autopkgtest regression above are due to armhf autopkgtest runner faults. The tests have been re-triggered and should succeed. Confirmed to fix VirGL graphics acceleration on my previously affected machine. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- 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/2038834 Title: GPU acceleration via VirGL is broken in qemu Status in Release Notes for Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Mantic: Fix Committed Status in mesa source package in Noble: Fix Released Bug description: [ Impact ] * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs * This was reported by someone else upstream and is already fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580. [ Test Plan ] * I've tested the patch on an affected macOS host running Ubuntu in UTM with OpenGL enabled on both Mantic and Noble VMs. * Anyone else can do the same on an affected host by simply installing the patched package and booting to the desktop. [ Where problems could occur ] * This patch fixes an upstream mesa regression which caused libvirglrendrer to crash on the host side. * This makes a non-working use case work, VirGL on affected hosts cannot regress as it simply didn't work before. * Risk of breakage is mainly from other packages possible affected by a mesa rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2042796] Re: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small
** Changed in: mutter Status: New => Fix Released -- 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/2042796 Title: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small Status in Mutter: Fix Released Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: In Progress Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2042796/+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 2042796] Re: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen are not sensitive
In review: https://salsa.debian.org/gnome-team/gnome- shell/-/merge_requests/76 ** Summary changed: - Ubuntu 20.04: Buttons/icons at the edge of the touchscreen are not sensitive + Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small -- 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/2042796 Title: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen don't respond to taps if they are very small Status in Mutter: New Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: In Progress Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2042796/+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 2042796] Re: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen are not sensitive
** Changed in: gnome-shell (Ubuntu) Status: Invalid => Fix Released ** Changed in: gnome-shell (Ubuntu Focal) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) ** Changed in: gnome-shell (Ubuntu Focal) Status: New => In Progress ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2042796 Title: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen are not sensitive Status in Mutter: New Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: In Progress Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2042796/+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 2042796] Re: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen are not sensitive
** Summary changed: - Ubuntu 20.04 The edge of the touchscreen is not sensitive + Ubuntu 20.04: Buttons/icons at the edge of the touchscreen are not sensitive -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2042796 Title: Ubuntu 20.04: Buttons/icons at the edge of the touchscreen are not sensitive Status in Mutter: New Status in OEM Priority Project: Triaged Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: In Progress Bug description: On Dell OptiPlex 7400 AIO, go to gnome-control-center > appearance, adjust the dock icon-size to 24. It is hard to launch corner app like firefox, or trigger the launcher. The app icon gets focus but not clicked. 1. Ubuntu version 20.04.6 2. gnome-shell 3.36.9-0ubuntu0.20.04.2 3. The app or launcher is launched after a click 4. Only see focus but no app launched To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2042796/+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 2045329] Re: The 'Files Selecting' window shows Asia fonts incompletely.
Thank you for your bug report. The issue seems with the fileselector widget from GTK and not the filemanager (nautilus) right? Which application are you using (to know what GTK serie the report is about)? Also could you describe the issue in a bit more details on how 'incomplete' the font is? ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/2045329 Title: The 'Files Selecting' window shows Asia fonts incompletely. Status in nautilus package in Ubuntu: Incomplete Bug description: The 'Files Selecting' windows shows Asia fonts incompletely. Please view the image I uploaded of it. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-13.13-generic 6.5.3 Uname: Linux 6.5.0-13-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 1 08:51:46 2023 GsettingsChanges: InstallationDate: Installed on 2023-10-26 (35 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-10-26 (35 days ago) 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/2045329/+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 2028698] Re: desktop freezes when copying file to android phone
Seems to be any file with a colon (:) character in the filename. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2028698 Title: desktop freezes when copying file to android phone Status in gvfs package in Ubuntu: Confirmed Bug description: If you try to copy a file named a:b.m4b using the nautilus file manager to a USB-connected Android phone in MTP mode, the desktop will freeze until you disconnect the USB cable. Then you'll get an error from nautilus: "Fehler beim Kopieren von »a:b.m4b«. Beim Kopieren der Datei nach mtp://Google_Pixel_7_291... mer%Speicher/Audiobooks ist ein Fehler aufgetreten libmtp-Fehler: Could not send object." This happens when the file to be copied contains the colon symbol : ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs-backends 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jul 25 21:46:45 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-08-20 (704 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: gvfs UpgradeStatus: Upgraded to jammy on 2022-09-10 (318 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2028698/+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 2028698] Re: desktop freezes when copying file to android phone
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2028698 Title: desktop freezes when copying file to android phone Status in gvfs package in Ubuntu: Confirmed Bug description: If you try to copy a file named a:b.m4b using the nautilus file manager to a USB-connected Android phone in MTP mode, the desktop will freeze until you disconnect the USB cable. Then you'll get an error from nautilus: "Fehler beim Kopieren von »a:b.m4b«. Beim Kopieren der Datei nach mtp://Google_Pixel_7_291... mer%Speicher/Audiobooks ist ein Fehler aufgetreten libmtp-Fehler: Could not send object." This happens when the file to be copied contains the colon symbol : ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs-backends 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jul 25 21:46:45 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-08-20 (704 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: gvfs UpgradeStatus: Upgraded to jammy on 2022-09-10 (318 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2028698/+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
