** Changed in: mir
Milestone: 0.16.0 => 0.17.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS or call notification
To manage notificatio
Ok, so following up.
bug 1495871 - u-a-l leaking fd's is truly critical and is what people are
experiencing in terms of a completely frozen ui. In the case of this bug,
people are able to blank/unblank the screen with their power button.
we are going to leave this bug open to see if there is a 2
and output from 'ls -lv /proc/$(pidof unity8)/fd'
** Attachment added: "list_unity8fds.log"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4464959/+files/list_unity8fds.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
ok, verified that u-s-c is still ok, power button works and screen blanks...but
ui is still completely frozen.
attaching sudo lsof just in case
tried to look at backtrace of unity8, but it seems corrupted
** Attachment added: "lsof_root_smsbug.log"
https://bugs.launchpad.net/canonical-device
Another way to leak fds is just opening and closing an app. It leaks an
fd of type 'anon_inode:[eventfd]' per app connection.
Still don't have enough info to verify (or disprove) that the fd leaks
are the cause of the original bug. The leak seems to be unity8 specific
and in previous reports ther
I reproduce the issue by following the "fd leak" lead with the following
test case:
1. Open 2 apps
2. Switch from the app scope to app1
3. Switch from app1 to the app scope
4. Switch from the app scope to app2
5 lock the screen (optional but it leaks even more fd)
At the same time monitor the nu
> i succeeded in getting my device stuck in a frozen state. it seems
alive, i can interact with the shell
How can you interact with the shell? Does it respond to input? Can you
turn the screen on/off with the power button?
> so i grabbed a dump from lsof as well.
> here's the list of open files d
ok, i was able to attach gdb to usc, here's the bt
** Attachment added: "usc-attached-gdb.log"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4464361/+files/usc-attached-gdb.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
here's the list of open files dump
** Attachment added: "lsof_output.log"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4464354/+files/lsof_output.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
i succeeded in getting my device stuck in a frozen state. it seems alive, i can
interact with the shell, top shows processes running and updating.
trouble is, gdb t a a bt yeilds no output. bt and bt-full result in "No stack."
I did check the unity8.log and noticed the log is fairly normal, until
Experienced this bug today on bq 4.5 with OTA-6. I got a text message.
The screen turned on, envelope went green and the led light started to
blink green. I was driving, so I didn't touch the phone and was just
waiting for the screen to dim. I've noticed the screen wss staying on
longer than it sho
note about the comment above - be careful, if you do not wish to have to
reflash your phone and lose user data, do not modify.
Also, the mir in rc-proposed is currently 15.1, and stable is 14.1 so loading
these symbols from the zip file won't help, you would need to get the matching
symbols. La
these are the current debug symbols for u-s-c and mir, for rc-proposed images
circa sept 14
adding this zip file to make it easy, b/c at the moment the phone images rely
on the stable-phone-overlay ppa so you cannot get these dbg symbols to
automagically install
for libc and libstdc++ just inst
I'm not sure if this is related or not, but the symptoms seem too
similar to not comment
With the blabble game in the store if you play the game (eg, start it,
then start finding words as fast as you can by tap, dragging and
lifting), after a while the UI gets stuck where several tiles are
hig
ran combinations of phone call, sms and swiping throughout the weekend,
no issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS or call noti
** Changed in: mir
Milestone: None => 0.16.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS or call notification
To manage notifications
altered script to include sms, phone call, sms in short order, ran over
night 8+hrs no issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS o
been running incoming text simulation for over 4 hrs, running at ~1 min
interval to allow for inactivity timer to fire after interaction & sleep
to allow for notification to disappear. no freeze yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Description changed:
RC proposed MX4 r100
This happened twice in the last two days
Receive an incoming text
Screen turns on and notification is shown
notification goes away
try to interact with the phone and nothing works
another text message is received and the notification is
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
** Changed in: mir
Importance: Undecided => Critical
** Changed in: mir
Status: New => In Progress
** Changed in: unity-system-compositor
> Note: the slide gesture doesn't always slide in the right direction, not sure
> why, but in any case you can see some effect on
screen
Increasing the first sleep in the script (sleep 2) to something longer
(e.g. sleep 3) seems to fix this, so probably it's just a matter of
trying to touch the
Note: For the slide gesture to work you need the python3-evdev package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS or call notification
** Summary changed:
- Shell not responsive after an incoming SMS
+ Shell not responsive after an incoming SMS or call notification
** Description changed:
RC proposed MX4 r100
This happened twice in the last two days
Receive an incoming text
Screen turns on and notification is shown
** Attachment added: "slide_gesture.py"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4461417/+files/slide_gesture.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I have been continuing my efforts to reproduce, but without any success
so far. I have created a script to automate the process which I am
sharing here in the hope that someone else will have more success with
it.
The script either uses simulated sms messages (powerd receives the SMS
event and te
** Attachment added: "bug_1491566.sh"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4461418/+files/bug_1491566.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
My take on the backtrace is that the set_screen_power_mode request
hangs somewhere in Mir, and since it holds the lock, it blocks both
dimmer_alarm_notification and keep_display_on_temporarily (which is a
result of user input). If my assumption is correct, we need to find why
and where in Mir we b
In the spirit of wag
in the stack I see the following in threads:
usc::MirScreen::set_screen_power_mode(MirPowerMode, PowerStateChangeReason) ()
usc::MirScreen::keep_display_on_temporarily()
usc::MirScreen::dimmer_alarm_notification()
is it possible a couple of these threads deadlock due to an u
To monitor an evdev file you have to apt-get install evemu-tools and then run
(on MX4):
$ sudo evemu-record /dev/input/event1
hint: to ensure that you're monitoring the correct event file you can check
them all with:
$ sudo evemu-describe
--
You received this bug notification because you are a
This means that while the device was unresponsive neither unity-system-
compostior nor qtmir ( in unity8 process) got any input events at all.
So this rules out at least qtmir and unity8.
I think the next step is to directly monitor the evdev files to see if
anything at all comes out of them whil
While the screen is unresponsive, nothing is logged to either log file when
touching the screen.
I do see the process mtk-tpd start using cpu in top.
A restart of lightdm returns it to the normal state
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
stack trace from u-s-c
** Attachment added: "usc_stack"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4460848/+files/usc_stack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Just got the issue again, debug logging should be enabled
** Attachment added: "unity8.log"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4460790/+files/unity8.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Attachment added: "unity-system-compositor.log"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+attachment/4460791/+files/unity-system-compositor.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
@a.balmashov full disclosure, anytime you make your phone writable and helping
with stuff like this, you might lose some of your data or need to reflash.
_only_ if you are ok with that should you attempt. if you are, then you can
turn on developer mode in system settings (under "about this phon
Wanted to apply patches from #12 and #13, but files are read-only. Looks
like I miss some knowledge. Any pointers are welcome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not
** Changed in: unity8 (Ubuntu)
Status: In Progress => Incomplete
** Changed in: qtmir (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Ti
Still can't reproduce it, by the way. So help on that is still welcome
and needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS
To manage n
** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
** Changed in: qtmir (Ubuntu)
Status: Confirmed => In Progress
** Changed in: unity8 (Ubuntu)
Status:
@pat the important thing to know in unity8 is whether it still prints
entries like the following in the log when you touch the screen after it
gets into this unresponsive state:
"""
qtmir.mir.input: Received
MirTouchInputEvent((id=586,action=up,x=586.491,y=468.756))
qtmir.mir.input: Sending to Qt
Please fix this one. I use my Ubuntu phone every day and texting quite a
bit. Meaning this bug happens often.. meaning I have to restart my
phone often.
It seems from my experience that the phone gets slower and slower the
more you text until it locks up completely. After restarting everything
is
"power +sound up + sound down" buttons simultaneously. (sorry for the
noise on 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/1491566
Title:
Shell not responsive after an incoming SMS
To
Unsure if related, but if I mash the vol up/down keys on arale a bit, it
makes unity8 freeze
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS
Hi. I've just run into this issue and I am unable to reboot the phone
and it is fully charged. I do not have the phone in developer mode.
(Battery is non-removable right?). I've installed phablet-shell but what
steps should I follow?
--
You received this bug notification because you are a member
Unity8 log at the time of the problem with debug enabled
Unfortunately u-s-c logs do not get retained over boot so that one is gone
In order to debug this we should change that behavior since getting into the
phone usually requires you to open the greeter but with greeter frozen you need
to reboo
I note two crash files from the day before, pulseaudio and unity-system-
compositor-spinner, so I wonder if they prevented seeing a newer crash
saved at the time I noticed the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Unity8 log at the time of the problem with debug enabled
Unfortunately u-s-c logs do not get retained over boot so that one is gone
In order to debug this we should change that behavior since getting into the
phone usually requires you to open the greeter but with greeter frozen you need
to reboo
This time a different set of symptoms but seems related
Incoming call rings, but there is no notification to accept the call
Inputs do not work
I push power twice to turn scren off and on, then twice again, and the
notification showed up so I could answer the call
--
You received this bug notifi
I've seen this happening also after notifications of incoming Telegram
messages. My impression is that this bug happens if I press the power
button to wake up the phone immediately after the notification has
arrived. And I think it has been happening since OTA-5, not just with
the last one.
--
Yo
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS
To manage notifications about this bug go to:
https://bugs.
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS
To manage notifications about this bug go to:
https://bugs.launchpad.n
The attachment "Enabling input logging in unity-system-compositor" seems
to be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Lau
> * power button. could not even reboot the phone (or maybe have not waited
> long enough? pressed on it for about a minute), had to do reboot via shell
Power button not responding indicates a problem at the level of USC
(since the power button is handled internally by USC). A backtrace of
USC whe
** Patch added: "Enabling input logging in unity-system-compositor"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1491566/+attachment/4457272/+files/usc-wrapper_add_logging.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Patch added: "Enabling input logging in unity8"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1491566/+attachment/4457273/+files/unity8_conf_add_logging.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Steps to get input logging from unity-system-compositor and unity8:
- Apply usc-wrapper_add_logging.diff to
/usr/share/ubuntu-touch-session/usc-wrapper
- Apply unity8_conf_add_logging.diff to /usr/share/upstart/sessions/unity8.conf
- phablet@ubuntu-phablet:~$ sudo restart lightdm
Then check logs
** Tags added: hotfix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not responsive after an incoming SMS
To manage notifications about this bug go to:
https://bugs.launchpad.ne
The two suspects here now are: Qt's input mechanism getting stuck or
unity8 losing focus in unity-system-compositor.
Daniel's preparing a set of steps to enable input debugging, if you saw
this issue and willing to help, please follow them and report back with
the requested logs.
--
You received
We have not been able to reproduce this yet, I'm afraid. We're looking
into ways of debugging this "remotely", we'll be preparing a silo with
more debugging enabled for unity8 and unity-system-compositor to
pinpoint the problem.
In the mean time, if you find yourself in such a state, please come t
** Summary changed:
- Greeter and edges not responsive after an incoming SMS
+ Shell not responsive after an incoming SMS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not resp
60 matches
Mail list logo
