pitti
this sru has hit Kubuntu in a strange way -> bug #1509334 (30 seconds
delay for final desktop)
JUST be4 the final release :-(
The fix for Wily is stuck now in the "proposed-queue", actually thinking
this bitesize-bugfix (there) should enter "wily-updates"
Could you take a look at it?
Hello,
Flames_in_Paradise [2015-11-06 15:49 -]:
> this sru has hit Kubuntu in a strange way -> bug #1509334 (30 seconds
> delay for final desktop)
>
> JUST be4 the final release :-(
>
> The fix for Wily is stuck now in the "proposed-queue", actually thinking
> this bitesize-bugfix (there)
Even if we would change our kernel package to always include bluetooth,
that still would make the package fail for custom/third-party kernels,
so I'd say this is neither required nor sufficient. Let's fix the bluez
packaging instead.
** Changed in: linux (Ubuntu Wily)
Status: New => Won't
> There is nothing we can do from bluez side.
Perhaps not from the daemon itself, but the packaging certainly needs to
be fixed. It could be that the .service file grows some Condition*= to
not start if we already know that it won't work; or the .postinst
shouldn't fail when the service fails (e.
We could just bind this to the condition if /sys/class/bluetooth is
available or not. So a
...
ConditionPathIsDirectory=/sys/class/bluetooth
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
> ConditionPathIsDirectory=/sys/class/bluetooth
Sounds perfect!
** Changed in: bluez (Ubuntu Wily)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Wily fix uploaded (might end up as an SRU, though). I also sent the
patch upstream, will add a link once it hits the upstream ML archives.
** Changed in: bluez (Ubuntu Wily)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch
Forwarded upstream:
http://article.gmane.org/gmane.linux.bluez.kernel/65182
** Changed in: bluez (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: bluez (Ubuntu Wily)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are
** Branch linked: lp:ubuntu/wily-proposed/bluez
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1506774
Title:
package bluez 5.35-0ubuntu1 failed to install/upgrade:
Great!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1506774
Title:
package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess
installed post-installation script
This bug was fixed in the package bluez - 5.35-0ubuntu2
---
bluez (5.35-0ubuntu2) wily; urgency=medium
* Add 0001-systemd-Check-if-bluetooth-is-supported-in-the-kerne.patch:
bluetooth.service: Check if bluetooth is supported in the kernel, to avoid
failing package
Trivially reproduces on e. g. the cloud images, but for completeness:
$ sudo systemctl status -l bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Tue
There is nothing we can do from bluez side. If the kernel interface we
need to do *any* work is not available we can't do anything else but
fail. The "bluetooth" module needs to be loaded or the kernel compiled
with CONFIG_BT=y rather than CONFIG_BT=m.
Is there any reason not to compile bluetooth
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1506774
Title:
package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess
14 matches
Mail list logo
