Reported as https://gitlab.gnome.org/GNOME/gdm/issues/438.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this
apport information
** Tags added: apport-collected bionic
** Description changed:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
-
apport info added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this bug go to:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1800277/+attachment/5206696/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can do that if really required, but this is not a bug with my system -
it's just the way the system works right now, so I'm suggesting an idea
for how we can make it better :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority
In this scenario, the user is returned to
Yep - that was handled with lp:~jamesodhunt/goget-ubuntu-touch/add-list-
images-option.
** Changed in: goget-ubuntu-touch (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ = Summary =
+
+ The version of Upstart in vivid is affected by a coule of bugs relating
+ to the flushing data from early-boot jobs to disk which can both result
+ in a crash:
+
+ == Problem 1 ==
+
+ An internal list is mishandled meaning a crash could occur randomly.
Hi Steve - ah, sorry - hadn't registered that you'd already copied the
package into the queue (we now have 2 :-) Could mine be deleted please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447756
** Changed in: upstart (Ubuntu Vivid)
Status: New = In Progress
** Changed in: upstart (Ubuntu Vivid)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Unfortunately, ondra no longer has the failing phones so we may need to
take a decision to just land this if QA are happy the change has not
regressed the behaviour for non-failing phones.
I've tried to raise QA but they are sprinting in the US this week so no
direct response.
I believe that
Thanks for nudging -proposed Steve.
I've silo 021 now includes upstart version 1.13.2-0ubuntu13.1 (which
sil2100 synced from wily).
Basic test plan is here: https://wiki.ubuntu.com/Process/TestPlans
/upstart-bug-1447756
I've tested this as follows:
$ wget
Looks like kernel bug 1429756 could block 1.13.2-0ubuntu14 landing for
wily (being a pre-req to getting this fix into vivid and utopic):
https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-
adt-upstart/ARCH=amd64,label=adt/9/
--
You received this bug notification because you
Hi Andy - any progress on this? Although the buildd's are running older
kernels, it seems that the DEP-8 Jenkins environment is running 3.19 and
is thus causing upstart tests to fail. For example:
https://jenkins.qa.ubuntu.com/view/Wily/view/AutoPkgTest/job/wily-adt-
** Changed in: upstart
Status: In Progress = Fix Committed
--
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 in log.c code causes phone reboot loops
To manage
** Also affects: upstart (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: upstart (Ubuntu Wily)
Importance: Critical
Assignee: James Hunt (jamesodhunt)
Status: In Progress
** Also affects: upstart (Ubuntu Vivid)
Importance: Undecided
Status
MP raised on lp:upstart to start the trickle-down to the rtm package.
--
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 in log.c code causes phone reboot loops
To manage
Applying the top 2 commits (r1665 and r1666) from
lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix [1] to
https://bugs.launchpad.net/ubuntu-
rtm/+source/upstart/1.13.2-0ubuntu1rtm1 is now working for me.
I've tested this by building on the device itself and also by building
in a ARCH=armhf
lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix contains the fix and
a new test (which correctly fails with the current lp:upstart but passes
with the fix in that branch).
The code has been tested on a failing device and a server system. I am
currently testing on a non-failing krillin device.
Hi Ondrej,
Regarding #15, I'm not sure this is correct. As you say, when the job
process terminates, job_process_terminated() gets called. This calls
log_handle_unflushed() and that function calls log_read_watch(), which
ultimately calls write(2). However, even if the write is successful
before
Ondrej - aha! with the debug, this is making more sense now. Yes, since
the ureadahead-touch job spawns a process in the background (ureadahead)
and then the job itself exits, the log associated with the main job
process gets added to the unflushed list. ureadahead then writes output
and the NihIo
Hi Ondrej,
Regarding #15, I'm not sure this is correct. As you say, when the job
process terminates, job_process_terminated() gets called. This calls
log_handle_unflushed() and that function calls log_read_watch(), which
ultimately calls write(2). However, even if the write is successful
before
\o/. Yes, Upstart uses asserts extremely agressively. It's unfortunate
that we've never hit this issue in testing but I'm currently working on
new tests for this slightly unusual scenario.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: upstart (Ubuntu)
Status: Confirmed = In Progress
** Changed in: upstart
Status: New = 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/1447756
Title:
segfault
ondra and I have been hammering away at this, but progress is painfully
slow given that:
a) the problem is not seen on every boot.
b) we can only view the end of kmsg log.
c) rebuild times are relatively slow.
From what ondra says he's seen today, it sounds as though we might be
hitting a stack
I've rebuild the fix in a clean environment and the init binary below
now boots fine for me on a bq aquaris E4.5:
http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi ondra/ogra - Can you comment on my suggestions in #6 and #7? My
device is still bricked so if you have any suggestions on how to perform
a full reset, that'd be great as udf is unable to recover it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
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 in log.c code causes phone reboot loops
I think I understand what's happening now - it's not the log that isn't
being freed, it's the list entry the log is attached to that is not
freed. The effect is the same though - calling log_clear_unflushed()
multiple times could trigger this issue since the still-valid (but
incorectly so) list
Screenshot showing the super-thin divider.
** Attachment added: scratch.jpg
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1368798/+attachment/4382842/+files/scratch.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i386+amd64 are packaged here:
https://launchpad.net/~jamesodhunt/+archive/ubuntu/bug-1447756/+packages
--
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 in log.c code causes
Test binaries are available here:
http://people.canonical.com/~jhunt/upstart/bugs/bug-1447756/armhf/
--
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 in log.c code causes phone
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Something else to try - disable /etc/init/flush-early-job-log.conf on
boot...
$ sudo mount -oremount,rw /
$ echo manual | sudo tee /etc/init/flush-early-job-log.override
$ sudo reboot
... and post-boot do the following:
$ for i in $(seq 17); do sudo initctl notify-disk-writeable; done
As Steve
I've tried the fix on my bq device and it appears to be in a reboot loop
(like the one the fix was supposed to resolve).
As such, I'd recommend testing the binaries only for the session init
initially (/usr/bin/ubuntu-touch-session / /usr/share/lightdm/sessions
/ubuntu-touch.desktop).
Also, for
This issue was resolved on MP
https://code.launchpad.net/~jamesodhunt/snappy/add-transactional-
updates-doc/+merge/255719.
** Changed in: golang-phablet-tools-ubuntu-device-flash (Ubuntu)
Status: Confirmed = Invalid
** Changed in: snappy-ubuntu
Status: Confirmed = Fix Released
--
Public bug reported:
The s-i archives that u-d-f unpacks specify the contents of /dev.
However, running the following on a snappy system gives unexpected
results:
ubuntu@localhost:~$ ls -l /dev|grep ^-|wc -l
0
ubuntu@localhost:~$ ls -l /dev|egrep ^(b|c)|wc -l
The inconsistency seems to originate in udf's diskimage/core_uboot.go.
** Also affects: golang-phablet-tools-ubuntu-device-flash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
LKML thread: https://lkml.org/lkml/2015/3/16/474
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Title:
FTBFS: upstart test_job_process fails in majority of cases / Kernel
returning
** Package changed: upstart (Ubuntu) = chromium-browser (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300235
Title:
init (chromium-browser) crashed with SIGSEGV
To manage notifications
I've written a basic program that surfaces this bug. To recreate:
$ cd /tmp
$ tar xvf bug-1429756.tgz
$ cd bug-1429756
$ make
$ ./bug-1429756.sh
loop 1
loop 2
ERROR: got failure scenario after 2 loops (got=16, count=17,
log=/tmp/tmp.uwZHkHh0mc)
$
** Attachment added: bug-1429756.tgz
Running with a 3.19.0-8-generic kernel I see:
- The Upstart test_job_process test fail within a few seconds when run in a
loop looking for the errror.
- My test program in #13 also finds the bug within ~30 seconds on my test
system.
Using the kernel in #11, I have run both tests simultaneously
** Summary changed:
- ubuntu-touch livefs builds kill upstart in host
+ [SRU] ubuntu-touch livefs builds kill upstart in host
** Changed in: upstart (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Playing around with strings(1), I've found this:
$ strings /usr/lib/chromium-browser/libs/libcontent.so|egrep \init\
init
The SUID sandbox created a new PID namespace but Zygote is not the init
process. Please, make sure the SUID binary is up to date.
Error creating an init process to reap
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430403
Title:
ubuntu-touch livefs builds kill upstart in host
** Also affects: upstart (Ubuntu Precise)
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/1430403
Title:
ubuntu-touch livefs builds kill upstart in host
** Description changed:
= Summary =
The version of Upstart in precise is affected by a bug in the way that
.override [1] file handling is performed.
If a job has an override file (/etc/init/*.override) and that override
file is deleted before the corresponding job configuration
** Description changed:
+ = Summary =
+
+ The version of Upstart in precise is affected by a bug in the way that
+ .override [1] file handling is performed.
+
+ If a job has an override file (/etc/init/*.override) and that override
+ file is deleted before the corresponding job configuration
lp keeps timing out on me when I attempt to attach a file. Meantime...
I've managed to force a crash after ~150 iterations of bug-1430403.sh
using http://people.canonical.com/~jhunt/upstart/bug-1430403.tgz.
To recreate:
$ sudo tar xvfz bug-1430403.tgz
$ sudo bash bug-1430403.sh
--
You
The crash seems to originate from the conf_delete_handler() where
although an error message gets logged, the actual error itself is not
cleared. Note that this bug is present in 1.5-0ubuntu7.2 (precise), but
is not present in trusty (1.12.1-0ubuntu4.2) or vivid (1.13.2-0ubuntu9).
--
You received
Attached is a minimal fix for the bug.
Note that since this issue does not affect newer releases, we cannot
follow the usual process of testing in the dev release. However, as can
be seen, the fix is small and quite clear. Note that the change to
main.c is required to make upstart build on
Note that we cannot add new unit tests for this fix without making it a
much bigger change since the problematic function is static.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430403
Title:
It is relatively simple to trigger the bug: run a script that loops
creating a .conf file and an .override file, then deletes the .conf file
before deleting the override file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: upstart (Ubuntu Vivid)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429756
Title:
FTBFS: test_job_process fails in majority
It does indeed seem to be related to the kernel. I've just run that
specific test 77 times on an amd64 system running a 3.18.0-11 kernel
with no failures. Once the broken deps issue is resolved, I'll retest on
the same system running the latest 3.19 kernel.
--
You received this bug notification
Updating the amd64 system, I see the failure on the 2nd test run.
The Upstart logging code doesn't seem to be the culprit fwics meaning
the most likely area is the pty-handling code (either in upstart or in
the kernel).
--
You received this bug notification because you are a member of Ubuntu
Some quick tests suggest that this issue only seems to affect long runs
of nul bytes (even if they are terminated by visible chars + a '\n').
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429756
The good news is that this test failure is a real bug: running 1024
job instances of what is effectively the failing tests shows...
- 3.18 kernel: 0 job instances have incorrect size.
- 3.19 kernel: 848 job instances have the **incorrect** size (!!)
Figures are from a fully-updated amd64 vivid
mk-sbuild now fails with a different error:
Setting up udev (219-4ubuntu3) ...
A chroot environment has been detected, udev not started.
/var/lib/dpkg/info/udev.postinst: 35: /var/lib/dpkg/info/udev.postinst:
update-initramfs: not found
dpkg: error processing package udev (--configure):
'mk-sbuild vivid' currently gives an error:
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
systemd-sysv : Conflicts: upstart but 1.13.2-0ubuntu9 is to be installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or
** Changed in: ubuntu-core-config (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Changed in: ubuntu-core-config (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: upstart (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425685
Title:
Missing input sanitation in upstart logrotation cronjob
To manage
Fixed in upstart 1.13.2-0ubuntu9, currently in the proposed pocket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425685
Title:
Missing input sanitation in upstart logrotation cronjob
To manage
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Note - this problem only affects vivid fwics. Further, it does not
affect Touch (since that uses Upstart as PID 1).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425685
Title:
Missing input
As another data point, using udf 0.3+14.10.20140807-0ubuntu1 and having
created an image using...
$ sudo ubuntu-device-flash -v --revision 220 core --size 3 -o
i386-r220.img --channel ubuntu-core/devel-proposed --developer-mode
--device generic_i386
... I'm able to boot successfully on real
Hi Serge,
Yep, updating to lxcfs 0.4, killing lxcfs, then a 'sudo chown -R james:
/sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-c2.scope'
allowed me to start the non-priv container.
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
Hi Serge,
Yep, updating to lxcfs 0.4, killing lxcfs, then a 'sudo chown -R james:
/sys/fs/cgroup/systemd/user.slice/user-1000.slice/session-c2.scope'
allowed me to start the non-priv container.
** Changed in: lxc (Ubuntu)
Status: Incomplete = New
--
You received this bug notification
Public bug reported:
Seems to be due to 1.1.0~rc1-0ubuntu1 landing?
$ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug
lxc-start: lxc_start.c: main: 345 The container failed to start.
lxc-start: lxc_start.c: main: 347 To get more details, run the container in
foreground mode.
Public bug reported:
Seems to be due to 1.1.0~rc1-0ubuntu1 landing?
$ lxc-start -n trusty --logfile /tmp/lxc.log --logpriority debug
lxc-start: lxc_start.c: main: 345 The container failed to start.
lxc-start: lxc_start.c: main: 347 To get more details, run the container in
foreground mode.
Ah - seems we'd actually need to add in a couple of loops in those
original dep-8 tests: run the tests as root, then run as a non-priv user
too! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah - seems we'd actually need to add in a couple of loops in those
original dep-8 tests: run the tests as root, then run as a non-priv user
too! :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Hi Brian - does running synaptic-pkexec in a terminal trigger the crash?
If not, we really need a trace showing what happens in cbOpenHomepage,
specifically what the 'cmd' vector contains.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Another use-case for this is if you start playing music, lock the screen
and put the phone in your pocket. Realising the volume is too low, you
raise it without removing the phone from your pocket. Again, we should
warn the user that they are about to cross the threshold somehow as they
are not
Public bug reported:
Currently, the Information() D-Bus method provides the following
something like:
current_build_number=129
device_name=generic_amd64
target_build_number=131
version_detail=ubuntu=20141205.1,raw-device=20141205.1,version=129
channel_name=ubuntu-core/devel
Public bug reported:
Additional to the work done on bug 1373404, I think we need to consider
adding an audio warning when the volume crosses the threshold value.
The way android works is that the user is asked if they want to allow
higher volume levels (they must click ok). Our approach is to
Public bug reported:
qemu-img _may_ be working as designed, but it feels like this could be a
bug. I'd certainly prefer to only allow unique snapshot names (unless
maybe something like a --force-non-unique-snapshot-names was also
specified).
If this really is correct behaviour, it should be
Public bug reported:
qemu-img _may_ be working as designed, but it feels like this could be a
bug. I'd certainly prefer to only allow unique snapshot names (unless
maybe something like a --force-non-unique-snapshot-names was also
specified).
If this really is correct behaviour, it should be
Problem still occuring.
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build
169
phablet@ubuntu-phablet:~$ cat /etc/device-build
20141119-db417fa
phablet@ubuntu-phablet:~$
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Fabian,
The problem you are having seem to be related to mtp-server respawning
continuously. This may not be the same issue as originally reported, so
please open a new bug against the mtp-server package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
krillin:
phablet@ubuntu-phablet:~$ cat /etc/ubuntu-build
161
phablet@ubuntu-phablet:~$ cat /etc/device-build
20141106-572f18d
phablet@ubuntu-phablet:~$
'strace -p $pid -s 1024 -Ffv' attached.
** Affects: ubuntu-system-settings (Ubuntu)
Importance: Undecided
I think this could be related to bug 1393427 since I am still unable to
install updates (there are more now).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394250
Title:
system-settings consuming
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
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:
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
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
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
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
Bugs, which is subscribed
Discussed with slangasek who is happy with having this package in the
archive (universe).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380674
Title:
[needs-packaging] Add new package
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
Bugs, which is
*** This bug is a security vulnerability ***
Public security bug reported:
If you enable pin unlock, then repeatedly enter the incorrect pin,
eventually you'll get a message stating that the phone cannot be
unlocked for 5 minutes. However, this restriction can be trivially
bypassed by simply
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
@dholbach: Thanks for reviewing! Package updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380674
Title:
[needs-packaging] Add new package ubuntu-core-upgrader
To manage notifications about
LGTM!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1380674
Title:
[needs-packaging] Add new package ubuntu-core-upgrader
To manage notifications about this bug go 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
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
Public bug reported:
Please add package lp:~ubuntu-foundations-team/+junk/ubuntu-core-
upgrader to the archive.
This package is required for the Ubuntu Core project.
** Affects: ubuntu
Importance: Undecided
Assignee: James Hunt (jamesodhunt)
Status: In Progress
** Tags
@Dylan - which packages did you purge?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379021
Title:
after utopic upgrade: boot delays for 2 minutes
To manage notifications about this bug go to:
1 - 100 of 2008 matches
Mail list logo
