Did we conclude this is more of a misconfiguration rather than a
thermald issue pe se, if so, I may remove thermald from the bug and
rename it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
This seems to be plausible as thermald would not start if dbus would not
start (which is the bug here (or probably a configuration issue)).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
It sounds like you may have modified files below /etc/initramfs-tools/
and/or /usr/share/initramfs-tools/, or created additional scripts that
are somehow modifying the boot path.
I have os-prober installed but removing it and updating initramfs and
grub doesn't solve the issue.
I would try
I have now made a look which files in /etc/initramfs-tools and
/usr/share/initramfs-tools belongs to which package. Here is the result:
sworddragon@ubuntu:~$ (find /etc/initramfs-tools -type f; find
/usr/share/initramfs-tools -type f) | xargs dpkg -S
initramfs-tools:
With your cursor on Ubuntu, with Linux 3.16.0-18-generic (recovery
mode), press 'e' and you should see 'recovery' specified somewhere on
the line that starts 'linux'.
I have made a look on my main computer and my laptop and I'm seeing on
both systems there single.
To test if recovery mode
It sounds like you may have modified files below /etc/initramfs-tools/
and/or /usr/share/initramfs-tools/, or created additional scripts that
are somehow modifying the boot path. Further, I think you need to
understand why single is being specified on the boot command-line as
that is non-standard.
apport information
** Tags added: apport-collected utopic
** Description changed:
- I'm using Ubuntu 14.10 dev with thermald 1.2-1 and if the system is
- started in the recovery mode it is not possible to unmount /dev/sda1
- because thermald is running. Interestingly lsof hasn't even showed
UPSTART_EVENTS=runlevel
UPSTART_INSTANCE=
UPSTART_JOB=rcS
This is the cause of your problem - you are not actually in recovery mode. What
is your /proc/cmdline? Have you modified /etc/default/grub or any of the
initramfs configuration?
--
You received this bug notification because you are a
What is your /proc/cmdline?
BOOT_IMAGE=/boot/vmlinuz-3.16.0-18-generic root=UUID=af27feae-4c9e-4b5f-
a1e1-900c0e71c5cb ro single nomodeset
Have you modified /etc/default/grub or any of the initramfs configuration?
I think not that I have changed something of initramfs but there are
some
On booting I'm holding shift to open the GRUB menu and selecting
Erweiterte Optionen für Ubuntu (translated probably Advanced options
for Ubuntu) and then Ubuntu, with Linux 3.16.0-18-generic (recovery
mode). It seems something is preventing here that the reconvery mode is
being entered.
--
You
@James, any idea why dbus is starting?
** Changed in: upstart (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1348784
Title:
I too am unable to recreate this problem - dbus should certainly not be
running in recovery mode because dbus is 'start on local-filesystems',
but that event will not have been emitted since mountall is not run in
recovery mode.
Can you confirm you are entering recovery mode from the grub menu
BTW, I'm going to slip the run level changes into thermald to address
another thermald bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1348784
Title:
thermald
13 matches
Mail list logo
