Whilst we investigate this issue, please disable logging by adding
"--no-log" to the kernel command-line. It is also possible to stop the
log from being flushed by disabling the "flush-early-job-log" Upstart
job (/etc/init/flush-early-job-log.conf), for example like this:
$ echo manual | sudo tee
Public bug reported:
$ sudo apt-get update && sudo apt-get -y dist-upgrade
:
:
Unpacking replacement libglib2.0-0 ...
Preparing to replace udev 175-0ubuntu4 (using .../udev_175-0ubuntu5_i386.deb)
...
Adding 'diversion of /sbin/udevadm to /sbin/udevadm.upgrade by fake-udev'
dpkg: unrecover
OK, sounds like you're in unchartered territory then. Try adding
"init=/bin/sh" to the grub command line and booting, then:
1) See what "ulimit -n" shows.
If it is < 1024, that might be your problem so try setting 'nofile' manually
to atleast 1024 and then manually exec-ing upstart:
ulimi
*** This bug is a duplicate of bug 935585 ***
https://bugs.launchpad.net/bugs/935585
** This bug has been marked a duplicate of bug 935585
[kernel panic] init: log.c:786: Assertion failed in log_clear_unflushed:
log->remote_closed
--
You received this bug notification because you are a m
@Lukas: can you confirm the perms are correct on /dev/ptmx? Also, see
comment #3 on bug 936293.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936667
Title:
init(4): no available ptys stops boot
To
Can those affected by this bug confirm they have a /var/log/upstart/
directory? Also, attaching the output of the following command would be
useful:
/sbin/initctl show-config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
@Daniele: add "init=/bin/sh" to your grub command line and boot. This
will drop you to a shell. You can then inspect permissions with "ls -l
/dev/ptmx".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/93
Sounds like this might be a "chicken-and-egg" issue where Upstart wants
a pty, but pty support isn't yet available (/dev/pts not mounted) as the
mountall job hasn't yet run. This being a side-effect of having no
initramfs since /dev/pts is normally mounted from there.
--
You received this bug not
@Michael: please can you confirm you too are using a custom kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936667
Title:
init(4): no available ptys stops boot
To manage notifications about t
** 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/935585
Title:
[kernel panic] init: log.c:786: Assertion failed in
log_clear_unflushed
Please would those affected by this bug test the new upstart build
version '1.4-0ubuntu9~bug935585' in the PPA below and provide feedback:
https://launchpad.net/~jamesodhunt/+archive/bug-935585/
Since we have still not managed to recreate this problem directly, it
would also be helpful to know wh
** Summary changed:
- init(4): no available ptys stops boot
+ Upstart early job logging causes boot failure for systems with no initramfs
(error is "No available ptys")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
*** This bug is a duplicate of bug 936667 ***
https://bugs.launchpad.net/bugs/936667
** This bug has been marked a duplicate of bug 936667
init(4): no available ptys stops boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
@Peter: Thank you for the information.
We are still unsure exactly what scenario is causing this assertion
failure so would encourage all those experiencing this issue to try the
Upstart version in comment #11. Feedback on this will provide us with
valuable information which will help us to resolv
Public bug reported:
Most of the time, apport gives no indication of _which_ application
crashed until you get redirected to the bugs.lauchpad.net page.
Currently, it shows on the title bar simply "Crash report" (no further
detail) and the window contents shows:
Sorry, Ubuntu 12.04 has experi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/938762
Title:
apport does not specify the application that crashed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sour
Public bug reported:
Attempting to start chromium-browser results in a core dump unless stdin
is /dev/null:
$ chromium-browser
Segmentation fault (core dumped)
$ chromium-browser < /dev/null # XXX: here, chromium works as expected.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: chromi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941812
Title:
chromium-browser core dumps unless stdin is /dev/null
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
One of the options in the friendly-recovery menu is "Check all file
systems" (aka fsck). However, selecting this option runs fsck via
mountall which produces no output. This could give users the impression
that their system has actually frozen (this feeling is compounded by th
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941813
Title:
allow verbose fsck via friendly-recovery
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-
>From the backtraces, this appears to be a kernel/hardware issue.
** Package changed: upstart (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941210
Title:
Ubuntu fails to
*** This bug is a duplicate of bug 935296 ***
https://bugs.launchpad.net/bugs/935296
** This bug has been marked a duplicate of bug 935296
java-atk-wrapper prevents java applications from starting
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
Whilst investigating bug 937611, I enabled the on-screen keyboard.
However, I subsequently switched if off via "System Settings" ->
"Universal Access" -> Typing tab -> "Typing Assistant".
As expected, the keyboard no longer displays on the desktop but when the
screen locks au
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942530
Title:
on-screen keyboard always displays once enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gn
*** This bug is a duplicate of bug 829980 ***
https://bugs.launchpad.net/bugs/829980
** This bug has been marked a duplicate of bug 829980
upstart-udev-bridge eats 100% cpu calling dbus_message_iter_append_basic()
--
You received this bug notification because you are a member of Ubuntu
Bu
This sounds like a bug with slim - try logging in on tty2 and looking at
what file descriptors it has open:
ls -al /proc/$(pgrep slim)/fd/
If it has /dev/tty1 open, that's the problem. A better search would be
to run the following as root which will tell you the pid of the process
that has /dev/t
I tried switching back to unity 3D this morning and haven't seen the
problem whilst using vim, gvim, urxvt and Emacs (all with "Ubuntu Mono"
font) extensively. I am running an up-to-date 12.04 system.
Package details:
$ dpkg -l|egrep "^ii
*(nvidia|\https://bugs.launchpad.net/bugs/861268
Title:
Public bug reported:
Plugging my Logitech H530 USB headset in shows the following message in
syslog:
Feb 29 14:12:57 azul kernel: [22917.814089] usb 2-1.2: new full-speed USB
device number 10 using ehci_hcd
Feb 29 14:12:57 azul mtp-probe: checking bus 2, device 10:
"/sys/devices/pci:00/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943284
Title:
Logitech H530 USB headset not usable due to MTP error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
I'm seeing what looks like the same problem on a fully updated 12.04
Lenovo T410 system with nvidia graphics. Note however, that the I see
this screen corruption:
- briefly on every boot after the Ubuntu plymouth splash has disappeared, but
just before the lightdm greeter appears.
- on every boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943891
Title:
do-release-upgrade fails with confusing (gnu screen) message "Press x
to destroy or r to resurrect window"
To manage notifications about
Public bug reported:
If do-release-update finds gnu screen installed, it will use it.
However, if do-release-upgrade using screen fails, the screen shows:
== Command terminated with exit status 1 () ==
If you press any key, we then get the truly bizarre message:
Press x to destroy or r
This message was seen on a lucid system btw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943891
Title:
do-release-upgrade fails with confusing (gnu screen) message "Press x
to destroy or r to re
This limitation can be worked around like this:
$ bzr merge
$ bzr diff --using=
$ bzr revert
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943922
Title:
'bzr merge --preview' does not allow '--usi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943922
Title:
'bzr merge --preview' does not allow '--using' option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
'bzr merge --preview' shows a diff of the merge, but does not actually
perform the merge.
However, that command does not provide a '--using' option limiting you
to a plain text dump. This is fine for small diffs, but for anything
sizeable, it would be extremely helpful (and c
This xset problem is caused by update-manager calling /usr/bin/xdg-
screensaver which in turns calls xset.
DistUpgrade/DistUpgradeQuirks.py in update-manager invokes 'xdg-
screensaver reset' repeatedly and xdg-screensaver makes a number of
calls to xprop and xset. An example of a problematic call
xdg-screensaver is being called (up to twice a minute) I think to stop
any possibility of a screensaver starting. Each time it is called, it
checks DPMS.
A better fix than I suggested in #11 would be for update-manager simply
not to call xdg-screensaver if DISPLAY is not set.
--
You received thi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959308
Title:
kvm does not generate a system uuid by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qem
Public bug reported:
Booting ubuntu_precise-desktop-i386.iso under kvm results in
/var/log/upstart/whoopsie.log containing:
Could not open the product uuid file.
This is because by default kvm does not create a uuid by default. As
such, there is no /sys/class/dmi/id/product_uuid file which who
Public bug reported:
Mar 19 17:26:39 ubuntu activate-dmraid: No Serial ATA RAID disks detected
Mar 19 17:26:39 ubuntu kernel: [ 434.465062] JFS: nTxBlock = 3965, nTxLock =
31724
Mar 19 17:26:39 ubuntu kernel: [ 434.532189] SGI XFS with ACLs, security
attributes, realtime, large block/inode num
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959620
Title:
ext4 backtrace observed with desktop install CD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/li
Hi Joseph,
Please see the attached 2 crash files and syslog (containing the same
stack trace), taken on a subsequent boot, again under kvm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959620
Title:
** Attachment added: "linux-image-3.2.0-19-generic-pae.130093.crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959620/+attachment/2900243/+files/linux-image-3.2.0-19-generic-pae.130093.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959620/+attachment/2900244/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959620
Title:
ext4 backt
** Attachment added: "linux-image-3.2.0-19-generic-pae.129251.crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/959620/+attachment/2900242/+files/linux-image-3.2.0-19-generic-pae.129251.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
@Dominik: do you remember if you ticked the "download updates while
installing"?
I suspect that if you do select "download updates while installing" and
get unlucky, 'update-apt-cache' will race with copy_all():
1) update-apt-cache created /target/var/cache/apt/archives/.
2) copy_all() (re)moved
Same problem with "des":
mbrola: Warning: d-e- unkown, replaced with _-_
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948884
Title:
mbrola is unable to pronounce the French word "les"
To manage n
@Seth: yes, the installer kept going. I only noticed the issue looking
in syslog for something else :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959620
Title:
ext4 backtrace observed with deskt
** Changed in: ubiquity (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/946663
Title:
Installer stuck at "Removing con
** Branch linked: lp:~jamesodhunt/ubiquity/bug-944191
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944191
Title:
Installation program crashed while typing username
To manage notifications about th
Public bug reported:
Mar 20 15:47:50 azul postfix/smtp[10429]: fatal: open database
/etc/postfix/generic.db: No such file or directory
Mar 20 15:47:51 azul postfix/master[3041]: warning: process
/usr/lib/postfix/smtp pid 10429 exit status 1
Mar 20 15:47:51 azul postfix/master[3041]: warning: /us
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/960335
Title:
kernel stacktrace triggered by udisks(?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bu
Public bug reported:
Mar 20 15:49:04 azul kernel: [ 1980.131204] whoopsie[2264]: segfault at 0 ip
0804c66a sp bfced614 error 4 in whoopsie[8048000+a000]
Mar 20 15:49:04 azul kernel: [ 1980.247962] init: whoopsie main process (2264)
killed by SEGV signal
Mar 20 15:49:04 azul kernel: [ 1980.248010
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/960326
Title:
whoopsie-daisy SIGSEGV but no crash file generated
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
The udisks crash I saw was bug 648757.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/960335
Title:
kernel stacktrace triggered by udisks(?)
To manage notifications about this bug go to:
https://bug
... but looking at syslog, we have:
umount: /mnt/tmpmount: device is busy.
This does indeed appear to be caused by finish.d/clear_partitions
failing for some reason.
If you can still reproduce this issue, please can you:
- wait for the hang to occur
- click the top-left "home" button
- type "
I have run a number of partition scenarios based on the inforomation
from Marcelo and Anthony, but so far have been unable to reproduce this
issue using todays ubuntu_precise-desktop-i386.iso image.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
What would also be very useful is a tar file of /var/lib/partman/:
tar cvfz /tmp/partman.tgz /var/lib/partman/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946663
Title:
Installer stuck at "Removi
@Marcelo: thank you. The architecture shouldn't make a difference in
this case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946663
Title:
Installer stuck at "Removing conflicting operating system
** Changed in: ubiquity (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/684309
Title:
Ubiquity Advanced Partitioning - Convert
I'm seeing this with ubuntu_precise-desktop-i386.iso from 20th March.
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubiquity (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/684309
Title:
Ubiquity Advanced Partitioning - Converting/Using ext4 to ext2 without
Does your system fail to boot or is it that you are simply unable to
login?
If it is failing to boot, please remove 'quiet' and 'splash' from your
kernel command-line and either attach a log of the console output, or
just attach a picture showing crash details.
--
You received this bug notificat
14:41 jodh: unfortunately I'm getting a black screen...
14:41 jodh: also removing splash and quiet I'm getting a fast log,
then the screen gets blank
14:43 (and nothing in /var/crash this time)
14:55 jodh: I'm using the custom cmd line for linux radeon.audio=1
14:55 jodh: rem
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Information type changed from Private to Public
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Assignee: (unassigned) => James Hunt (james
** 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/1197225
Title:
upstart-file-bridge assert failure: string.c:396: Assertion failed in
Public bug reported:
My machine was responding sluggishly. Top showed PID 1 consuming almost
70% CPU. The culprit seems to be the startpar-bridge job which had 2
running instances:
$ sudo initctl list|grep startpar
get_started is a job that also specifes 'start on started', so upstart
was chasing both jobs constantly: only 1 job can reasonably specify such
an unspecific start condition.
** Changed in: sysvinit (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you a
** Changed in: upstart
Status: Fix Committed => 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/1197225
Title:
upstart-file-bridge assert failure: string.c:396: Assertion failed in
** Changed in: upstart
Status: In Progress => Fix Released
** Changed in: upstart (Ubuntu)
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/1188642
Title:
** Summary changed:
- Update to 1.9.1 causes system hang at configure
+ Update to 1.8-0ubuntu1.2 in raring causes system hang at configure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1198649
Title:
** 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/1197529
Title:
upstart in saucy needs a build-depends
@Sworddragon - Thanks for reporting. Is this on a single system? Do you
just have a single instance of the /proc/self/fd/9 process?
Please can you run 'apport-collect 1197789' on an affected system and
follow the prompts to help debug this.
--
You received this bug notification because you are a
Approximately how many running jobs do you have after you've created 40k
containers? If you stop all those network interfaces, is the memory
reclaimed?
Please provide further details so we can investigate more fully.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is by design:
- http://upstart.ubuntu.com/cookbook/#symbolic-links-don-t-work-in-etc-init
- init(5) under RESTRICTIONS.
** Changed in: upstart (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Also affects: upstart
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/1201865
Title:
upstart on nexus4 is frequently writing :sys:power_supply-device-
This is rather an interesting one: we first added support for running
upstart as a non-priv user, we forced it to run in debug mode (since
debugging was the main reason for running init as a non-priv user). As
such, when you run "init --user", you are automatically in debug mode
('initctl log-prior
** 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/1201865
Title:
upstart on nexus4 is frequently writing :sys:power_sup
** Changed in: upstart
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/1201865
Title:
upstart on nexus4 is frequently writing :sys:power_supply-device-
changed ev
Public bug reported:
Latest update to lightdm broke boot for me as ligthdm crashes on
startup.
dmesg shows:
[ 38.108529] lightdm[1621]: segfault at 3f7 ip b74ada42 sp bff82ccc error 4
in libglib-2.0.so.0.3703.0[b746b000+102000]
[ 39.364988] init: lightdm main process (1621) killed by SEGV s
** Changed in: lightdm (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/1203660
Title:
lightdm crashed with SIGSEGV in g_list_last()
To manage notifications abou
Public bug reported:
Patch attached.
NB: Also noticed that the bzr branch is showing as OUT-OF-DATE.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: Fix Committed
** Attachment added: "apport-upstart-bug.diff"
https://bugs.launchpad.net/bugs/1203744/+attachment/3745
Manually downloading the old revision and rebooting does resolve the
problem for me:
$ wget
http://gb.archive.ubuntu.com/ubuntu/pool/main/l/lightdm/lightdm_1.7.4-0ubuntu1_i386.deb
$ wget
http://gb.archive.ubuntu.com/ubuntu/pool/main/l/lightdm/liblightdm-gobject-1-0_1.7.4-0ubuntu1_i386.deb
$ sudo
Public bug reported:
The 3.10.0-4-generic update broke a few things for me:
1) IBM thinkpad acpi fan-control no longer works:
$ sudo modprobe thinkpad_acpi fan_control=1
ERROR: could not insert 'thinkpad_acpi': Unknown symbol in module, or unknown
parameter (see dmesg)
$ dmesg|grep -i fan
Public bug reported:
The latest nvidia update breaks X on my system:
[ 108.858] (II) Open ACPI successful (/var/run/acpid.socket)
[ 108.858] (II) APM registered successfully
[ 108.870] (EE) NVIDIA(GPU-0): EVO Push buffer channel allocation failed
[ 108.870] (EE) *** Aborting ***
[ 108.
Looks like this issue may in fact be bug 1203211.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203751
Title:
ibm fan control broken and iwlwifi no longer accepts 11n_disable
option
To manage no
The default behaviour of the boot with this bug is that the greeter
never appears; you just see the Ubuntu pulsing plymouth theme.
However, the system has booted so you can switch to a text console
(control+alt+f1 for example), login and take remedial action as shown in
#6.
--
You received this
@Sworddragon - Thanks for reporting. This is in fact an innocuous
message: the upstart-dbus-bridge should not run at the system level. The
next update will remove the .conf file to make this message go away.
@r0tter77: this problem has nothing to do with the behaviour you
describe. Please raise a
xnox - could you take a look at establishing why upstart.maintscript
isn't doing what it should?
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => Dmitrijs Ledkovs (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
This looks like a recurrence of bug 525958 however, I have this issue on
cold boot - no suspend/resume involved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203754
Title:
nvidia 304.88-0ubuntu6 b
** Changed in: upstart (Ubuntu)
Status: Triaged => 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/1163103
Title:
upstart file bridge: "unable to write pid file"
To manage notific
Public bug reported:
Happened soon after a cold boot. I wonder if there is a way to detect
these sorts of bugs from userland (some sort of dmesg/syslog sniffer)
and prompt the user to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.30
ProcVersio
Relevant chunk of dmesg attached.
** Attachment added: "dmesg-bug.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1180270/+attachment/3677120/+files/dmesg-bug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Public bug reported:
Problem affects both 1.9 and 1.9.1.
** Affects: upstart
Importance: High
Assignee: James Hunt (jamesodhunt)
Status: New
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart
Importance: Undecided => H
** 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/1199778
Title:
upstart crashes if re-exec'ed with active chroot sessions
To manage not
Hi Brian,
If you use a glob pattern in FILE, the way to determine the name of the
matching file in the job is via the MATCH variable:
start on file FILE=/var/crash/*.crash EVENT=create
exec echo "matching file was $MATCH"
** Changed in: upstart
Status: New => Invalid
** Changed in: upst
Forgot to mention that this is documented in file-event(7).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1199499
Title:
upstart file bridge sets FILE to glob pattern instead of specific file
To ma
This problem affects those systems hosting chroots but also affects
those with sbuild/pbuilder installed. The failure process is as follows:
- user builds a package in the sbuild/pbuilder env.
- upstart gets updated within the sbuild/pbuilder chroot as part of the package
build.
- as part of the
Correction to the process above: a session only gets created when a job
is queried so a maintainer script is probably invoking
status/start/stop/restart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
1501 - 1600 of 1868 matches
Mail list logo
