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) Obse
= isodate =
Availability: Currently in universe.
Rationale: Build dependency.
Security: No security history.
Quality Assurance:
- DEP-8 tests + watch file added to package:
https://code.launchpad.net/~jamesodhunt/ubuntu/utopic/isodate/add-dep8-tests/+merge/233902
- No debconf prompting.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1367411
Title:
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 notific
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: ad
Availability: Currently in universe.
Rationale: Dependency.
Security: No security history.
Quality Assurance:
- Package works out of the box with no prompting.
- No debconf prompting.
- There are no bugs in Debian currently:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;
There is a dep problem here though:
We're wanting to have python-rdflib Build-Depend on python-
sparqlwrapper, but python-sparqlwrapper Depends on python-rdflib.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
As doko has noticed, we also need to understand why the python3 tests
have been disabled in the sparql-wrapper-python_1.6.0-2 in proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349899
Title:
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 h
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
PYBUILD_DISABLE_python3=test is set because of syntax errors reported by
python3.
However, there is a newer version of the package (1.6.4) which includes
python3 fixes and I've successfully run the python3 tests with that.
Debian Bug#761177 raised to get version 1.6.4 into Debian.
--
You receiv
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 recei
Public bug reported:
I think this issue started some time this week. My phone is fully up-to-
date but the main system settings screen keeps showing there is 1 update
available. Clicking the icon displays the spinner which then tells me my
phone is up-to-date.
** Affects: ubuntu-system-settings (
root@ubuntu-phablet:~# cat /etc/ubuntu-build
30
root@ubuntu-phablet:~# cat /etc/device-build
20140908-d8c11f3
14.09 rtm branch.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
sorry, it's krillin. I've just gone to check again, but now the
mysterious update message has vanished.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368253
Title:
main screen shows updates availab
No, I don't think I had a red "[1]" on the launcher whilst system-
settings was still showing 1 update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368253
Title:
main screen shows updates availab
Giorgio - the spec doesn't appear to specify the colour that should be
used for the highlights. If the highlight colour is fixed as say yellow,
it would have no effect if the background colour of the page was the
same colour. What if the background colour is white but the text is
yellow?
--
You r
** Changed in: system-image (Ubuntu)
Assignee: James Hunt (jamesodhunt) => Michael Vogt (mvo)
** Changed in: system-image (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@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:
htt
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
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 o
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 one
@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 t
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:
https://bugs.launchpad.net/ub
Public bug reported:
Running the following as part of an lxc unprivileged container setup
(see [1]) used to work fine:
pactl load-module module-native-protocol-unix auth-anonymous=1
socket=$PULSE_PATH
However, as of today, this fails. Looking in syslog I see:
___
Public bug reported:
Attempting to run keychain from my ~/.profile results in my being
prompted (successfully) for my ssh passphrase (using /usr/lib/openssh
/gnome-ssh-askpass). However, when prompted for my gpg passphrase via
pinentry (using /usr/bin/pinentry-qt4), I am unable to enter my
passphr
Checking my setup, I see that I'm forcing ssh passphrases to use gtk
rather than qt by specifying the following in my ~/.profile:
export SSH_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass
See bug 924731.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
This looks like a local customization you have added to the initramfs
since file /usr/share/initramfs-tools/scripts/local-top/kbdrate.sh is
not / no longer provided by an archive package. Somehow that script
seems to have lost its execute bit.
I would check the contents of that file and if you rec
Jeremie and Peter - thanks for attaching the crash files, but like the
others affected the core file encoded inside '_sbin_init.0.crash' were
generated by chrome / chromium-browser so we cannot use these to debug
the system crash. There seems to be some strange interaction between
chrome, upstart,
*** 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 rebo
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 th
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 t
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 su
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 ubuntu-core-u
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 t
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: "r
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 becau
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 n
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 not
Thank you for reporting this bug. However, to help us diagnose the
issue, please can you run the following:
$ apport-collect 1237587
This should attach crash file '/var/crash/_sbin_init.1000.crash' to this
report which will allow us to understand what caused the crash.
--
You received this bug
This may explain bug 1234731.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1238078
Title:
global environment table is not serialised
To manage notifications about this bug go to:
https://bugs.laun
See bug 1238078.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1234731
Title:
calling 'initctl set-env -g' from within an upstart job is lost
To manage notifications about this bug go to:
https://b
The problem is not observed when the only connections to upstart are the
standard upstart bridges (since they use nih_dbus_connect()).
For reference, here is nih_dbus_setup() which includes one or more calls
that unity seemingly should be calling itself:
http://bazaar.launchpad.net/~ubuntu-
branc
This problem can now be demonstrated with a single connection to upstart
that makes the following calls:
dbus_connection_open()
nih_dbus_proxy_new ()
The problem is not seen if the app instead calls:
- nih_dbus_connect (upstart_session, disconnect_handler)
- nih_dbus_proxy_
This seems to be because ProblemType was "RecoverableProblem" which is
not currently handled by the upstart apport hook.
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
Y
Note that disabling libIndicatorsQml.so with #44 did not resolve the
problem. However, I am confident this is because there were other
connections to the Session Init (probably resulting from libupstart-app-
launch1).
This does need to be confirmed though.
--
You received this bug notification b
C program to trigger this bug. Run it in an environment with
UPSTART_SESSION set (such as a desktop/Touch environment), then run the
about-to-be attached spam.sh script.
** Attachment added: "trigger-bug-1235649.c"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/387261
Run as:
$ spam.sh
** Attachment added: "spam.sh"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3872619/+files/spam.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12
Program attached in #51 demonstrates the incorrect calling behaviour. To
demonstrate the correct behaviour change the #if0/else/endif such that
rather than calling dbus_connection_open(), the program calls
nih_dbus_connect().
nih_dbus_connect(): No memory growth.
dbus_connection_open(): Memory gro
Public bug reported:
The main libreoffice icon seen in the dash is too bland.
I can see that it is attempting to represent in the most minimal way the
overall office suite (by not including text, cells, formulae, etc),
however, subtracting all content from the icon gives it an overly
ascetic air
Public bug reported:
In certain areas, Ubuntu Touch needs to use D-Bus activation to start
Upstart jobs.
= Overview =
This bug is for tracking the re-enabling of Upstart service activation
in D-Bus.
In certain areas, Ubuntu Touch needs to use D-Bus activation to start
Upstart jobs. The version
** Changed in: upstart (Ubuntu)
Status: Confirmed => 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/1238058
Title:
upstart apport hook asks me in a crash report whether this is f
** 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/1238078
Title:
global environment table is not serialised
To man
Note that the following call on the server side does not resolve the
issue:
while (dbus_connection_dispatch (connection) == DBUS_DISPATCH_DATA_REMAINS)
;
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Neither does calling the following help:
dbus_connection_flush (connection);
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upsta
Just got a much more interesting valgrind run. Juicy excerpt:
==9366== 147,560 bytes in 1,190 blocks are still reachable in loss record 187
of 188
==9366==at 0x402B965: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==9366==by 0x408E730: dbus_malloc0 (dbus-memory.c:572)
==
Hi Steve,
The trace in #59 was produced by:
- Running Upstart via valgrind which upstart linked against debug builds of nih
and dbus.
- Running a single instance of the test program (#51).
- Running spam.sh (#52).
- Waiting until init was consuming ~200MB, then sending SIGTERM to the
init/valgr
Another valgrind log taken using the same precedure as above. However,
this time I waited until the init process was consuming over 2GB of RAM.
Top showed:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
15329 james 20 0 2463m 2,0g 12m R 100,0 26,1 6:51.59 memcheck-
** 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/1238078
Title:
global environment table is not serialised
To manage notifications about this b
@alien: Please raise a new bug with full details - take a picture of the
screen showing these messages if possible and attach to the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1120660
Title:
** Attachment added: "test_nih_dbus_client.c"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878664/+files/test_nih_dbus_client.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
** Attachment added: "spam_dbus_server.sh"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878665/+files/spam_dbus_server.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I can now recreate the memory bloat using a basic NIH D-Bus server
program and associated client program.
1) Run the server as:
$ ./test_nih_dbus_server unix:abstract=/com/hunt/james/foo
com.hunt.james.Foo /com/hunt/james/Foo
2) Run the client as:
$ ./test_nih_dbus_client unix:a
Valgrind log from test_nih_dbus_server.c run using 'valgrind --num-
callers=100 ...'.
** Attachment added: "vg-test_nih_dbus_server.log.gz"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878682/+files/vg-test_nih_dbus_server.log.gz
--
You received this bug notifica
** Changed in: upstart-cookbook
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/1227115
Title:
upstart-file-bridge EVENT documentation examp
FWICS D-Bus is behaving as designed: since the client has not called
dbus_connection_set_wakeup_main_function(), and since D-Bus messaging is
reliable, all libdbus is able to do when a signal is sent to a
connection is cache any messages the client has not yet processed in the
hope that at some fut
TBC, using the patch on #69 results in no memory bloat.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
massive am
** Changed in: upstart-cookbook
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227115
Title:
upstart-file-bridge EVENT documentation examples incorrect in cookbook
: (unassigned) => James Hunt (jamesodhunt)
** 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 subscrib
This is not an Upstart issue:
- Upstart in Ubuntu provides a logrotate script that is run to compress session
logs in ~/.cache/upstart/. So, by removing logrotate you have broken that
facility.
- Upstart is correctly capturing the seemingly huge amount of data generated by
these applications,
** Also affects: systemd (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/1342586
Title:
[utopic] [proposed] cgmanager breaks lightdm login
To mana
Note: systemd packaging branch is out-of-date.
Attached patch stops a NULL deref which would explain this issue.
** Patch added: "Don't nih_unref NULL value."
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1342586/+attachment/4154594/+files/bug-1342586.patch
--
You received this bug
Upstart 1.13 now provides _three_ options for full flexibility:
--confdir=, --append-confdir= and --prepend-confdir=. All options can be
specified multiple times. See the MP for details and examples and
init(5) for the gory details:
https://code.launchpad.net/~jamesodhunt/upstart/bug-1315060/+merg
Public bug reported:
Attempting to scan via wifi from a Brother MFC-7860 DW fails; the
scanner shows scanning but:
- no image appears in simple-scan.
- simple-scan consumes 100% CPU
- the ~/.cache/simple-scan/simple-scan.log grows indefinately until disk space
is exhausted.
This used to work pe
When simple-scan is spinning, the following entry is added to the log
repeatedly until ENOSPC:
[+15,29s] DEBUG: scanner.vala:1310: sane_read (0) -> (SANE_STATUS_GOOD,
0)
Further details:
$ cat /proc/$(pidof simple-scan)/stack
** Attachment added: "strace snapshot of simple-scan consuming 100% CPU"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1344869/+attachment/4156869/+files/bug-1344869-strace.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
*** This bug is a security vulnerability ***
Public security bug reported:
When my machine comes out of suspend, I am shown the lightdm greeter.
However, occasionally I am unable to enter my password since the
password box is not given focus. Clicking with the mouse in the password
box also doesn
Hi Robert,
Sorry to be vague, but I don't actually scan much so the last time I
recall doing it I was running trusty.
Yes, the proprietary brother drivers are required for wireless scanning
AIUI.
$ dpkg -l | grep brscan
ii brscan-skey 0.2.4-1
'ltrace -o /tmp/bug-1344869-ltrace-xsane.log -s 1024 -fl libsane.so.1
xsane' log from a successful wireless scan using xsane.
** Attachment added: "ltrace -o /tmp/bug-1344869-ltrace-xsane.log -s 1024 -fl
libsane.so.1 xsane"
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1344869/+
Yes, I confirm that the issue is resolved with 3.13.4.2-0ubuntu1.
Not relevant to this bug, but I do notice that the scan speed is quit
slow using simple-scan. Comparing with xsane at the same resolution
(300dpi):
- xsane: 23 seconds
- simple-scan: 2 minutes.
Thanks very much for the fast turn-a
** Summary changed:
- lock scren leaks keystrokes to window "behind" greeter
+ lock screen leaks keystrokes to window "behind" greeter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1345505
Title:
l
Public bug reported:
$ sudo apt-get --purge --reinstall install ttf-mscorefonts-installer
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 0 non mis
à
** Changed in: upstart (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324096
Title:
dbus call needed to set multiple environment variables in a si
I've found a way to trigger this without needing to suspend (which
hopefully will make it easier to debug :-)...
1) Open a terminal.
2) Run: "sleep 5 && gnome-terminal --maximize"
3) Quickly (before 5 seconds has elapsed), press "CTRL+l" to lock the screen.
4) Don't touch keyboard or mouse for abo
** Changed in: upstart
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
ma
Public bug reported:
$ cat >>foo.c<
#include
int
main (int argc, char *argv[])
{
printf ("hello world\n");
exit (EXIT_SUCCESS);
}
EOT
$ gcc -ggdb -O0 foo.c
$ ./a.out
hello world
$ gdb ./a.out
GNU gdb (Ubuntu 7.7.91.20140723-0ubuntu1) 7.7.91.20140723-cvs
Copyright (C) 2014 Free Software F
tatus: New => Confirmed
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New =>
ureadahead itself hasn't changed in any significant way for a long time
now, so this is looking like a possible kernel issue.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Problem is seen on i386 and amd64, but NOT on armhf (panda ARMv7).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085766
Title:
/var/log/upstart/ureadahead.log contains garbage
To manage notificati
I tried this using ...
linux-headers-3.8.0-999_3.8.0-999.201301110405_all.deb
linux-headers-3.8.0-999-generic_3.8.0-999.201301110405_i386.deb
linux-image-3.8.0-999-generic_3.8.0-999.201301110405_i386.deb
linux-image-extra-3.8.0-999-generic_3.8.0-999.201301110405_i386.deb
... however, removing the
Looking more closely at my /var/log/upstart/ureadahead.log, this looks
like memory corruption:
ureadahead:^P^P_í,<8b><97>¿add): Ignored relative path
ureadahead:^P^P_í,<8b><97>¿irqd: Ignored relative path
ureadahead:^P^P_í,<8b><97>¿er/0: Ignored relative path
ureadahead:^P^P_í,<8b><97>¿er/0: Ignor
Investigation shows that this problem is only triggered by '/forcefsck':
the actual problem results from jobs that satisfy both conditions below:
- *end* before /var/log/upstart/ becomes writeable.
- has spawned one or more processes that continue to run *after* the job has
finished and after /va
Status: Fix Committed => In Progress
** Changed in: upstart
Importance: Undecided => High
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this
Public bug reported:
I am trying to report a bug against the Ubuntu kernel. On my system...
$ uname -a
Linux azul 3.8.0-0-generic #3-Ubuntu SMP Fri Jan 11 17:26:08 UTC 2013 i686 i686
i686 GNU/Linux
$ cat /proc/version
Linux version 3.8.0-0-generic (buildd@lamiak) (gcc version 4.7.2 (Ubuntu/Linar
Public bug reported:
Noticed when my USB serial device failed to appear, but seems unrelated to that.
__
[ 131.963067] EXT4-fs (mmcblk0): mounted filesystem with ordered data mode.
Opts: (null)
[ 132.527081] EXT2-fs (sdb1): warning: mounting unchecked fs, running e2fsck
is recommended
This also affects apport-collect. Running:
$ apport-collect -p linux-image-3.8.0-0-generic 1100202
... reports the erroneous mainline kernel message and then hangs hard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Due to apport bug 1100198, I am unable to run apport-collect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100202
Title:
IPI backtrace in dmesg
To manage notifications about this bug go to:
https
Branch lp:~jamesodhunt/ubuntu/precise/upstart/sru-bug-980917 updated and
new package created and uploaded (upstart_1.5-0ubuntu7.2) to correct
build failure seen on ARM.
Note that the changes are purely test code changes: the code for Upstart
itself has not changed in this new version.
--
You rec
901 - 1000 of 1868 matches
Mail list logo
