Attached examples with changes to address this bug:
https://git.launchpad.net/~ondrak/ubuntu/+source/opensc/commit/?h=ubuntu/focal=5866e8c8397b896f002e784ecc3d03005943e00a
https://git.launchpad.net/~ondrak/ubuntu/+source/libp11/commit/?h=ubuntu/focal=6df6a659416fcc1c3ffc46346e7edb38eb10b3d4
--
** Also affects: libp11 (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/1968175
Title:
Allow runtime configuration of pkcs11 modules through
Public bug reported:
To be able to switch modules at runtime via configuration file change the
default module from opensc-pkcs11 to p11-proxy module, which by default loads
opensc-pkcs11 module unless configured by administrator to use something else.
This also allows configuration where
OK this would mean that kernel modules in the linux-modules-extra packages are
not signed.
kernel enforces kernel module signature check if SB is enabled.
But our modules should be signed.
@Renat, can you confirm exact versions of all the stage packages?
As those need to be aligned for signing
** Summary changed:
- snapdragon: wcn36xx connection error
+ snapdragon: LEDs on dragonboard 410c does not work correctly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776725
Title:
snapdragon:
** Summary changed:
- raspi2: snapcraft scriptlet syntax outdated
+ raspi2: Pi3B plus is not supported
** Summary changed:
- raspi2: Pi3B plus is not supported
+ raspi2: Pi3 B plus is not supported
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- snapdragon: wcn36xx connection error
+ snapdragon: cross snap build broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776723
Title:
snapdragon: cross snap build broken
Public bug reported:
SRU Justification
Impact:
LEDs on dragonboard401c are not fully supported. Particularly WiFi and BT
activity LEDs, heartbeat user LEDs
Step to reproduce:
- Boot DragonBoard 410c and observer BT, WiFI LEDs and User LEDs
Expected result:
LEDs are switched ON correctly
Public bug reported:
SRU Justification
Impact:
snap cross building is broken and snap package can only build natively
additionally snapcraft.yaml is using deprecated scriptlet syntax for
install overrides
this syntax has been deprecated by snapcraft and should be replaced with
new
Public bug reported:
SRU Justification
Impact:
WiFi connection is unstable for connections over 2 hours
Step to reproduce:
- Config device to connect to wifi AP
- ssh into device and ping the 8.8.8.8
expected result: Wifi connection can continue ping to target ip over 2 hours
actual
Public bug reported:
SRU Justification
Impact:
Newly released hardware Raspberry Pi3 B plus is not currently supported. Pi3
B+ is very similar to existing Pi3B+ and requires only new dtb file describing
differences from Pi3B
TEST CASE:
Pi3B+ hw should be fully booting and all peripherals
Public bug reported:
SRU Justification
Impact:
current snapcraft.yaml is using deprecated scriptlet syntax. To make snap
builds more future proof, snapcraft.yaml should migrate to new snapcraft syntax
TEST CASE:
kernel snap should build without snapcraft complaining about deprecated
Public bug reported:
Start building ubuntu core images for Compute Module 3
Signed model assertion can be found attached to this ticket:
https://portal.admin.canonical.com/103446#
I have already requested store to upload the assertion to the store, so
eventually it should be available under:
Public bug reported:
when configure hook is invoked, there are several reasons leading to it, just
to mention:
- user calling snap set =
- installing snap first time
- updating snap
- rollback
Each of this situation requires potentially different way to be be handled. At
the moment it's
Public bug reported:
preconditions:
$ snap install
$ snap set KEY1="VALUE"
$ snap set KEY2="VALUE"
$ snap remove
$ snap install
$ snap set KEY1="VALUE"
expected result:
when calling last $ snap set, configure hook associated to this "snap set" I'd
expect snapctl only to return value for
Public bug reported:
precondition:
calling $ snap remove
expected result:
all snap data are removed, this included all the user snap data for snap
registered user, root, any other local user, and snap service data under
/var/snap/
actual result:
some snap data are left behind, /root// is
Public bug reported:
when calling snap refresh on raspberry pi3 from stable to edge device broke.
I refreshed core, gadget and kernel snap at the same time, in this order:
core->gadget->kernel
closer investigation showed that dtb files from new kernel snap were not
copied over to boot/uboot
Public bug reported:
running snap refresh from stable to edge for core, gadget, kernel snap seem to
brake netplan configuration
this happened on raspberry pi3
core changes from 933->939
gadget from 5 -> 6
kernel from 21 -> 22
** Affects: snapd (Ubuntu)
Importance: Undecided
Public bug reported:
channel: rc-proposed/meizu.en/turbo v 70
url: http://www.crossrail.co.uk/route/improved-journeys
In "JOURNEY TIME CALCULATOR" Departure and arrival station selectors
fault to show list of stations to select from
** Affects: webbrowser-app (Ubuntu)
Importance: Undecided
so I did use new script for LXC
Now I can see that Android init process is started but it fails quite soon,
with not much logs indicating actual issue.
This is just speculation, but probably still issue how /proc and /dev are
mounted to container?
Here are all the logs I get from Android init:
Finally some time to check more.
Using new /etc/init/lxc-android-config.conf from Stephane
http://paste.ubuntu.com/15264484/
When running manually $ lxc-start -n android -F -- /init
I can see init process be created, but then it exits. Also there are no logs in
syslog or /proc/kmesg
So looks
Finally some time to check more.
Using new /etc/init/lxc-android-config.conf from Stephane
http://paste.ubuntu.com/15264484/
When running manually $ lxc-start -n android -F -- /init
I can see init process be created, but then it exits. Also there are no logs in
syslog or /proc/kmesg
So looks
missing android signal was caused by double mounting of cgroup cpu,
which was already mounted. Fixing that did take boot further, now
lightdm becomes alive, still boot fails, and kills adb in the process...
--
You received this bug notification because you are a member of Ubuntu
Server Team,
missing android signal was caused by double mounting of cgroup cpu,
which was already mounted. Fixing that did take boot further, now
lightdm becomes alive, still boot fails, and kills adb in the process...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
more debugging and android signal is still not emitted, though android init
process is running
Will keep debugging to get closer to the issue
we are progressing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
more debugging and android signal is still not emitted, though android init
process is running
Will keep debugging to get closer to the issue
we are progressing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
lxc-container is now running, system still does not boot, but container is no
more issue
needed changes:
install
https://launchpad.net/ubuntu/+source/cgroup-lite/1.10/+build/6001591/+files/cgroup-lite_1.10_all.deb
and modify /etc/init/lxc-android-config.conf to this:
lxc-container is now running, system still does not boot, but container is no
more issue
needed changes:
install
https://launchpad.net/ubuntu/+source/cgroup-lite/1.10/+build/6001591/+files/cgroup-lite_1.10_all.deb
and modify /etc/init/lxc-android-config.conf to this:
update from running system:
$ cat /proc/cgroups
#subsys_namehierarchy num_cgroups enabled
debug 3 1 1
cpu 1 1 1
cpuacct 2 1 1
freezer 4 1 1
$ cat /proc/self/cgroup
5:name=systemd:/
4:freezer:/
3:debug:/
2:cpuacct:/
1:cpu:/
--
update from running system:
$ cat /proc/cgroups
#subsys_namehierarchy num_cgroups enabled
debug 3 1 1
cpu 1 1 1
cpuacct 2 1 1
freezer 4 1 1
$ cat /proc/self/cgroup
5:name=systemd:/
4:freezer:/
3:debug:/
2:cpuacct:/
1:cpu:/
--
Public bug reported:
Cleverly constructed key signature tarball can bypass signature check.
If tarball contains symbolic link to the directory outside of the working
folder followed then by file based on this symbolic link , tar will follow the
link and creates new file outside of the working
Not sure if that is best way to tackle this problem.
Using inspiration from another OS, I think best strategy is to use
indicator which makes distinction between different modes location service
is running in.
like this user can easily see when phone actually uses accurate location,
and then check
Having exactly same issue on MX4, there was lot's of app for update before
release 4, now after updating to release 4, there are 5 apps which refuse to
update. Reboot, attempt to manually update them on by one, all fails.
Device: MX4
Release: 4
--
You received this bug notification because you
So issue is caused by Ubuntu one account being invalid though still listed in
online accounts.
Workaround is to remove Ubuntu one account and then add it again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Option for only wifi + cellular is not really needed for user to chose from.
It is still used by the device, when application does not require precise
location, in order to preserve battery, but this is not to be controlled by
user. In my option no need to have any option like this here.
Still
I disagree with statement that GPS (less accurate)
this is simply not true.
It gives impression that GPS is less accurate, and when selecting second
option (with wifi) user will get better accuracy. But this is not true.
From all location providers available, GPS is most accurate one,
So is this it? Are we sticking to the version that Wifi based location is more
accurate than GPS.
I strongly disagree to mark this as invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421623
Public bug reported:
When in recovery installing OTA updates, screen only shows infinite
progress and animation.
There should be also warning to user, not to disturb update in any way, such as
trying to power phone off, removing battery.
Preferably progress or more verbose could be added.
Interesting question is if text in English is enough.
Because in recovery we don't have language variants, also in case of factory
reset operations, we won't even have any settings to determine language.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That makes sense and I have no preference where it should be implemented.
If there is better home for this bug, we should move it there.
I assigned this bug to Settings app since there it's visible, so it was
good starting point :)
If we create new bug please add it here, so we can track it for
Just to confirm. I just received another device exhibiting boot loop issue and
after quick investigation it was same problem, race of chid process continuing
logging after parent died but before writable disk signal.
Once I used patched upstart binary, device booted normally, so all good.
--
I'm not expert in click manifest, but that surely cannot have something as
dynamic as size of application data which do change as user uses application.
I can imagine manifest having actual path to where application data should be
stored, but it still should be calculated as we enter
I'm not sure what is best component to file this bug against. If there
is better home for this bug, please advice :)
I'm not sure how much logic click should have, but surely uninstaller
daemon should not rely on information in click package, it should clean
application data even if it has broken
I think I have nailed it down now, here is brief description what is happening
(if I read code right)
There seems to be race, when we get new log data for one of the jobs after job
has been terminated, and while processing it we call log_io_reader and
eventually log_file_write which will try to
Sorry for spamming, but I guess that log_io_reader is called by nih_io_watcher
which has been initialised by nih_io_reopen
which I suppose is called when job starts?
So that would go back to my original finding, job dies and is restarted before
we get signal about disk being writable, but at
So when job gets terminated we don't succeed to write to to the disk and it is
added to the unflushed list.
Problem is another call to write function later on, but before we get writable
disk signal:
[7.460627]init: log_handle_unflushed:778:len=32673,
So one thing which I still cannot track down is how is that unidentified
log_io_reader called. Or who is calling it.
I have put traces to log_read_watch under condition if (io-recv_buf-len) {
where we call log_io_reader but call is not coming from there.
So what are other options for
Public bug reported:
When app is uninstalled it's data under ~/.local is preserved.
This makes it impossible to track where all the free space went, since app is
not even installed to be shown in storage view in the Settings app, and yet it
can happily leave behind hundreds of MB of obsolete
** Description changed:
When going to Settings-About phone - Storage
Storage used per app count does not include space used by app in
~/.local/app/
- This makes is hard to determine which app is actually eating all the storage.
+ This makes is hard to determine which app is actually eating
Public bug reported:
When going to Settings-About phone - Storage
Storage used per app count does not include space used by app in ~/.local/app/
This makes is hard to determine which app is actually eating all the storage.
It also makes whole list kinda pointless, since we can have easily app
I can confirm fix: http://paste.ubuntu.com/11095313/ does the job.
It will safely ignore entries of log_unflushed_files list which have
log-unflushed-len set to zero. Since we know how this state is reached it
seems like previous nih_assert (log-unflushed-len); was too aggressive.
--
You
Sorry in previous comment, replace all flash with flush
Actually one more issue I can see there is this:
Job dies - it's added to log_unflushed_files when it has unflushed data
but if job is restarted before we get disk writable signal, it will mess up the
things, job will still remain in
Agreed, either we open new bug to track this, or we don't mark this as
fixed. This is the time one could use state workaround
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
Title:
segfault
hi James
So one way is to disable upstart logging all together with --no-log kern
command option. We are going with this option for next OTA, till we can crack
actual root cause of this issue.
As for restore, best bet is with MTK flash_tool
--
You received this bug notification because you are
Yep, we don't support dualboot on Nexus 7 anymore, it has too small partition
for recovery where Ubuntu boot.img does not fit anymore.
So when you try to reboot to Ubuntu it will fail. Only way out would be some
sort of repacking of Ubuntu boot image on the device and slimming it down to
fit in
Ups sorry wrong bug. Ignore my comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435784
Title:
SMS and calls working, but no mobile internet
To manage notifications about this bug go to:
GPS is most accurate positioning system we have on the phone. However it
comes with price, here are some of the bad features of GPS: drains
battery, does not work indoors, takes long to get initial location when
used first time (or long after last use)
Therefore number of supporting used to
there seems to be two issues:
One is focus-mode getting stacked in auto mode and not returning back to
continuous-picture mode.
This could be reproduced by letting camera settle in continuous-picture mode,
then tasking camera away and back, camera is restarted in auto mode. Not sure
what is
To observe focus_mode do following:
$ adb shell
$ sudo /system/bin/logcat | grep focus-mode
Tapping on the screen switched focus-mode to auto focus to defined coordinates
When moving phone around, phone should default to
focus-mode=continuous-picture
This is not always done when resuming camera
Public bug reported:
First boot welcome wizard in location sections claims GPS is less accurate than
network based location service from HERE.
While this can be theoretically true in some insane corner case, in normal life
GPS is far more accurate.
To help form correct text here are main
Public bug reported:
Formatting user data from settings app or from recovery does not actually
format userdata partition.
This is not what user expects from function description.
- One would expect to be able to use this functionality as recovery from
corrupted fs
- if filesystem is corrupted
Conf file without double assignment.
** Attachment added: custom-apparmor-cache.override
https://bugs.launchpad.net/apparmor/+bug/1385382/+attachment/4261047/+files/custom-apparmor-cache.override
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm all up to move it to more appropriate config, even to separate config,
rather than override, this was just place where I was testing it, to make
sure time is adjusted before we start validating custom apparmor caches.
I did not managed to get working TIME_ROOTFS formula in one go, that's the
Some breakthrough:
Problem is caused by corrupted nvram data, when gps stack fails to identify
underlying hw and therefore does not know how to function.
Underlying hw info is stored in /userdata/android-data/misc/GPS_CHIP.cfg, which
is empty on broken phones, it should have text with chipset
0x6582%s from /userdata/android-data/misc/GPS_CHIP.cfg is correct value.
6582 represents mtk platform m6582.
When nvram gets corrupted GPS_CHIP.cfg is empty, as gps stack was not able to
determine underlying platform.
So this seems to be different issue what you are seeing Rick.
--
You received
Corrupted nvram file issue is now tracked by new bug in specific to
krillin: Bug #1389865
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387708
Title:
[TOPBLOCKER] Location services not getting
I have investigated similar issue on krillin.
In case of krillin hw clock is set at the factory to 1st of January 2014,
0:00am.
This causes first boot (out of the box experience) to last 2mins 40 seconds
before welcome wizard appears, with over 2minutes of it being white screen with
bootloader
Related bug: https://bugs.launchpad.net/bugs/1385382
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353591
Title:
Ubuntu Touch devices sometimes come up with hwclock set to 1970
To manage
Jonas: HW we are using is capable of switching active technology used on
each SIM slot. There is hw limitation that only one SIM slot can have 3G
technology enabled at the time, since phone has only one rf module.
Radio Interface Daemon can alter technologies used on each SIM slot,
this operation
About prettiness: for example Orientation lock and Flight mode could
be easily put on same row, making space for other icons.
About need to rotate itself. Here I'd answer with question, why don't we rotate
indicator bar then? Because you can argue that indicator bar is probably first
place
Idea for this bug was to provide task to implement support in ofono to switch
SIM slot technologies.
It is not intention of this bug to tackle whole user experience, and under
which condition technology in SIM slots should be altered.
This is only to provide foundation in case UX requires to do
Tony are you sure it's as simple as writing 'TechnologyPreference' for each
slot?
How does it handle fact that there are hw limitations to and only one slot at
the time can have 3G enabled.
Also when I tried this on Android, it seems like this actually reboots modem.
While I believe you can
*** This bug is a duplicate of bug 1321627 ***
https://bugs.launchpad.net/bugs/1321627
Tony I have observer same issue on Krillin. It was up to date on rtm channel.
Same symptoms, phone was not detecting any SIM card, ofonod crashing. And only
way out was to wipe the phone and start from the
Oli where do we delete /data/system-data with ubuntu-device-flash?
Are we actually calling adb shell rm -rf /data/system-data from
ubuntu-device-flash?
I just checked latest bootable/recovery/system-image-upgrader and we do not
delete system-data unless you format /data partition. And in that
Upgraded from 12.04 where I was using sipe pluging, my account kept working
after upgrade, though I could not actually see it in my online accounts.
I had to change sipe account's password, so now I'm buggered, since there is no
way I can update my account settings.
It's definitely bug. My
Not exactly this bug, but potentially related.
Since mouse battery is shown as default, it raised interesting question, what
is active power mode On Battery Power or When Plugged in?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
76 matches
Mail list logo
