** Changed in: canonical-devices-system-image
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/1623853
Title:
Device appears to be off after updating to
** Changed in: canonical-devices-system-image
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/1623853
Title:
Device appears to be off after updating to
This bug was fixed in the package ubuntu-touch-session -
0.108+16.10.20161014-0ubuntu1
---
ubuntu-touch-session (0.108+16.10.20161014-0ubuntu1) yakkety; urgency=medium
[ Alexandros Frantzis ]
* Keep the display on during boot (LP: #1623853) (LP: #1623853)
-- Łukasz Zemczak
This bug was fixed in the package repowerd -
2016.10+16.10.20161007-0ubuntu1
---
repowerd (2016.10+16.10.20161007-0ubuntu1) yakkety; urgency=medium
* New 2016.10 release
- Fix typo in brightness config value (LP: #1618391)
- Update repowerd-cli help text
- Handle
The repowerd part of the fix has landed in repowerd 2016.10. Now waiting
for the upstart script addition to land:
https://code.launchpad.net/~afrantzis/ubuntu-touch-session/keep-display-
on-during-boot
** Changed in: repowerd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in:
** Changed in: canonical-devices-system-image
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/1623853
Title:
Device appears to be off after updating to
** Merge proposal linked:
https://code.launchpad.net/~repowerd-team/repowerd/+git/repowerd/+merge/307941
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623853
Title:
Device appears to be off
** Changed in: ubuntu-touch-session (Ubuntu)
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/1623853
Title:
Device appears to be off after updating to 15Sept2016's
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
** Changed in: repowerd (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~afrantzis/ubuntu-touch-session/keep-display-on-
during-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623853
Title:
Device appears to be off after updating to
** Also affects: ubuntu-touch-session (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-touch-session (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-touch-session (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
You
I tested it and it is much better although obviously still lacks any
indication things are happening. Along with a note for people to expect
it to take some time on the boot screen should be ok until we can
address it further.
--
You received this bug notification because you are a member of
Note that the fix above doesn't implement my earlier suggestion to start
USC before apparmor finishes reprofiling. Unfortunately the way the job
dependencies are structured makes this change very difficult.
I would suggest that we clearly and prominently mention in our release
notes (and also
** Attachment added: "Updated repowerd.conf file"
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1623853/+attachment/4755807/+files/repowerd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "New keep-display-on-during-boot.conf file"
https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1623853/+attachment/4755812/+files/keep-display-on-during-boot.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have attached two upstart .conf files implementing a fix that keeps
the display on until the phone has booted. In particular it acquires a
display-on lock when repowerd has started and releases it when lightdm
has started. After the display-on lock is released the display stays on
for 30s-1m
> You can trigger the compilation by
> sudo rm /var/cache/apparmor/*
> sudo rm /var/lib/apparmor/profiles/*
Thanks Pat. I also found another way to do the same, tricking the
apparmor boot script into thinking this is the first it runs:
sudo rm /var/lib/apparmor/profiles/.apparmor.md5sums
--
You can trigger the compilation by
sudo rm /var/cache/apparmor/*
sudo rm /var/lib/apparmor/profiles/*
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623853
Title:
Device appears to be off after
> Can repowerd simply hold a lock until the screen dbus service is
connected?
(I am assuming you are referring to a display-on lock, which also
disallows suspends).
repowerd could hold a lock, but, IMO:
1. repowerd is the wrong place to put this logic. repowerd shouldn't
have to know, even
** Changed in: canonical-devices-system-image
Assignee: Pat McGowan (pat-mcgowan) => Stephen M. Webb (bregma)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623853
Title:
Device appears to be
@alf per comment #31
we need to regenerate the compiled profiles for installed apps when new
rules are provided. This needs to be done before any apps can be
launched, so unity8 cannot be started. We could consider starting usc
but unsure the dependencies there.
Can repowerd simply hold a lock
No need to annoy you with the same operatins and events list.
Take as my reference the experience of Marcin.
Sane events sequence, same fear, same good end.
Thanks for further investigating and to never repeat it again...Ok?!?!.
;-)
Thanks and
Regards.
D
--
You received this bug notification
Done, @pat-mcgowan.
URL --> https://bugs.launchpad.net/canonical-devices-system-
image/+bug/1626672
I'll have a look to the top information.
Thanks for your attention.
Regards.
David.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
> can you compare what powerd used to do with what repowerd is doing now
in this scenario
Based on jibel's theory from comment #23:
With powerd the timeout logic was in USC, so if USC hasn't started (e.g.
because of apparmor recompilation in this case?) the device won't
suspend.
With repowerd
@alf can you compare what powerd used to do with what repowerd is doing
now in this scenario
** Changed in: repowerd (Ubuntu)
Importance: Undecided => High
** Changed in: repowerd (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
You received this bug notification
@Davilinux can you open a new bug for that issue and if it persists run
top to see what if anything is consuming the cpu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623853
Title:
Device appears
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: repowerd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623853
Title:
Hello.
I have a BQ E4.5
Yesterday updated my phone with the last OTA-13 and, unfortunately, with
the same results after flashing... that means I had to plug the power
cord to boot the device on, because it seems to be bricked.
The worst: The battery is consuming a lot of power.
Usually, I have
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Pat McGowan (pat-mcgowan)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: repowerd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
30 matches
Mail list logo
