I already published the backported patch, but the problem is that the
patch is huge, and as the release will be out in a few days, besides
being an LTS one, I don't think the patch will be incorporated.
The good thing is that at the time they decide to update the kernel to
2.6.33 this fix will be
@HaroldAling: can you paste the result of "$ lspci -vnn | grep RaLink"?
In my EeePC 1000HE I get:
01:00.0 Network controller [0280]: RaLink RT2860 [1814:0781]
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https://bugs.launchpad.net/bugs/496093
Yo
This doesn't seems to be fixed at the current kernel repository, so this
should probably work just for some time.
Let us know if this is stable for you, and also your device id.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https://bugs.launchpad
@jh: the problem is that this driver is still alpha/beta software, even
upstream.
The upstream is basing the driver from the vendor's 2.1 version, but the
vendor already released the 2.3 one.
Neither one is stable or in a state that can be merged upstream, so
issues like these ones are, somehow,
@nicleuskore: if doesn't work, please post the output of "$ lspci -vnn |
grep RaLink" here.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https://bugs.launchpad.net/bugs/496093
You received this bug notification because you are a member of Ubuntu
@John D.: the patch was submitted already, but the kernel team is
responsible for reviewing and applying it, if they decide that this is
the way to go.
Probably the review will happen in the next weeks.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networ
They should first work to get the driver upstream, and this has nothing
to do with Ubuntu itself.
What I saw is that there is a community effort to improve the quality of
the driver, to then be able to push it at Linus' tree. At the moment
this driver is located at the staging, and it's older than
Public bug reported:
Binary package hint: compiz
If you use the window menu to send a not fullscreen window to a
different workspace, the window will be located in a different position
(x and y).
Reproduce:
1. Using default compiz "Normal" settings.
2. Using Gnome 2.30 with Ubuntu Lucid Beta 2
3
This problem doesn't happen when I remove the visual effects (using
metacity).
--
Move to another workspace doesn't keep the window original position.
https://bugs.launchpad.net/bugs/561177
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's the link of the upstream bug:
https://bugzilla.kernel.org/show_bug.cgi?id=15749
At comment #7 you can check the proposed fix, but it's still outside
Linus' tree.
** Bug watch added: Linux Kernel Bug Tracker #15749
http://bugzilla.kernel.org/show_bug.cgi?id=15749
--
2.6.32.30 reproduci
Yes, this bug is fixed with latest version of the driver. The driver's
code that you can find at 2.6.33 is enough to get it working, and that's
why I'm using the backported patch.
As I think this is not going to be merged into Lucid (huge patch), the
easier solution is to install the latest vendor
I also noticed this bug when I installed the latest Lucid in my eeepc
1000he.
Checking linux mainline, I saw that they updated the driver with almost
40 patches, but the main important one was the update from vendor's
V2.1.0.0 driver, that could possible fix this issue.
Tested with 2.6.34-rc3 and
@Claudius: does it work when you use the latest driver provided by the
vendor?
Currently the latest version available to download is v2.3.0.0
(RT2870USB(RT2870/RT2770)). The release notes doesn't say anything
specific to this bug, but it'd be nice to know if it's fixed so we can
work on updating t
@lispy: can you post your device id?
You can easily get the device ID by running "lspci -nn -vv". Please
attach the output at the bug so we can match which device you're
currently using.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https://bugs.
@Claudius: I was able to build it following the same steps you can find
at comment #48.
After installing the module, just load it with "sudo modprobe
rt2870sta".
After loading the driver you'll probably be able to access your wireless
interface.
--
[lucid] rt2860 frequently fails to connect to
@Claudius: after installing the module, you can check if it was loaded
successfully by checking the "lsmod" output.
Also, "dmesg" should say something when loading the driver.
After loading it, try giving "ifconfig -a", see if you can see your
wireless interface there.
--
[lucid] rt2860 frequen
@Laurent: can you also post your device id?
You can easily get the device ID by running "lspci -nn -vv". Please
attach the output at the bug so we can match which device you're
currently using.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https:
Attached you can find the backported patch regarding the update of this
driver.
At mainline we have many other patches, but most are cosmetic changes,
to follow the kernel coding style.
This patch got into 2.6.33, and the original hash is
ca97b8388838ee9ea4b4bad04948f8f7f8a607a3 .
The only thing
I'm also maintaining the kernel with the backported patch at
http://rsalveti.net/pub/ubuntu/kernel/lucid for those who want to test
it, but it's easier to just install the vendor's driver.
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https://bugs
The proper patch to apply on top of the stable one that caused this bug
just got mainline, and the hash is
2060c44576c79086ff24718878d7edaa7384a985.
--
2.6.32.30 reproducible oops at startup in acpi_ex_read_data_from_field
https://bugs.launchpad.net/bugs/561151
You received this bug notification
@Joseph: what's your hardware id?
--
[lucid] rt2860 frequently fails to connect to mixed mode WPA/WPA2 secured
wireless networks
https://bugs.launchpad.net/bugs/496093
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
@Chase Douglas: I also believe that bringing the newer version from
2.6.34 into linux-backports-modules-wireless is the best option. We saw
from this bug that none of the solutions actually fixed most of the bugs
reported, so it's hard to select the best option.
Even the upstream code is in a dedi
@Chase Douglas: tested your package, with the backported driver from
2.6.34 and it seems to be working fine. This fix is included in upstream
since 2.6.33, that's the version with the updated driver.
My hardware is an EeePC 1000HE, with following description and code:
01:00.0 Network controller [0
** Patch added: "0001-UBUNTU-Config-Add-amd-xgbe-to-nic-modules-udeb.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597573/+attachment/4692523/+files/0001-UBUNTU-Config-Add-amd-xgbe-to-nic-modules-udeb.patch
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
Kernel: 4.4.0-21.37 (xenial)
Installer fails to detect the XGBE network interface on AMD Overdrive,
making it impossible to proceed with the network installer.
Checking the kernel udeb modules, we're missing amd-xgbe as part of nic-
modules.
** Affects: linux (Ubuntu)
Public bug reported:
Kernel: 4.4.0-28.47
debian.master/config/config.common.ubuntu: # CONFIG_ARCH_SEATTLE is not
set
The AMD Seattle SoC is used by the AMD Overdrive board and LeMaker
Cello.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ub
** Patch added: "0001-UBUNTU-Config-Enable-the-AMD-Seattle-platform.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597574/+attachment/4692525/+files/0001-UBUNTU-Config-Enable-the-AMD-Seattle-platform.patch
--
You received this bug notification because you are a member of Ubuntu
No need for logs here.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Yakkety)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Yakkety)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: unity8 (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253804
Title:
[regression] Indicator icons don't match the settings they display
T
Critical as it's a regression.
** Changed in: unity (Ubuntu)
Importance: Undecided => Critical
** Summary changed:
- Indicator icons don't match the settings they display
+ [regression] Indicator icons don't match the settings they display
--
You received this bug notification because you a
in: android-src-vendor (Ubuntu)
Status: New => Triaged
** Changed in: android-src-vendor (Ubuntu)
Importance: Undecided => Medium
** Changed in: android-src-vendor (Ubuntu)
Assignee: (unassigned) => Ricardo Salveti (rsalveti)
--
You received this bug notification becau
** Summary changed:
- telepathy-ofono isn't automatically started, which prevents modem from being
onlined
+ [regression] Ubuntu touch cannot get GSM signal if not joined to a WLAN
network
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Critical as it's a regression.
** Summary changed:
- Webbrowser tries to open file:///usr/share/webbrowser-app/'URL' instead of
the URL directly
+ [regression] Webbrowser tries to open file:///usr/share/webbrowser-app/'URL'
instead of the URL directly
** Changed in: upstart-app-launch
Impor
** Changed in: telepathy-ofono (Ubuntu)
Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252737
Title:
[regression] Ubuntu touch cannot ge
This is indeed not a bug, it's by design. We don't want applications
running in background as that will kill your battery, that's why we
force it to stop. If your app wants to keep something in background, we
need a separated service for it, and request a lock with powerd to keep
the system running
** Changed in: android (Ubuntu)
Status: New => In Progress
** Changed in: android (Ubuntu)
Importance: Undecided => High
** Changed in: android (Ubuntu)
Assignee: (unassigned) => Ricardo Salveti (rsalveti)
--
You received this bug notification because you are a member
Probably a regression, as it's the first time I had this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253810
Title:
Messages in Incoming not always display the correct date and content
To
Confirming bug with r32.
** Attachment added: "indicator.png"
https://bugs.launchpad.net/indicator-messages/+bug/1253810/+attachment/3917762/+files/indicator.png
** Changed in: indicator-messages (Ubuntu)
Status: New => Confirmed
** Changed in: indicator-messages (Ubuntu)
Importanc
The timestamp is correct from ofono, and the message is also displayed
correctly in the messaging app, seems the bug is indeed in the
indicator.
And I could easily reproduce the problem today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Fixed in r32 (telepathy-mission-control-5 1:5.16.0-1ubuntu3).
** Changed in: telepathy-ofono (Ubuntu)
Status: Confirmed => Invalid
** Changed in: telepathy-mission-control (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member
More debug output:
phablet@ubuntu-phablet:~$ gdbus call --session --dest
com.canonical.indicator.messages --object-path
/com/canonical/indicator/messages/phone --method org.gtk.Menus.Start [0,1] |
grep x-canonical-text
([(uint32 0, uint32 0, [{'action': <'indicator.messages'>, 'action-namespa
>From camera-app:
Max nice priority 00
Max realtime priority 00
We're not setting the nice value as done by android since we flipped the
container, and afaik we still don't have a policy that describes the
Are you able to reproduce this issue after a reboot? Flashed #43 a few
times (also did a few reboots), and unable to reproduce it locally.
Anything at /var/crash?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
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 term
** 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.
https://bu
This was fixed in 0.1.0+git20130606+c5d897a-0ubuntu22 (still in
proposed).
** Project changed: powerd => libhybris (Ubuntu)
** Changed in: libhybris (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Description changed:
SDK applications need the following AppArmor policy to run:
/dev/binder rw,
The writes to /dev/binder allow applications to attack binder directly
which weakens our application confinement policy.
- Update 2013-08-08:
+ Update 2013-09-04 (audioflinger and
** Summary changed:
- Not possible to get the IMEI without a SIM
+ [rilmodem] Not possible to get the IMEI without a SIM
** Changed in: ofono (Ubuntu)
Status: New => Confirmed
** Changed in: ofono (Ubuntu)
Importance: Undecided => High
** Changed in: ofono (Ubuntu)
Assignee: (una
Just a heads up that this is not exactly the same problem as described
by bug 1103064, which was fixed already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1221473
Title:
Wrong battery level repor
Public bug reported:
Saucy with upower 0.9.21-3.
The power indicator keeps reporting that my logitech mouse battery level
is with 1% from time to time, which is quite annoying (beside displaying
the wrong information).
Looking further, it's upower the one responsible for sending the wrong level,
Probably related with the upstream bug
https://bugs.freedesktop.org/show_bug.cgi?id=60827
** Summary changed:
- Wrong battery level report for Logitech wireless mouse
+ Wrong battery level report for Logitech wireless mouse (1%)
--
You received this bug notification because you are a member of
I built a custom version with the hidpp rework that was just applied
upstream at http://people.canonical.com/~rsalveti/upower/.
Testing and it seems to be working as expected.
Martin, as you're constantly in contact with upstream, would you prefer
to backport the new hidpp related patches or do y
** Also affects: indicator-power (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/1221871
Title:
indicator-power-service is a lightly busy all the t
+1 on option 3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197133
Title:
SDK applications require hardware-specific direct access to graphics
devices
To manage notifications about this bug go
Not sure if a regression on qtbase or qtdeclarative, would be nice to
know if this ever worked with a more recent revision besides 5.0.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222988
Title:
/*!
\fn QMetaObject *QMetaObject::superClass() const
Returns the meta-object of the superclass, or 0 if there is no
such object.
\sa className()
*/
/*!
\internal
Returns \a obj if object \a obj inherits from this
meta-object; otherwise returns 0.
*/
QObject *QMetaObj
Public bug reported:
Using unity8 from https://launchpad.net/~canonical-
qt5-edgers/+archive/qt5-beta-proper together with Qt 5.1.1, which
following packages:
unity8 1:7.81.3+13.10.20130905.2 -0+201309091433~302~ubuntu13.10.1
libqt5core5:armhf 5.1.1+dfsg-2ubuntu1~saucy1~test5
libqt5opengl5:armhf
Public bug reported:
Using unity8 from https://launchpad.net/~canonical-
qt5-edgers/+archive/qt5-beta-proper together with Qt 5.1.1, which
following packages:
unity8 1:7.81.3+13.10.20130905.2 -0+201309091433~302~ubuntu13.10.1
libqt5core5:armhf 5.1.1+dfsg-2ubuntu1~saucy1~test5
libqt5opengl5:armhf
Public bug reported:
Using the following Qt5.1.1 packages from https://launchpad.net
/~canonical-qt5-edgers/+archive/qt5-beta-proper:
libqt5core5:armhf 5.1.1+dfsg-2ubuntu1~saucy1~test5
libqt5opengl5:armhf 5.1.1+dfsg-2ubuntu1~saucy1~test5
Steps to reproduce:
1 - Open the camera-app
2 - Take a pic
Looking internally how the naming happens, it's basically a fixed socket
and adb host command that only allows the port itself to change from one
instance to another.
Without specifying any port when calling the emulator, it'll start at
5554 and increase +2 for every other instance, until it reach
As we discussed today at the IRC, it'd probably be better for us to just
export the --port argument in ubuntu-emulator, and let the SDK tool to
decide which port to use when starting the emulator. That way the SDK
itself can keep map the image with the running instance.
As we can't start 2 differe
The issue here is that the linker binary crated with the gcc-i686-linux-
android toolchain contains a .plt section, when it shouldn't.
The consequence is that once you execute a binary that depends on any
shared library, the linker will fail when it tries to initialize itself,
because it can't con
And where it fails:
bionic/linker/linker.cpp:
1303 static bool soinfo_link_image(soinfo* si) {
...
1360 case DT_JMPREL:
1361 si->plt_rel = (Elf32_Rel*) (base + d->d_un.d_ptr);
...
1543 if (si->plt_rel != NULL) {
1544 DEBUG("[ relocating %s plt ]", si->name );
1545
When comparing the readelf output:
+000201e8 0101 R_386_32 8210 rtld_db_dlactivity
+
+Relocation section '.rel.plt' at offset 0x99c contains 5 entries:
+ Offset InfoTypeSym.Value Sym. Name
+0001ffe0 0107 R_386_JUMP_SLOT 8210 rtld_db_dlactivity
+
In the ARM case I believe the symbols would fit STB_WEAK, otherwise it'd
also fail in the same way.
Just confirmed that the results are generated in the final stage of the
linking process, and it doesn't depend on the object files used.
Using prebuilts/gcc/linux-x86/x86/i686-linux-android-4.7/bin
The difference is that the -Bsymbolic flag is given to the linker when
using the pre-build toolchain (it seems for every shared library).
Our toolchain doesn't use that flag, causing the plt to be generated.
I'm able to successfully build a working linker by forcing this specific flag
in Android
Actually the other warnings listed above is because of DT_TEXTREL. Not
sure yet why we get them with our compiler yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1305315
Title:
Android container
Public bug reported:
current build number: 302
device name: mako
channel: ubuntu-touch/trusty-proposed
last update: 2014-04-17 11:40:41
version version: 302
version ubuntu: 20140417
version device: 20140411.3
Added a google account and it started to automatically sync my calendar.
Before the sync
** Attachment added: "Crash file."
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1309162/+attachment/4086513/+files/_usr_bin_unity8.32011.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
current build number: 302
device name: mako
channel: ubuntu-touch/trusty-proposed
last update: 2014-04-17 11:40:41
version version: 302
version ubuntu: 20140417
version device: 20140411.3
Added a google account that then created a bunch of calendar entries
because of the cale
** Attachment added: "_usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash"
https://bugs.launchpad.net/ubuntu/+source/qtorganizer5-eds/+bug/1309186/+attachment/4086567/+files/_usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash
--
You received this bug notification because you are a
Bt:
(gdb) bt full
#0 0x0030 in ?? ()
No symbol table info available.
#1 0xb0244cc8 in QOrganizerEDSEngine::cancelRequest (this=,
req=0x1e988b0) at
/build/buildd/qtorganizer5-eds-0.1.1+14.04.20140415.1/qorganizer/qorganizer-eds-engine.cpp:981
data = 0x1d7e5f0
#2 0xb195bc9c in QtOrg
** Package changed: phablet-tools (Ubuntu) => android (Ubuntu)
** Changed in: android (Ubuntu)
Status: New => Confirmed
** Summary changed:
- Emulator does not display scopes
+ Unity8 does not display the new scopes when running on the emulator
--
You received this bug notification beca
Seems this is more common during first boot, as it's really hard to
reproduce with following reboots.
** Changed in: android (Ubuntu)
Importance: Critical => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Not an issue with hybris, as you can't run the android binary from the
Ubuntu side, as Android is running in the container.
To run this binary specifically, please make sure you're also running it
from the container (you can get inside the container by calling lxc-
console -nandroid -t0).
rsalvet
This is indeed happening with Android 4.4, but in your case you're not
correctly executing the test case (you should run the android executable
from the android container).
To run this test case specifically:
rsalveti@evasys:~$ adb shell
root@ubuntu-phablet:/# lxc-console -nandroid -t0
Connected
** Changed in: powerd
Status: New => 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/1298869
Title:
Screen unlock broken on image #265 through test automation
To manage notificati
** Changed in: powerd (Ubuntu)
Status: New => 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/1289517
Title:
Screen brightness resets after turning the screen off-on
To manage not
** Changed in: powerd (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/1292565
Title:
light sensors don't seem to do anything.
To manage notifications
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 Ubuntu
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 t
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, Thread::threa
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 this
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.
h
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.
** 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 man
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
> eglDestroyS
** 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:
https://bugs.launchpad.net/ubu
** 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 enablin
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 notifications
** 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 beca
** 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 th
** 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
Thanks for taking care of this Tim :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597574
Title:
Config: missing AMD Seattle platform support
To manage notifications about this bug go to:
https:
make[1]: *** /lib/modules/4.2.0-36-generic/build: No such file or
directory. Stop.
That means you didn't have the headers package installed for this
kernel. Mind installing that and retrying?
** Changed in: rtl8812au (Ubuntu)
Status: New => Incomplete
--
You received this bug notificati
** Changed in: rtl8812au (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/1509859
Title:
Edimax AC-1200 (rtl8812au) does not work on boot
To manage notificatio
*** This bug is a duplicate of bug 1509859 ***
https://bugs.launchpad.net/bugs/1509859
** This bug has been marked a duplicate of bug 1509859
Edimax AC-1200 (rtl8812au) does not work on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
1 - 100 of 2156 matches
Mail list logo
