** Description changed:
For applications such as OBS 30.1.2 and Blender 4.1 to use CUDA and
NVENC, the Nvidia driver for servers must be installed first, followed
by the normal Nvidia driver, in that order. I believe this to be a bug
because the server driver is lighter than the normal
Hi Martin,
thank you very much for the bug report. I think this should be fixed
with frameworks 5.116, recently uploaded.
Let us know if there's still any issue.
** Changed in: extra-cmake-modules (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because
Public bug reported:
For applications such as OBS 30.1.2 and Blender 4.1 to use CUDA and
NVENC, the Nvidia driver for servers must be installed first, followed
by the normal Nvidia driver, in that order. I believe this to be a bug
because the server driver is lighter than the normal driver and
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
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
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
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:
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)
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
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:
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
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:
** 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
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
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:
** 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
** 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
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.
**
** 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:
> 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
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
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
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
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)
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]:
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
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
** 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
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
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
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:
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)
** 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
-
** 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
> 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
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)
+ -
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
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
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
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 =
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
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"
** 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.
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
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
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
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
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.launchpa
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
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:
> 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
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:
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!
--
** 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
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
** 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) =&
. 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
** 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.
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
> 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
> 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
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
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
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
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
** 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.
** 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.
** 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:
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
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
*
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:
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
> 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
D.
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-r
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
.
** 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
** 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
** 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
> 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
** 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.
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
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
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
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.
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
** 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 Ja
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
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++
*
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
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
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
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
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
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
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
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
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.
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
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
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
1 - 100 of 3582 matches
Mail list logo
