[Bug 1487839] Re: Crash when closing window

2015-08-25 Thread Albert Astals Cid
@Marius: I can not reproduce this issue using that same image, do you have any custom scope or something special you did to your phone you think could be causing this crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1487839] Re: Crash when closing window

2015-08-25 Thread Albert Astals Cid
@Daniel: the channel for that image is ubuntu-touch/stable/bq-aquaris.en -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1487839 Title: Crash when closing window To manage notifications about this

[Bug 1487839] Re: Crash when closing window

2015-08-25 Thread Albert Astals Cid
By doing that you basically put yourself in the we can't help you territory. don't run apt-get on the phone unless you *really* know what you're doing. Which command did you use to reflash your phone? -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1487839] Re: Crash when closing window

2015-08-25 Thread marius
I ran the following commands from the phone's terminal sudo mount -o remount,rw / sudo apt-get update sudo apt-get upgrade I had an error for the powerd package, it wouldn't install. Yesterday I reset the phone using the recovery boot and I'm having the same problem. -- You received this bug

[Bug 1487839] Re: Crash when closing window

2015-08-25 Thread marius
I know that now. I reset the phone using the factory settings option in About your phone. I just finished flashing the phone using BQ's flash utility and everything's back to normal. I'll close the bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1487839] Re: Crash when closing window

2015-08-25 Thread Albert Astals Cid
** Changed in: mir Status: New = Invalid ** Changed in: mir (Ubuntu) Status: New = Invalid ** Changed in: unity8 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1487839] Re: Crash when closing window

2015-08-24 Thread Albert Astals Cid
Can you run adb shell from a terminal in your pc with the phone connected and unlocked to connect to it? Does /var/crash/ in the phone contain crash files? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1487839] Re: Crash when closing window

2015-08-24 Thread marius
Yes, I can run adb shell. Attached the two .crash files I found in /var/crash/ ** Attachment added: crash.zip https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1487839/+attachment/4451851/+files/crash.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1487839] Re: Crash when closing window

2015-08-24 Thread Daniel van Vugt
Thanks marius. You might have to submit *.crash using the ubuntu-bug command to get them analysed properly: ubuntu-bug /path/to/each/crash/file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1487839] Re: Crash when closing window

2015-08-23 Thread marius
Steps to reproduce : - open a window in Ubuntu Touch - close it by sliding it up from the list of applications opened -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1487839 Title: Crash when

[Bug 1487839] Re: Crash when closing window

2015-08-23 Thread Daniel van Vugt
** Also affects: mir 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/1487839 Title: Crash when closing window To manage notifications about this bug go

[Bug 1487839] Re: Crash when closing window

2015-08-23 Thread Daniel van Vugt
I'm trying on a BQ Aquaris 4.5 but can't yet reproduce the problem. Although I'll need to try a few channels to find the exact OS revision mentioned too. This bug will stay open on the chance some developer can reproduce it... Although a more likely resolution will come from automated problem