apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874177/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubuntu
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874179/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955287
Ti
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874180/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9552
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874181/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955287
Ti
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874182/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874183/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubun
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874184/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ubun
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874185/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955287
Title:
Ub
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874187/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/955287/+attachment/2874178/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/955287
Hi Colin,
Since running tp-thermstat, I just cannot make my machine overheat no
matter what workloads I give it (with fans set to "auto"). Will keep
trying.
I have used the disengaged mode and certainly couldn't force a shutdown
with that either, although it did sound like I was working in a mach
Public bug reported:
Running update-grub gives the error:
grep: input file '/tmp/grub.cfg.new' is also the output
This problem is caused by a combination of...
250 exec > ${grub_cfg}.new
and ...
285 if [ "x${grub_cfg}" != "x" ] && ! grep -q "^password "
${grub_cfg}.new ; then
e
Although it builds locally, util-linux is failing to build in launchpad.
There is a large queue of jobs in front of mine, so we have to wait to
see what a rebuild shows...
Busybox code is fixed (but again, not yet built). file (libmagic) fix is
available - awaiting feedback from upstream.
--
You
After discussion with Scott, the best short-term solution would seem to
be:
1) Modify /etc/init.d/umountfs to call the following in do_stop before
calling umount/swapoff:
"initctl emit unmount-filesystem"
2) Modify /etc/init.d/umountroot to call the following in do_stop before
calling umoun
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: linux-image-2.6.35-23-generic-pae
To recreate on T410 with Nvidia NVS 3100 graphics card:
1. boot kernel linux-image-2.6.35-23-generic-pae
2. Observe that gdm is not displayed (you get a text login window only)
3. Reboot with kernel linux-image-2.6.35-22
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692888
Title:
2.6.35-23 kernel + nvidia fails to display gdm on Thinkpad T410 (with Nvidia
NVS 3100)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Public bug reported:
Binary package hint: cups
/var/log/kern.log show:
Dec 21 08:46:08 azul kernel: [ 1759.118058] usb 2-1.1.5: new full speed USB
device using ehci_hcd and address 8
Dec 21 08:46:08 azul kernel: [ 1759.213679] usblp1: USB Bidirectional printer
dev 8 if 0 alt 0 proto 2 vid 0x04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/692892
Title:
Switching on my usb-connected brother HL-2140 printer generates apparmor
denial message
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Fortuitously, this morning brings a tasty new kernel and I think I've
spotted the problem:
___
Setting up linux-image-2.6.35-24-generic-pae (2.6.35-24.42) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.35-24-generic-pae
Examining /etc/kernel/postinst.d.
** Changed in: upstart (Ubuntu)
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/672067
Title:
There is no bash-completion for the commands in upstart
--
u
@Michael: yes, this should be "stop on unmount-filesystem or single-
user" (we can create a new event for single-user to make the logic
clearer).
@Clint: I agree that full migration sounds like the best approach. I
have had a few discussions previously with Scott on the idea of abstract
jobs. Ther
Update:
- dmalloc shows up nothing.
- memcpy() calls seem legitimate after checking with an interpositioning tool.
I've attempted both a top-down and bottom-up approach to hone in on this
issue:
- I've attempted to stimulate a segv by writing an app doing "similar" things
to "dpkg -l" but no jo
** Changed in: dpkg (Ubuntu Natty)
Status: Triaged => In Progress
--
dpkg segfaults during debootstrap on natty armel
https://bugs.launchpad.net/bugs/674146
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
** Patch added: "temporary fix to build dpkg without optimizations on armel"
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/674146/+attachment/1735325/+files/dpkg-gcc-optimization-bug-workaround-armel.patch
--
dpkg segfaults during debootstrap on natty armel
https://bugs.launchpad.net/b
The plot thickens...
Noted that "-O1" does not cause SIGSEGV with gcc-4.5. Confirmed that the
equivalent set of gcc options for "-O1"...
gcc-4.5 -Q -O1 --help=optimizers|grep enabled|awk '{print $1}'|tr '\n'
' '
... does not cause SIGSEGV. However, it appears that "-O2" is not the
same as...
Public bug reported:
Binary package hint: checkbox
The System Testing app "checkbox-gtk" prompts for the administrators
password just after clicking next. However, if at this stage you click
"cancel" rather than entering a password, checkbox fails to detect this
and runs forever showing the main
--
checkbox (System->Administrator->System Testing) cannot be aborted when cancel
clicked at password prompt
https://bugs.launchpad.net/bugs/676659
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Public bug reported:
Binary package hint: gdb
The tui "layout" commands appear rather "fragile":
1) "layout regs" causes a gdb internal error
To recreate:
gcc -g file.c
gdb --tui a.out
(gdb) b main
(gdb) layout regs
(gdb) r
Starting program: /h
--
gdb tui support broken ("layout regs" gives internal error, "layout split"
gives core dump
https://bugs.launchpad.net/bugs/676891
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Notes:
- problem occurs with and without ~/.gdbinit
- problem appears independent of terminal size (occurs with 24x80 and 48x143).
--
gdb tui support broken ("layout regs" gives internal error, "layout split"
gives core dump
https://bugs.launchpad.net/bugs/676891
You received this bug notificat
Public bug reported:
Binary package hint: cgroup-bin
[ja...@azul]:~> sudo apt-get install cgroup-bin
[sudo] password for james:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libcgroup1
The followi
** Attachment added: "default /etc/cgconfig.conf file"
https://bugs.launchpad.net/bugs/681724/+attachment/1745644/+files/cgconfig.conf
--
cgroup-bin package installs with errors (failure to parse /etc/cgconfig.conf)
https://bugs.launchpad.net/bugs/681724
You received this bug notification be
Tested with Matthias' gcc-4.5 (4.5.1-10ubuntu3): when compiling with
"-O2" seg fault no longer observed.
--
dpkg segfaults during debootstrap on natty armel
https://bugs.launchpad.net/bugs/674146
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
@cltang: thank you very much for identifying the cause+fix!
--
dpkg segfaults during debootstrap on natty armel
https://bugs.launchpad.net/bugs/674146
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Checked and this bug exists in Debians util-linux and upstream
(http://ftp.kernel.org/pub/linux/utils/util-linux/v2.18/).
--
kernel hibernate signature has changed from S1SUSPEND to LINHIB0001
https://bugs.launchpad.net/bugs/683605
You received this bug notification because you are a member of Ub
For info, an "unused" (mkswap'ed only) swap image looks like this:
fc0:
fd0:
fe0:
ff0: 5357
Issue is not with dpkg, but with gcc so change status for dpkg.
** Changed in: dpkg (Ubuntu Natty)
Status: Confirmed => Invalid
--
dpkg segfaults during debootstrap on natty armel
https://bugs.launchpad.net/bugs/674146
You received this bug notification because you are a member of Ubuntu
Fix (for testing!) created in PPA:
https://launchpad.net/~jamesodhunt/+archive/cerulean/+packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683605
Title:
kernel hibernate signature has change
Andrei - thanks for reporting this and thanks too for a fix!
As mentioned by Zaur, this bug stops you running isearch-forward-regexp
which is bound to control+alt+S in emacs by default.
Adding a new entry in gnome-keybinding-properties for control+alt/meta+S
(to try and override tracker) doesn't
Public bug reported:
Binary package hint: gnome-control-center
> gnome-about-me
(gnome-about-me:4710): libebook-WARNING **: ebook.c:2254: cannot get book from
factory: Invalid source
(gnome-about-me:4710): libebook-WARNING **: ebook.c:2254: cannot get
book from factory: Invalid source
about-me
** Description changed:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685848
Title:
gnome-about-me crashes with invalid source
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
This bug is natty-specific. I don't have the super powers seemingly to
specify this :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685848
Title:
gnome-about-me crashes with invalid source
--
ubu
This issue has now been fixed in upstream git repository:
http://git.gnome.org/browse/tracker/commit/?id=8338b23d1c2617588ed9917f1ffa7d781d6c501d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672614
Interestingly, the problem is also seen if chromium is restarted and one
of the tabs is http://translate.google.com - closing that tab resolves
the cpu usage issue, and subsequently opening a new tab and going to
http://translate.google.com does *not* manifest the problem.
--
You received this bu
Public bug reported:
ubuntu-emulator knows how to retrieve the latest image, but it can also
download a specific image.
To avoid having to manually crawl around looking through .json files, it
would be great if an option could be provided to dump details of the
available images (atleast all avail
*** This bug is a duplicate of bug 1222705 ***
https://bugs.launchpad.net/bugs/1222705
** This bug has been marked a duplicate of bug 1222705
init assert failure: alloc.c:633: Assertion failed in nih_unref: ref != NULL
--
You received this bug notification because you are a member of Ubun
Public bug reported:
[0.70] BUG: Bad page state in process modprobe pfn:0
[0.70] page:81041000 count:0 mapcount:-127 mapping: (null) index:0x0
[0.70] page flags: 0x0()
[0.70] Modules linked in:
[0.70] [<80012bb8>] (unwind_backtrace+0x0/0x11c) from [<80
** Changed in: upstart (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222705
Title:
init assert failure: alloc.c:633: Assertion failed in nih_unref: ref
!= N
Michał - if you can trigger this issue frequently, please could you
attach a .tgz of ~/.cache/upstart/ and ~/.xsession-errors or better yet
provide steps to allow me to recreate this issue. Also, if you could
provide details of how these tests run, that would be useful. Can you
tell me if multiple
Yes. And with --memory=2048 and --memory=4096. The crash is triggered by
any key press fwiw.
What's interesting is that if I press a key immediately (that is to say
*before* the kernel has started and the emulator is busy spewing out
information on its config), the panic won't occur until after th
** Branch linked: lp:~jamesodhunt/upstart/bug-1222705-reprise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222705
Title:
init assert failure: alloc.c:633: Assertion failed in nih_unref: ref
!= N
Thanks Michał - your steps to recreate the issue helped me track down
the cause :-)
Essentially, any job containing 'initctl unset-env' or 'initctl unset-
env --global' in any process stanza (post-stop, pre-start, etc) will
trigger the issue when that job is restarted.
Note that the problem is no
** Changed in: upstart
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222705
Title:
init assert failure: alloc.c:633: Assertion failed in nih_unref: ref
!= NULL
To m
Public bug reported:
/var/log/kern.log shows:
Aug 28 17:32:20 faire kernel: [37077.847109] EXT4-fs (sde1): warning: maximal
mount count reached, running e2fsck is recommended
Aug 28 17:32:20 faire kernel: [37077.848127] EXT4-fs (sde1): recovery complete
Aug 28 17:32:20 faire kernel: [37077.8489
** Summary changed:
- systemd-shim fails to handle cgmanager being unavailable
+ upstart can race with cgmanager when using remove-on-empty
** Changed in: upstart
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
>From @teds findings:
"The Upstart job creates the cgroup as it goes through each phase in the
job, but it sets the cgroup to be destroyed when all of its PIDs are
gone. When starting the second or later task (what ever that might be,
seems to be post-stop a lot though) there is then a race betwee
Public bug reported:
The fix for upstart bug 1357252 has highlighted the fact that systemd-
shim does not support functionality required by logind, namely:
- abandoncgroup (delete if possible)
- stopsession(kill all tasks and remove cgroup)
Because of this, systemd-shim sets the remove-on-empty
Bug 1363134 raised for the systemd-shim work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
upstart can race with cgmanager when using remove-on-empty
To manage notifications about t
Public bug reported:
Looking at a launchpad bug shows the body of the bug is a very thin (1/3
screen width?) column when held vertically.
Rotating device to landscape mode shows a wider display, but only ~60%
of the screen width is used.
** Affects: webbrowser-app (Ubuntu)
Importance: Undec
Public bug reported:
Once a passphrase has been set, it seems to be impossible to revert to
"swipe".
There is also a rather nasty issue in that if you attempt to do that,
the "Switch to swipe" password box pops up but the osk does not appear a
lot of the time (*). You can touch 'cancel' but you c
Public bug reported:
The blue convex pentagon used as a cursor to allow editing of text boxes
is too small.
As a result of this, it is necessary (for me atleast) to cover the
entire shape when moving the cursor meaning you cannot actually see
where there cursor is being moved too (since the small
** Summary changed:
- cannot disable passphrase
+ cannot revert from passphrase back to swipe
** Description changed:
Once a passphrase has been set, it seems to be impossible to revert to
"swipe".
There is also a rather nasty issue in that if you attempt to do that,
the "Switch to sw
Public bug reported:
If you set a purely numeric passphrase, you cannot then switch to a pin
number (again, purely numeric) unless you change the value.
Which leads to the question: Is it valid for the user to change only the
method by which they are being authenticated?
** Affects: ubuntu-syste
Hmm, well attempting to switch from pin to passphrase to allow me to be
more descriptive gives me an error: "internal error: user not loaded".
root@ubuntu-phablet:/# cat /etc/ubuntu-build
11
root@ubuntu-phablet:/# cat /etc/device-build
20140829-678239d
Will try the silo...
--
You received thi
Yes silo 003 does resolve the ability to revert from passphrase to
swipe.
But it does not resolve the issue mentioned in the description where the
password box disallows text input.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
Currently, if you attempt to make an emergency call *without* unlocking
the phone, you get presented with the dialer with all options disabled.
That is to say, you cannot change any options or access the addressbook.
This is clearly the safest strategy but in a real emergency
Public bug reported:
Further to reporting bug 1364482 I know see that in fact I cannot make
an emergency call without unlocking the phone.
I can enter a number but the green dialer icon thing always stays greyed
out.
root@ubuntu-phablet:/# cat /etc/ubuntu-build
11
root@ubuntu-phablet:/# cat /et
Public bug reported:
Ideally also show local time for that country in brackets.
Would be great to see the flags + time in the dialer too.
** Affects: address-book-app (Ubuntu)
Importance: Undecided
Status: New
** Affects: dialer-app (Ubuntu)
Importance: Undecided
Sta
Ah - I see how this works now...
By emergency call, we really mean only that. It appears you can only
dial a "recognised" emergency number. 911 and 999 both enable the green
icon.
In which case, please can we consider either:
1) pre-populating the number field with the country-specific emergency
Public bug reported:
Background->Custom->"Add an image..." currently launches the gallery
app. It should really offer the user a choice between gallery and camear
** Affects: ubuntu-system-settings (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification be
** 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.
** 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
Tit
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.
https://bugs.
Hi Alan,
Is this reproducable? If so, a 'ps -efwww' would be useful so we can see
what is actually running initctl and what it is trying to do. Also, if
you can 'strace -o /tmp/initctl.strace -s 1024 -fFv -p pid-of-initctl'
and attach /tmp/initctl.strace to the bug that would be very useful.
** C
** Changed in: upstart (Ubuntu)
Assignee: James Hunt (jamesodhunt) => (unassigned)
** 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.launchp
This isn't really a bug with Upstart since it appears the problem is
that bamfdaemon is spamming dbus somehow. Upstart is simply logging the
output.
That said, there is an outstanding merge proposal to have the session
logrotate job run periodically which would have avoided so much disk
space bein
** Package changed: bamf (Ubuntu) => dbus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284164
Title:
~/.cache/upstart grows enormous
To manage notifications about this bug go to:
https:/
Scott - agreed. However, the root cause has nothing to do with Upstart.
Yes, we can make Upstart perform more frequent rotations, but I think we
need to understand why your log is growing so fast: yours seems to be
growing at ~32MB / day, mine grows at ~100k.
Taking a slighly longer peek, it appe
Just noticed the tagging on this bug - please can you raise a new
upstart bug attaching upstart.state (fro /var/log/ or
~/.cache/upstart/). Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/128416
It looks like the main culprit is the web browser and/or the Google
plugins - every Google connection apears to result in a multi-line burst
of json being logged. Are you running the browser/plugins with any debug
enabled?
--
You received this bug notification because you are a member of Ubuntu
B
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
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 'i
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 'i
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
\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 Ubuntu
** 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:
segfaul
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. I
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 utopi
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 notific
** 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 notificati
** 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
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 ar
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-
upstart/ARCH=amd64,label=adt/l
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 http://people.canonical.com/~jhm/baraj
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 sil2
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.
https
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
** 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
301 - 400 of 1868 matches
Mail list logo
