And for it to go to wired headset, https://code.launchpad.net/~rsalveti
/telepathy-ofono/adding_support_for_hsp/+merge/229292 needs to be
merged.
** Changed in: pulseaudio (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Our expected result is for the ringtone to come out just at the default
output device (speaker or wired headset). If the user has a bt device
connected, it'll use speaker as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Assigning it to tvoss as he created the hybris abstraction for camera.
** Changed in: android (Ubuntu)
Assignee: Ricardo Salveti (rsalveti) = Thomas Voß (thomas-voss)
** Changed in: camera-app
Assignee: Ricardo Salveti (rsalveti) = Thomas Voß (thomas-voss)
--
You received this bug
** Also affects: unity8 (Ubuntu)
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/1351097
Title:
[emulator] bottom edge swipe broken
To manage
Public bug reported:
root@ubuntu-phablet:~# system-image-cli -i
current build number: 166
device name: generic_x86
channel: ubuntu-touch/utopic-proposed
last update: 2014-07-31 17:40:46
version version: 166
version ubuntu: 20140731.1
version device: 20140728.1
Can't use the bottom edge swipe
That's by design, same happens with the phones. The only difference is
that the touch screen for the phone starts and ends after the screen
part of it, so it gives the impression you're coming from the outside
frame.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
root@ubuntu-phablet:~# system-image-cli -i
current build number: 166
device name: generic_x86
channel: ubuntu-touch/utopic-proposed
last update: 2014-07-31 17:40:46
version version: 166
version ubuntu: 20140731.1
version device: 20140728.1
Just boot the emulator, and you'll
This was working on image 151 (afaik mako 149). So it could be a
regression on the unity8/mir side.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1351097
Title:
[emulator] bottom edge swipe broken
Tested with image 160 and it finally worked as we expect.
It seems wizard is crashing sometimes, but I'm still investigating that
one.
pitti, I'm able to swipe back to the main screen just fine here (and
also access the launcher). Just make sure you start the swipe movement
from the first valid
Moving to high as one piece already landed and it's way harder to
reproduce the issue with latest image.
** Changed in: urfkill (Ubuntu)
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Did push the a new sync for latest ui-toolkit, let's check this bug
again after it lands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349444
Title:
[emulator] unity8 fails to start since image
Quite a few things changed on 149, so not clear yet on the issue:
http://people.canonical.com/~lzemczak/landing-team/149.commitlog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349444
Title:
Public bug reported:
Unity8 fails to start on emulator (tested on x86).
Wizard works fine, but after complete it, screen stays black.
Checking via adb shell, unity8 is running but nothing showing up at the
screen.
Follows the unity8 log:
phablet@ubuntu-phablet:~$ cat
Public bug reported:
Image 148 on mako/flo, try importing file
http://people.canonical.com/~rsalveti/Existance.mp3, and you'll see
mediascanner consuming most of the resources available, until killed.
Probably an issue with gstreamer itself.
** Affects: mediascanner2 (Ubuntu)
Importance:
While I understand the reasoning, I don't think powerd should track
notify-osd, as in this case notify-osd should instead request the screen
to be on for a short period of time (by talking to the system-
compositor).
In this case you want to make sure that the phone stays up until you see
the
Worked fine after calling '$ bluetooth-agent --adapter hci0
00:1F:82:05:7D:66' and restarting the device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347106
Title:
[bluetooth] can't connect
This bug is not yet in trunk, opening it here as cyphermox requested it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1347106
Title:
[bluetooth] can't connect to headset
To manage notifications
Public bug reported:
Using the current code available at https://code.launchpad.net/~mathieu-
tl/ubuntu-system-settings/bluetooth-redesign/+merge/227385, I'm still
unable to connect to my bt headset device.
Follows the syslog:
After powering up my device (see that it tries to connect to the
Public bug reported:
Starting from image 137, with mir 0.5, Mir fails to start on Nexus 5
(hammerhead), as it fails to turn the vsync signal on.
This is what I get from logcat:
D/libEGL ( 3038): loaded /vendor/lib/egl/libEGL_adreno.so
D/libEGL ( 3038): loaded
From
http://launchpadlibrarian.net/180157436/mir_0.4.1%2B14.10.20140714-0ubuntu1_0.5.0%2B14.10.20140717-0ubuntu1.diff.gz
it seems that the reason is that now this error is fatal, while before
it wasn't even checking the return value.
Do we need this error to be fatal?
** Also affects: mir
Did you test the upstream implementation first to see if that is already
enough for you? While I like the change you proposed, that would differ
us from upstream, and the next rebase would mean dropping your change.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Google pushed quite a few updates to the upstream tree
(https://android.googlesource.com/kernel/goldfish/+log/android-
goldfish-3.4), including stable changes, so it'd be nice for us to
rebase our tree as well.
Not sure if that helps fixing the gcc 4.6 dependency issue, but
Are you able to reproduce the error when running with '--memory=1024' ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1329374
Title:
kernel panic pressing return in terminal that spawned emulator
** Changed in: unity8 (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/1339700
Title:
Device locks randomly on welcome screen
To manage notifications about
Public bug reported:
current build number: 102
device name: flo
channel: ubuntu-touch/utopic-proposed
last update: 2014-06-27 18:19:49
version version: 102
version ubuntu: 20140627.1
version device: 20140625
I get the following crash when it stops (after it finishes):#0 0xa23f7090 in
?? ()
No
Worked fine when mediascanner 1 was used instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1334940
Title:
Can't scan videos on ubuntu touch (flo, image 100)
To manage notifications about this
Public bug reported:
current build number: 100
device name: flo
channel: ubuntu-touch/utopic-proposed
last update: 2014-06-27 02:47:20
version version: 100
version ubuntu: 20140626.2
version device: 20140625
Flashed a clean image, tried to import the videos from
Public bug reported:
Attached picture shows the bug.
Started since we landed qt 5.3, and can't reproduce it all the time.
Reproducible with emulator, flo and mako.
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: emulator-unity8.png
I thought I checked that when submitting this bug, but yeah, follows the denial:
Jun 27 04:46:40 ubuntu-phablet kernel: [ 92.764892] type=1400
audit(1403844400.411:73): apparmor=DENIED operation=open parent=3331
profile=/usr/bin/mediascanner-service-2.0
As mediascanner uses gst directly, I imagine the policy needs to be
similar to media-hub (libhybris/etc).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1334940
Title:
Can't scan videos on ubuntu
Worked fine after I added the following at
/etc/apparmor.d/usr.bin.mediascanner-service-2.0:
/dev/ashmem rw,
# libhybris
/{,var/}run/shm/hybris_shm_data rw,
/usr/lib/@{multiarch}/libhybris/*.so mr,
/{,android/}system/build.prop r,
# These libraries can be in any of:
# /vendor/lib
Public bug reported:
Currently on flo I get the following message every time someone calls the
vibrate function:
com.canonical.usensord.Error: open /sys/class/timed_output/vibrator/enable: no
such file or directory
That's basically because there's no vibrator hardware/driver available
for flo.
** Changed in: android (Ubuntu)
Status: Confirmed = 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/1331285
Title:
phablet user is unable to use light sensors (lack of permission
Public bug reported:
By design the indicator-sound is only storing/restoring the master
volume, not handing sink-port specifics.
Meanwhile we have pulse also storing/restoring the per sink-port values
once the daemon is started, but it gets reset again once indicator-sound
is started with the
On touch, as it is single-user mode for now, we could just let pulse do
all the store/restore handling, but that would possibly break the
desktop and the convergence model.
There is also another issue that the greeter would need to be able to
control the main volume independently, and that
a2dp devices are working as expected, hsp is still being investigated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1240979
Title:
[bluetooth] After claiming to connect no audio is routed to the
After setting trusted to yes, it worked fine:
python3 `which bluez-test-device` trusted 00:0C:8A:B5:21:56 yes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331642
Title:
[bluetooth] device can't
Public bug reported:
current build number: 87
device name: flo
channel: ubuntu-touch/utopic-proposed
last update: 2014-06-18 15:21:48
version version: 87
version ubuntu: 20140618
version device: 20140530
After successfully creating a connection with a device (soundlink mini
bose), it can't auto
Public bug reported:
Using Ubuntu Utopic:
kernel: 3.15.0-6-generic
hardware: Intel Corporation Centrino Advanced-N 6235
I'm able to successfully connect to any device, but can't enable the HSP
profile (Input/Output error). A2DP works fine though.
Tested with Jabra Halo (HSP and A2DP) and
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134510/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134503/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134508/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
Title:
Fails
apport information
** Tags added: apport-collected utopic
** Description changed:
Using Ubuntu Utopic:
kernel: 3.15.0-6-generic
hardware: Intel Corporation Centrino Advanced-N 6235
I'm able to successfully connect to any device, but can't enable the HSP
profile (Input/Output
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134506/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134514/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134511/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134513/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134507/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
Title:
Fails
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134509/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134512/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
apport information
** Attachment added: getfacl.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134515/+files/getfacl.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
Title:
apport information
** Attachment added: rfkill.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134516/+files/rfkill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
Title:
apport information
** Attachment added: syslog.txt
https://bugs.launchpad.net/bugs/1331748/+attachment/4134518/+files/syslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: hci dump
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331748/+attachment/4134521/+files/hci.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331748
Title:
Fails
From hcidump:
2014-06-18 18:22:57.986031 HCI Event: Command Status (0x0f) plen 4
Setup Synchronous Connection (0x01|0x0028) status 0x1a ncmd 1
Error: Unsupported Remote Feature / Unsupported LMP Feature
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: pulse, bluetoothd and hcidump
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1331843/+attachment/4134548/+files/bt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After a few reboots I'm able to connect again, so this doesn't happen
all the time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331843
Title:
[bluetooth] unable to reconnect to a device
To
Public bug reported:
current build number: 87
device name: flo
channel: ubuntu-touch/utopic-proposed
last update: 2014-06-18 15:21:48
version version: 87
version ubuntu: 20140618
version device: 20140530
After a clean flash I'm able to scan and connect to my bt headset, but
after a few a reboot
I'm able to connect using system-settings but pulseaudio can't play the
stream:
Jun 18 22:32:30 ubuntu-phablet pulseaudio[1885]: [bluetooth] bluetooth-util.c:
Failed to release transport /org/bluez/2118/hci0/dev_00_23_78_AB_89_AC/fd8: Did
not receive a reply. Possible causes include: the remote
** Attachment added: Complete log (pulse, bluetoothd, hcidump)
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1273629/+attachment/4134553/+files/bt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I proposed the needed patches to change to 0664 system:input, which
should be enough for phablet. While input might not be ideal, at least
we avoid creating yet another group for such functionality.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This shouldn't be handled by ofono, and the tech specifics should also
be handled by the client side, not ofono.
Percentage is not ideal, and not linear, but it was what was used by
ofono initially (see
https://lists.ofono.org/pipermail/ofono/2011-January/007827.html).
We could just change it to
Also check how this is handled by Android:
http://androidxref.com/4.4.2_r2/xref/frameworks/base/telephony/java/android/telephony/SignalStrength.java
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
But then we'd break the ofono API as rilmodem is doing exactly the same
thing as we have for the other modems (check at modem and others).
People using the ofono API is expecting the percentage to be basically
the asu values (in case of a gsm modem).
--
You received this bug notification
Just uploaded 4.4.2-1-0ubuntu1, updating every header with AOSP 4.4.2.
Please reopen the bug in case of issues.
** Changed in: libhybris (Ubuntu)
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
** Package changed: libhybris (Ubuntu) = android-headers (Ubuntu)
** Changed in: android
Public bug reported:
libhybris_0.1.0+git20131207+e452e83-0ubuntu17 includes a test program
that uses the light sensors (for light notifications), but it fails to
run as phablet user, as it lacks the needed permissions in
/sys/class/leds.
The test works fine as root, and strace shows the files
** Changed in: android (Ubuntu)
Status: New = Confirmed
** Changed in: android (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331285
Title:
phablet
** Changed in: indicator-network (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/1329945
Title:
WWAN signal strength is reported lower than android in same
* 6% x 16% - POOR (1 bar)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1329945
Title:
WWAN signal strength is reported lower than android in same location
To manage notifications about this bug
The forma to calculate the signal strength depends on the technology,
and our ofono-rilmodem driver basically converts the ASU values to
percentage (0-31, 99).
Here's how android calculates the signal bars (for GSM):
int asu = getGsmSignalStrength();
if (asu = 2 || asu == 99) level =
David, while I don't see the need to change Pulse in order to be able to
notify the user that a recording is in place, how should we proceed on
the trusted helper side (the user prompt, such as Foo wants to use the
microphone. Is this ok? Yes|No)?
--
You received this bug notification because
Mind uploading your /var/log/syslog ? Hard to tell without more logs.
Wonder if this is related with the camera app/server.
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ubuntu-system-settings (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274618
Title:
Cellular page: set to manual network detection can't
** Changed in: pulseaudio (Ubuntu)
Status: New = Confirmed
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided = High
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
--
You received this bug notification because you are a member
** Changed in: android (Ubuntu)
Status: New = Confirmed
** Changed in: android (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327259
Title:
goldfish
Public bug reported:
current build number: 48
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/utopic-proposed
last update: 2014-05-25 13:27:58
version version: 48
version ubuntu: 20140525
version device: 20140523
Core was generated by `/usr/bin/mtp-server'.
Program
** Attachment added: _usr_bin_mtp-server.32011.crash
https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1323205/+attachment/4119666/+files/_usr_bin_mtp-server.32011.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: ubuntu-system-settings (Ubuntu) = ofono (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1322356
Title:
GSM does not work on r44
To manage notifications about this bug go
** Project changed: touch-preview-images = indicator-network (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320619
Title:
mako Ubuntu 14.10(r28) shows Celluar settings 3 times in drop menu
** Package changed: xserver-xorg-video-intel (Ubuntu) = linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1239186
Title:
[Lenovo ThinkPad X220] External screens shut off randomly
To
On Fri, May 16, 2014 at 2:49 AM, Thomas Voß 1319...@bugs.launchpad.net wrote:
Trying to clarify on your latest comment: With app you are referring to
an actual application running in the emulator? If so, I would propose to
start digging into qtubuntu and see if we fail to call
** Package changed: powerd (Ubuntu) = ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319796
Title:
suspend fails
To manage notifications about this bug go to:
** Summary changed:
- 'Failed to start RenderThread' after opening/closing applications
+ emulator: 'Failed to start RenderThread' after opening/closing applications
** Also affects: qtubuntu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
I'm to reproduce this issue with my manta, and not only that, but also
the one that shows the indicator with wifi-off.
Here's the syslog with NM using --log-level=DEBUG:
http://paste.ubuntu.com/7494813/
The interface is up, unavailable for NM and indicator showing WIFI -
OFF.
And after enabling
Worked fine after disabling urfkill: http://paste.ubuntu.com/7494848/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320249
Title:
Manta has no network connection by default
To manage
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided = High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification
** Changed in: android (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/1319119
Title:
Emulator x86 not functioning on amd gfx
To manage notifications about
After discussing this bug with ricmm, we came down into two possible solutions:
1 - Changing Mir/Unity8 and app lifecycle to gracefully terminate the app
instead of sending sigkill;
2 - Changing Mir to make sure that every surface used is properly released;
So, opening a bugtask for mir as well.
The qemu uart console was disabled to avoid such issues, and also
because that wasn't supported on x86. Marking as wontfix.
** Changed in: android (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Using:
ubuntu-emulator 0.2+14.10.20140429.1-0ubuntu1
ubuntu-emulator-runtime 20140501-2310-0ubuntu3
Emulator starts fine, but after a few opening/closing apps in a row (a
bunch of times, at least 20), emulator gives the 'Failed to start
RenderThread' error.
At that point
The error actually happens when RendorControl tries to start a new thread
(host), so it can handle the new GLES surface:
shared/OpenglOsUtils/osThreadUnix.cpp
bool
Thread::start()
{
pthread_mutex_lock(m_lock);
m_isRunning = true;
int ret = pthread_create(m_thread, NULL,
After adding a bit of more debug entries, it's clear that the window
surface gets allocated when the app is instantiated, but it's never
released.
When opening a new app:
Framebuffer::createWindowSurface
Framebuffer::createColorBuffer
When destrying the app:
Framebuffer::closeColorBuffer
In
The bug happens because eglDestroySurface never gets called when the app
is closed. That function is the one responsible to tell the emulator
stack that the surface should be destroyed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would be nice to have the package version used (binary one) as well.
From your logs:
emulator: Initializing hardware OpenGLES emulation support
signal: segmentation fault (core dumped)
It's probably crashing when trying to create the gl window that accepts
the gl commands translated by the gles
Public bug reported:
How to reproduce:
sudo ubuntu-emulator create --channel=ubuntu-touch/utopic-proposed
--use-raw-disk --arch=i386 --revision=22 test_x86
ubuntu-emulator run test_x86 --memory=720
From time to time upstart doesn't start lightdm, leaving the emulator
window with just a black
'initctl emit runlevel RUNLEVEL=2 PREVLEVEL=1' runs fine here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318681
Title:
lightdm not started when running the ubuntu-touch x86 emulator
To manage
** Attachment added: upstart.json
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1318681/+attachment/4110792/+files/upstart.json
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318681
Public bug reported:
When booting the x86 kernel (touch x86 emulator):
[0.00] Fast TSC calibration failed
[0.00] TSC: Unable to calibrate against PIT
[0.00] TSC: No reference (HPET/PMTIMER) available
[0.00] Marking TSC unstable due to could not calculate TSC khz
So yeah, -Bsymbolic is the reason :-)
Check http://gcc.gnu.org/ml/gcc/2013-03/msg00304.html. And
http://gcc.gnu.org/ml/gcc/2013-04/msg00016.html as follow up.
So the prebuilt Android toolchain forces -Bsymbolic for every shared
library.
As this is not the case with our toolchain, the linker
** Changed in: powerd (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/1314678
Title:
Display brightness adjustable but does nothing when Adjust
automatically
601 - 700 of 2173 matches
Mail list logo
