[Bug 1937024] Re: xrdp log created with wrong permissions
Hi, Please, mark it as solved. I've tested in 24.04 (desktop) and has been corrected: xrdp does not start if log not correctly configured (permissions). root@ubuntu:/var/log# ls -l xrdp* -rw-r- 1 root adm 2322 May 3 10:09 xrdp-sesman.log -rw-r- 1 xrdp adm 9139 May 3 10:08 xrdp.log toot@ubuntu:/var/log# systemctl restart xrdp Job for xrdp.service failed because the control process exited with error code. See "systemctl status xrdp.service" and "journalctl -xeu xrdp.service" for details. root@ubuntu:/var/log# journalctl -xeu xrdp.service (...) ░░ The job identifier is 3708. May 03 10:10:06 ubuntu xrdp[9049]: Could not start log May 03 10:10:06 ubuntu xrdp[9049]: Could not start log May 03 10:10:06 ubuntu xrdp[9049]: error opening log file [The log is not properly started]. quitting. May 03 10:10:06 ubuntu systemd[1]: xrdp.service: Control process exited, code=exited, status=1/FAILURE (...) Thanks!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937024 Title: xrdp log created with wrong permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1937024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063359] Re: [FFe] Use of NDEBUG in d/rules for 2.3.3+dfsg-0ubuntu2 on Noble generates an incompatible ABI
Need to convert the issue into an SRU now that Noble is out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063359 Title: [FFe] Use of NDEBUG in d/rules for 2.3.3+dfsg-0ubuntu2 on Noble generates an incompatible ABI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/2063359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063359] Re: [FFe] Use of NDEBUG in 2.3.3 on Noble generates an incompatible ABI
The Gazebo simulator running on a Noble container :) ** Attachment added: "Image of Gazebo Harmonic on Noble" https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/2063359/+attachment/5770080/+files/Screenshot%20from%202024-04-24%2018-36-29.png ** Description changed: Version bump for current ogre on Noble - - Tested on PPA with version: ogre-next - 2.3.3+dfsg-6~202404240955~ubuntu24.04.1 - https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe/+packages - - MR: + - Tested on PPA with version: ogre-next - 2.3.3+dfsg-6~202404240955~ubuntu24.04.1 + https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe/+packages + - MR: https://code.launchpad.net/~j-rivero/ubuntu/+source/ogre-next/+git/ogre-next-2/+merge/464934 The latest bump in ogre-next for 2.3.3+dfsg-0ubuntu2 version came with an addition in d/rules of: -DCMAKE_CXX_FLAGS="$(CXXFLAGS) -DDEBUG=0 -D_DEBUG=0". See https://git.launchpad.net/ ubuntu/+source/ogre-next/tree/debian/rules#n15. That is generating incompatible ABIs if the same set of flags is not used in third party software. Specially difficult to detect since the problems will appear in the loading of the OGRE plugins not during the building. See the full justification for the long story: [Justification] For the current version 2.3.3+dfsg-0ubuntu2 the build process, the test suite and the autopkgtest did not detect any problem in the build or run of the different OGRE components. However when we (Gazebo simulator team) used the library to build our gazebo-rendering library we found problems with missing symbols at runtime when trying to load plugins. """ /ws/harmonic/install_noble/gz-rendering8/lib/gz-rendering-8/engine-plugins/libgz-rendering-ogre2.so: undefined symbol: _ZThn944_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE """ If we demangle that symbol the "T non-virtual thunk to Ogre::HlmsPbs::_changeRenderSystem(Ogre::RenderSystem*)" appears and that method do exists o the current OGRE version. The problem is that the ABI symbol has a different offset after _ZThn: instead of 944 it has 1008. So the symbol is not the same for the loader: - 1. _ZThn944_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE (in gz-rendering) - 2. _ZThn1008_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE (in 2.3.3+dfsg-0ubuntu2) + 1. _ZThn944_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE (in gz-rendering) + 2. _ZThn1008_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE (in 2.3.3+dfsg-0ubuntu2) It is hard to know where this difference in the offset is coming from but I was able to track the problem to the use of -DDEBUG=0 -D_DEBUG=0 in debian/rules added for the 2.3.3 version bump with respect to jammy 2.2.5. Removing it, solves the offset difference. [Updating details] The MR linked to the bug just remove the custom NDEBUG flags added to d/rules. ogre-next does not have any reverse dependency at this moment in Ubuntu. [Testing done] Using the packages generated with the proposed change keeps the package building in all arches, passing the autopkgtest and allow use to run the Gazebo Simulator with the OGRE-Next libraries for the first time in Noble. With current 2.3.3+dfsg-0ubuntu2: - 8 --- [GUI] [Msg] Loading plugin [gz-rendering-ogre2] Error while loading the library [/usr/local/google/home/addisuzt/ws/harmonic/install_noble/gz-rendering8/lib/gz-rendering-8/engine-plugins/libgz-rendering-ogre2.so]: /usr/local/google/home/addisuzt/ws/harmonic/install_noble/gz-rendering8/lib/gz-rendering-8/engine-plugins/libgz-rendering-ogre2.so: undefined symbol: _ZThn944_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE [GUI] [Err] [RenderEngineManager.cc:501] Failed to load plugin [gz-rendering-ogre2] : couldn't load library on path [/usr/local/google/home/addisuzt/ws/harmonic/install_noble/gz-rendering8/lib/gz-rendering-8/engine-plugins/libgz-rendering-ogre2.so]. - - 8 --- + - 8 --- With changes in proposed 2.3.3+dfsg-0ubuntu3: - - 8 --- + - 8 --- [GUI] [Wrn] [Application.cc:908] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:67:3: QML EntityContextMenu: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead. failed to create drawable [GUI] [Msg] Loading plugin [gz-rendering-ogre2] [GUI] [Msg] Move to service on [/gui/move_to] [GUI] [Msg] Follow service on [/gui/follow] [GUI] [Msg] Move to pose service on [/gui/move_to/pose] [GUI] [Msg] Camera pose topic advertised on [/gui/camera/pose] [GUI] [Msg] Follow offset service on [/gui/follow/offset] [Msg] Found no
[Bug 2063359] [NEW] [FFe] Use of NDEBUG in d/rules for 2.3.3+dfsg-0ubuntu2 on Noble generates an incompatible ABI
Public bug reported: Revision bump for current ogre on Noble - Tested on PPA with version: ogre-next - 2.3.3+dfsg-6~202404240955~ubuntu24.04.1 https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe/+packages - MR: https://code.launchpad.net/~j-rivero/ubuntu/+source/ogre-next/+git/ogre-next-2/+merge/464934 The latest bump in ogre-next for 2.3.3+dfsg-0ubuntu2 version came with an addition in d/rules of: -DCMAKE_CXX_FLAGS="$(CXXFLAGS) -DDEBUG=0 -D_DEBUG=0". See https://git.launchpad.net/ ubuntu/+source/ogre-next/tree/debian/rules#n15. That is generating incompatible ABIs if the same set of flags is not used in third party software. Specially difficult to detect since the problems will appear in the loading of the OGRE plugins not during the building. See the full justification for the long story: [Justification] For the current version 2.3.3+dfsg-0ubuntu2 the build process, the test suite and the autopkgtest did not detect any problem in the build or run of the different OGRE components. However when we (Gazebo simulator team) used the library to build our gazebo-rendering library we found problems with missing symbols at runtime when trying to load plugins. """ /ws/harmonic/install_noble/gz-rendering8/lib/gz-rendering-8/engine-plugins/libgz-rendering-ogre2.so: undefined symbol: _ZThn944_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE """ If we demangle that symbol the "T non-virtual thunk to Ogre::HlmsPbs::_changeRenderSystem(Ogre::RenderSystem*)" appears and that method do exists o the current OGRE version. The problem is that the ABI symbol has a different offset after _ZThn: instead of 944 it has 1008. So the symbol is not the same for the loader: 1. _ZThn944_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE (in gz-rendering) 2. _ZThn1008_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE (in 2.3.3+dfsg-0ubuntu2) It is hard to know where this difference in the offset is coming from but I was able to track the problem to the use of -DDEBUG=0 -D_DEBUG=0 in debian/rules added for the 2.3.3 version bump with respect to jammy 2.2.5. Removing it, solves the offset difference. [Updating details] The MR linked to the bug just remove the custom NDEBUG flags added to d/rules. ogre-next does not have any reverse dependency at this moment in Ubuntu. [Testing done] Using the packages generated with the proposed change keeps the package building in all arches, passing the autopkgtest and allow use to run the Gazebo Simulator with the OGRE-Next libraries for the first time in Noble. With current 2.3.3+dfsg-0ubuntu2: - 8 --- [GUI] [Msg] Loading plugin [gz-rendering-ogre2] Error while loading the library [/usr/local/google/home/addisuzt/ws/harmonic/install_noble/gz-rendering8/lib/gz-rendering-8/engine-plugins/libgz-rendering-ogre2.so]: /usr/local/google/home/addisuzt/ws/harmonic/install_noble/gz-rendering8/lib/gz-rendering-8/engine-plugins/libgz-rendering-ogre2.so: undefined symbol: _ZThn944_N4Ogre7HlmsPbs19_changeRenderSystemEPNS_12RenderSystemE [GUI] [Err] [RenderEngineManager.cc:501] Failed to load plugin [gz-rendering-ogre2] : couldn't load library on path [/usr/local/google/home/addisuzt/ws/harmonic/install_noble/gz-rendering8/lib/gz-rendering-8/engine-plugins/libgz-rendering-ogre2.so]. - 8 --- With changes in proposed 2.3.3+dfsg-0ubuntu3: - 8 --- [GUI] [Wrn] [Application.cc:908] [QT] file::/EntityContextMenuPlugin/EntityContextMenuPlugin.qml:67:3: QML EntityContextMenu: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead. failed to create drawable [GUI] [Msg] Loading plugin [gz-rendering-ogre2] [GUI] [Msg] Move to service on [/gui/move_to] [GUI] [Msg] Follow service on [/gui/follow] [GUI] [Msg] Move to pose service on [/gui/move_to/pose] [GUI] [Msg] Camera pose topic advertised on [/gui/camera/pose] [GUI] [Msg] Follow offset service on [/gui/follow/offset] [Msg] Found no publishers on /stats, adding root stats topic [Msg] Found no publishers on /clock, adding root clock topic [Msg] Serving scene information on [/world/shapes/scene/info] [Msg] Serving graph information on [/world/shapes/scene/graph] - 8 --- The simulator loads just fine. ** Affects: ogre-next (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Merge proposal linked: https://code.launchpad.net/~j-rivero/ubuntu/+source/ogre-next/+git/ogre-next-2/+merge/464934 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063359 Title: [FFe] Use of NDEBUG in d/rules for 2.3.3+dfsg-0ubuntu2 on Noble generates an incompatible ABI To manage notifications about this bug go to:
[Bug 2054477] Re: [FFe] Update ogre-next to 2.3.3 for Noble
The ogre-next update was released and ignition-cmake was removed in https://bugs.launchpad.net/ubuntu/+source/ros-catkin/+bug/2063103. I've updated the statuses. All done here. ** Changed in: ogre-next (Ubuntu) Status: Triaged => Fix Released ** Changed in: ignition-cmake (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054477 Title: [FFe] Update ogre-next to 2.3.3 for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-cmake/+bug/2054477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053254] Re: [FFe] Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages)
The ignition-common and ignition-physics packages has be removed from
Ubuntu in https://bugs.launchpad.net/ubuntu/+source/ros-
catkin/+bug/2063103 yesterday.
It can be totally omitted totally. I'm going to close the MR and edit
the description.
** Summary changed:
- [FFe] Update urdfdom, dart and ignition-physics for Noble (Open Robotics
packages)
+ [FFe] Update urdfdom and dart for Noble (Open Robotics packages)
** Description changed:
Versions bump for the Open Robotics Community packages:
- urdfdom to 4.0.0-0ubuntu1
(Imported from https://salsa.debian.org/science-team/urdfdom)
- dart to 6.13.1+ds-0ubuntu2
https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/log/?h=ubuntu/devel
-
- As a side effect ignition-physics package needs also to be patch updated:
- - ignition-physics to 5.1.0+ds1-4.1ubuntu2
- (Imported from https://salsa.debian.org/science-team/ignition-physics)
-
- The review found that there was a problem with a missing ignition-common
package in s390:
- - ignition-common (needs a rev bump)
-
https://git.launchpad.net/~j-rivero/ubuntu/+source/ignition-common/log/?h=ubuntu/noble
Package PPA:
https://launchpad.net/~j-rivero/+archive/ubuntu/urdfdom4-noble/+packages
(three merge-request are ready for review)
[Other info]
I have both version bumps ready on Debian but the 64bit_time transition[1] is
preventing the
packages to go through the lib transition since two weeks ago and counting.
As we want to
have these new versions in 24.04 (feature freeze is coming soon), we do the
version bump
directly on Ubuntu.
[Justification]
Important updates in a couple of packages used by the Open Robotics
Community, particularly affecting ROS (Robot Operative System) and the
- ignition/Gazebo simulator.
+ Gazebo simulator.
* urdfdom is changing the ABI/API completely by replacing tinyxml with
tinyxml2
* Dart current version 6.12.1 was released in .. 2019.
There are important bugfixes in DART, specially the fix for a ton of
compiler warnings with gcc-13 and patches for skeleton trees and
grouping of constraints.
Both packages should be lintian clean.
[Transition details]
- The PPA includes all direct dependencies of urfdom and DART (ignition-
- physics and ros-urdf).
-
- * ignition-physics include a patch to work with new DART adding conditional
code to deal with
- minor DART API renames.
+ The PPA includes all direct dependencies of urfdom and DART (ros-urdf).
All the previous architectures where the software was building before
are also supported in the update with an important exception: new DART
upstream releases do not support 32 bits, so armhf is lost from the
list.
[1] https://lists.debian.org/debian-devel-announce/2024/02/msg0.html
+
+
+ {edited on Apr 23rd -- removed since ignition packages were removed from
Ubuntu}
+
+ As a side effect ignition-physics package needs also to be patch updated:
+ - ignition-physics to 5.1.0+ds1-4.1ubuntu2
+ (Imported from https://salsa.debian.org/science-team/ignition-physics)
+
+ The review found that there was a problem with a missing ignition-common
package in s390:
+ - ignition-common (needs a rev bump)
+
https://git.launchpad.net/~j-rivero/ubuntu/+source/ignition-common/log/?h=ubuntu/noble
** Description changed:
Versions bump for the Open Robotics Community packages:
- urdfdom to 4.0.0-0ubuntu1
(Imported from https://salsa.debian.org/science-team/urdfdom)
- dart to 6.13.1+ds-0ubuntu2
https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/log/?h=ubuntu/devel
Package PPA:
https://launchpad.net/~j-rivero/+archive/ubuntu/urdfdom4-noble/+packages
(three merge-request are ready for review)
[Other info]
I have both version bumps ready on Debian but the 64bit_time transition[1] is
preventing the
packages to go through the lib transition since two weeks ago and counting.
As we want to
have these new versions in 24.04 (feature freeze is coming soon), we do the
version bump
directly on Ubuntu.
[Justification]
Important updates in a couple of packages used by the Open Robotics
Community, particularly affecting ROS (Robot Operative System) and the
Gazebo simulator.
* urdfdom is changing the ABI/API completely by replacing tinyxml with
tinyxml2
* Dart current version 6.12.1 was released in .. 2019.
There are important bugfixes in DART, specially the fix for a ton of
compiler warnings with gcc-13 and patches for skeleton trees and
grouping of constraints.
Both packages should be lintian clean.
[Transition details]
The PPA includes all direct dependencies of urfdom and DART (ros-urdf).
All the previous architectures where the software was building before
are also supported in the update with an important exception: new DART
upstream releases do not support 32 bits, so armhf is lost from the
list.
[1]
[Bug 2058279] Re: [FFe] Sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental (main)
Thanks Utkarsh! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058279 Title: [FFe] Sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcl/+bug/2058279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054477] Re: [FFe] Update ogre-next to 2.3.3 for Noble
I'm afraid that we are stuck in transitioning https://ubuntu-archive- team.ubuntu.com/proposed-migration/update_excuses.html#ogre-next because there is a problem with autopkgtest. Sorry for that. I've created a new merge-request to solve the problem https://code.launchpad.net/~j-rivero/ubuntu/+source/ogre-next/+git/ogre- next/+merge/464598. Adding back ubuntu-sponsors to help with the upload. Thanks! > I'm not clear from the above if FFe acceptance was given for ignition-cmake so I'm leaving that for now. That is waiting for release-team, I provided contexts and info in https://bugs.launchpad.net/ubuntu/+source/ogre- next/+bug/2054477/comments/3 ** Merge proposal linked: https://code.launchpad.net/~j-rivero/ubuntu/+source/ogre-next/+git/ogre-next/+merge/464598 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054477 Title: [FFe] Update ogre-next to 2.3.3 for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-cmake/+bug/2054477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053254] Re: [FFe] Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages)
Friendly ping. I've created the three merge request for trying to move this forward and make it easier for reviewers. Let me know what else needs to be done more to help the testing. Thanks! ** Merge proposal linked: https://code.launchpad.net/~j-rivero/ubuntu/+source/dart/+git/dart/+merge/464445 ** Merge proposal linked: https://code.launchpad.net/~j-rivero/ubuntu/+source/ignition-common/+git/ignition-common/+merge/464446 ** Description changed: Versions bump for the Open Robotics Community packages: - urdfdom to 4.0.0-0ubuntu1 (Imported from https://salsa.debian.org/science-team/urdfdom) - dart to 6.13.1+ds-0ubuntu2 https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/log/?h=ubuntu/devel As a side effect ignition-physics package needs also to be patch updated: - ignition-physics to 5.1.0+ds1-4.1ubuntu2 (Imported from https://salsa.debian.org/science-team/ignition-physics) The review found that there was a problem with a missing ignition-common package in s390: - ignition-common (needs a rev bump) https://git.launchpad.net/~j-rivero/ubuntu/+source/ignition-common/log/?h=ubuntu/noble Package PPA: https://launchpad.net/~j-rivero/+archive/ubuntu/urdfdom4-noble/+packages + + (three merge-request are ready for review) [Other info] I have both version bumps ready on Debian but the 64bit_time transition[1] is preventing the packages to go through the lib transition since two weeks ago and counting. As we want to have these new versions in 24.04 (feature freeze is coming soon), we do the version bump directly on Ubuntu. [Justification] Important updates in a couple of packages used by the Open Robotics Community, particularly affecting ROS (Robot Operative System) and the ignition/Gazebo simulator. * urdfdom is changing the ABI/API completely by replacing tinyxml with tinyxml2 * Dart current version 6.12.1 was released in .. 2019. There are important bugfixes in DART, specially the fix for a ton of compiler warnings with gcc-13 and patches for skeleton trees and grouping of constraints. Both packages should be lintian clean. [Transition details] The PPA includes all direct dependencies of urfdom and DART (ignition- physics and ros-urdf). * ignition-physics include a patch to work with new DART adding conditional code to deal with minor DART API renames. All the previous architectures where the software was building before are also supported in the update with an important exception: new DART upstream releases do not support 32 bits, so armhf is lost from the list. [1] https://lists.debian.org/debian-devel-announce/2024/02/msg0.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053254 Title: [FFe] Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dart/+bug/2053254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053254] Re: [FFe] Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages)
** Merge proposal linked: https://code.launchpad.net/~j-rivero/ubuntu/+source/urdfdom/+git/urdfdom/+merge/464439 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053254 Title: [FFe] Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dart/+bug/2053254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058914] Re: [FFe] python-pytest-flake8 FTBFS against python-flake8 7
python-flake8 7.0.0 is no Noble (main repo). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058914 Title: [FFe] python-pytest-flake8 FTBFS against python-flake8 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/2058914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058914] Re: python-pytest-flake8 FTBFS against python-flake8 7
Given that the solution proposed is to ship a custom patch, I'm going to
bump this to a FFe to get acceptance of the release-team and also
unblock the excuses transition in existing Noble development cycle.
* Merge request:
https://code.launchpad.net/~j-rivero/ubuntu/+source/python-pytest-flake8/+git/python-pytest-flake8/+merge/464197
* Build tested:
https://code.launchpad.net/~j-rivero/+recipe/python-pytest-flake8-daily
[Justification]
This package is stopping the transition in Noble from noble-proposed to noble
of python3-flake8, see
https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#python-flake8
If you install python3-flake8 in regular Noble right now, you get version
5.0.4.
flake8 depends on pydocstyle, which was updated to a newer version (6.3.0),
which changed API. So attempting to run flake8 fails at startup, trying to call
an invalid API.
python3-flake8 7.0.0 and 8.1.1 (the latest) both fix this issue.
8.1.1 is currently the version in noble-proposed. However, it has been stuck
in
proposed for several months because pythonpytest-flake8 fails tests when used
against that version.
See the problem in the long build of the ROS buildfarm:
https://build.ros2.org/view/Rdev/job/Rdev__ros2cli__ubuntu_noble_amd64/2/console
8< -
08:29:45 _ test_flake8
__
08:29:45 /usr/lib/python3/dist-packages/flake8/plugins/finder.py:296: in
_load_plugin
08:29:45 obj = plugin.entry_point.load()
08:29:45 /usr/lib/python3.12/importlib/metadata/__init__.py:205: in load
08:29:45 module = import_module(match.group('module'))
08:29:45 /usr/lib/python3.12/importlib/__init__.py:90: in import_module
08:29:45 return _bootstrap._gcd_import(name[level:], package, level)
08:29:45 /usr/lib/python3/dist-packages/flake8/plugins/pycodestyle.py:25: in
08:29:45 from pycodestyle import missing_whitespace_around_operator as
_missing_whitespace_around_operator # noqa: E501
08:29:45 E ImportError: cannot import name
'missing_whitespace_around_operator' from 'pycodestyle'
(/usr/lib/python3/dist-packages/pycodestyle.py). Did you mean:
'whitespace_around_operator'?
8< -
[Testing done]
We have been injecting the python3-flake version in noble-proposed into the ROS
buildfarm build, see that there are no failures any more, software run as
expected:
https://ci.ros2.org/job/ci_linux/20828/console
8< --
[33m=== warnings summary
===[0m
test/test_flake8.py::test_flake8
test/test_flake8.py::test_flake8
test/test_flake8.py::test_flake8
test/test_flake8.py::test_flake8
test/test_flake8.py::test_flake8
test/test_flake8.py::test_flake8
test/test_flake8.py::test_flake8
test/test_flake8.py::test_flake8
/usr/lib/python3.12/multiprocessing/popen_fork.py:66: DeprecationWarning:
This process (pid=259742) is multi-threaded, use of fork() may lead to
deadlocks in the child.
self.pid = os.fork()
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
---
8< --
The ROS buildfarm is a large project for testing lot of software packages in
open
source robotics and the use of flake8 is integrated into each python package. We
have been using it last weeks without problems.
** Summary changed:
- python-pytest-flake8 FTBFS against python-flake8 7
+ [FFe] python-pytest-flake8 FTBFS against python-flake8 7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058914
Title:
[FFe] python-pytest-flake8 FTBFS against python-flake8 7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/2058914/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058914] Re: python-pytest-flake8 FTBFS against python-flake8 7
** Merge proposal linked: https://code.launchpad.net/~j-rivero/ubuntu/+source/python-pytest-flake8/+git/python-pytest-flake8/+merge/464197 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058914 Title: python-pytest-flake8 FTBFS against python-flake8 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/2058914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060852] Re: nvidia-driver-550-open fails with secure boot enabled
** Changed in: nvidia-graphics-drivers-550 (Ubuntu) Assignee: (unassigned) => Kuba Pawlak (kuba-t-pawlak) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060852 Title: nvidia-driver-550-open fails with secure boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-550/+bug/2060852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060717] Re: colcon-core argument parsing is broken by recent changes to Python 3.11+
In coordination with Scott, we have raised this to be a FFe since the
package is severity damaged as it is now and probably unusable for any
use case that is not completely trivial.
I've created and linked the merge-request with the bumped version
against ubuntu/devel and testing the package.
** Description changed:
+ Patch version to solve a critical problem with colcon argument parsing
+ mechanism.
+
+ * Merge request:
https://code.launchpad.net/~j-rivero/ubuntu/+source/ros2-colcon-core/+git/ros2-colcon-core/+merge/464037
+ * PPA related:
https://code.launchpad.net/~j-rivero/+archive/ubuntu/noble-pkgs
+
+
+ [Justification]
+
+ Recent changes to Python which have been backported to Python 3.11 and
+ 3.12 break colcon argument parsing due to a dependency on private API in
+ argparse. A fix has been released in colcon-core 0.16.1 which should be
+ backported to any platforms which will receive the updated Python
+ releases. The python3-colcon-core package currently in Ubuntu Noble is
+ suffering from this issue now.
+
+ The current version in 0.15.2-1 fails to build due to problem in the
+ test suite that detect this problem:
+ https://code.launchpad.net/~j-rivero/+archive/ubuntu/noble-
+ pkgs/+build/28042968
+
+ A quick test on Noble reports the problem:
+ - 8<
+ $ mkdir /tmp/colcon-repro && cd /tmp/colcon-repro
+ $ colcon build --cmake-args --no-warn-unused-cli
+
+ Expected:
+
+ Summary: 0 packages finished
+
+ Actual:
+
+ usage: colcon [-h] [--log-base LOG_BASE] [--log-level LOG_LEVEL]
{build,extension-points,extensions,graph,info,list,metadata,test,test-result,version-check}
...
+ colcon: error: unrecognized arguments: --no-warn-unused-cli
+ - 8<
+
+
+ [testing done]
+
+ After using the changes proposed:
+
+ - 8<
+ jrivero@22d248d84027:~/code/ubuntu$ sudo dpkg -i
python3-colcon-core_0.15.2-1ubuntu1_all.deb
+ (Reading database ... 58627 files and directories currently installed.)
+ Preparing to unpack python3-colcon-core_0.15.2-1ubuntu1_all.deb ...
+ Unpacking python3-colcon-core (0.15.2-1ubuntu1) over (0.15.2-1) ...
+ Setting up python3-colcon-core (0.15.2-1ubuntu1) ...
+ jrivero@22d248d84027:/tmp/colcon-repro$ colcon build --cmake-args
--no-warn-unused-cli
+
+ Summary: 0 packages finished [0.28s]
+ - 8<
+
+ Playing with other colcon workspaces does not show any problem to
+ my eyes when passing different cmake-args like modifying the CMAKE_BUILD_TYPE.
+
+
+ [Original Scott email]
+ --- 8< ---
+
Recent changes to Python which have been backported to Python 3.11 and
3.12 break colcon argument parsing due to a dependency on private API in
argparse.
A fix has been released in colcon-core 0.16.1 which should be backported
to any platforms which will receive the updated Python releases.
The python3-colcon-core package currently in Ubuntu Noble is suffering
from this issue now.
https://github.com/colcon/colcon-core/pull/635
** Summary changed:
- colcon-core argument parsing is broken by recent changes to Python 3.11+
+ [FFe] colcon-core argument parsing is broken by recent changes to Python 3.11+
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060717
Title:
[FFe] colcon-core argument parsing is broken by recent changes to
Python 3.11+
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ros2-colcon-core/+bug/2060717/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060717] Re: colcon-core argument parsing is broken by recent changes to Python 3.11+
** Merge proposal linked: https://code.launchpad.net/~j-rivero/ubuntu/+source/ros2-colcon-core/+git/ros2-colcon-core/+merge/464037 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060717 Title: [FFe] colcon-core argument parsing is broken by recent changes to Python 3.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ros2-colcon-core/+bug/2060717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058914] Re: python-pytest-flake8 FTBFS against python-flake8 7
> Not sure what would be best, if RM the package or invest time into patching it. Since no action happened last week, my teammate Chris Lalancette patched the existing version to work with current flake8 on noble-proposed 7.0.0. I have updated the upstream PR with the information https://github.com/tholo/pytest-flake8/pull/96#issuecomment-2032433686, tested changes in a docker noble with: * flake8 7.0.0-1 (probably any version above 6 could work) * pytest 7.4.4-1 and pytest 8.0.2-1 I've created a PPA for testing the changes in proposed, builds fine in amd64 https://launchpad.net/~j-rivero/+archive/ubuntu/python-pytest-flake8-noble/+packages The .debdiff against current noble version is attached in this comment. ** Patch added: "python-pytest-flake8_1.1.1-4ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/python-pytest-flake8/+bug/2058914/+attachment/5761331/+files/python-pytest-flake8_1.1.1-4ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058914 Title: python-pytest-flake8 FTBFS against python-flake8 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/2058914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053256] Re: [FFe] Update lcm to 1.5 for Noble
I think I've answered the feedback in the last 5 commits and the MR is ready: https://code.launchpad.net/~j-rivero/ubuntu/+source/lcm/+git/lcm/+merge/463155 P.D: Vladimir I added you as a reviewer, I hope it is fine for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053256 Title: [FFe] Update lcm to 1.5 for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lcm/+bug/2053256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053256] Re: [FFe] Update lcm to 1.5 for Noble
Thanks Andres, Vladimir. I'll try to get the merge request ready in the next couple of days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053256 Title: [FFe] Update lcm to 1.5 for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lcm/+bug/2053256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058914] Re: python-pytest-flake8 FTBFS against python-flake8 7
We (at the Open Robotics Foundation Alliance) are interested in helping with the transition of python-flake8 from noble-proposed to noble and have been monitoring the transition for some weeks. There is an attempt of fixing the code in https://github.com/tholo/pytest-flake8/pull/96 that we can work on trying to make it to work, although seems not to work on pytest8 which is the one in Ubuntu noble-proposed. That said, it is true that the repository does not host new commits since 2 years ago. Not sure what would be best, if RM the package or invest time into patching it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058914 Title: python-pytest-flake8 FTBFS against python-flake8 7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/2058914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054477] Re: [FFe] Update ogre-next to 2.3.3 for Noble
Thanks for the info Andreas! Update: yesterday ignition-rendering was removed from Noble in https://bugs.launchpad.net/ubuntu/+source/ignition- rendering/+bug/2058851. I'm going to update the description to remove the references to ignition-rendering. ** Changed in: ignition-rendering (Ubuntu) Status: Triaged => Invalid ** Description changed: Version bump for ogre-next to version 2.3.3, well tested by Open Robotics under the Gazebo simulator. * Package PPA: - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe * Git ubunut/devel branch - https://code.launchpad.net/~j-rivero/ubuntu/+source/ogre-next/+git/ogre-next [Justification] ogre-next current version is 2.2.5 and was released in 2021. It does not support vulkan which probably make the release not interesting for the vast majority of current rendering developers. The bump also fixes LP: #1987207 and LP: #2003346. [Changelog] Upstream does not provide a Changelog file nor a NEWS file nor other updated mechanism that is not the GitHub release information notes. The list of bugfixes and features listed from 2.2.5 is simply huge: https://github.com/OGRECave/ogre-next/releases [Other Info] The package is not included in Debian. The version bump to 2.3.1 has been used by the Gazebo simulator team for the latest releases of Gazebo during several years and I've included the patches that has proven to be necessary, specially for vulkan support. Many of the Open Robotics patches has been merged upstream. Changes done with respect to ubuntu/devel branch: 1dc7fa0 (HEAD -> ubuntu/devel, origin/ubuntu/devel) Update d/changelog fe78c7b Upstream fixed install paths to be standard b272862 Update d/copyright 5ccf1e5 Massive cleanup of d/rules c020ca5 Update d/changelog 5cb9fdb [PATCH] Added suport for riscv64 and ppc64 6ca8aa6 Rediff patches 3b2cb51 Update d/control and .install to 2.3.3 3d60843 Update upstream source from tag 'upstream/2.3.3+dfsg' 687514e (tag: upstream/2.3.3+dfsg, origin/upstream, upstream) New upstream version 2.3.3+dfsg 547df32 Fix blender-ogre conflict name 3940cc5 Update d/changelog d50eb7e Added a d/gbp.conf 3286c7d Initial commit on orphan branch Changes in d/changelog: * New upstream version 2.3.3+dfsg * Rediff patches * Massive cleanup of d/rules after upstream merges * Update d/control and .install to 2.3.3 * Update d/copyright * Fix package name for conflict with 1.9 (LP: #1987207) (LP: #2003346) * Fix blender-ogre conflict name * [PATCH] Added support for riscv64 and ppc64 [Dependencies] - There is one direct dependency of ogre-next, ignition-rendering. Given - that the version in Debian/Ubuntu is too old and probably a candidate to - be removed, I've uploaded a new version of ignition-rendering that drops - the support for ogre-next. It is still useful since it can use ogre-1.9. - - * Same package PPA with ogre-next - - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe - * Git and code for 6.1.0+ds-0ubuntu3: - - https://code.launchpad.net/~j-rivero/ubuntu/+source/ignition-rendering/+git/ignition-rendering/+ref/ubuntu/devel + Update from March 24: ignition-rendering was removed from Noble in + https://bugs.launchpad.net/ubuntu/+source/ignition- + rendering/+bug/2058851. There is no direct dependency for ogre-next in + Noble. There is another package that deal with ogre-next in an indirect manner providing build helpers: ignition-cmake. I've also patched this package to improve the ogre-next patch: * Same package PPA with ogre-next 2.17.1-2ubuntu2 - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe * Git and code for - https://code.launchpad.net/~j-rivero/ubuntu/+source/ignition-cmake/+git/ignition-cmake/+ref/ubuntu/devel + + + [Outdated info related to ignition-rendering] + + Outdated after the removal of ignition-rendering on March 24th from Noble. + + There is one direct dependency of ogre-next, ignition-rendering. Given that the version in Debian/Ubuntu is too old and probably a candidate to be removed, I've uploaded a new version of ignition-rendering that drops the support for ogre-next. It is still useful since it can use ogre-1.9. + + * Same package PPA with ogre-next + - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe + * Git and code for 6.1.0+ds-0ubuntu3: + - https://code.launchpad.net/~j-rivero/ubuntu/+source/ignition-rendering/+git/ignition-rendering/+ref/ubuntu/devel + ** Changed in: ignition-cmake (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054477 Title: [FFe] Update ogre-next to 2.3.3 for Noble To manage notifications about this bug go to:
[Bug 2058279] Re: [FFe] Sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental (main)
Thanks Utkarsh! The pcl package does not have autopkgtest itself, but the ros-perception-pcl has a large set of them. I ran them in a noble docker image, seems fine to me (selected output): autopkgtest [19:37:43]: starting date and time: 2024-03-22 19:37:43+0100 autopkgtest [19:37:43]: version 5.32ubuntu3 autopkgtest [19:37:43]: host 26fb015185f5; command line: /usr/bin/autopkgtest --no-auto-control -- null autopkgtest [19:37:44]: testbed dpkg architecture: amd64 autopkgtest [19:37:44]: testbed apt version: 2.7.12 autopkgtest [19:37:44]: testbed running kernel: Linux 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 autopkgtest [19:37:44]: unbuilt-tree . autopkgtest [19:37:44]: testing package ros-perception-pcl version 1.7.5-1build2 autopkgtest [19:37:44]: build needed for binaries autopkgtest [19:39:03]: test libpcl-conversions-dev: preparing testbed autopkgtest [19:39:07]: test libpcl-conversions-dev: ./debian/tests/compilation pcl_conversions pcl_conversions/pcl_conversions.h autopkgtest [19:39:07]: test libpcl-conversions-dev: [--- autopkgtest [19:39:12]: test libpcl-conversions-dev: ---] autopkgtest [19:39:12]: test libpcl-conversions-dev: - - - - - - - - - - results - - - - - - - - - - autopkgtest [19:39:12]: test libpcl-ros-dev: preparing testbed autopkgtest [19:39:17]: test libpcl-ros-dev: ./debian/tests/compilation pcl_ros pcl_ros/point_cloud.h autopkgtest [19:39:17]: test libpcl-ros-dev: [--- autopkgtest [19:39:21]: test libpcl-ros-dev: ---] autopkgtest [19:39:22]: test libpcl-ros-dev: - - - - - - - - - - results - - - - - - - - - - autopkgtest [19:39:22]: test python3-pcl-ros: preparing testbed autopkgtest [19:39:29]: test python3-pcl-ros: python3 -c "import pcl_ros" autopkgtest [19:39:29]: test python3-pcl-ros: [--- autopkgtest [19:39:29]: test python3-pcl-ros: ---] autopkgtest [19:39:29]: test python3-pcl-ros: - - - - - - - - - - results - - - - - - - - - - autopkgtest [19:39:29]: summary autopkgtest [19:39:29]: Binaries: resetting testbed apt configuration """ I also compiled and run the https://pcl.readthedocs.io/projects/tutorials/en/master/cloud_viewer.html#cloud- viewer example, without problems. Ran the pcl_viewer with the milk.pcd pointcloud from their repository and got the expected visualizer window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058279 Title: [FFe] Sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcl/+bug/2058279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2033518] Re: spyder 5.4.4+ds-1 autopkgtest fails
Upstream fix was merged and released in 5.5.0. Noble is shipping this patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2033518 Title: spyder 5.4.4+ds-1 autopkgtest fails To manage notifications about this bug go to: https://bugs.launchpad.net/spyderlib/+bug/2033518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053254] Re: Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages)
Changelog from existing version on Noble ** Attachment added: "changelog_dart" https://bugs.launchpad.net/ubuntu/+source/dart/+bug/2053254/+attachment/5757532/+files/changelog_dart.txt ** Description changed: Versions bump for the Open Robotics Community packages: - urdfdom to 4.0.0-0ubuntu1 -(Imported from https://salsa.debian.org/science-team/urdfdom) + (Imported from https://salsa.debian.org/science-team/urdfdom) - dart to 6.13.1+ds-0ubuntu2 -https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/log/?h=ubuntu/devel + https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/log/?h=ubuntu/devel As a side effect ignition-physics package needs also to be patch updated: - ignition-physics to 5.1.0+ds1-4.1ubuntu2 -(Imported from https://salsa.debian.org/science-team/ignition-physics) + (Imported from https://salsa.debian.org/science-team/ignition-physics) The review found that there was a problem with a missing ignition-common package in s390: - - ignition-common (needs a rev bump) - https://git.launchpad.net/~j-rivero/ubuntu/+source/ignition-common/log/?h=ubuntu/noble + - ignition-common (needs a rev bump) + https://git.launchpad.net/~j-rivero/ubuntu/+source/ignition-common/log/?h=ubuntu/noble Package PPA: https://launchpad.net/~j-rivero/+archive/ubuntu/urdfdom4-noble/+packages [Other info] I have both version bumps ready on Debian but the 64bit_time transition[1] is preventing the packages to go through the lib transition since two weeks ago and counting. As we want to have these new versions in 24.04 (feature freeze is coming soon), we do the version bump directly on Ubuntu. [Justification] Important updates in a couple of packages used by the Open Robotics Community, particularly affecting ROS (Robot Operative System) and the ignition/Gazebo simulator. * urdfdom is changing the ABI/API completely by replacing tinyxml with tinyxml2 - * Dart current version 6.9.2 was released in .. 2019 :( + * Dart current version 6.12.1 was released in .. 2019. + + There are important bugfixes in DART, specially the fix for a ton of + compiler warnings with gcc-13 and patches for skeleton trees and + grouping of constraints. Both packages should be lintian clean. [Transition details] The PPA includes all direct dependencies of urfdom and DART (ignition- physics and ros-urdf). * ignition-physics include a patch to work with new DART adding conditional code to deal with minor DART API renames. All the previous architectures where the software was building before are also supported in the update with an important exception: new DART upstream releases do not support 32 bits, so armhf is lost from the list. [1] https://lists.debian.org/debian-devel-announce/2024/02/msg0.html ** Summary changed: - Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages) + [FFe] Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053254 Title: [FFe] Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dart/+bug/2053254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053254] Re: Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages)
** Description changed: Versions bump for the Open Robotics Community packages: - urdfdom to 4.0.0-0ubuntu1 +(Imported from https://salsa.debian.org/science-team/urdfdom) - dart to 6.13.1+ds-0ubuntu2 +https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/log/?h=ubuntu/devel As a side effect ignition-physics package needs also to be patch updated: - ignition-physics to 5.1.0+ds1-4.1ubuntu2 +(Imported from https://salsa.debian.org/science-team/ignition-physics) + + The review found that there was a problem with a missing ignition-common package in s390: + - ignition-common (needs a rev bump) + https://git.launchpad.net/~j-rivero/ubuntu/+source/ignition-common/log/?h=ubuntu/noble Package PPA: https://launchpad.net/~j-rivero/+archive/ubuntu/urdfdom4-noble/+packages - (let me know if you prefer the code in bzr) [Other info] I have both version bumps ready on Debian but the 64bit_time transition[1] is preventing the packages to go through the lib transition since two weeks ago and counting. As we want to have these new versions in 24.04 (feature freeze is coming soon), we do the version bump directly on Ubuntu. [Justification] Important updates in a couple of packages used by the Open Robotics Community, particularly affecting ROS (Robot Operative System) and the ignition/Gazebo simulator. * urdfdom is changing the ABI/API completely by replacing tinyxml with tinyxml2 * Dart current version 6.9.2 was released in .. 2019 :( Both packages should be lintian clean. [Transition details] The PPA includes all direct dependencies of urfdom and DART (ignition- physics and ros-urdf). * ignition-physics include a patch to work with new DART adding conditional code to deal with minor DART API renames. All the previous architectures where the software was building before are also supported in the update with an important exception: new DART upstream releases do not support 32 bits, so armhf is lost from the list. [1] https://lists.debian.org/debian-devel-announce/2024/02/msg0.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053254 Title: Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dart/+bug/2053254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053254] Re: Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages)
The PPA now has the s390x package of dart finally. Answering the issues that Lucas found in the packaging: > And FWIW, we are using git to maintain ubuntu package (using git-ubuntu), bzr > has not been used for packages for a while AFAIK. But if it is easier for you > to provide the packages in a PPA, that's also works IMO. I've migrated the bazaar changes to Git and commit new changes to ubuntu/devel https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/log/?h=ubuntu/devel > Thanks for the updated packages! I think you also noticed that two packages > there, in the PPA, are failing to build from source in s390x, right? We need > to > fix that because s390x is a officially supported architecture. Could you > please > take a look to see if you can identify any issue? Took me a little bit to debug things of a large package on s390x emulation but finally found the problem in one of the dependencies of dart. I reported it upstream with the result of my research, it is not trivial to fix: https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/commit/?h=ubuntu/devel=84595c63d173c78f1c2653d3dd872ae44bbc48b5 > Missing build dependencies: libignition-common-dev (>= 4.0.0) > If you check the version of this package in Noble you will notice that it should be satisfiable: > libignition-common-dev | 4.7.0+ds2-2ubuntu1 | noble/universe | amd64, arm64, armhf, ppc64el, riscv64 Also invested a bit of time debugging this, seems to me like there were some platforms related to problems detailed in https://bugs.debian.org/977638 I've upload a new ignition-common package from the ubuntu/nobel branch that built on s390x: https://git.launchpad.net/~j-rivero/ubuntu/+source/ignition-common/log/?h=ubuntu/noble that > Regarding the dart armhf unsupportability, if upstream says it is not > supported, you should change the Architecture fields in debian/control to > reflect that. If you leave arch:any then it will be built in all > architectures, > you'd need to exclude armhf. Done in https://git.launchpad.net/~j-rivero/ubuntu/+source/dart/commit/?h=ubuntu/devel=a6a3f90252d0b47ec73638566f1b046a22ee1134 ** Bug watch added: Debian Bug tracker #977638 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977638 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053254 Title: Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dart/+bug/2053254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058279] [NEW] [FFe] Sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental (main)
Public bug reported: Please sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental (main) Changelog entries since current noble version 1.13.0+dfsg-4build2: pcl (1.14.0+dfsg-1) experimental; urgency=medium * Update Files-Excluded to drop zlib sources * New upstream version 1.14.0+dfsg * Update d/copyright * Rediff patches * Rename library packages due to Soname bump -- Jochen Sprickerhof Wed, 07 Feb 2024 08:31:15 +0100 = FFe Information = Version bump for the pcl package to latest 1.14 [Justification] Current PCL in noble is from 2022, the latest 1.14 was released this same year. There are a good bunch of bugfixes specially in 1.13.1 that are relevant. The new version specially fixes a warning during the configuration phase for current CMake + Eigen3: --8<--- CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/pcl/PCLConfig.cmake:147 (find_package): Policy CMP0144 is not set: find_package uses upper-case _ROOT variables. Run "cmake --help-policy CMP0144" for policy details. Use the cmake_policy command to set the policy and suppress this warning. CMake variable EIGEN_ROOT is set to: /usr/include/eigen3 --8<--- Attached is the file with changes for versions 1.13.1 and 1.14.0. [Other Info] The package has been more than one month in debian experimental, probably delaying the migration to unstable by the time_64t ABI transition. [Dependencies] I've set up a Noble PPA to test the only dependency on Noble which is the ros-perception-pcl that needs to be recompiled against this new version bump. Compiles fine in all architectures: - https://launchpad.net/~j-rivero/+archive/ubuntu/pcl-1.14-noble ** Affects: pcl (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Description changed: Please sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental (main) Changelog entries since current noble version 1.13.0+dfsg-4build2: pcl (1.14.0+dfsg-1) experimental; urgency=medium - * Update Files-Excluded to drop zlib sources - * New upstream version 1.14.0+dfsg - * Update d/copyright - * Rediff patches - * Rename library packages due to Soname bump + * Update Files-Excluded to drop zlib sources + * New upstream version 1.14.0+dfsg + * Update d/copyright + * Rediff patches + * Rename library packages due to Soname bump - -- Jochen Sprickerhof Wed, 07 Feb 2024 08:31:15 + -- Jochen Sprickerhof Wed, 07 Feb 2024 08:31:15 +0100 + + + --- FFe Information --- + + + Version bump for the pcl package to latest 1.14 + + [Justification] + + Current PCL in noble is from 2022, the latest 1.14 was released this + same year. There are a good bunch of bugfixes specially in 1.13.1 that + are relevant. The new version also specially fixes warnings during the + configuration phase for current Eigen3: + + --8<--- + CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/pcl/PCLConfig.cmake:147 (find_package): Policy CMP0144 is not set: find_package uses upper-case _ROOT variables. Run "cmake --help-policy CMP0144" for policy details. Use the cmake_policy + command to set the policy and suppress this warning. + + CMake variable EIGEN_ROOT is set to: /usr/include/eigen3 + + --8<--- + + Attached is the file with changes for versions 1.13.1 and 1.14.0. + + [Other Info] + + The package has been more than one month in debian experimental, + probably delaying the migration to unstable by the time_64t ABI + transition. + + [Dependencies] + + I've set up a Noble PPA to test the only dependency on Noble which is + the ros-perception-pcl that needs to be recompiled against this new + version bump. Compiles fine in all architectures: + + - https://launchpad.net/~j-rivero/+archive/ubuntu/pcl-1.14-noble ** Description changed: Please sync pcl 1.14.0+dfsg-1 (universe) from Debian experimental (main) Changelog entries since current noble version 1.13.0+dfsg-4build2: pcl (1.14.0+dfsg-1) experimental; urgency=medium * Update Files-Excluded to drop zlib sources * New upstream version 1.14.0+dfsg * Update d/copyright * Rediff patches * Rename library packages due to Soname bump -- Jochen Sprickerhof Wed, 07 Feb 2024 08:31:15 +0100 - - --- FFe Information --- - + = + FFe Information + = Version bump for the pcl package to latest 1.14 [Justification] Current PCL in noble is from 2022, the latest 1.14 was released this same year. There are a good bunch of bugfixes specially in 1.13.1 that are relevant. The new version also specially fixes warnings during the configuration phase for current Eigen3: --8<--- - CMake Warning (dev) at /usr/lib/x86_64-linux-gnu/cmake/pcl/PCLConfig.cmake:147 (find_package):
[Bug 2053254] Re: Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages)
Thanks Benjamin. I've been working on Lucas comments during the last week and hope to have ready the changes in this week. Yesterday upstream releases a new version that fixes all the compiler warnings for GCC-13 and I want to include it so we don't need to disable them: https://code.launchpad.net/~j-rivero/ubuntu/+source/dart/+git/dart/+ref/ubuntu/devel I'll prepare the FFe ASAP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053254 Title: Update urdfdom, dart and ignition-physics for Noble (Open Robotics packages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dart/+bug/2053254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054477] Re: [FFe] Update ogre-next to 2.3.3 for Noble
Thanks Steve for the approval. > I'm not sure why there's an ignition-cmake task here, please clarify. ignition-cmake are a set of CMake helpers used by the ignition/gazebo family but can also be used alone. One of the helpers is a Find module for ogre-next (also named Ogre2) https://salsa.debian.org/science- team/ignition-cmake/-/blob/master/cmake/FindIgnOGRE2.cmake. Now that ogre-next used a more standard approach for installing files and dirs, we need to update the module to drop hacks and other ugly patches. Final note: I realized yesterday that the vulkan support was not being detected in the packaging so I've imported a couple of patches to make it work on all arches. Final d/changelog: ogre-next (2.3.3+dfsg-0ubuntu1) UNRELEASED; urgency=medium * New upstream version 2.3.3+dfsg * Rediff patches * Massive cleanup of d/rules after upstream merges * Update d/control and .install to 2.3.3 * Update d/copyright * Fix package name for conflict with 1.9 (LP: #1987207) (LP: #2003346) * Fix blender-ogre conflict name * Added vulkan dependencies * [PATCH] Added support for riscv64 and ppc64 * [PATCH] Avoid shaderrc vulkan dependency * [PATCH] Fix armhf vulkan build Corresponding 2.3.3+dfsg-5 build in the PPA https://code.launchpad.net/~j-rivero/+recipe/ogre-next-daily-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054477 Title: [FFe] Update ogre-next to 2.3.3 for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-cmake/+bug/2054477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054477] Re: Update ogre-next to 2.3.3 for Noble
** Description changed: - Version bump for ogre-next to version 2.3.1, well tested by Open + Version bump for ogre-next to version 2.3.3, well tested by Open Robotics under the Gazebo simulator. - * Package PPA: - - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe - * Bzr and code: -- https://code.launchpad.net/~j-rivero/+junk/ogre-next + * Package PPA: + - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe + * Git ubunut/devel branch + - https://code.launchpad.net/~j-rivero/ubuntu/+source/ogre-next/+git/ogre-next + + + [Justification] + + ogre-next current version is 2.2.5 and was released in 2021. It does not support vulkan which probably make the release not interesting for the vast majority of current rendering developers. The bump also fixes + LP: #1987207 and LP: #2003346. + + [Other Info] - The package is not included in Debian. The version bump to 2.3.1 has - been used by the Gazebo simulator team for the latest releases of Gazebo - during several years and I've included the patches that has proven to be - necessary, specially for vulkan support. + The package is not included in Debian. The version bump to 2.3.1 has been used by the Gazebo simulator team for the latest releases of Gazebo during several years and I've included the patches that has proven to be necessary, specially for vulkan support. Many of the + Open Robotics patches has been merged upstream. - Changes done in the version bump: - * Upload upstream code 2.3.1 - * Update d/copyright - * Fix package name for conflict with 1.9 -(LP: #1987207) (LP: #2003346) - * Include vulkan patches - * Include upstream patch to rename the project to Ogre-Next - * Include patches to deal with the rename and clean up d/rules - * Include patch for building with recent gcc - * Remove tinyxml embedded in code + Changes done with respect to ubuntu/devel branch: + + 1dc7fa0 (HEAD -> ubuntu/devel, origin/ubuntu/devel) Update d/changelog + fe78c7b Upstream fixed install paths to be standard + b272862 Update d/copyright + 5ccf1e5 Massive cleanup of d/rules + c020ca5 Update d/changelog + 5cb9fdb [PATCH] Added suport for riscv64 and ppc64 + 6ca8aa6 Rediff patches + 3b2cb51 Update d/control and .install to 2.3.3 + 3d60843 Update upstream source from tag 'upstream/2.3.3+dfsg' + 687514e (tag: upstream/2.3.3+dfsg, origin/upstream, upstream) New upstream version 2.3.3+dfsg + 547df32 Fix blender-ogre conflict name + 3940cc5 Update d/changelog + d50eb7e Added a d/gbp.conf + 3286c7d Initial commit on orphan branch + + Changes in d/changelog: + * New upstream version 2.3.3+dfsg + * Rediff patches + * Massive cleanup of d/rules after upstream merges + * Update d/control and .install to 2.3.3 + * Update d/copyright + * Fix package name for conflict with 1.9 + (LP: #1987207) (LP: #2003346) + * Fix blender-ogre conflict name + * [PATCH] Added support for riscv64 and ppc64 [Dependencies] There is one direct dependency of ogre-next, ignition-rendering. Given that the version in Debian/Ubuntu is too old and probably a candidate to be removed, I've uploaded a new version of ignition-rendering that drops the support for ogre-next. It is still useful since it can use ogre-1.9. - * Same package PPA with ogre-next - - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe - * Git and code for 6.1.0+ds-0ubuntu3: -- https://code.launchpad.net/~j-rivero/ubuntu/+source/ignition-rendering/+git/ignition-rendering/+ref/ubuntu/devel + * Same package PPA with ogre-next + - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe + * Git and code for 6.1.0+ds-0ubuntu3: + - https://code.launchpad.net/~j-rivero/ubuntu/+source/ignition-rendering/+git/ignition-rendering/+ref/ubuntu/devel There is another package that deal with ogre-next in an indirect manner providing build helpers: ignition-cmake. I've also patched this package to improve the ogre-next patch: - - * Same package PPA with ogre-next 2.17.1-2ubuntu2 - - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe - * Git and code for -- https://code.launchpad.net/~j-rivero/ubuntu/+source/ignition-cmake/+git/ignition-cmake/+ref/ubuntu/devel - - - [Justification] - - ogre-next current version is 2.2.5 and was released in 2021. It does not - support vulkan which probably make the release not interesting for the - vast majority of current rendering developers. + * Same package PPA with ogre-next 2.17.1-2ubuntu2 + - https://code.launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-recipe + * Git and code for + - https://code.launchpad.net/~j-rivero/ubuntu/+source/ignition-cmake/+git/ignition-cmake/+ref/ubuntu/devel ** Description changed: Version bump for ogre-next to version 2.3.3, well tested by Open Robotics under the Gazebo simulator. * Package PPA: -
[Bug 2054477] Re: Update ogre-next to 2.3.3 for Noble
** Summary changed: - Update ogre-next to 2.3.1 for Noble + Update ogre-next to 2.3.3 for Noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054477 Title: Update ogre-next to 2.3.3 for Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-cmake/+bug/2054477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053256] Re: [FFe] Update lcm to 1.5 for Noble
> Regarding how you are providing the package to be sponsored, I personally would prefer a git branch against pkg/ubuntu/devel. For these cases where we go ahead of debian, what I would do is have the first commit on top of pkg/ubuntu/devel be the new upstream version, and then whatever changes are needed in the packaging to get that built for noble. I did that and published https://code.launchpad.net/~j-rivero/ubuntu/+source/lcm/+git/lcm/+ref/ubuntu/devel ** Description changed: Version bump for the lcm package to latest version 1.5.0+repack-0ubuntu1 - Package PPA: + Git changes and Package PPA: + - Ubuntu/devel git fork: + https://code.launchpad.net/~j-rivero/ubuntu/+source/lcm/+git/lcm/+ref/ubuntu/devel - https://launchpad.net/~j-rivero/+archive/ubuntu/lcm-1.5 -1.5.0+repack-0ubuntu1 - - Debian Git Merge request -https://salsa.debian.org/debian/lcm/-/merge_requests/1 - + 1.5.0+repack-0ubuntu1 + - Debian Git Merge request + https://salsa.debian.org/debian/lcm/-/merge_requests/1 Build logs for all architectures are available in the PPA. [Justification] Current lcm version 1.3.1 comes from 2016 and is quite broken for different use cases when using the tools provided by the package with modern versions of java and/or python, see https://bugs.launchpad.net/ubuntu/+source/lcm/+bug/1956368 as an example. Running a quick test for lcm-logplayer-gui in a Noble docker container: - 8< - jrivero@86d205b40951:~$ lcm-logplayer-gui + jrivero@86d205b40951:~$ lcm-logplayer-gui Unrecognized option: -Xincgc Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. - 8< [Other info] I have the version bump ready on Debian but the 64bit_time transition[1] is preventing the - packages to go through the lib transition since two weeks before the Import Freeze. + packages to go through the lib transition since two weeks before the Import Freeze. https://salsa.debian.org/debian/lcm/-/merge_requests/1 Changes done in the packaging: * New upstream version 1.5.0+repack * Formatter changes * Bump standards to 4.6.2 * Use default-jdk package for java support * Bump version to 1.5.0+repack1 * Rediff patches: * PATCH: use gnuinstalldirs in CMake * PATCH: use gtest from system * PATCH: use java system dependencies instead of embedded files * PATCH: Encode utf8 characters to fix the java build * PATCH: fix manpages name to make lintian happy * Add CMake to d/control * Use --no-parallel for testing * Cleanup d/rules * Update liblcm-doc.docs for new paths * Generalize d/liblcm-dev.install * Convert package to use pybuild. Change d/rules heavily. * Update java dependencies in d/control * Update d/copyright file * Keep lcm-java.pc only in the java package * Remove .doctrees from the -docs package * Add bindnow to DEB_BUILD_MAINT_OPTIONS * Replace embedded fonts and jquery with system dependencies * Remove .gitignore from liblcm-doc installation * Update existing patch for javadoc generation * Update d/changelog * Rework java patch to use offline generation * Reorder java dependencies: in -bin and -java * Adding Section: to packages * Added autotest: install and build-cpp [Risk analysis - Library transition] There is no package depending on lcm currently in the Ubuntu repository. No library transition needs to performed. [Testing done] In the same Noble container I added the PPA and check the upgrade: --- 8< - The following additional packages will be installed: - libapache-pom-java libcommons-io-java libcommons-logging-java libcommons-parent-java libhamcrest-java libjchart2d-java libjide-oss-java liblcm-bin liblcm-java liblcm1 - libxmlgraphics-commons-java + libapache-pom-java libcommons-io-java libcommons-logging-java libcommons-parent-java libhamcrest-java libjchart2d-java libjide-oss-java liblcm-bin liblcm-java liblcm1 + libxmlgraphics-commons-java Suggested packages: - libcommons-io-java-doc libavalon-framework-java libexcalibur-logkit-java liblog4j1.2-java libjchart2d-java-doc libjide-oss-java-doc libxmlgraphics-commons-java-doc + libcommons-io-java-doc libavalon-framework-java libexcalibur-logkit-java liblog4j1.2-java libjchart2d-java-doc libjide-oss-java-doc libxmlgraphics-commons-java-doc The following NEW packages will be installed: - libapache-pom-java libcommons-io-java libcommons-logging-java libcommons-parent-java libhamcrest-java libjchart2d-java libjide-oss-java liblcm-dev liblcm-java libxmlgraphics-commons-java + libapache-pom-java libcommons-io-java libcommons-logging-java libcommons-parent-java libhamcrest-java libjchart2d-java libjide-oss-java liblcm-dev liblcm-java
[Bug 2053256] Re: Update lcm to 1.5 for Noble
Diff of upstream changes from version 1.3.1 to 1.5.0 ** Description changed: Version bump for the lcm package to latest version 1.5.0+repack-0ubuntu1 Package PPA: - - https://launchpad.net/~j-rivero/+archive/ubuntu/lcm-1.5 - (let me know if you prefer a Bzr branch) + - https://launchpad.net/~j-rivero/+archive/ubuntu/lcm-1.5 +1.5.0+repack-0ubuntu1 + - Debian Git Merge request +https://salsa.debian.org/debian/lcm/-/merge_requests/1 + + + Build logs for all architectures are available in the PPA. + + [Justification] + + Current lcm version 1.3.1 comes from 2016 and is quite broken for + different use cases when using the tools provided by the package with + modern versions of java and/or python, see + https://bugs.launchpad.net/ubuntu/+source/lcm/+bug/1956368 as an + example. + + Running a quick test for lcm-logplayer-gui in a Noble docker container: + - 8< + jrivero@86d205b40951:~$ lcm-logplayer-gui + Unrecognized option: -Xincgc + Error: Could not create the Java Virtual Machine. + Error: A fatal exception has occurred. Program will exit. + - 8< [Other info] I have the version bump ready on Debian but the 64bit_time transition[1] is preventing the - packages to go through the lib transition since two weeks ago and counting. As we want to - have these new versions in 24.04 (feature freeze is coming soon), we need to do the version bump directly on Ubuntu. + packages to go through the lib transition since two weeks before the Import Freeze. + + https://salsa.debian.org/debian/lcm/-/merge_requests/1 Changes done in the packaging: - * New upstream version 1.5.0+repack - * Formatter changes - * Bump standards to 4.6.2 - * Use default-jdk package for java support - * Bump version to 1.5.0+repack1 - * Rediff patches: - * PATCH: use gnuinstalldirs in CMake - * PATCH: use gtest from system - * PATCH: use java system dependencies instead of embedded files - * PATCH: Encode utf8 characters to fix the java build - * PATCH: fix manpages name to make lintian happy - * Add CMake to d/control - * Use --no-parallel for testing - * Cleanup d/rules - * Update liblcm-doc.docs for new paths - * Generalize d/liblcm-dev.install - * Convert package to use pybuild. Change d/rules heavily. - * Update java dependencies in d/control - * Update d/copyright file - * Keep lcm-java.pc only in the java package - * Remove .doctrees from the -docs package - * Add bindnow to DEB_BUILD_MAINT_OPTIONS - * Replace embedded fonts and jquery with system dependencies - * Remove .gitignore from liblcm-doc installation - * Update existing patch for javadoc generation - * Update d/changelog - * Rework java patch to use offline generation - * Reorder java dependencies: in -bin and -java - * Adding Section: to packages - * Added autotest: install and build-cpp - - [Justification] - - Current lcm version 1.3.1 comes from 2016 !! and is broken for different - use cases when using the tools provided by the package with modern - versions of java and/or python. - - Curated changelog summary: - - Release 1.5.0 - General - Several bug fixes - Fixed general and deprecation warnings on recent versions of Python and Java - Build system - Updated CMake to fix warnings - Java - Version 1.8 or later is now required - Release 1.4.0 - Build system - Switch to CMake - Add CPack support - lcm-gen - Allow arrays to be sized with const values - C - Add lcm_subscription_get_queue_size() - Standardize C/C++ code formatting with clang-format - C++ - Add support for some C++11 features (lambda subscribe) - add lcm::Subscription::getQueueSize() - Python -Add dimensions and typenames fields for better introspection - lcm-logger - flush buffers before exiting - General - Lots of misc bugfixes + * New upstream version 1.5.0+repack + * Formatter changes + * Bump standards to 4.6.2 + * Use default-jdk package for java support + * Bump version to 1.5.0+repack1 + * Rediff patches: + * PATCH: use gnuinstalldirs in CMake + * PATCH: use gtest from system + * PATCH: use java system dependencies instead of embedded files + * PATCH: Encode utf8 characters to fix the java build + * PATCH: fix manpages name to make lintian happy + * Add CMake to d/control + * Use --no-parallel for testing + * Cleanup d/rules + * Update liblcm-doc.docs for new paths + * Generalize d/liblcm-dev.install + * Convert package to use pybuild. Change d/rules heavily. + * Update java dependencies in d/control + * Update d/copyright file + * Keep lcm-java.pc only in the java package + * Remove .doctrees from the -docs package + * Add bindnow to DEB_BUILD_MAINT_OPTIONS + * Replace embedded fonts and jquery with system dependencies + * Remove
[Bug 2054151] Re: New http_relay package for Noble (for Robotics community)
Now in Noble/Universe. Fix Released. ** Changed in: http-relay (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054151 Title: New http_relay package for Noble (for Robotics community) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/http-relay/+bug/2054151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054151] Re: New http_relay package for Noble (for Robotics community)
It is now on noble proposed https://launchpad.net/ubuntu/+source/http- relay/2.1.3-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054151 Title: New http_relay package for Noble (for Robotics community) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2054151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054151] Re: New http_relay package for Noble (for Robotics community)
The package has been uploaded in Debian to the NEW queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054151 Title: New http_relay package for Noble (for Robotics community) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2054151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959098] Re: [ovn] metadata route missing on the guest
Actually I can confirm ovn_metadata_enabled is set to "True". I was looking in the wrong place (compute/metadata agent server) and this seems to be set in the API server node: /etc/neutron# grep -r ovn_metadata plugins/ml2/ml2_conf.ini:ovn_metadata_enabled = True ovn.ini:#ovn_metadata_enabled = false -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959098 Title: [ovn] metadata route missing on the guest To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1959098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959098] Re: [ovn] metadata route missing on the guest
affected network/subnet information ** Attachment added: "LP1959098-affected-network.txt" https://bugs.launchpad.net/neutron/+bug/1959098/+attachment/5588891/+files/LP1959098-affected-network.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959098 Title: [ovn] metadata route missing on the guest To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1959098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959098] Re: [ovn] metadata route missing on the guest
unaffected network/subnet information ** Attachment added: "LP1959098-unaffected-network.txt" https://bugs.launchpad.net/neutron/+bug/1959098/+attachment/5588890/+files/LP1959098-unaffected-network.txt ** Attachment removed: "LP1959098-affected-network.txt" https://bugs.launchpad.net/neutron/+bug/1959098/+attachment/559/+files/LP1959098-affected-network.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959098 Title: [ovn] metadata route missing on the guest To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1959098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959098] Re: [ovn] metadata route missing on the guest
** Attachment added: "LP1959098-affected-network.txt" https://bugs.launchpad.net/neutron/+bug/1959098/+attachment/559/+files/LP1959098-affected-network.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959098 Title: [ovn] metadata route missing on the guest To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1959098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959098] Re: [ovn] metadata route missing on the guest
We hit this issue today as well. Same symptoms:
* Failed to get metadata during VM launch - consistently and only on the
"affected" network. Other networks like "unaffected" are OK.
* Missing metadata route inside VM
* After adding the route manually to the .2 IP we can ping/curl the metadata
endpoint with no issues, so it seems the route is the only thing missing.
* The workaround of adding the metadata route explicitly to the relevant router
allows new VMs in the affected network to get metadata without problems.
These are the current packages:
ii neutron-common 2:16.4.2-0ubuntu1
ii neutron-ovn-metadata-agent 2:16.4.2-0ubuntu1
ii python3-neutron 2:16.4.2-0ubuntu1
ii python3-neutron-lib 2.3.0-0ubuntu1
ii python3-neutronclient 1:7.1.1-0ubuntu1
I am attaching the information requested above for an "affected" and
"unaffected" network. The main difference I see is that the "unaffected"
subnet has the following option in the ovn-nb that is missing from the
"affected" subnet:
classless_static_route="{169.254.169.254/32,10.131.83.2,
0.0.0.0/0,10.131.83.1}"
The two patches you mention are indeed included in python3-neutron
2:16.4.2-0ubuntu1. I additionally confirmed by checking
/usr/lib/python3/dist-
packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovn_client.py
Regarding "ovn_metadata_enabled", I didn't find it set to "true" in any
config under /etc/neutron. I can only see the default commented out and
no mention in neutron_ovn_metadata_agent.ini, which has the ovs/ovn
config in it (but I am no expert)
/etc/neutron# grep -r ovn_metadata
ovn.ini:#ovn_metadata_enabled = false
The creation logs are no longer available. The ports for the .2 IPs are
created in the subnet, and they do have a device_id of
ovnmeta-, but the device_owner is network:dhcp and not
network:distributed as you seem to be expecting. I added the output of
`port show` for them as well. Note that other networks on the same
compute nodes have no issues providing metadata, including the
"unaffected" network (data attached).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959098
Title:
[ovn] metadata route missing on the guest
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1959098/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970707] [NEW] unable to install new version of '/usr/share/themes/Pop-dark/gtk-3.20/gtk.css': No such file or directory
Public bug reported: Release of Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Version of the package Version 5.2.0~1586289568~20.04~f35b83b~ubuntu1 dpkg: error processing archive /var/cache/apt/archives/pop-gtk-theme_5.2.0~1586289568~20.04~f35b83b~ubuntu1_all.deb (--unpack): unable to install new version of '/usr/share/themes/Pop-dark/gtk-3.20/gtk.css': No such file or directory No apport report written because the error message indicates an issue on the local system Errors were encountered while processing: /var/cache/apt/archives/pop-gtk-theme_5.2.0~1586289568~20.04~f35b83b~ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pop-gtk-theme 3.1.2~1535402967~18.04~cc107bf ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178 Uname: Linux 5.4.0-109-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 10:58:36 2022 InstallationDate: Installed on 2022-04-08 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pop-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-10-28T20:41:46 ** Affects: pop-gtk-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970707 Title: unable to install new version of '/usr/share/themes/Pop- dark/gtk-3.20/gtk.css': No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pop-gtk-theme/+bug/1970707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970030] [NEW] package calamares-settings-debian (not installed) failed to install/upgrade: trying to overwrite '/etc/calamares/modules/bootloader.conf', which is also in package calamares-settin
Public bug reported: I am trying to download application. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: calamares-settings-debian (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 AptOrdering: calamares-settings-debian:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 23 05:21:11 2022 DpkgTerminalLog: Preparing to unpack .../calamares-settings-debian_11.0.5-2_all.deb ... Unpacking calamares-settings-debian (11.0.5-2) ... dpkg: error processing archive /var/cache/apt/archives/calamares-settings-debian_11.0.5-2_all.deb (--unpack): trying to overwrite '/etc/calamares/modules/bootloader.conf', which is also in package calamares-settings-lubuntu 1:22.04.4 DuplicateSignature: package:calamares-settings-debian:(not installed) Unpacking calamares-settings-debian (11.0.5-2) ... dpkg: error processing archive /var/cache/apt/archives/calamares-settings-debian_11.0.5-2_all.deb (--unpack): trying to overwrite '/etc/calamares/modules/bootloader.conf', which is also in package calamares-settings-lubuntu 1:22.04.4 ErrorMessage: trying to overwrite '/etc/calamares/modules/bootloader.conf', which is also in package calamares-settings-lubuntu 1:22.04.4 InstallationDate: Installed on 2022-04-22 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: calamares-settings-debian Title: package calamares-settings-debian (not installed) failed to install/upgrade: trying to overwrite '/etc/calamares/modules/bootloader.conf', which is also in package calamares-settings-lubuntu 1:22.04.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: calamares-settings-debian (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970030 Title: package calamares-settings-debian (not installed) failed to install/upgrade: trying to overwrite '/etc/calamares/modules/bootloader.conf', which is also in package calamares-settings-lubuntu 1:22.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-debian/+bug/1970030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960940] Re: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
Thanks so much Graham! I was testing the installation and the simulator and seems to work fine. There is a minor inconvenient for users that is trivial to fix: https://bugs.launchpad.net/ubuntu/+source/ignition- gazebo/+bug/1969803. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960940 Title: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969803] [NEW] [needs-sponsor] Change Suggests by Recommends for ignition-tools in ignition-gazebo in Jammy
Public bug reported: Minor change to move ignition-tools from Suggest to Recommends in ignition-gazebo. The ign tool inside ignition-tools is required to be able to star the Ignition Gazebo simulator. The number of cases where an user want to have the libraries but never start the simulator are unusual. Attached is the debdiff against current version. ** Affects: ignition-gazebo (Ubuntu) Importance: Undecided Assignee: Jose Luis Rivero (j-rivero) Status: New ** Tags: jammy ** Patch added: "ignition-gazebo_recommends_tools.debdiff" https://bugs.launchpad.net/bugs/1969803/+attachment/5582140/+files/ignition-gazebo_recommends_tools.debdiff ** Changed in: ignition-gazebo (Ubuntu) Assignee: (unassigned) => Jose Luis Rivero (j-rivero) ** Summary changed: - [needs-sponsor] Change Suggests by Recommends for ignition-tools in ignition-gazebo + [needs-sponsor] Change Suggests by Recommends for ignition-tools in ignition-gazebo in Jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969803 Title: [needs-sponsor] Change Suggests by Recommends for ignition-tools in ignition-gazebo in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-gazebo/+bug/1969803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960940] Re: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
I think I have it. I added more details in the commit to bzr and in the patch description according to DEP-3. In summary: The test is failing due to a problem in ignition-tools version 1.4.1 (coming from Debian). It does not include libignition-tools-backward lib due to a bug in Debian packaging (requiring a new package + NEW queue, I'll fix it in Debian where I'm the maintainer). The bug is triggering a warning in output "Library error: libignition- tools-backward.so not found. Improved backtrace generation will be disabled". That support is optional so I have changed the tests to expect a substring with the real value instead of fully match the real value, that should make it to work with both: backwards support or not in ignition-tools. Commit with the patch: https://bazaar.launchpad.net/~j-rivero/+junk/ignition-launch/revision/2 Bump revision at: https://bazaar.launchpad.net/~j-rivero/+junk/ignition-launch/revision/3 Tested: https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages/+build/23559082 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960940 Title: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960940] Re: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
Looking at it now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960940 Title: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960940] Re: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
> We just need a couple of small patches: > - ignition-physics for amd64 > https://bugs.launchpad.net/ubuntu/+source/ignition-physics/+bug/1965064 > - ignition-rendering > https://bugs.launchpad.net/ubuntu/+source/ignition-rendering/+bug/1967888 These open bugs are now fixed. We should be in a good position to review and import ignition-gazebo and ignition-launch. ** Tags removed: needs-packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960940 Title: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969289] [NEW] Secondary display does not work
Public bug reported: Secondary display does not work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 20:29:43 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06fd] InstallationDate: Installed on 2022-04-14 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) MachineType: Dell Inc. Inspiron 13-7359 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=3b34bc2c-2f64-49d2-9734-d6ff9a9d3b14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2016 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.12.00 dmi.board.name: 0X1DP8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.12.00:bd09/06/2016:br1.12:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0X1DP8:rvrA00:cvnDellInc.:ct9:cvr:sku06FD: dmi.product.name: Inspiron 13-7359 dmi.product.sku: 06FD dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969289 Title: Secondary display does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965780] Re: [needs-sponsor] Sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main)
Hello Łukasz: I think we did a good work with versioning and the upload should have gone just fine. In fact, I was able to test Gazebo 11.10.2+dfsg-1 directly from Jammy repositories and works like a charm. It does not conflict anymore with opencv. Thanks so much for the review and upload! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965780 Title: [needs-sponsor] Sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gazebo/+bug/1965780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773811] Re: [SRU] Missing static libs in the -dev package metadata
** Changed in: gazebo (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773811 Title: [SRU] Missing static libs in the -dev package metadata To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gazebo/+bug/1773811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960940] Re: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
Hello Łukasz: Is there anything more I can do to help with these two remaining packages? We have been tested ignition-gazebo simulator on Jammy and it works great. We just need a couple of small patches: - ignition-physics for amd64 https://bugs.launchpad.net/ubuntu/+source/ignition-physics/+bug/1965064 - ignition-rendering https://bugs.launchpad.net/ubuntu/+source/ignition-rendering/+bug/1967888 With these two patches, the two packages ignition-gazebo and ignition- launch were tested successfully in a Jammy system. Thanks for the help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960940 Title: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967888] Re: Patch to fix unusable ign-rendering on Jammy
** Patch added: "ignition-rendering_6.1.0+ds-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/ignition-rendering/+bug/1967888/+attachment/5577343/+files/ignition-rendering_6.1.0+ds-0ubuntu2.debdiff ** Changed in: ignition-rendering (Ubuntu) Assignee: (unassigned) => Jose Luis Rivero (j-rivero) ** Summary changed: - Patch to fix unusable ign-rendering on Jammy + [needs-sponsor] Patch to fix unusable ign-rendering on Jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967888 Title: [needs-sponsor] Patch to fix unusable ign-rendering on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-rendering/+bug/1967888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967888] [NEW] [needs-sponsor] Patch to fix unusable ign-rendering on Jammy
Public bug reported: Current version of ign-rendering on Jammy 6.1.0+ds-0ubuntu1 lack of some basic linking on ogre-next to make the software really usable, otherwise the loader fails to find the needed ogre2 symbols. On top of this, OGRE2_RESOURCE_PATH coming from ogre-next is not correct. The patch attached implements: * Add the missing libraries to the link of ogre2, in 0003-use-ogre-next-debian patch. * Inject right OGRE2_RESOURCE_PATH path to the build instead of leaving the default wrong one ** Affects: ignition-rendering (Ubuntu) Importance: Undecided Assignee: Jose Luis Rivero (j-rivero) Status: New ** Tags: jammy ** Description changed: Current version of ign-rendering on Jammy 6.1.0+ds-0ubuntu1 lack of some basic linking on ogre-next to make the software really usable, otherwise the loader fails to find the needed ogre2 symbols. On top of this, OGRE2_RESOURCE_PATH coming from ogre-next is not correct. The patch attached implements: - * Add the missing libraries to the link of ogre2, in 0003-use-ogre-next-debian patch. - * Inject right OGRE2_RESOURCE_PATH path to the build instead of leaving the default wrong one + * Add the missing libraries to the link of ogre2, in 0003-use-ogre-next-debian patch. + * Inject right OGRE2_RESOURCE_PATH path to the build instead of leaving the default wrong one -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967888 Title: [needs-sponsor] Patch to fix unusable ign-rendering on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-rendering/+bug/1967888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965780] Re: [needs-sponsor] Sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main)
** Summary changed: - Sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main) + [needs-sponsor] Sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965780 Title: [needs-sponsor] Sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gazebo/+bug/1965780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965780] [NEW] Sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main)
Public bug reported: Please sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main) Explanation of the Ubuntu delta and why it can be dropped: * (Build-)depend on libtbb2-dev instead of libtbb-dev. Current Gazebo version in Debian Sid and Ubuntu Jammy is version 11.10.1, the upstream sources were not prepared to use the new tbb, Debian was under an unfinished ongoing transition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007222. Ubuntu Jammy ships the new version of tbb and the solution decided for going forward was to split tbb packages in two different ones conflicting each other. Gazebo was changed to use tbb2-dev (old version of tbb): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006920 This is not needed anymore since 11.10.2 Gazebo is ready for using new tbb. The current setup is causing problems to the robotics community, see https://github.com/ros-planning/navigation2/pull/2852#issuecomment-1072789270 Changelog entries since current jammy version 11.10.1+dfsg-2ubuntu1: gazebo (11.10.2+dfsg-1) experimental; urgency=medium * New upstream version 11.10.2+dfsg * Rediff patches * Use static manpages, Remove dependency on ronn to avoid installing ruby. * Target experimental to test tbb/onetbb transition #1007222 11.10.2 upstream source should be ready for it. -- Jose Luis Rivero Sat, 19 Mar 2022 19:58:37 + I've tested this new version on Jammy under my PPA (Gazebo is amd64 only): https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages/+build/23487008 ** Affects: gazebo (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Tags added: jammy ** Description changed: Please sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main) Explanation of the Ubuntu delta and why it can be dropped: - * (Build-)depend on libtbb2-dev instead of libtbb-dev. + * (Build-)depend on libtbb2-dev instead of libtbb-dev. - Current Gazebo version in Debian Sid and Ubuntu Jammy is version 11.10.1, the - upstream sources were not prepared to use the new tbb, Debian was under an - unfinished ongoing transition + Current Gazebo version in Debian Sid and Ubuntu Jammy is version 11.10.1, the upstream sources were not prepared to use the new tbb, Debian was under an unfinished ongoing transition https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007222. - Ubuntu Jammy ships the new version of tbb and the solution decided for going - forward was to split tbb packages in two different ones conflicting each other. - Gazebo was changed to use tbb2-dev (old version of tbb): + Ubuntu Jammy ships the new version of tbb and the solution decided for going forward was to split tbb packages in two different ones conflicting each other. Gazebo was changed to use tbb2-dev (old version of tbb): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006920 - This is not needed anymore since 11.10.2 Gazebo is ready for using new tbb. The - current setup is causing problems to the robotics community, see + This is not needed anymore since 11.10.2 Gazebo is ready for using new tbb. The current setup is causing problems to the robotics community, see https://github.com/ros-planning/navigation2/pull/2852#issuecomment-1072789270 Changelog entries since current jammy version 11.10.1+dfsg-2ubuntu1: gazebo (11.10.2+dfsg-1) experimental; urgency=medium - * New upstream version 11.10.2+dfsg - * Rediff patches - * Use static manpages, Remove dependency on ronn - to avoid installing ruby. - * Target experimental to test tbb/onetbb transition #1007222 - 11.10.2 upstream source should be ready for it. + * New upstream version 11.10.2+dfsg + * Rediff patches + * Use static manpages, Remove dependency on ronn + to avoid installing ruby. + * Target experimental to test tbb/onetbb transition #1007222 + 11.10.2 upstream source should be ready for it. - -- Jose Luis Rivero Sat, 19 Mar 2022 + -- Jose Luis Rivero Sat, 19 Mar 2022 19:58:37 + I've tested this new version on Jammy under my PPA (Gazebo is amd64 only): https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages/+build/23487008 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965780 Title: Sync gazebo 11.10.2+dfsg-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gazebo/+bug/1965780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960260] Re: [needs-sponsor] Include ignition rendering packages in Ubuntu Jammy
> keep an eye on the builds and always available to provide patches as needed. I just checked that ignition-gui, ignition-rendering and ignition- sensors have been built just fine in amd64, arm64, armhf, ppc64el and riscv64. The only remaining problem would be s390x but the issue is the lack of one of the dependencies (ignition-common) which I believe is out of the scope of this request. I think that we can call it done, thanks for the reviews and fixes Łukasz! ** Changed in: ubuntu Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960260 Title: [needs-sponsor] Include ignition rendering packages in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960940] Re: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
> I have sponsored the rendering packages from the other bug. Not sure if I'll have the cycles to sponsor/review the others today. No worries Łukasz. I've been using these last days to check that all pieces are in place and found a weird bug on ignition-physics amd64 (which is a dependency of ignition-gazebo) that make testsuite to segfault when using Ubuntu's linker optimization flto=auto -ffat-lto- objects. I've fixed the build together with ppc64 in: https://bugs.launchpad.net/ubuntu/+source/ignition-physics/+bug/1965064 (patches are trivial). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960940 Title: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965064] Re: ignition-physics testsuite segfaults on amd64 when using flto=auto -ffat-lto-objects
Attached is the debdiff that solves the problem for the amd64 build by filtering out the flto=auto -ffat-lto-objects. The patch also includes a fix for the ppc64 build now that we are at it. Both changes are reflected in the Changelog and tested in my PPA: * amd64 https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages/+build/23249466 * ppc64 https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages/+build/23249469 ** Patch added: "ignition-physics_5.1.0+ds1-4ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/ignition-physics/+bug/1965064/+attachment/5569797/+files/ignition-physics_5.1.0+ds1-4ubuntu1.debdiff ** Summary changed: - ignition-physics testsuite segfaults on amd64 when using flto=auto -ffat-lto-objects + [needs-sponsor] ignition-physics testsuite segfaults on amd64/Jammy when using flto=auto -ffat-lto-objects -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965064 Title: [needs-sponsor] ignition-physics testsuite segfaults on amd64/Jammy when using flto=auto -ffat-lto-objects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-physics/+bug/1965064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965064] [NEW] ignition-physics testsuite segfaults on amd64 when using flto=auto -ffat-lto-objects
Public bug reported: Current ignition-physics version 5.1.0+ds1-4 fails on amd64 with segfaults in some of the tests: https://launchpadlibrarian.net/589246385/buildlog_ubuntu-jammy-amd64.ignition-physics_5.1.0+ds1-4_BUILDING.txt.gz The situation was unusual since the same version imported from Debian Sid built just fine. I was debugging the problem in upstream issue tracker: https://github.com/ignitionrobotics/ign-physics/issues/330. Summary: Ubuntu Jammy is using linker optimizations -flto=auto -ffat- lto-objects that make the package to fail when running tests in ignition-physics. ** Affects: ignition-physics (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965064 Title: ignition-physics testsuite segfaults on amd64 when using flto=auto -ffat-lto-objects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ignition-physics/+bug/1965064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942695] Re: DeskTop freezes for up to 5 seconds the first keystroke on Gnome terminal after boot.
I am testing Ubuntu 22.04 and until now (03/15/2022) issue solved on RPI4. Thanks anybody, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942695 Title: DeskTop freezes for up to 5 seconds the first keystroke on Gnome terminal after boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1942695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960260] Re: [needs-sponsor] Include ignition rendering packages in Ubuntu Jammy
Thanks so much Łukasz for reviews and comment. > why is NEWS excluded from the ingnition-rendering tarball? It's just an URL. Basically I'd normally not repack the tarball and exclude sources unless really necessary (like when for instance upstream ships something bad in the tarball, like compiled binaries etc.). Not an strong reason for excluding NEWS more than get rid of some not very useful files. I agree, not worth it. I'm using repacking as my normal workflow as Debian maintainer to get rid of embedded libs, copyrighted files and usually include other not so critical files like .github/ or other CI configurations. > ...oh, and since not all architectures were enabled on the PPA (please be sure to enable as many as possible!), please be sure to check if the packages build successfully on ALL the arches after upload. Thanks. And I recommend switching the other arches for future builds. Ouch, enabled ARM but forgot the other previously. I've already enabled all to be checked in possible future iterations. I keep an eye on the builds and always available to provide patches as needed. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960260 Title: [needs-sponsor] Include ignition rendering packages in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960260] Re: [needs-sponsor] Include ignition rendering packages in Ubuntu Jammy
** Summary changed: - [needs-packaging] Include ignition rendering packages in Ubuntu Jammy + [needs-sponsor] Include ignition rendering packages in Ubuntu Jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960260 Title: [needs-sponsor] Include ignition rendering packages in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960940] Re: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
** Summary changed: - [needs-packaging] Include ignition-gazebo simulator in Ubuntu Jammy + [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960940 Title: [needs-sponsor] Include ignition-gazebo simulator in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963583] Re: Needs rebuild in Jammy for python3.10
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963583 Title: Needs rebuild in Jammy for python3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyside2/+bug/1963583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960940] Re: [needs-packaging] Include ignition-gazebo simulator in Ubuntu Jammy
Hello Mathew: Please note that the software is already packaged and can be found in: PPA: https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages Bzr: * https://code.launchpad.net/~j-rivero/+junk/ignition-gazebo * https://code.launchpad.net/~j-rivero/+junk/ignition-launch Could we please revert the changes? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960940 Title: [needs-packaging] Include ignition-gazebo simulator in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960260] Re: [needs-packaging] Include ignition rendering packages in Ubuntu Jammy
Hello Mathew: Please note that I've already packaged the software and it is ready for review. You can access to via: PPA: * https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages Bzr: * https://code.launchpad.net/~j-rivero/+junk/ignition-rendering * https://code.launchpad.net/~j-rivero/+junk/ignition-gui * https://code.launchpad.net/~j-rivero/+junk/ignition-sensors Can we please revert the change in the tittle? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960260 Title: [needs-packaging] Include ignition rendering packages in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961319] Re: ogre-next SMID fix for ppc64el, riscv64, s390x
Thanks Łukasz! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961319 Title: ogre-next SMID fix for ppc64el, riscv64, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/1961319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961319] Re: ogre-next SMID fix for ppc64el, riscv64, s390x
I think I solved it. Attached is the debdiff with the pacth to d/rules and the bump to d/changelog. I tested it in all the arches in https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next- jammy/+packages (bump there from 0ubuntu2 to 0ubuntu2.1 was nothing but rebuild with all arches enabled in the PPA). I've also updated the bzr branch, commits 8 and 9 https://code.launchpad.net/~j-rivero/+junk/ogre-next Thanks. ** Patch added: "ogre-next_2.2.5+dfsg3-0ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/1961319/+attachment/5561668/+files/ogre-next_2.2.5+dfsg3-0ubuntu2.debdiff ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961319 Title: ogre-next SMID fix for ppc64el, riscv64, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/1961319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960149] Re: Include ogre-next in Ubuntu Jammy
> Okay, the bad news is: it looks like the ogre-next source package FTBFS on ppc64el and s390x. Can you take a look at the build logs and see if this is something that can be fixed with a follow-up upload? Ouk, trivial to fix if I'm not wrong. > I'd recommend a separate bug for that then. Here we go https://bugs.launchpad.net/ubuntu/+source/ogre- next/+bug/1961319 Thanks again Łukasz. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960149 Title: Include ogre-next in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961319] [NEW] ogre-next SMID fix for ppc64el, riscv64, s390x
Public bug reported: Following up the last comment in https://bugs.launchpad.net/ubuntu/+bug/1960149: ogre-next is failing for ppc64el, riscv64, s390x with the following massage in the three of them: https://launchpad.net/ubuntu/+source/ogre-next/2.2.5+dfsg3-0ubuntu1 """ /<>/ogre-next-2.2.5+dfsg3/OgreMain/include/Math/Array/OgreArrayConfig.h:155:10: error: #error "Unknown platform or platform not supported for SIMD. Build Ogre without OGRE_USE_SIMD" 155 | #error "Unknown platform or platform not supported for SIMD. Build Ogre without OGRE_USE_SIMD" | ^ """ The reason is that the configuration leave enabled the OGRE_USE_SIMD for anything but arm*. The logic should be reverted and only enable it on x64. ** Affects: ogre-next (Ubuntu) Importance: Undecided Assignee: Jose Luis Rivero (j-rivero) Status: New ** Tags: jammy ** Changed in: ogre-next (Ubuntu) Assignee: (unassigned) => Jose Luis Rivero (j-rivero) ** Description changed: Following up the last comment in https://bugs.launchpad.net/ubuntu/+bug/1960149: ogre-next is failing for ppc64el, riscv64, s390x with the following massage in the three of them: + https://launchpad.net/ubuntu/+source/ogre-next/2.2.5+dfsg3-0ubuntu1 """ /<>/ogre-next-2.2.5+dfsg3/OgreMain/include/Math/Array/OgreArrayConfig.h:155:10: error: #error "Unknown platform or platform not supported for SIMD. Build Ogre without OGRE_USE_SIMD" - 155 | #error "Unknown platform or platform not supported for SIMD. Build Ogre without OGRE_USE_SIMD" - | ^ + 155 | #error "Unknown platform or platform not supported for SIMD. Build Ogre without OGRE_USE_SIMD" + | ^ """ The reason is that the configuration leave enabled the OGRE_USE_SIMD for anything but arm*. The logic should be reverted and only enable it on x64. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961319 Title: ogre-next SMID fix for ppc64el, riscv64, s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ogre-next/+bug/1961319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960149] Re: Include ogre-next in Ubuntu Jammy
Thanks for review Łukasz. Fixes and comments inline. With the requested change in the version number, I'm using a different PPA to upload the version since it is lower than the one in jammy-package PPA. New one is: https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-jammy > Remark re: the .orig tarball. Even though I think this is generally *fine* but when re-downloading (and auto-repacking) with uscan the current 2.2.5 tarball, there are a few additional files present in the tarball in comparison to the tarball used in the PPA upload (there's some .hgignore, .travis.yaml etc. files in it). I would normally expect to get the exact same tarball contents from running uscan. In this case I think it's fine, but this might mean that the debian/copyright exclude list needs to be modified or, otherwise, no hand modifications done to the source please. The explanation of the difference comes from the fact of having that configuration to exclude some files in my ~/.gbp.conf file. I added what I found to the d/copyright for completeness. > * I see that in Debian new a previous version of ogre-next is staged - ogre-next_2.2.5+dfsg3-1. From what I can tell that version has a different set of binary packages (libogre-next2.2 instead of the set of libogrenext*2.2.5 binaries). Would it be possible for you to submit -2 to Debian NEW? In case this gets accepted by Debian, it would be troublesome if a different set of binary packages was generated there. I requested to my usual sponsors in Debian to have the package re- uploaded. > * Regarding that point above ^ - the binary package name numbers feel a bit confusing, with their description and purpose not being quite clear. Are those the 'final' binary package names? If so, could we expand their individual long descriptions to be a bit more clear on what their purpose is? I've added the reason why we are using the whole version in the package names. In summary: upstream does not guarantee ABI compatibility even in patch version bumps. The whole information is available in the README.Debian. > * The version number needs fixing. 2.2.5+dfsg3-2ubuntu2 means that Debian has 2.2.5+dfsg3-2 and we introduce an ubuntu delta on top. Since this package is not accepted into Debian as of yet, the version number needs to be 2.2.5+dfsg3-0ubuntu2 (or, possibly, -0ubuntu1), with -0ubuntuX indicating 'Debian doesn't have this yet, but Ubuntu does'. This makes it easier for us to switch to Debian once the package is available there as well. Makes sense to me. Changed to -0ubuntu1. Thanks again, let me know if I need to fix anything more. ** Description changed: Please include the software ogre-next in Ubuntu Jammy. * Package name : ogre-next * Version : 2.2.5 * Upstream Author : https://github.com/OGRECave/ogre-next/blob/master/AUTHORS * URL : https://github.com/OGRECave/ogre-next * License : MIT * Programming Lang: C++ * Description : Ogre is a 3D graphics rendering engine (next generation) The Ogre project was divided into Ogre and Ogre-next, this last one hosts the old 2.x branches. Both are maintained and developed and incompatible with each other. For more details see: https://www.ogre3d.org/about/what-version-to-choose Packaging for Jammy is ready: * 2.2.5 in PPA https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages/+packages (amd64, arm64, armhf). * I've also updated to bzr https://code.launchpad.net/~j-rivero/+junk/ogre-next + * After review comments, follow in https://launchpad.net/~j-rivero/+archive/ubuntu/ogre-next-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960149 Title: Include ogre-next in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960940] [NEW] [needs sponsor] Include ignition-gazebo simulator in Ubuntu Jammy
Public bug reported: Please include the ignition-gazebo Simulator in Ubuntu Jammy. Ignition Gazebo is the successor of Gazebo and would be a very valuable addition for the Robotics community using Ubuntu Jammy LTS. This issue will require the ignition rendering packages to be in the repository before we can build it: https://bugs.launchpad.net/ubuntu/+bug/1960260 The ignition-gazebo simulator uses a small package called ignition- launch to be triggered. I've including it in this same issue. * Package name: ignition-gazebo Version : 6.4.0 Upstream Author : Open Robotics * URL : https://github.com/ignitionrobotics/ign-gazebo * License : Apache2 Programming Lang: C++ Description : Ignition Gazebo is an open source robotics simulator. Through Ignition Gazebo, users have access to high fidelity physics, rendering and sensor models. * Package name: ignition-launch Version : 5.0.0 Upstream Author : Open Robotics * URL : https://github.com/ignitionrobotics/ign-launch * License : Apache2 Programming Lang: C++, Description : Ignition Launch, a component of Ignition Robotics, provides a command line interface to run and manager application and plugins. I have done the packaging work for the three of them, they build fine in the PPA https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages for the arches available: amd64, arm64, armhf. The packages are also available via bzr: * https://code.launchpad.net/~j-rivero/+junk/ignition-gazebo * https://code.launchpad.net/~j-rivero/+junk/ignition-launch Should have no errors or warnings coming from Lintian as far as I can say but count me in for fixing anything needed. ** Affects: ubuntu Importance: Undecided Assignee: Jose Luis Rivero (j-rivero) Status: New ** Tags: jammy ** Description changed: Please include the ignition-gazebo Simulator in Ubuntu Jammy. Ignition Gazebo is the successor of Gazebo and would be a very valuable addition for the Robotics community using Ubuntu Jammy LTS. This issue will require the ignition rendering packages to be in the repository before we can build it: https://bugs.launchpad.net/ubuntu/+bug/1960260 The ignition-gazebo simulator uses a small package called ignition- launch to be triggered. I've including it in this same issue. - * Package name: ignition-gazebo - Version : 6.4.0 - Upstream Author : Open Robotics + Version : 6.4.0 + Upstream Author : Open Robotics * URL : https://github.com/ignitionrobotics/ign-gazebo * License : Apache2 - Programming Lang: C++ - Description : Ignition Gazebo is an open source robotics simulator. Through - Ignition Gazebo, users have access to high fidelity physics, rendering, - and sensor models. + Programming Lang: C++ + Description : Ignition Gazebo is an open source robotics simulator. + Through Ignition Gazebo, users have access to high + fidelity physics, rendering and sensor models. * Package name: ignition-launch - Version : 5.0.0 - Upstream Author : Open Robotics + Version : 5.0.0 + Upstream Author : Open Robotics * URL : https://github.com/ignitionrobotics/ign-launch * License : Apache2 - Programming Lang: C++, - Description : Ignition Launch, a component of Ignition Robotics, provides a - command line interface to run and manager application and plugins. + Programming Lang: C++, + Description : Ignition Launch, a component of Ignition Robotics, + provides a command line interface to run and manager + application and plugins. I have done the packaging work for the three of them, they build fine in the PPA https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages for the arches available: amd64, arm64, armhf. The packages are also available via bzr: - * https://code.launchpad.net/~j-rivero/+junk/ignition-gazebo - * https://code.launchpad.net/~j-rivero/+junk/ignition-launch + * https://code.launchpad.net/~j-rivero/+junk/ignition-gazebo + * https://code.launchpad.net/~j-rivero/+junk/ignition-launch Should have no errors or warnings coming from Lintian as far as I can say but count me in for fixing anything needed. ** Changed in: ubuntu Assignee: (unassigned) => Jose Luis Rivero (j-rivero) ** Summary changed: - Include ignition-gazebo simulator in Ubuntu Jammy + [needs sponsor] Include ignition-gazebo simulator in Ubuntu Jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960940 Title: [needs sponsor] Include ignition-gazebo simulator in Ubuntu Jammy To manage notifications about this bug
[Bug 1960260] Re: [needs sponsor] Include ignition rendering packages in Ubuntu Jammy
** Tags removed: needs-packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960260 Title: [needs sponsor] Include ignition rendering packages in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960260] Re: [needs-packaging] Include ignition rendering stack in Ubuntu Jammy
** Description changed: - Please include the software ignition-rendering in Ubuntu Jammy. It will - require ogre-next to work, in + Please include the ignition rendering stack, composed by three packages + ignition-rendering, ignition-gui and ignition-sensors. + + It will require ogre-next to work, in https://bugs.launchpad.net/ubuntu/+bug/1960149 + * Package name: ignition-rendering + Version : 6.1.0 + Upstream Author : Open Robotics + * URL : https://github.com/ignitionrobotics/ign-rendering/ + * License : Apache2 + Programming Lang: C++ + Description : Ignition Rendering is a C++ library designed to provide an abstraction for different rendering engines. + + * Package name: ignition-gui + Version : 6.3.0 + Upstream Author : Open Robotics + * URL : https://github.com/ignitionrobotics/ign-gui + * License : Apache2 + Programming Lang: C++, + Description : Ignition GUI ships with several widgets ready to use and offers a plugin interface which can be used to add custom widgets. + + + * Package name: ignition-sensors Version : 6.1.0 Upstream Author : Open Robotics - * URL : https://github.com/ignitionrobotics/ign-rendering/ + * URL : https://github.com/ignitionrobotics/ign-sensors/ * License : Apache2 Programming Lang: C++ - Description : Ignition Rendering is a C++ library designed to provide an abstraction for different rendering engines. + Description : Ignition Sensors, a component of Ignition Robotics, provides numerous sensor models designed to generate realistic data from simulation environments. - Ignition Rendering is a C++ library designed to provide an abstraction for - different rendering engines. It offers unified APIs for creating 3D graphics - applications. + I have done the packaging work for the three of them, they build fine in the PPA https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages + for the arches available: amd64, arm64, armhf. - Ignition Rendering is a component in the ignition framework, a set of libraries - designed to rapidly develop robot applications. + The packages are also available via bzr: + * https://code.launchpad.net/~j-rivero/+junk/ignition-rendering + * https://code.launchpad.net/~j-rivero/+junk/ignition-gui + * https://code.launchpad.net/~j-rivero/+junk/ignition-sensors + + Should have no errors or warnings coming from Lintian as far as I can + say but count me in for fixing anything needed. ** Summary changed: - [needs-packaging] Include ignition rendering stack in Ubuntu Jammy + Include ignition rendering packages in Ubuntu Jammy ** Summary changed: - Include ignition rendering packages in Ubuntu Jammy + [needs sponsor] Include ignition rendering packages in Ubuntu Jammy ** Description changed: Please include the ignition rendering stack, composed by three packages ignition-rendering, ignition-gui and ignition-sensors. It will require ogre-next to work, in https://bugs.launchpad.net/ubuntu/+bug/1960149 - * Package name: ignition-rendering Version : 6.1.0 Upstream Author : Open Robotics * URL : https://github.com/ignitionrobotics/ign-rendering/ * License : Apache2 Programming Lang: C++ - Description : Ignition Rendering is a C++ library designed to provide an abstraction for different rendering engines. + Description : Ignition Rendering is a C++ library designed to + provide an abstraction for different rendering + engines. * Package name: ignition-gui - Version : 6.3.0 - Upstream Author : Open Robotics + Version : 6.3.0 + Upstream Author : Open Robotics * URL : https://github.com/ignitionrobotics/ign-gui * License : Apache2 - Programming Lang: C++, - Description : Ignition GUI ships with several widgets ready to use and offers a plugin interface which can be used to add custom widgets. - + Programming Lang: C++, + Description : Ignition GUI ships with several widgets ready to use + and offers a plugin interface which can be used to + add custom widgets. * Package name: ignition-sensors - Version : 6.1.0 - Upstream Author : Open Robotics + Version : 6.1.0 + Upstream Author : Open Robotics * URL : https://github.com/ignitionrobotics/ign-sensors/ * License : Apache2 - Programming Lang: C++ - Description : Ignition Sensors, a component of Ignition Robotics, provides numerous sensor models designed to generate realistic data from simulation environments. + Programming Lang: C++ + Description : Ignition Sensors, a component of Ignition Robotics, + provides numerous sensor models designed to generate + realistic data from
[Bug 1960149] Re: Include ogre-next in Ubuntu Jammy
> I'll look into this in a moment, thank you for preparing the packages in the PPA. Thanks Łukasz. Let me know if I can help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960149 Title: Include ogre-next in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960260] Re: [needs-packaging] Include ignition rendering stack in Ubuntu Jammy
** Summary changed: - [needs-packaging] Include ignition-rendering in Ubuntu Jammy + [needs-packaging] Include ignition rendering stack in Ubuntu Jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960260 Title: [needs-packaging] Include ignition rendering stack in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960266] Re: [needs sponsor] Sync to Jammy Gazebo11 simulator + dependencies (DART, ignitions) from Debian Unstable
Thanks so much Sebastien! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960266 Title: [needs sponsor] Sync to Jammy Gazebo11 simulator + dependencies (DART, ignitions) from Debian Unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960266] Re: [needs sponsor] Sync to Jammy Gazebo11 simulator + dependencies (DART, ignitions) from Debian Unstable
Thanks Sebastien for the comment. I was checking my Debian QA page https://qa.debian.org/developer.php?login=jriv...@osrfoundation.org and did not check the -proposed pocket, I see now that the packages are there using rmadison (not sure if there is a better dashboard for the check). I'm available to help with the riscv64 failure in DART if finally there is a valid bug there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960266 Title: [needs sponsor] Sync to Jammy Gazebo11 simulator + dependencies (DART, ignitions) from Debian Unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889851] Re: Driver QMysql can't be loaded
I would like to report the same problem happening again with the latest version of libmysqlclient21. I am speaking about this bug: https://stackoverflow.com/questions/63307453/cannot-allocate-memory-in-static-tls-block-in-a-python-flask-application Which again was solved downgrading to the previous version: 8.0.28-0ubuntu0.20.04.3 Thanks :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889851 Title: Driver QMysql can't be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1889851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960149] Re: [needs-packaging] Include ogre-next in Ubuntu Jammy
I added packaging in: * 2.2.5 in PPA https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages/+packages (amd64, arm64, armhf). * I've also updated to bzr https://code.launchpad.net/~j-rivero/+junk/ogre-next ** Description changed: Please include the software ogre-next in Ubuntu Jammy. * Package name : ogre-next * Version : 2.2.5 * Upstream Author : https://github.com/OGRECave/ogre-next/blob/master/AUTHORS * URL : https://github.com/OGRECave/ogre-next * License : MIT * Programming Lang: C++ * Description : Ogre is a 3D graphics rendering engine (next generation) The Ogre project was divided into Ogre and Ogre-next, this last one hosts the old 2.x branches. Both are maintained and developed and incompatible with each other. For more details see: https://www.ogre3d.org/about/what-version-to-choose + + Packaging for Jammy is ready: + + * 2.2.5 in PPA https://launchpad.net/~j-rivero/+archive/ubuntu/jammy-packages/+packages (amd64, arm64, armhf). + * I've also updated to bzr https://code.launchpad.net/~j-rivero/+junk/ogre-next ** Summary changed: - [needs-packaging] Include ogre-next in Ubuntu Jammy + Include ogre-next in Ubuntu Jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960149 Title: Include ogre-next in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960266] [NEW] [needs sponsor] Sync to Jammy Gazebo11 simulator + dependencies (DART, ignitions) from Debian Unstable
Public bug reported: Hello: I'm the maintainer of Gazebo and all the related dependencies listed her in Debian. There were some transitions affecting Gazebo in the last months, one affecting DART library (a dependency of Gazebo) and another important transition to duplicate the ignition libraries that needs Gazebo to run (to unblock new ignition of those libraries which are incompatible with Gazebo). Checking Ubuntu auto migration excuses I found that, ignition-common seems to be blocked and msgs5 too: * https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ignition-common * https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ignition-msgs5 They had problems in Debian some weeks ago but are now fully clean (all them are also in testing except DART that has no blocker right now). List of source packages and versions to sync from Debian unstable # src:package | debian version | Ubuntu comment on Jammy versions - dart 6.12.1+dfsg4-10 (Jammy has 6.9.5-4u1) - gazebo 11.9.1+dfsg-8 (Jammy has 11.9.1+dfsg-2 needs 8 revision to use new dependencies) - ignition-common3 3.14.0+dfsg-5 (Jammy has no ignition-common3 but ignition-common) - ignition-common 4.4.0+ds-5 (Jammy has 3.14.0+dfsg-1) - ignition-fuel-tools4 4.4.0+ds-3 (Jammy has no ignition-fuel-tools4 but ignition-fuel-tools) - ignition-fuel-tools 7.0.0+ds-2 (Jammy has 4.1.0+dfsg-6) - ignition-msgs5 5.8.1+ds-2 (Jammy has no ignition-msgs5 but ignition-msgs) - ignition-msgs 8.2.0+ds-1 (Jammy 5.1.0+dfsg-7) - ignition-transport 11.0.0+ds-3 (Jammy has 8.0.0+dfsg-3) - ignition-transport8 8.2.1+ds-2 (Jammy has no ignition-transport8 but ignition-transport) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960266 Title: [needs sponsor] Sync to Jammy Gazebo11 simulator + dependencies (DART, ignitions) from Debian Unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960149] Re: [needs-packaging] Include ogre-next in Ubuntu Jammy
** Changed in: ubuntu Assignee: (unassigned) => Jose Luis Rivero (j-rivero) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960149 Title: [needs-packaging] Include ogre-next in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960260] [NEW] [needs-packaging] Include ignition-rendering in Ubuntu Jammy
Public bug reported: Please include the software ignition-rendering in Ubuntu Jammy. It will require ogre-next to work, in https://bugs.launchpad.net/ubuntu/+bug/1960149 * Package name: ignition-rendering Version : 6.1.0 Upstream Author : Open Robotics * URL : https://github.com/ignitionrobotics/ign-rendering/ * License : Apache2 Programming Lang: C++ Description : Ignition Rendering is a C++ library designed to provide an abstraction for different rendering engines. Ignition Rendering is a C++ library designed to provide an abstraction for different rendering engines. It offers unified APIs for creating 3D graphics applications. Ignition Rendering is a component in the ignition framework, a set of libraries designed to rapidly develop robot applications. ** Affects: ubuntu Importance: Undecided Assignee: Jose Luis Rivero (j-rivero) Status: New ** Tags: jammy needs-packaging ** Changed in: ubuntu Assignee: (unassigned) => Jose Luis Rivero (j-rivero) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960260 Title: [needs-packaging] Include ignition-rendering in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960149] [NEW] Include ogre-next in Ubuntu Jammy
Public bug reported: Please include the software ogre-next in Ubuntu Jammy. * Package name : ogre-next * Version : 2.2.5 * Upstream Author : https://github.com/OGRECave/ogre-next/blob/master/AUTHORS * URL : https://github.com/OGRECave/ogre-next * License : MIT * Programming Lang: C++ * Description : Ogre is a 3D graphics rendering engine (next generation) The Ogre project was divided into Ogre and Ogre-next, this last one hosts the old 2.x branches. Both are maintained and developed and incompatible with each other. For more details see: https://www.ogre3d.org/about/what-version-to-choose ** Affects: ubuntu Importance: Undecided Status: New ** Tags: jammy needs-packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960149 Title: Include ogre-next in Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959515] [NEW] While installing Ubuntu in the final state I got the message: " Unable to install GRUB in /dev/sda
Public bug reported: Unable to install GRUB in /dev/sda executing grub-install /dev/sda ·failed" This is a fatal error ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.10 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 30 17:03:57 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=es_ES.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.10.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959515 Title: While installing Ubuntu in the final state I got the message: " Unable to install GRUB in /dev/sda To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1959515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958435] Re: Icons on Dock get stuck in Dragging Mode
Though hardly an ideal solution, I can confirm that this bug is no longer present on 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1958435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958435] Re: Icons on Dock get stuck in Dragging Mode
Additional info: $ gsettings list-recursively org.gnome.shell org.gnome.shell enabled-extensions ['sound-output-device-choo...@kgshank.net'] org.gnome.shell command-history ['r'] org.gnome.shell remember-mount-password false org.gnome.shell always-show-log-out true org.gnome.shell had-bluetooth-devices-setup false org.gnome.shell looking-glass-history @as [] org.gnome.shell disable-user-extensions false org.gnome.shell app-picker-view uint32 0 org.gnome.shell disable-extension-version-validation true org.gnome.shell development-tools true org.gnome.shell enable-hot-corners false org.gnome.shell favorite-apps ['org.gnome.Terminal.desktop', 'firefox.desktop', 'discord.desktop', 'steam.desktop', 'spotify_spotify.desktop', 'org.remmina.Remmina.desktop', 'net.lutris.Lutris.desktop', 'gnome-control-center.desktop', 'org.gnome.Nautilus.desktop', 'signal-desktop.desktop', 'org.gnome.Screenshot.desktop'] org.gnome.shell.keyboard keyboard-type 'touch' org.gnome.shell.keybindings toggle-message-tray ['v', 'm'] org.gnome.shell.keybindings open-application-menu ['F10'] org.gnome.shell.keybindings pause-resume-tweens @as [] org.gnome.shell.keybindings toggle-application-view ['a'] org.gnome.shell.keybindings focus-active-notification ['n'] org.gnome.shell.keybindings toggle-overview ['s'] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1958435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958435] [NEW] Icons on Dock get stuck in Dragging Mode
Public bug reported: $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.3 Candidate: 0.9.1ubuntu18.04.3 Version table: *** 0.9.1ubuntu18.04.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages What I expect to happen: When I drag an icon on the Dock, I expect the dragging to finish once I release the mouse. What happened instead: The icon gets stuck in dragging mode. When my mouse clicks on the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. Related bug reports: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 12:38:15 2022 InstallationDate: Installed on 2019-10-04 (837 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 - $ apt-cache policy gnome-shell-extension-ubuntu-dock + $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: - Installed: 0.9.1ubuntu18.04.3 - Candidate: 0.9.1ubuntu18.04.3 - Version table: - *** 0.9.1ubuntu18.04.3 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages - 100 /var/lib/dpkg/status - 0.9.1 500 - 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages + Installed: 0.9.1ubuntu18.04.3 + Candidate: 0.9.1ubuntu18.04.3 + Version table: + *** 0.9.1ubuntu18.04.3 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages + 100 /var/lib/dpkg/status + 0.9.1 500 + 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages What I expect to happen: When I drag an icon on the Dock, I expect the dragging to finish once I release the mouse. What happened instead: - The icon gets stuck in dragging mode. When my mouse moves over the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. + The icon gets stuck in dragging mode. When my mouse clicks on the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. Related bug reports: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 12:38:15 2022 InstallationDate: Installed on 2019-10-04 (837 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode To manage notifications about this bug go to:
[Bug 1880764] Re: Dragging icons frozen in place without finishing
Hello, I am affected by the same bug. The output of your command is the following: gsettings list-recursively org.gnome.shell org.gnome.shell enabled-extensions ['sound-output-device-choo...@kgshank.net'] org.gnome.shell command-history ['r'] org.gnome.shell remember-mount-password false org.gnome.shell always-show-log-out true org.gnome.shell had-bluetooth-devices-setup false org.gnome.shell looking-glass-history @as [] org.gnome.shell disable-user-extensions false org.gnome.shell app-picker-view uint32 0 org.gnome.shell disable-extension-version-validation true org.gnome.shell development-tools true org.gnome.shell enable-hot-corners false org.gnome.shell favorite-apps ['org.gnome.Terminal.desktop', 'firefox.desktop', 'discord.desktop', 'steam.desktop', 'spotify_spotify.desktop', 'org.remmina.Remmina.desktop', 'net.lutris.Lutris.desktop', 'gnome-control-center.desktop', 'org.gnome.Nautilus.desktop', 'signal-desktop.desktop', 'org.gnome.Screenshot.desktop'] org.gnome.shell.keyboard keyboard-type 'touch' org.gnome.shell.keybindings toggle-message-tray ['v', 'm'] org.gnome.shell.keybindings open-application-menu ['F10'] org.gnome.shell.keybindings pause-resume-tweens @as [] org.gnome.shell.keybindings toggle-application-view ['a'] org.gnome.shell.keybindings focus-active-notification ['n'] org.gnome.shell.keybindings toggle-overview ['s'] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880764 Title: Dragging icons frozen in place without finishing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899294] Re: Não consigo atualizar
enho instalado o Ubuntu 20.04 LTS e recebi para atualizar o Ubuntu mas não consegui Ocorreu um problema sem solução, enquanto estava calculando uma atualização descrito pelo sistema dessa forma: Ocorreu um problema sem solução, enquanto estava calculando a atualização. Isto deve ter sido causado por: * Pacotes de software não oficiais nao disponibilizados por Ubuntu Por favor use a ferramenta 'ppa-purge' do pacote ppa-purge para remover software do Launchpad PPA e tente a atualização novamente. Se nada disto servir, então por favor comunique a falha usando o comando 'ubuntu-bug ubuntu-release-upgrader-core' no terminal. Se você quiser investigar isto por si os ficheiros de registro em '/var/log/dist- upgrade' contém detalhes sobre a atualização. Olhe especialmente para 'main.log' e 'apt.log'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899294 Title: Não consigo atualizar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1899294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952669] [NEW] package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade
Public bug reported: I was upgrading some packages with Synaptic and the aforementioned one failed claiming that it had some dependency issues. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-470 470.86-0ubuntu0.20.04.1 Uname: Linux 5.15.2-051502-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 29 17:43:14 2021 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-11-15 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952669 Title: package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952543] [NEW] sudo do-release-upgrade -d error
Public bug reported: I am new to linux and don't know what other details to include. My apologies. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Nov 27 20:23:33 2021 InstallationDate: Installed on 2021-11-15 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2021-11-28 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952543 Title: sudo do-release-upgrade -d error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1952543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948055] Re: Landscape Repository Profile Lost After Access Group Change
I reported this on the the wrong thread. I re-posted under the correct thread. https://bugs.launchpad.net/landscape/+bug/1948455 You can close this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948055 Title: Landscape Repository Profile Lost After Access Group Change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1948055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948055] [NEW] Landscape Repository Profile Lost After Access Group Change
Public bug reported: On standalone (on-prem) landscape web page, I created a new access group, and bulk assigned the new access group to several computers, landscape then generated a bulk activity to "apply repository profiles". The repository profile file for these computers in /etc/apt/sources.list.d/ was changed to .SAVENo new repository profile .LIST file was created. I had to manually move the .SAVE back to .LIST to restore the file. Seems like landscape wants to have a tight link between the repo profile and the access group, when it should not. My understanding is that the repo profile should be tightly linked to the Tag only. I assume if I remove any reference to the access group in the repo profile through landscape-api that this problem might go away. However, I don't think the Landscape software should care about that association. OS: Description:Ubuntu 18.04.5 LTS Release:18.04 Package details: Unsure of specific landscape package that executes the landscape Web Server activities described above, so just used this landscape package to provide you with a reference: $apt-cache policy landscape-common landscape-common: Installed: 18.03~1075~git.256ad02~ubuntu18.04.1 Candidate: 18.03~1075~git.256ad02~ubuntu18.04.1 Version table: *** 18.03~1075~git.256ad02~ubuntu18.04.1 500 500 https://archive.landscape.canonical.com bionic/main amd64 Packages 500 http://ppa.launchpad.net/landscape/19.10/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 18.01-0ubuntu3.5 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 18.01-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948055 Title: Landscape Repository Profile Lost After Access Group Change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1948055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943097] Re: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb
Thanks Juerg, Now it is booting... kernel 5.13. But now Desktop is frizzing with no return, no mouse movement and no keyboard response. Once during sudo apt update, other during sudo apt install vlc and other time during updating Region and Language... So I gave up... What do I do, Open another report??? Thanks again, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943097 Title: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942695] Re: DeskTop freezes for up to 5 seconds the first keystroke on Gnome terminal after boot.
Issue Update. Now desktop freeze is taking about 8:23 secs... After 14 days from first report and after a new install and updates... update... As you can see on image attached System Monitor from 38 sec to 45 sec one core remains 100%. And only Gnome Terminal an System Monitor are running on Desktop. Has anybody seen this issue on any platform? Thanks, ** Attachment added: "Desktop screen capture" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1942695/+attachment/5526299/+files/Terminal%20freeze1%202021-09-19%2014-18-21.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942695 Title: DeskTop freezes for up to 5 seconds the first keystroke on Gnome terminal after boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1942695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943097] Re: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb
Hi Juerg, The workaround is not working for me. I took a new .img from Daily Builds (kernel 5.13 already installed) and made a SDCard install. sudo apt update sudo apt install linux-modules-extra-5.13.0-1006-raspi rebooted. Working. Using another OS, in gparted copied SDCard to a SSD. This system does not boot, only a black screen. Hi Satmandu, You are right, theorically. Indeed the system does not boot. Thanks to all, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943097 Title: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943097] Re: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb
Hi Juerg, The workaround is not working for me. I took a new .img from Daily Builds (kernel 5.13 already installed) and made a SDCard install. sudo apt update sudo apt install linux-modules-extra-5.13.0-1006-raspi rebooted. Working. Using another OS, in gparted copied SDCard to a SSD. This system does not boot, only a black screen. Hi Satmandu, You are right, theorically. Indeed the system does not boot. Thanks to all, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943097 Title: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919083] Re: [FFe] KDE Frameworks 5.80.0 into Hirsute archive
** Changed in: plasma-framework (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919083 Title: [FFe] KDE Frameworks 5.80.0 into Hirsute archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-framework/+bug/1919083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
