Per the discussion above, this could be anywhere (qtmir, untiy8) not
necessarily in unity8 per se.
It does seem that this is specific to "unity8 on dragonboard" though.
We know that...
- mir-kiosk examples works on dragonboard
- unity8 works on arm64 m10
** Summary changed:
- arm64: history
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
dragonboard: history daemon dereferences a
** Summary changed:
- arm64 kernel panic for l2 mmu with unity8 session snap
+ arm64 kernel panic for l2 mmu with unity8 session snap (& deb as well)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
is there any update to this bug?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 mmu with unity8 session snap
Status in Snappy:
New
Status in
@ppisati - didi you need anything else?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel
@ppisati - if you have a classic deb based filesystem that is Xenial based, add
the ppa:ci-train-ppa-service/stable-phone-overlay (update/upgrade), then you
can simply apt-get install unity8-desktop-session-mir. Once that is installed,
you can toggle between unity8 & unity7 by clicking the
@ppisati sorry about that, must've had too many tabs open. Corrected the
link and shared the doc with you as well.
** Description changed:
we are running the unity8 session snap on amd64 without any problems.
- to setup and reproduce the problem follow the "on Dragonboard" section of
so to be clear, this on ubuntu-core dragonboard image from the beta
images
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 mmu with unity8
@ogra actually we do! we all lucked out, recently (like within the last
month) someone somewhere turned on gallium/freedreno drivers for our
mesa builds. So i've got the full stack, i've already run the mir-
server/client snap on it with no problems (really need to blog that)
--
You received
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1625805
Title:
arm64 kernel panic for l2 mmu with unity8
Public bug reported:
on latest rc-proposed for frieza seeing the following
1. connect bt mouse, no problem
2. turn on bt keyboard (logitech k480)
3. click sync
4. u-s-s spinner goes
expect: to see keyboard icon in list and availble to click on
actual: keyboard icon flashes for just a moment,
** Changed in: canonical-devices-system-image
Assignee: Michał Sawicz (saviq) => Stephen M. Webb (bregma)
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Milestone: None =>
** Description changed:
NOTE: kgunn suggests this bug be about 1) not 2) here
1)
I have been noticing my phone and tablet occasionally turning on without
interaction. Several times with my phone in my pocket I found it in the
emergency call UI
- I also see the tablet display turn on
>Fix 1: I think the policy for screen management is simple,
> never turn the display on if proximity is detected, it should
> not be specific to SMS or calls.
So you are saying we should have the proximity sensor on all the time ?
I disagree, first that's a power drain. Second, people will
@pat - also does the screen dim/blank at after expected expiry in the case of
#1) ?
and second, same question in the case of #2) ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552371
It seems like there is 1 bug and then 1 potential bug/feature depending
based on the original description
1) actual bug - display turning on by itself (btw, i know this happens
with Flo/N7 as well)
2) feature - bt devices are input, and we do want the screen to wake up
on keypress or mouse move.
** Changed in: canonical-pocket-desktop
Importance: Undecided => Critical
** Changed in: canonical-pocket-desktop
Assignee: (unassigned) => kevin gunn (kgunn72)
** Changed in: mir
Importance: Undecided => Critical
** Changed in: mir (Ubuntu)
Importance: Undecided =&
Public bug reported:
using mako, every no and then when having bt mouse/keyboard connected - you
will see when selecting a text box there is a repeating character (there is no
specific character, but always repeats)
it seems to be related somehow to bt devices disconnecting
the only cure is a
Public bug reported:
So I've been running ubuntu-pd on Nexus4 over a few days and began
noticing this.
1. connect bt mouse and keyboard
2. connect to external monitor
3. use device for extended period of time
sometimes the devices will appear to disconnect, as well as be forgotten.
I can't tell
I'm not sure if this needs a new bug or if i am correct in adding this
information.
But I made a quick video to show exactly the problem i'm seeing
https://www.youtube.com/watch?v=Mkql0gSq1RQ
hope that helps.
--
You received this bug notification because you are a member of Kernel
Packages,
so currently holding up promotion of mir - so, just noting here (mainly for
alan) we're disabling this test on mir 0.19.1 rel, if this bug gets fixed, we
should reinstate test if we do a 0.19.2
aiui, we've left it active on devel - so might be fixed by time we do mir0.20
and this will be moot
this is effecting mir-snap work as well
** Changed in: linux (Ubuntu)
Importance: High => Critical
** Changed in: mir
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm seeing this with an HP bt mouse and a logitech keyboard.
I'd say 30% of the time.
I was testing N7 convergence pretty heavily yesterday.
I was having to hit "forget device" then reconnect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Public bug reported:
while testing pd, had trouble connecting a previously connected mouse.
attempted the restart indicator-bluetooth trick, this didn't help.
I could see the mouse in the list, but never would connect when selecting the
"connect" button.
in the end had to "forget device" then
Public bug reported:
Every time i flash, needing to connect my bt mouse/keyboard, i open
u-s-s and go to the bt icon, select it and tap on "connect a
device"...little orange spinner spins...but list never populates.
I have to log on to the device shell and restart indicator-bluetooth at
which
** Changed in: canonical-pocket-desktop
Importance: Medium => High
** Changed in: bluez (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1481136
Public bug reported:
spawned from bug 1513450
as well as some investigation by tvoss
devices need to be tuned to utililze the interactive governor; available method
employed by android/apple is to switch to interactive when the device is picked
up (sensor) or screen is unblanked
this actually
spawned bug 1518418 for the governor topic
** No longer affects: linux-flo (Ubuntu)
** No longer affects: linux-mako (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-flo in Ubuntu.
https://bugs.launchpad.net/bugs/1513450
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Released
** Changed in: ubuntu-system-settings-online-accounts
Status: New => Fix Released
** Changed in: canonical-pocket-desktop
Status: New => Fix Released
--
You received this bug notification
adding projects linux-mako & linux-flo, is it possible to change to the
interactive governor by default (instead of OnDemand)
also, not just for mako/flo but this is a question that should be
asked/answered for all devices (arale, krillin,... as well)
** No longer affects: qtmir
** No longer
it's better, but i still see failure about 25% of the time
** Changed in: canonical-pocket-desktop
Importance: High => Medium
** Changed in: bluez (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Also affects: qtmir
Importance: Undecided
Status: New
** No longer affects: qtmir (Ubuntu)
** No longer affects: qtmir
** Also affects: canonical-pocket-desktop
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
** Changed in: canonical-pocket-desktop
Importance: Undecided = High
** Changed in: canonical-pocket-desktop
Status: New = In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
touching this bug as on our unity8 windowed mode i see this as
1. go to system settings
2. select connect device
3. select mouse detected
4. select connect
(put user back to bt first view)
expected: to be connected
result: have to go back to the mouse bt page and hit connect again.
this is really
in order to help set priority, we're hoping to have this functionality
to support convergence demonstrations ~Feb 22015
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1400827
Title:
dang it...that's 2015, not 22015so few months, not 20,000 years+few
months
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1400827
Title:
BlueZ crashing when connecting input channel
** Changed in: linux (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1195811
Title:
nouveau: Abnormally high FPS and tearing (no vsync) on
** Summary changed:
- nouveau: Abnormally high FPS and tearing (no vsync) on natively mir testing
demo-clients.
+ nouveau: Abnormally high FPS and tearing (no vsync) on native mir
demo-clients. (root caused nv kernel)
--
You received this bug notification because you are a member of Kernel
38 matches
Mail list logo
