** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-messages in
Ubuntu.
https://bugs.launchpad.net/bugs/1365875
Title:
mail notification displayed even when
Public bug reported:
When I re-connect to a known network, I am prompted for the WPA2
password. However, clicking cancel then successfully connects to this
network!
This is only happening for one of my networks. Not currently sure why
since the other main network I use is also WPA2 protected and
Public bug reported:
Clicking a pdf link still claims there is no PDF handler to view the
file.
However,
1) I have PdfjsViewer installed.
2) I should be able to download the file to the disk and open it later.
** Affects: webbrowser-app (Ubuntu)
Importance: Undecided
Status: New
Public bug reported:
1) Touch a contact so that the grey bust icon appears to the right of it.
2) Long-press the same contact by touching the name to go into edit mode - a
green tick will appear next to the contact.
3) Press the bust icon to switch to the full details view.
4) Press back.
5)
Public bug reported:
Long contact name handling seems to behave somewhat erratically but
normally ends in The expectation is that turning the screen
sideways would allow the full contact name to be shown but the app
doesn't seem to support this yet.
** Affects: address-book-app (Ubuntu)
Public bug reported:
subject says it all really :)
** Affects: address-book-app (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
Public bug reported:
The entry remains in the list but is no longer selectable and has a very
slightly darker grey background to the remaining list entries.
** Affects: address-book-app (Ubuntu)
Importance: Undecided
Status: New
** Tags: avengers
--
You received this bug
Public bug reported:
Searching for a term that is _not_ in the contact names makes the search
dialog spin forever until I touch the cross to cancel it.
Expected behaviour: present a message saying not found.
Ideal behaviour: search all contact fields, not only the contact names.
** Affects:
Public bug reported:
1) swipe up to open Manage Dash.
2) open a scope.
3) swipe left.
4) touch orange ubuntu logo.
Expected outcome: main home screen displayed (phone, messaging, contacts, etc).
Actual outcome: the scope you opened in (1) is displayed.
Steps to get from the scope back to the
Public bug reported:
Both iOS and Android cameras have an option to overlay 2 evenly-spaced
vertical and 2 evenly-spaced horizonal white guide lines.
These are a very useful alignment aid when composing a shot.
For details: http://en.wikipedia.org/wiki/Rule_of_thirds
Bonus points if we could
1) Connect to network A.
2) Connect to network B.
3) Re-connect to network A.
4) Attempt to re-connect to network B - this results in a password prompt (it
shouldn't as I've already connected in (2)).
5) If I click cancel, I *do* connect to network B (not the original network
A).
--
You
Hi Antii,
Having taken a look at them, I don't think they are actually relevant
since they are identical apart from the obvious fields (id, uuid, ssid,
psk).
I'll try and do further tests over the w/e with both networks...
--
You received this bug notification because you are a member of
Public bug reported:
The pin code entry screen has what appears to be a 1 pixel high line
horizontal line that goes almost to the left and right borders of the
screen, just above the unlock keypad.
I can see the value of such a horizontal rule but it is _so_ thin that
when I looked at it earlier
root@ubuntu-phablet:~# cat /etc/ubuntu-build
32
root@ubuntu-phablet:~# cat /etc/device-build
20140908-d8c11f3
device: krillin
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
Public bug reported:
1) Add contact.
2) Touch '+' to add a picture.
3) Select a data source (gallery, camera, file manager, etc).
4) Slow swipe from right to show all running apps windows.
5) Observe an app window that has a spinner on a white dialog background with
text Transfer in progress
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build
40
phablet@ubuntu-phablet:~$ cat /etc/device-build
20140908-d8c11f3
phablet@ubuntu-phablet:~$
krillin.
** Also affects: indicator-location (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
*** This bug is a security vulnerability ***
Public security bug reported:
This is atleast a privacy issue but could also be a security depending
on exactly what apps the user has pinned to their launcher.
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Tags:
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build
40
phablet@ubuntu-phablet:~$ cat /etc/device-build
20140908-d8c11f3
krillin
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Android gives the user a warning if they attempt to raise the volume to
100% when headphones are plugged.
This is a sensible precaution both to save the user from tinnitus and to
avoid any potential legal repercussions.
** Affects: indicator-sound (Ubuntu)
Importance:
You can also re-order the launcher icons.
--
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/1369457
Title:
able to left swipe and launch apps without unlocking phone
Status
This is worse that I originally though since you can actually *launch*
any app on the launcher without unlocking the phone. You can't see it,
but it is running (unlocking confirms this).
** Summary changed:
- able to left swipe and see launcher icons without unlocking phone
+ able to left swipe
To start an app:
1) Swipe left to show launcher.
2) Keeping finger down in (1) long press an app icon in the launcher.
3) Remove both fingers from screen.
4) Swipe left to show launcher again.
5) Launcher should remain on screen allowing you to touch an app icon to launch
it. See attached.
**
Note sure if this is also a bug (I think it is), but in testing this, I
have inadvertantly managed to delete the system settings icon by moving
it. It seems the operation failed as shown in the screenshot.
** Attachment added: floating-system-settings.png
That failed operation has seemingly corrupted a list somewhere since now
touching my gmail icon actually launches system settings (spoofing
potential here). Attached screenshot shows this.
** Attachment added: gmail-is-now-system-settings.png
Personally, I'm happy for the lock screen to show date+time but I would
prefer everything else to be hidden (or ateast hideable with a system-
setting) until the phone is unlocked.
The majority of users may not mind if the notification bar is displayed
when the screen is locked (Android does
Update to #6: rebooting the phone brought back the original set of icons
such that touching system-settings launches the correct app and ditto
for gmail.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
Ah thanks - didn't know about those options! Disabled both now :-)
The use case for launching apps from the lockscreen is that as a user, you
think oh I want to go to facebook,
click facebook, we start the app in the background so that once you enter
your passcode, it's sitting there ready.
Back link to test plan: https://wiki.ubuntu.com/Process/TestPlans
/systemd-shim
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
upstart can race with
*** This bug is a duplicate of bug 1235245 ***
https://bugs.launchpad.net/bugs/1235245
** This bug has been marked a duplicate of bug 1235245
upstart-monitor cannot run without gtk libraries installed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1235245
Title:
upstart-monitor cannot run
Confirmed - thanks!
** Description changed:
Actually, there are a couple of problems here:
1) If you reverse pinch to zoom into an image, this appears to trigger
zoom to maximum size (aka double-tap). Reverse pinch should just zoom
- on.
+ in.
2) Having zoomed into an image, if
Testing on krillin image #44, the problem is no longer seen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1365492
Title:
selecting previously visited site from
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1338637
Title:
continuous re-exec can result
** Summary changed:
- continuous re-exec can result in a build-up of inotify fds
+ continuous re-exec can result in a build-up of inotify fds [SRU]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
** Description changed:
+ = PROBLEM =
+
+ The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
+ from a couple of problems which in combination could make upgrading
+ difficult on systems with high uptimes.
+
+ The 2 issues are:
+
+ == bug 901038 ==
+
+ The issue here is
** Attachment added: Output of force-reexec.sh on a trusty system with fixes
for both bugs, showing the problem has been resolved.
https://bugs.launchpad.net/upstart/+bug/1338637/+attachment/4207317/+files/typescript.good
** Description changed:
= PROBLEM =
The version of Upstart
The fix for bug 901038 is available upstream but is not yet in Utopic.
Since this is a fundamental system tool, we need to wait until this has
had testing in utopic prior to progressing this SRU.
Plan:
1) Get lp:~jamesodhunt/upstart/bug-1360208 reviewed and landed upstream
(hopefully this
** Description changed:
= PROBLEM =
The version of Upstart currently in trusty (1.12.1-0ubuntu4.2) suffers
from a couple of problems which in combination could make upgrading
difficult on systems with high uptimes.
The 2 issues are:
== bug 901038 ==
The issue here is
A test branch is available here: lp:~jamesodhunt/ubuntu/trusty/upstart
/SRU-bugs-901038+1338637
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1338637
Title:
continuous
A few questions:
1) Has this problem always been present for you since upgrading both systems to
utopic?
2) Do you have any other systems running utopic that do not manifest the issue?
3) How are you shutting the systems down? Via the Unity menu or via the command
line.
4) When you say that
Can you try replacing your /etc/init.d/umountroot and
/etc/init.d/umountfs with the ones from
http://bazaar.launchpad.net/~jamesodhunt/ubuntu/trusty/sysvinit/log-
open-files-on-shutdown/revision/193 and attaching an updated syslog
file?
The end of your syslog shows that wpa_supplicant is still
Looks like the shutdown never got as far as running umountroot. Do you
have a /var/log/shutdown-lsof.log that you can attach to this bug?
I see that all the nullmailer output has gone, but we're still left with
wpa_supplicant and dnsmasq output at the end of the log. As such, could
you try
@n-zbuntu-4: actually, it can - see
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345505/comments/3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1349128
Title:
Public bug reported:
The 3 buttons are currently stacked vertically but:
1) The spacing between them looks cramped.
2) The height of each button is too low to be comfortable.
If you compare this menu with the Android equivalent, on Android the
buttons actually touch _but_ they are atleast as
Public bug reported:
The dash icon is shown as an orange square (with very hard straight
edges btw) with the Ubuntu logo within.
This seems odd since it is so markedly different to the dash icon on
desktop systems (the swirl).
** Affects: unity8 (Ubuntu)
Importance: Undecided
Public bug reported:
If I play a single song in the music app, the welcome shows 1 songs
played today. This is not grammatically correct.
Here's the relevant chunk from the music-app.qml:
Metric {
id: songsMetric
name: music-metrics
format: b%1/b + i18n.tr(songs played today)
Using system image 165 btw.
--
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/1351423
Title:
dash icon significantly different to that on other platforms
Status in “unity8”
... Same applies to the calculator and the camera. And yet, oddly, other
icons deviate distinctly (such as the calendar).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
Hi Seb - yes, that's exactly what I was meaning.
** Package changed: ubuntu-system-settings (Ubuntu) = unity8 (Ubuntu)
--
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/1351410
Public bug reported:
This is incorrect for 2 reasons:
1) The overlay should show a microphone icon since that is what is being
toggled.
2) It's currently using the same icon as the speaker / sound output mute hotkey
(ALT + F1).
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package:
Hi Andrew,
Yes, that's the simplest fix of course. However, care is going to need
to be taken to ensure all consumers of libusermetrics apply such a
format.
I suggest we atleast review all the core apps since although this issue
does not affect the functionality of the apps...
- the issue is
I wonder if this issue points to our needing another layer in the API to
make such indicator behaviour consistent?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-location in
Ubuntu.
Public bug reported:
There is inconsistency between the bluetooth indicator and the location
indication. Currently (image #171):
- if location+GPS are disabled, the indicator persists.
- if bluetooth is disabled, it disappaears.
Which behaviour is correct?
Further, even if the location
Public bug reported:
Currrently, if you have undisplayed notifications, the notification icon
shows as a green bell.
Since all the other notification icons are monochromatic, I think the
behaviour should be:
- no undisplayed notifications: show an unfilled white bell (or simply don't
display
This is incorrect - Upstart does reopen log files when a job produces
output *after* the log file has been deleted.
So in normal operation, logrotate will run and say rotate foo.log to
foo.log.1.gz. At this point, the file associated with the fd for foo.log
will indeed show as deleted. But, if
@Dylan - which packages did you purge?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1379021
Title:
after utopic upgrade: boot delays for 2 minutes
Status in “upstart”
The most appropriate way to do this would probably be to use apport to
check for respawn limit messages in:
- the system log, and
- the users $HOME/.xsession-errors file.
Even at the default upstart log priority of 'message', when a job
reaches the respawn limit, upstart will log a message to
Note that the kerneloops packages communicates with apport using the
/usr/share/apport/kernel_oops pipe program so a script could be
written to make use of similar pipe specifically for respawn failures.
Ideally, that kernel_oops utility would be made generic, accepting args
to specify the name of
Public bug reported:
A swipe from the right edge of the phone towards the center fans out all
the apps, showing a carousel-like view.
However, the background is always black, whereas I would have expected
the background to be the selected background image.
Black is problematic since if one of
brian has pointed out that changing /usr/share/apport/kernel_oops isn't
necessary; apport now has a generic pipe program in the form of
/data/bzr/apport/apport/data/recoverable_problem.
We will need to make minor changes to the recoverable_problem utility
since it currently requires a pid but in
Seems that the camera issue is not only just when the lens is covered.
The live preview feature has gone away, so if the camera is running, the
carousel will show an invisible black camera app every time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I've added more info to the cookbook wrt respawn. Here's the simplest
method of detecting hitting the respawn limit:
http://upstart.ubuntu.com/cookbook/#detecting-a-job-hitting-its-respawn-
limit
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Something like the attached can be put into /usr/share/upstart/sessions/
and it will detect when system-level and session-level jobs hit their
respawn limit.
We could then use whitelists to identify the desired behaviour (restart
job, reboot, etc) for particular services.
** Attachment added:
The oldest of the two unity8 proceses (pid 2640) has been SIGSTOP'ed.
Since unity8 uses SIGSTOP to indicate to upstart that it is ready, this
suggests that when lightdm died, the session init was killed somehow
before unity8 was ready (either on first start or respawn).
--
You received this bug
Daniel - please can you attach the existing /var/crash/_sbin_init* to
this bug. I appreciate they do not represent the current issue, but if
may have been a re-occurence of the problem which did generated the
crash files so I'd like to see those anyway.
--
You received this bug notification
To be clear, this issue was observed on Touch.
Interestingly, we already have a fix for this, but it hasn't landed in
the archive or on Tocuh; the upstart session init has a logrotate job
(/usr/share/upstart/sessions/logrotate.conf) which is used to rotate the
users session init log files. I'd
Public bug reported:
Currently, the system-image package requires system-image-common. The
latter provides /etc/system-image/client.ini which is configurated for a
Touch environment.
However, to allow system-image to be used on systems other than Touch,
it would be useful to have the ability to
That should be ubuntu-bug 1373588 of course :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1373588
Title:
Starting/Stopping services causes init: Error while reading
Thanks for reporting. Please run ubuntu-bug 373588 which will attach
required logs to this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1373588
Title:
As discussed on irc, the problem seemed to be that the plymouth-ready
event was not being emitted since udev was not tagging a graphics device
with PRIMARY_DEVICE_FOR_DISPLAY, so it looked like the problem was
udev/kernel related.
According to jibel, if he enters the grub boot menu lightdm will
Note also that I do have PRIMARY_DEVICE_FOR_DISPLAY=1 in /var/log/udev.
Recreation is under kvm.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does
I have now recreated using utopic-desktop-amd64.iso (20140923) and
http://people.canonical.com/~jhunt/upstart/conf/rebooter.conf to force
continuous reboots.
It appears that the problem only occurs if quiet splash is specified
since I ran 25 boots without those options and was unable to recreate
It's looking like either quiet or more likely splash is the
triggering factor here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into
After removing both 'quiet' and 'splash' options from
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, and running 'sudo
update-grub', I am no longer able to recreate the bug (over 100 boots on
a 64-bit kvm instance using utopic-desktop-amd64.iso (20140923)).
@elfy: can you provide details on how
205 boots and no problem with the 2 options removed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into graphical interface after
@arges: can you try reproducing without quiet splash as that seems to
be the best lead we have so far.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily
Public bug reported:
/lib/systemd/system/ifup@.service specifies:
ExecStart=/sbin/ifup --allow=hotplug %I
This really needs to be:
ExecStart=/sbin/ifup --allow=hotplug %I
Since otherwise, for systems that don't use network-manager, the service
will only bring up interfaces which have
Upstart only gained the ability to re-exec statefully in Raring. The man
page for telinit on Lucid explains that state is not preserved and also
warns that running this command is not recommended.
Note that upstart has to re-exec itself on Lucid if certain key packages
are upgraded to ensure a
$ systemctl status networking
networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
`-50-insserv.conf-$network.conf
Active: active (exited) since Mon 2014-09-29 09:22:44 UTC; 1min 51s ago
I too am unable to recreate this problem - dbus should certainly not be
running in recovery mode because dbus is 'start on local-filesystems',
but that event will not have been emitted since mountall is not run in
recovery mode.
Can you confirm you are entering recovery mode from the grub menu
@elfy - is plymouth is still crashing for you?
$ sudo grep SEGV /var/log/syslog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651
Title:
Daily does not boot into
UPSTART_EVENTS=runlevel
UPSTART_INSTANCE=
UPSTART_JOB=rcS
This is the cause of your problem - you are not actually in recovery mode. What
is your /proc/cmdline? Have you modified /etc/default/grub or any of the
initramfs configuration?
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1198180 ***
https://bugs.launchpad.net/bugs/1198180
** This bug has been marked a duplicate of bug 1198180
possible leak in upstart 1.5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
This almost sounds like bug 1235649, but unlikely given that the
upstart-udev-bridge uses the correct NIH D-Bus calls.
I suspect the reason for the memory growth is that the events that are
being created cannot be destroyed until some other job has finished with
them. Once that happens, memory
@Fabian - thanks for reporting but we need a lot more detail before we
can get to the bottom of this (ps output, strace [you need to install it
in dev mode], etc).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in
It sounds like you may have modified files below /etc/initramfs-tools/
and/or /usr/share/initramfs-tools/, or created additional scripts that
are somehow modifying the boot path. Further, I think you need to
understand why single is being specified on the boot command-line as
that is non-standard.
Please can you run 'apport-collect 1376283' (ideally when your system is
experiencing the issue).
Also, assuming you have not created any jobs yourself that might contain
confidential information (?), it would be extremely useful if you could
run the following when experiencing the problem and
Public bug reported:
Setting up lxc (1.1.0~alpha1-0ubuntu5) ...
Failed to issue method call: Unit lxc.service failed to load: No such file or
directory.
invoke-rc.d: initscript lxc, action start failed.
dpkg: error processing package lxc (--configure):
subprocess installed post-installation
Public bug reported:
Currently, after downloading the latest image, system-image-cli reboots
the system.
It would be extremely useful if rather than hard-coding this, system-
image-cli could conditionally call a hook script when it has finished.
Ideally, it would be possible to specify this in
Just got this running hud 14.10+14.10.20140924-0ubuntu1. Just typing in
a console and my CPU chewing script popped up a window to alert me to
the fact.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to hud in Ubuntu.
Public bug reported:
Holding the physical power button displays the shutdown menu with
options to shutdown, restart or cancel. These buttons are colour-coded
but for added clarity I think we should add icons to represent the
operations.
Note that if this menu is changed, there are other parts of
Rationale for adding icons:
1) The standard shutdown (power) icon, and the restart (circular arrow)
are almost universally recognised (to the extent that you wonder if we
could actually remove the text).
2) Colours only work if you can discriminate between then. Red and green
are alas an
** Also affects: ubuntu-ux
Importance: Undecided
Status: New
--
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/1351423
Title:
dash icon significantly different to
I still don't understand why the current icon:
a) is hard-edged - every other icon (in fact every other widget?) has
rounded corners.
Is this simply to discriminate it from everything else? If so, is there any
other way we can do this that is more in keeping with
the softer-edged
Public bug reported:
Currently client.ini specifies:
[gpg]
archive_master: /etc/system-image/archive-master.tar.xz
The problem is that file in /etc are automatically marked as conffiles
by debhelper and as such don't get moved into place until the dpkg
configure step.
This caused an issue for
@uj__:
The init process is certainly leaking memory.
How have you proved that init is leaking memory? Can you say that PID 1 is not
just still busy processing the flurry of events that would result from starting
all these docker containers? Please provide further details.
I've looked at the
Public bug reported:
system-image currently supports a 'bootme' option that may be present in
the JSON and instructs Touch to reboot _after it has finished
downloading the current file_.
However, Core has a slightly different requirement. It attempts to
minimise reboots, but when certain
Hi Dylan,
Thanks for taking the time to report this issue. Please can you do the
following:
1) Run 'apport-collect 1379021' to attach required logs to this bug
report.
2) Attach /etc/network/interfaces (and any files you've created in
/etc/network/interfaces.d/).
3) Attach /etc/fstab
4) Add
Public bug reported:
The menu doesn't offer a find/search option to look for text on a web
page.
** Affects: webbrowser-app (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Where do I add --debug? The Linux command line?
Yes:
1) Hold down control key at power-on to enter grub menu.
2) Press 'e' to edit the top (default) kernel command-line.
3) Use the cursor keys to move down the the line that begins with
linux.
4) Press the END key (or use cursors again).
5)
1 - 100 of 196 matches
Mail list logo
