** Also affects: sosreport (Ubuntu Oracular)
Importance: High
Assignee: Arif Ali (arif-ali)
Status: Triaged
** Changed in: sosreport (Ubuntu Oracular)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: sosreport (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077428
Title:
[sync] sos upstream 4.8.0
To manage notifications about this bug g
Abandoning change, with consideration of syncing directly from Debian.
4.8.0-1 is currently being reviewed on mentors, and hope to have it in
unstable soon.
Will then request for sync to happen.
The plan is to have both Ubuntu and Debian package to be identical now,
and will create a new test fo
** Patch removed: "oracular-4_8_0.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2077428/+attachment/5808059/+files/oracular-4_8_0.debdiff
** Patch added: "oracular-4_8_0.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2077428/+attachment/5810402/+files
** Patch removed: "oracular-4_8_0.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2077428/+attachment/5807384/+files/oracular-4_8_0.debdiff
** Patch added: "oracular-4_8_0.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2077428/+attachment/5808059/+files
** 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/2077428
Title:
[sync] sos upstream 4.8.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s
** Patch added: "oracular-4_8_0.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2077428/+attachment/5807384/+files/oracular-4_8_0.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
n will now properly obfuscate ceilometer and
hooks.log.
* The networking plugin will now capture nmstatectl output.
* The maas plugin has been significantly refactored.
** Affects: sosreport (Ubuntu)
Importance: Medium
Assignee: Arif Ali (arif-ali)
Status: Triaged
** Affects:
: High
Status: Unknown
** Affects: sosreport (Ubuntu)
Importance: High
Assignee: Arif Ali (arif-ali)
Status: Triaged
** Bug watch added: Debian Bug tracker #1018639
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018639
** Also affects: sosreport via
https
sos collect testing below
focal: https://paste.ubuntu.com/p/XH4HRQy2Nm/
jammy: https://paste.ubuntu.com/p/XWcQF9BvNY/
noble: https://paste.ubuntu.com/p/MVpTcWgnh9/
sos basic testing across all distros
https://paste.ubuntu.com/p/fgnWm68Ctp/
--
You received this bug notification because you are
The patches for grafana appeared in 3.9 for sosreport, based on the PR
abve
Both xenial and bionic have them in -updates, so marking as fixed
released for both
xenial has 3.9.1 in -updates
bionic has 4.4 in -updates
** Changed in: sosreport (Ubuntu Xenial)
Status: New => Fix Released
**
boto3 is only main in noble and oracular and in universe for the others.
Hence we thought it didn't make sense to have it in f,j and m and to
depend or recommend from the universe pocket
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tested the package in the same as before, and compared to the PPA I
created as well
1. First test
normal do-release-upgrade with the -proposed pocket enabled, no issues
2. Second Test
* Add proposed
* Change all xenial to bionic in all apt sources
* Upgrade sosreport
Encountered no issues; thi
** Changed in: sosreport (Ubuntu Oracular)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054395
Title:
[sru] sos upstream 4.7.2
To manage notifications a
** Changed in: sosreport (Ubuntu Noble)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054395
Title:
[sru] sos upstream 4.7.2
To manage notifications about
** Patch added: "focal-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/sosreport/+bug/2054395/+attachment/5792167/+files/focal-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Patch added: "jammy-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/sosreport/+bug/2054395/+attachment/5792166/+files/jammy-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Patch added: "noble-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/sosreport/+bug/2054395/+attachment/5792164/+files/noble-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Patch added: "mantic-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/sosreport/+bug/2054395/+attachment/5792165/+files/mantic-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Bug watch added: github.com/sosreport/sos/issues #3683
https://github.com/sosreport/sos/issues/3683
** Also affects: sosreport via
https://github.com/sosreport/sos/issues/3683
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
We have discovered this is due to the fact the command being run is
writing to a file directly and strict confinement of snaps not able to
write the file is the problem. We were able to reproduce the problem
with the following python snippet
from subprocess import Popen, PIPE, STDOUT
command = ['t
** Patch added: "oracular-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/sosreport/+bug/2054395/+attachment/5791152/+files/oracular-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Description changed:
[ Impact ]
* A new sosreport version is available upstream, and following the
https://wiki.ubuntu.com/SosreportUpdates policy for stable release
- exception we will now SRU the sosreport 4.7.0 upstream release.
+ exception we will now SRU the sosreport 4.7.2 upstre
** Summary changed:
- [sru] sos upstream 4.7.0
+ [sru] sos upstream 4.7.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054395
Title:
[sru] sos upstream 4.7.2
To manage notifications about this b
From the latest/edge snap, and some initial debugging
Working with "sudo sos report -o sunbeam -a --batch --build"
ubuntu@sunbeam:~$ sudo ls -lh
/var/tmp/sosreport-sunbeam-2024-06-20-vvzypam/sos_commands/sunbeam
total 120K
-rw-r--r-- 1 root root 1.2K Jun 20 08:55
juju_controller-config_-c_sunbe
Public bug reported:
I am observing something strange, but maybe there is an explanation to
this?
```
self.add_cmd_output([
'snap info maas',
'maas status'
])
```
When I run sos report -o maas then sos_commands/maas/maas_status
contains expected data, however if I do sos report -o maas -
A quick update, the PR has now been merged, we're now awaiting SRU,
which is likely next version i.e. 4.7.2
If you would like to try it out, the latest snap in latest/edge channel
should have this new plugin and allow you to collect the data.
--
You received this bug notification because you are
Hi Mauricio,
I recreated the deb from the original control file as well as with the
new Version option. Both debs now produced have the
/usr/share/locale/*/LC_MESSAGES/sos.mo files. So I suspect this may be
something that ma have been introduced as part of a different package.
Here is a debdiff o
A new PR for this has been created and in progress
https://github.com/sosreport/sos/pull/3674
** Changed in: sosreport (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
> Why, when this is an upstream release for which Canonical is the
upstream, are there local Debian patches included here?
Good point, we started the SRU process after 4.7.0 was released, but the
time it took us to test the PPA and then the beginning of the patch
pilot the noble released a minor v
Hi Athos, sounds good to me; thanks for your detailed notes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054395
Title:
[sru] sos upstream 4.7.0
To manage notifications about this bug go to:
https
** Description changed:
+ [impact]
+
This is what I got when I tried do-release-upgrade from 16.04 to 18.04
Setting up sosreport (4.4-1ubuntu0.18.04.1) ...
File "/usr/lib/python3/dist-packages/sos/report/plugins/gcp.py", line 99
f"Failed to communicate with Metadata Server "
Thanks for your comments, and the amendments that you have asked for.
The relevant Origin + Bugs for DEP3 have all been updated on all the
debdiffs. I have also updated mantic changelog, and focal to be
consistent.
To answer your question on the `X-Python3-Version: >= 3.6`, this is
explicitly show
** Patch added: "focal-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5778350/+files/focal-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "jammy-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5778348/+files/jammy-sosreport.debdiff
** Patch removed: "focal-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776707/+fi
** Patch added: "mantic-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5778347/+files/mantic-sosreport.debdiff
** Patch removed: "jammy-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776706/+
** Patch removed: "noble-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776703/+files/noble-sosreport.debdiff
** Patch added: "noble-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5778346/+fi
** Patch removed: "oracular-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5777621/+files/oracular-sosreport.debdiff
** Patch added: "oracular-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/57
Updated debdiff as suggested
** Patch removed: "oracular-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776702/+files/oracular-sosreport.debdiff
** Patch added: "oracular-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosrepo
The new patch that was added at the end was about the msr module loading
and was also present in the CI testing we found upstream and hence added
it on.
In the original patch that is in noble it was == 24.04 and now it's
>=24.04 this will ensure it covers any series that is noble and above, I
hope
** Patch added: "focal-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776707/+files/focal-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "jammy-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776706/+files/jammy-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "mantic-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776704/+files/mantic-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054395
Title:
[sru] sos upstream 4.7.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/2054395/+subscriptions
** Patch added: "oracular-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776702/+files/oracular-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Patch added: "noble-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5776703/+files/noble-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch removed: "focal-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775312/+files/focal-sosreport.debdiff
** Patch removed: "jammy-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775311/+
y and August. We plan to
stick to that release process and potentially one intermediate. We have
an internal testing criteria that can take some time to get our releases
out, and hence the SRU was started a month after release, and you can
see the release numbers in my PPA https://launchpad.net/~arif
** Patch added: "jammy-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775311/+files/jammy-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "noble-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775309/+files/noble-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "focal-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775312/+files/focal-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "mantic-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5775310/+files/mantic-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Patch removed: "oracular-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5773527/+files/oracular-sosreport.debdiff
** Patch removed: "noble-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/577
Sounds good to me, I'll revert the copyright change and upload new
debdiffs for all. We can tackle the copyright file in a later SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054395
Title:
[sr
Hi Andreas,
This was discussed in the PR [1], let me see if I can answer your
questions
* All the files that need a copyright have the copyright at the top of the
files, and hence not therefore require here. If we started to add all the
copyright stuff, then this file would be considerably long
** Patch added: "oracular-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/oracular/+source/sosreport/+bug/2054395/+attachment/5773527/+files/oracular-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
new debdiff with new oracular being the version, and building on top of
the 2 versions that were not there previously
** Patch removed: "noble-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/oracular/+source/sosreport/+bug/2054395/+attachment/5772881/+files/noble-sosreport.debdiff
** Pat
** Also affects: sosreport (Ubuntu Oracular)
Importance: Medium
Assignee: Arif Ali (arif-ali)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054395
Title:
[sru
** Changed in: sosreport (Ubuntu Jammy)
Assignee: (unassigned) => Arif Ali (arif-ali)
** Changed in: sosreport (Ubuntu Mantic)
Assignee: (unassigned) => Arif Ali (arif-ali)
** Changed in: sosreport (Ubuntu Noble)
Assignee: Adam Bell (arbell) => Arif Ali (arif-ali)
** C
No merge from debian is required, as we are already using a newer
version in Ubuntu, and we are currently in the process of SRU to 4.7.0
in #2054395
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/206438
Updated noble debdiff with a couple of fixes for py3.12 and `msr` module
load on noble
** Patch removed: "noble-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/sosreport/+bug/2054395/+attachment/5757528/+files/noble-sosreport.debdiff
** Patch added: "noble-sosreport.debdiff
** Changed in: sosreport (Ubuntu Bionic)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038648
Title:
package sosreport 4.4-1ubuntu0.18.04.1 failed to instal
Undecided => Medium
** Changed in: sosreport (Ubuntu Focal)
Assignee: (unassigned) => Arif Ali (arif-ali)
** Changed in: sosreport (Ubuntu Jammy)
Assignee: (unassigned) => Arif Ali (arif-ali)
** Changed in: sosreport (Ubuntu Mantic)
Assignee: (unassigned) => Arif Ali (ari
@Lucas, it is ready.
We were planning to resolve that bug as part of the whole SRU of 4.7.0.
When n/m/j/f are done, we'll get the bionic one done too, and that will
be 4.7.0 as well, I hope that makes sense.
Or, would you prefer us to fix the current version there first, and then
do the SRU for
We have a planned SRU of sosreport 4.7.0 which would have this fix
already which we're still waiting for the sponsors to pick in
LP:2054395, that would resolve this bug as well as updating sosreport to
the new version.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: sosreport (Ubuntu)
Status: New => Confirmed
** Changed in: sosreport (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059386
Title:
c
Hi Mauricio,
The version that sosreport currently supports is 3.6 and there are plans to
potentially move on from 3.6 for the next major release of sosreport. My current
idea and plan was, when upstream make that change we would then update the
X-Python3-Version based on the upstream python compat
> One of the requirements is the newer releases (supported & devel) are fixed.
> Can you please provide the debdiffs for them, for us to proceed?
>
> $ for release in noble mantic jammy focal bionic; do git show
> pkg/ubuntu/${release}-devel:debian/control | grep 'X-Python-Version:'; done
> $
T
** Changed in: ubuntu-pro
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2028327
Title:
[sru] sos upstream 4.5.6
To manage notifications about this bug go to:
bionic was never released, so marking it invalid as we had 4.4
** Changed in: sosreport (Ubuntu Bionic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941745
Tit
So, did the tests again to get more data
Below is the diff between the 2 apt-term.log, which shows the ordering
of installation of the packages. The main differences are dates, the
version of sosreport being installed and loads of data around "Reading
database"
https://paste.ubuntu.com/p/8wZ5bsXc
The above debdiffs have been added, and ready for verification
We are waiting for the 4.4 main patch for bionic in #2038648 to be
uploaded before we crack on with the Pro update for bionic for 4.7.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Patch added: "focal-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757531/+files/focal-sosreport.debdiff
** Tags added: sts-sru-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Patch added: "noble-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757528/+files/noble-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "jammy-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757530/+files/jammy-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Patch added: "mantic-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2054395/+attachment/5757529/+files/mantic-sosreport.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
The 4.4 minimal change debdiff attached. tested this in lab, and works
as expected
** Patch added: "bionic-4_4-sosreport.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5757522/+files/bionic-4_4-sosreport.debdiff
** Tags added: sts-sru-needed
--
You rec
** Attachment added: "apt-term.log"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756026/+files/apt-term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038648
T
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756025/+files/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/2038648
Title:
pa
Excerpts from the logs with the upgrade using the PPA
apt.log
100 MarkInstall python3 [ amd64 ] < 3.5.1-3 -> 3.6.7-1~18.04 > ( python ) FU=0
101 Installing python3.6 as Depends of python3
102 MarkInstall python3.6 [ amd64 ] < none -> 3.6.9-1~18.04ubuntu1.12 > (
python ) FU=0
103 Insta
** Attachment added: "main.log"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756028/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038648
Title:
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/2038648/+attachment/5756027/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038648
Tit
rt,4.7.0-0ubuntu1~18.04.7
+ii,sosreport,4.4-1ubuntu0.18.04.1
ii,squashfs-tools,1:4.3-6ubuntu0.18.04.4
ii,ssh-import-id,5.7-0ubuntu1.1
ii,strace,4.21-1ubuntu1
I hope that this helps and avoids any concerns on the extra package
dependancies.
[1] https://launchpad.net/~arif-ali/+archive/ubuntu/sosre
ned) => Arif Ali (arif-ali)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038648
Title:
package sosreport 4.4-1ubuntu0.18.04.1 failed to install/upgrade:
installed sosreport package post-instal
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947351
Title:
chown not in rootwrap when only installing cinder-backup
To manage notifications about this bug go to:
https://bugs.l
Public bug reported:
series: bionic
openstack: queens
We have an issue with a user, where the cinder-backup and services are
installed, and separated from cinder-volume nodes.
As part of the cinder-backup, it is required to grab iscsi devices, and
hence the likes of /dev/sd* would be there to be
[VERIFICATION HIRSUTE]
I ran the following command:
# sos report -o ubuntu --upload # The important bit here is the --upload
option, the rest is just to generate the sos archive.
The above command line output:
"
Attempting upload to Canonical Support File Server
Uploaded archive successful
Tested on bionic, focal, groovy and hirsute, specifically the --clean
and --mask options
Ran these commands, and all came out
sos report --mask --all-logs -a --batch
sos report --clean --all-logs -a --batch
sosreport --mask --all-logs -a --batch
sosreport --mask --all-logs -a --batch
sos report
So based on that debian bug, that was resolved, so I would think that we
should be able to move forward, as that comment on the publishing
history was dated "2019-11-05 00:10:09 GMT" for version 2018.3.
There's no explanation why it was blocked later with version 3000
--
You received this bug no
Public bug reported:
noticed that focal did not ship salt in focal, based on the rmadison
output below
$ rmadison salt-minion
salt-minion | 0.17.5+ds-1 | trusty/universe | all
salt-minion | 2015.8.8+ds-1 | xenial/universe | all
salt-minion
Initial Test
* sos report
Ran through the simple.sh as per the document. Had to change all the
/var/tmp to /tmp, and then all went through without a problem
sos report passed, and didn't have any problems
same test using sosreport instead, as that is what customers would be
used to
Ran all my
A suggestion on bringing sos 4.0 to bionic
Leave the original sosreport as it is, so that it doesn't break anything
for any users
Introduce a new package called sosreport4 which packages sos 4.0. This
would will then give the opportunity to use the new version of sos so
that newer data can be col
Verified the netinstall images i.e. initrd.gz and vmlinuz from
https://people.canonical.com/~mruffell/sf289200/ work for me, and I am
now able to deploy instance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
1) Is there anything i can help you folks with?
2) Let me know the exact use case/workflow and I will test it out and give your
details.
As i understand issue is only in suspend and resume, it wont cause troble
for me as i wont use these features,
if there is an issue. As long as shu
Hi There,
I am getting Dell-Precision-T1650.
I want to know if I can go for Xubuntu 12.04 or 13.10.
Would I face similar issue.
-Arif
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/114
Public bug reported:
Please find the screenshot, its happening even after reboot.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xfce4-panel 4.10.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture:
ubiquity folder doesn;t exists in my /var/log
let me know hwo else i can help you ?
another note. i left my cpmuter as it is after waitinf for 4 hours ( 4 hours
in "restoring previously installed packages" )
and slept next day morning i saw it was done.
most people on IRC said that it was bec
Now after 20-30 minutes.
software cetner - > VM 1860 MB , RSS : 650 MB , CPU usage 5-40 % (mostly 5%)
, still unresponsive
system -> Total RAm 1GB, 85% RAM used, total swap space 2 GB, 58% swap space is
used.
so clearly RAM is bottleneck. I had similar issue while upgrading from xubuntu
12.1
hi some more infomation
I have 1 GB RAM , Pentium 4 processor with Hyper threading, INtel 915
motherboard.
memoty usage of software c enter are as follow
VM : 1523 MB , RSS : 680 MB
I also see that 80% of computer's entire memory is under use and 35% of swap
area is also under use.
so that cle
** Attachment added: "screenshot of software center when unresponsive"
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1175072/+attachment/3661195/+files/so9ftware%20center.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1 - 100 of 111 matches
Mail list logo
