Public bug reported:
I noticed from our automated certification tests on raspberry pi Noble
desktop images that the pd-mapper service was failing on boot. It looks
like this is a package only intended for qualcomm desktop system, and
not something that is needed by raspberry pi.
It looks like thi
*** This bug is a duplicate of bug 2062667 ***
https://bugs.launchpad.net/bugs/2062667
** This bug has been marked a duplicate of bug 2062667
Fails on (and should be removed from) raspi desktop
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
One of the tests we run for the network manager snap uncovered this
problem on uc18 with network-manager 1.10 snap, but I've also been able
to reproduce it in the previous snap version, as well as with core20 and
with focal.
On a laptop with intel wifi card, we installed a fr
>From a xenial system, I tried upgrading to bionic with do-release-
upgrade with -f DistUpgradeViewNonInteractive and *not* setting up the
force-confdef option, and it asks for input
Here's where it got stuck waiting for input:
Configuration file '/etc/ntp.conf'
==> Modified (by you or by a scri
Strange, that link seems to suggest it is in proposed already, but when I try
to run 'do-release-upgrade -p -f DistUpgradeViewNonInteractive', I don't seem
to get that. Do I need to do some other manual step to get it first, or do I
need it from xenial instead since that's where I'm coming from?
Ok, yeah I see it running:
/usr/bin/python3 /tmp/ubuntu-release-upgrader-n98wh3a9/bionic --mode=server
--frontend=DistUpgradeViewNonInteractive
and
$ sudo cat /tmp/ubuntu-release-upgrader-n98wh3a9/DistUpgradeVersion.py
VERSION = '18.04.33'
after letting it run a while, I did see it seemed to be
hah, ok that makes more sense then. Looks like this works, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1796193
Title:
DistUpgradeViewNonInteractive crashes / requir
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1796193
Title:
DistUpgradeViewNonInteractive
Public bug reported:
I'm trying to do some automated testing that involved upgrading a system
from xenial to bionic, so I need it to not ask for user input.
Before running do-release-upgrade, the system got a fresh dist-upgrade
and reboot.
To avoid interactive responses, I'm using:
$ sudo do-rel
I was able to test this on a m10 tablet. The fix seems to have gone
through to the cooler image I was trying to test - r13 in ubuntu-
touch/staging/bq-aquaris-pd.en, and now no longer hangs on install.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
For the xenial->bionic question, I had already implemented the
workaround mentioned here to use Dpkg::Options::="--force-confdef"
across all upgrade tests, which has been working fine. I can remove the
workaround and try it if you are specifically interested in finding out
whether it's necessary on
I also tried this on my pi400 and confirmed I can see and connect to
bluetooth devices after updating to bluez 5.55-0ubuntu1.1 from groovy-
proposed
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug
*** This bug is a duplicate of bug 1384450 ***
https://bugs.launchpad.net/bugs/1384450
The new phablet-tools from the bug that this is duped to does not help. I tried
reinstalling initramfs-tools after reinstalling my device with the new
phablet-tools and I still get this:
phablet@ubuntu-pha
Public bug reported:
Trying to do a dist-upgrade in utopicI'm getting:
Errors were encountered while processing:
dbus
E: Sub-process /usr/bin/dpkg returned an error code (1)
Details from term.log:
Setting up dbus (1.8.6-1ubuntu1) ...
insserv: warning: script 'S99autotest' missing LSB tags and ov
Public bug reported:
In some test runs, we see unlocking fail with:
I: Unlock failed, script output: 'Error:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
com.canonical.UnityGreeter was not provided by any .service files
It's not reliably reproducible, but probably happens at
Strange, I rebuilt the snap today, built a new amd64 snappy image, and
ran through all the tests in kvm twice with no crash. Did something go
in that could have fixed it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmo
I'll keep running to see if I can reproduce it again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on snap disconnect from within a snap
Stat
Unfortunately no, I mentioned earlier that I'm no longer able to
reproduce the problem but John said nothing went in that should have
fixed it. I'll leave it up to you guys if you'd like to invalidate it
or keep it open, but for me it is now unreproducible. :(
--
You received this bug notificati
** Attachment added: "/var/cache/apparmor"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+attachment/4657381/+files/var-cache-apparmor.tgz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubunt
** Attachment added: "/var/lib/snapd/apparmor/profiles"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+attachment/4657380/+files/profiles.tgz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ub
Tail end of syslog:
May 6 16:03:58 localhost kernel: [ 595.676922] audit: type=1400
audit(1462550638.144:10477): apparmor="ALLOWED" operation="recvmsg"
profile="snap.snappy-tests.snappy-tests//null-/usr/bin/sudo" pid=1908
comm="sudo" family="netlink" sock_type="raw" protocol=9
requested_mask=
Public bug reported:
First, a bit of background: I've built a go binary of the upstream
snappy integration tests, and built them into a snap so that we can
easily keep them up to date, and call them from other test suites.
I'm running through the tests in qemu on a current 16 image (built
yestera
Linux localhost.localdomain 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18
18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/157913
@Jamie: simply building that snap and installing it, and even
connecting/disconnecting the slots doesn't seem to reproduce the problem
easily. The easiest way I can come up with for reproducing it is to use the
snap that I'm using [attached]. To run into the problem I see, install this
snap, a
I saw what may be a variation of this on an update from 112 to 114 this
morning. When I unlocked after the update/reboot, I did not see the
"scopes" screen, but the home screen of unity8 instead - except there
were no icons. After about 1-2 minutes, it flickered slightly and went
dark, then went to
Any ideas on this? We're seeing it on some of the MP testing jobs too it
seems.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1370644
Title:
unity8-autopilot device unlock
As mentioned, it's not every job, but when it happens it brings things to a
halt pretty quickly. It can be pretty annoying for someone trying to land
something too I suspect if they need to retry, but spend time trying to
sort out if this is something they caused.
On Fri, Sep 26, 2014 at 7:23 AM,
Public bug reported:
We ran baselines of many processes on an idle nexus4 using health-check
for the last trusty image, and some of those have regressed since then.
These could be real regressions, or they could be something that's
expected due to changes that happened since that image. We need s
Public bug reported:
We ran baselines of many processes on an idle nexus4 using health-check
for the last trusty image, and some of those have regressed since then.
These could be real regressions, or they could be something that's
expected due to changes that happened since that image. We need s
Public bug reported:
We ran baselines of many processes on an idle nexus4 using health-check
for the last trusty image, and some of those have regressed since then.
These could be real regressions, or they could be something that's
expected due to changes that happened since that image. We need s
Public bug reported:
We ran baselines of many processes on an idle nexus4 using health-check
for the last trusty image, and some of those have regressed since then.
These could be real regressions, or they could be something that's
expected due to changes that happened since that image. We need s
Looking at syslog on my phone after a fresh install, I'm seeing this:
Jul 16 18:14:03 ubuntu-phablet whoopsie[2080]: whoopsie 0.2.34 starting up.
Jul 16 18:14:03 ubuntu-phablet whoopsie[2080]: Using lock path:
/var/lock/whoopsie/lock
Jul 16 18:14:28 ubuntu-phablet whoopsie[2154]: Could not connect
I think one thing going on here is that there's some too-aggressive
timeout that is causing whoopsie to think it's offline before the
network has a chance to fully come up. If I modify the upstart job to
make whoopsie start later, or even just restart whoopsie after boot, it
seems to continue work
Yeah, I seem to be getting stuck at
system_bus = g_bus_get_sync (G_BUS_TYPE_SYSTEM, NULL, &err);
if (err) {
log_msg ("Could not connect to the system bus: %s\n", err->message);
g_error_free (err);
return FALSE;
}
I was thinking about retrying it just that part,
Changing the upstart job to have it start/stop with dbus does not work for me.
It still thinks it's not online and I get messages like this in syslog:
Jul 22 16:18:06 ubuntu-phablet whoopsie[850]: Not online; processing later
(/var/crash/_usr_lib_arm-linux-gnueabihf_url-dispatcher_update-director
Also, if I start whoopsie with --assume-online, it seems to work more
reliably. I think Brian noted this before as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/13406
Public bug reported:
This is what we see sometimes in our CI runs:
I: Unlock failed, script output: 'The ubuntuuitoolkit.emulators module is
deprecated. Import the autopilot helpers from the top-level ubuntuuitoolkit
module.
INFO:unity8.process_helpers:b'unity8 stop/waiting\n'
INFO:unity8.proces
I'm running the new version locally right now, and it seems to be
working. I did have a .crash file that existed before I did the upgrade
that didn't get processed even after rebooting after the upgrade.
However, when I made something crash, both it and the new .crash file
were processed right away
38 matches
Mail list logo
