** Changed in: qtmir (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: qtmir (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
** Description changed:
Ubuntu 16.10 + proposed
Xmir 2:1.18.4-1ubuntu4
wheel mouse scrolling is too fast, tried with firefox and geany.
run firefox on mir scroll up/down some random long page using the mouse
wheel
+
+ TEST CASE:
+
+ 1. env MIR_CLIENT_INPUT_RECEIVER_REPORT=log
Confirmed in all cases it's just that the X11/Xmir apps can't detect the
session bus address of the login (which is on a different TTY BTW).
Forcing DBUS_SESSION_BUS_ADDRESS solves the problem.
Here are some stack traces of the hangs:
gedit:
(gdb) bt
#0 0x7705e853 in select () at
Even with the fix GTK apps under Xmir are hung trying to connect to the
wrong dbus address. Moved that to bug 1604704.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
*** This bug is a duplicate of bug 1604704 ***
https://bugs.launchpad.net/bugs/1604704
I'm making this a duplicate of bug 1604704 now which is clearer.
The fix for bug 1604872 has not solved it.
** This bug is no longer a duplicate of bug 1604872
Apps can't connect to the user's session
The yakkety fix for bug 1604872 has not solved this. So no longer a
duplicate.
** This bug is no longer a duplicate of bug 1604872
Apps can't connect to the user's session bus, even though it exists
** This bug has been marked a duplicate of bug 1603904
X apps that use dbus (GTK, Firefox)
I have tried that earlier. In my case, I can set Internal Mic, Headset
Mic, or Headphone Mic as the Capture source. The hiss does not go away
when it is set to Internal or Headset Mic. When I set it to Headphone
Mic, it stops, but so does all sound output, so it does not work for me.
--
You
** Package changed: lightdm (Ubuntu) => unity (Ubuntu)
** Summary changed:
- LightDM (in locked state) shows desktop if I try to change keyboard layout
+ Screenlock shows desktop if I try to change keyboard layout
--
You received this bug notification because you are a member of Ubuntu
Touch
I've made a release with just this change (1.18.2-0ubuntu2).
** Changed in: lightdm
Status: Confirmed => Fix Committed
** Changed in: lightdm
Milestone: None => 1.18.3
** Changed in: lightdm (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: lightdm
Importance:
I just used 15% of my root directory, where the /boot resides. This
shouldn't be a failure caused by disk space.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
*** This bug is a duplicate of bug 1536751 ***
https://bugs.launchpad.net/bugs/1536751
Thanks for your bug report.
You will first need to fix your TV settings as that will make everything blurry
on your screen
-> bug 1607445
Second, we have known issues with the quality of font rendering
Weird. I did a Super key fix in Mir recently however AFAIK that
regression both occurred and was fixed between releases and never made
it onto any devices.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
Fix committed to lp:mir/0.23 at revision 3528, scheduled for release in
Mir 0.23.5
** Changed in: mir/0.23
Status: New => Fix Committed
** Changed in: mir/0.23
Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny)
--
You received this bug notification because you are a member
I see no evidence or history of work on this topic in the Mir code.
Please clarify if there were any code changes for it in Mir 0.24.0
** Changed in: mir
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
In bug 1565236 I'm not yet convinced that if a Mir fix is required or
exists that we have released it yet. That fix was targeted for Mir
0.24.0 which is not released yet. But also there's no concrete evidence
of a Mir fix existing either.
--
You received this bug notification because you are a
TVs are usually set up to chop off the edges of the image they get by
default(!). I've found this is almost always true with mine.
You need to go into your TV/monitor settings and tell it to display
images at full size, and not crop the edges.
** Changed in: mir (Ubuntu)
Status: New =>
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Status: New => Confirmed
** Changed in: mir
Importance: Undecided => Critical
** Changed in: mir (Ubuntu)
Importance: Undecided => Critical
** Changed in: unity8 (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 1556795 ***
https://bugs.launchpad.net/bugs/1556795
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1556795, so it is being marked as such. Please
No you can't. I mentioned in the bug description; on krillin the
launcher is too small to be able to do that with a finger.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
On Wed, Jul 27, 2016 at 4:19 PM, ernsteiswuerfel
wrote:
> In the meantime you could try to get one of the other drivers
>> "modesetting", "fbdev", "fbdevhw" to work with 24 bit depth. You can use
>> my xorg.conf as starting point and edit it manually. Just put it in
>>
Marking v-done, based on IRC feedback.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1577734
Title:
This bug was fixed in the package libdrm - 2.4.67-1ubuntu0.14.04.1
---
libdrm (2.4.67-1ubuntu0.14.04.1) trusty; urgency=medium
* Backport xenial package to trusty.
* Adjust revert-65041c4a1.diff to only keep drmAllocCopy, though it
has never been in the header file and not
This bug was fixed in the package libxrandr - 2:1.5.0-1~trusty1
---
libxrandr (2:1.5.0-1~trusty1) trusty; urgency=medium
* Backport for lts-xenial stack. (LP: #1577734)
-- Timo Aaltonen Tue, 03 May 2016 16:25:01 +0300
** Changed in: libxrandr (Ubuntu
The verification of the Stable Release Update for x11proto-randr has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.5
---
isc-dhcp (4.2.4-7ubuntu12.5) trusty; urgency=medium
* debian/apparmor-profile.dhclient: Add the attach_disconnected flag to
prevent
disconnected path denials (LP: #1568485).
-- Jorge Niedbalski
This bug was fixed in the package x11proto-randr - 1.5.0-1~trusty1
---
x11proto-randr (1.5.0-1~trusty1) trusty; urgency=medium
* Backport for lts-xenial stack. (LP: #1577734)
-- Timo Aaltonen Tue, 03 May 2016 16:41:48 +0300
** Changed in: x11proto-randr
This bug was fixed in the package llvm-toolchain-3.8 -
1:3.8-2ubuntu3~trusty4
---
llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty4) trusty; urgency=medium
* rules, libllvmX.Y.{links,install}.in: Rename libllvm3.8 to
libllvm3.8v4.
llvm-toolchain-3.8 (1:3.8-2ubuntu3~trusty3) trusty;
The fix is currently in silo 005, and was just marked 'Lander Approved'.
The version containing the fix will be 1.2.2-0ubuntu1~xenial3, and
should hopefully land in the next few days.
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug
It appears the solution to my problem was to use the dconf-editor and
set org.settings-daemon.plugins.power.critical-battery-action to
nothing. My laptop currently displays 19% battery life and continues to
work. Thanks, Anita.
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
I think you may be right, Henry. I went out on a walk along a country
lane this afternoon and decided to try out uNav. I don't think that app
expects the device to have a location to hand to it when it starts. Your
press an icon in the header to determine you current location, and it
worked. As
The photos above are a bit big. You have to scroll them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1607552
Title:
Blue dots for highlighting a text/cursor
** Attachment added: "image20160729_001833810.jpg"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1607552/+attachment/4708988/+files/image20160729_001833810.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "image20160729_001827714.jpg"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1607552/+attachment/4708987/+files/image20160729_001827714.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Just because we cover everything with the finger and are unable to place
the cursor where we want to. Correct is a BIG raindrop(Android) >under<
the cursor so that we can put the finger on a blue control point and
precisely put the cursor where we want to. On Ubuntu Touch:
Hi!, I have the same computer model, and activate the "headset mic" in
alsamixer fix the problem (sorry for my English).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtsystems-opensource-src (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtsystems-opensource-src
I am a Ubuntu supporter and was one of the first to buy the Ubuntu BQ
M10 tablet. We, the Portuguese speaking supporters were surprised that
was not possible to write in PORTUGUESE with the EXTERNAL KEYBOARD. We
were assured that this issue would be resolved soon. But… it's been
months and several
I am a Ubuntu supporter and was one of the first to buy the Ubuntu BQ
M10 tablet. We, the Portuguese speaking supporters were surprised that
was not possible to write in PORTUGUESE with the EXTERNAL KEYBOARD. We
were assured that this issue would be resolved soon. But… it's been
months and several
** Attachment added: "screenshot20160728_155621480.png"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4708954/+files/screenshot20160728_155621480.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Attachment added: "screenshot20160728_155227118.png"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4708957/+files/screenshot20160728_155227118.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Attachment added: "screenshot20160728_155617313.png"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4708956/+files/screenshot20160728_155617313.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Today I tried with OTA12. Actually nothing changed BUT!!! I see the
problem somewhere else! I tried to pair my phone with a few car audio
systems. What You will see in the photos that i'm gonna attach below
seems not to be a problem with the bluetooth itself but with the system.
My bq4.5 displays
** Attachment added: "screenshot20160728_155456921.png"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040/+attachment/4708955/+files/screenshot20160728_155456921.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Today I've updated my BQ 4.5 phone to Ubuntu 15.04 (OTA-12), can not
open clock APP any more. Just after the splash screen appears it closes
immediately.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
** Description changed:
[Impact]
- Using yakkety with systemd user session makes telepathy unhappy because
- access to /run/user//bus is denied
+ Systemd user sessions makes telepathy unhappy because access to
+ /run/user//bus is denied
[Test Case]
In yakkety:
- sudo apt
Default Comment by Bridge
** Attachment added: "SOS report for systemd PCI Roce Interface renaming"
https://bugs.launchpad.net/bugs/1602737/+attachment/4708952/+files/sosreport-HGrauer-20160713144947.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Touch
Hello, Any update on this defect?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1589775
Title:
ifupdown of ucarp interface fails
Status in ifupdown package in Ubuntu:
The problem persist in OTA-12 and bqm10. In xapps it works perfect but
in native apps. In addiction, the 'arroba' character and the "altgr
characters" works in all native apps except default navigator.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
I have disabled location services in each scope(top checkbox). Later
option to re-enable is not present(all remaining boxes are checked).
Afterwards I have allowed location detection to scopes (initially this
was not required. see
Confirmed fixed on @robert123m post #5 above on ubuntu 16.04.1 LTS.
Can't thank you enough. Here is my env for reference:
$ dpkg -l | grep 'pulse\|bluetooth'
ii blueman 2.0.4-1ubuntu2
ii gir1.2-gnomebluetooth-1.0:amd64 3.18.2-1ubuntu2
ii
** Description changed:
+ [Impact]
+
Using yakkety with systemd user session makes telepathy unhappy because
access to /run/user//bus is denied
+
+ [Test Case]
+
+ In yakkety:
+
+ sudo apt install dbus-user-session empathy
+
+ Restart the session (or reboot), start empathy. It fails
** Description changed:
+ [Impact]
+
+ Applications which use libapparmor's aa_change_onexec() to set up an
+ AppArmor profile transition across an upcoming exec() cannot pre-
+ initialize the environment. This is caused by AppArmor unconditionally
+ setting the AT_SECURE flag on the process,
** Description changed:
+ [Impact]
+
+ The AppArmor regression tests are ran as part of the kernel SRU
+ verification process. One of the tests, onexec.sh, contains a racy
+ section that introduces intermittent failures. Such failures introduce
+ doubt in the kernel SRU process and generate
>From what I understand, systemd does not rename devices a second time:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1579130
So, it's possible that existing udev rules have already applied to the
device in question and your .link file is "too late".
This maybe a dupe of that; but
I just tried the test application I attached to the bug, and I can still
reproduce this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1578619
Title:
** Description changed:
+ [Impact]
+
+ AppArmor policy developers cannot use aa-logprof without it exiting with
+ a traceback on certain denial messages.
+
+ [Test Case]
+
+ $ echo 'type=AVC msg=audit(1463403689.381:267599): apparmor="ALLOWED" \
+ operation="file_perm" profile="foo" pid=13215
** Also affects: apparmor (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apparmor (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: apparmor (Ubuntu Xenial)
Status: New => In Progress
** Changed in: apparmor (Ubuntu Xenial)
Assignee:
** Description changed:
+ [Impact]
+
+ AppArmor policy developers cannot use aa-logprof without it exiting with
+ a traceback on certain denial messages.
+
+ [Test Case]
+
+ $ echo 'Apr 30 21:53:05 nova kernel: [24668.960760] audit: \
+ type=1400 audit(1462045985.636:2154): apparmor="DENIED" \
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: ubuntu-z-systems
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Server
** Changed in: apparmor (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: apparmor (Ubuntu)
Importance: Undecided => Medium
** Changed in: apparmor (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: apparmor (Ubuntu Xenial)
Assignee: (unassigned) =>
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Alt-Gr works for me in XApps, but not in normal apps as Uwriter or
Telegram. Bq M10 FHD. OTA 12.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1565236
Title:
AltGr not
Maybe make display-manager.service into an actual service file (rather
than a symlink), and have that start whatever /etc/X11/default-display-
manager points to?
What I want is to be able to disable and then re-enable the display
manager starting on boot using similar administrative commands,
Stefan Freyr, if you install the xenial xorg enablement stack following
https://wiki.ubuntu.com/Kernel/LTSEnablementStack is this issue still
reproducible?
** Tags removed: bios-outdated-1.24
** Tags added: latest-bios-1.25
** Changed in: xorg (Ubuntu)
Importance: Low => Medium
** Changed
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-landing-071
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1584601
Title:
Mir fails to build in:
** Branch linked: lp:~awe/lxc-android-config/fix-emulator-networking-
xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1587808
Title:
Ubuntu-emulator no
Oliver, in 14.04, which version of the nvidia driver were you using
specifically?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1607212
Title:
HDMI connection issue (Ubuntu
Hello Mark, or anyone else affected,
Accepted software-properties into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.20.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Public bug reported:
Following upgrades to OTA 12 the location failed to work on the BQ 4.5
and the Finger print option was missing from the setting menu on the Pro
5. A further reboot of both fixed the problems. I therefore assume that
the upgrade process is not initialising some programs
I got it again working by "disabling roaming" in the data connection.
http://askubuntu.com/questions/603101/gps-unvailable-on-
aquaris-e45?noredirect=1=1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ok after Marks comment I tried again but without any luck. However I
also have a Pro 5 and the finger print function did not work (was not in
the menu). I rebooted and it appeared so In did the same with the E4.5
and the new location icon started to change colour and within a few
minutes it was
This is a nice trick @dino99 - and one of the points i left Ubuntu!
The report was made with Xubuntu 15.10 alpha...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1480415
My Meizu MX4 is paired with my car (Renault with Carminat TomTom), but
the connection breaks within 2 sec. after connecting.
The sad thing is that it did work a bit before OTA 9.
Will this be fixed by the new silo?
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 1590515 ***
https://bugs.launchpad.net/bugs/1590515
** This bug has been marked a duplicate of bug 1590515
AltGr composed keys don't work in the browser content
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This problem is present in Ubuntu 16.04 Xenial Desktop build, as well
Quick workaround:
$ rm /run/resolvconf/interface/NetworkManager
Deleting /run/resolvconf/interface/NetworkManager and re-running
ifdown/ifup will result in the /etc/network/interfaces dns-nameservers
to be populated into
Hey Pat,
I'm happy to try this out on my own phone as an additional data point if
you think getting someone else to try out the fix might be helpful.
Though I'll have to dig around a bit to figure out how to build and swap
in a modified nuntium, as I'll admit I'm not familiar with that
component.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-bluetooth (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
For this bug, I don't think we can really fix the general "account gets
deleted" complaint in any reasonable time frame or manner. And even if
we could, the same issues which are causing the account to be deleted,
would still cause a request to log in again, but the complaint would
just be "u1
** Branch linked: lp:~awe/lxc-android-config/fix-emulator-networking
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1587808
Title:
Ubuntu-emulator no network
Did the update to OTA12 on a Meizu MX4 and trying to connect to an Audi
bluetooth system:
Small step forwards...
Works:
- Car bluetooth is detected
- The car bluetooth is shown (not just unknown...)
- If I press 'connect', I'm asked for the pincode
- If I enter the correct pincode, ubuntu says
Public bug reported:
This bug is related to bug#1606555. But this is also a security and
privacy threat.
release of Ubuntu: Ubuntu 16.04
What's happening:
I lock my machine(Super + L key)
LightDM greeter is showing.
If I push hotkey to change keyboard layout, LightDM flashes and then it shows
** Description changed:
MX4/arale
ubuntu-touch/rc-proposed/meizu.en #387
Flash phone with --bootstrap, and walk through the welcome wizard. Once
you have a phone to use, visit the BT settings, and pair a mono 'HSP'
headset. In my case an old Jabra OTE-1.
Once the device is
It's working perfectly for me now with OTA 12 with my bq E4.5 phone and
bq M10 tablet. All services like uNav, Here Maps and Google Maps are
working with GPS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service
"Tenten36 (tenten) wrote on 2016-07-27:
The problem still exists with kernel 4.6 and 4.7 from the mainline
build.
$ DRI_PRIME=1 glxgears
gives black screen"
That seems like a regression or the newest kernels weren't patched.
Currently using 4.4.14 and it still works.
--
You received this bug
I plan to capture logs, following the instructions here:
https://wiki.ubuntu.com/DebuggingBluetooth
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1607466
Title:
Mono
I discovered this apparent regression while testing the silo 60+37 combo
@koza is using to land bluez 5.41, but note that the bug appears (and
then disappears) on vanilla 387 vs 381.
** Changed in: canonical-devices-system-image
Milestone: None => 13
--
You received this bug notification
Public bug reported:
MX4/arale
ubuntu-touch/rc-proposed/meizu.en #387
Flash phone with --bootstrap, and walk through the welcome wizard. Once
you have a phone to use, visit the BT settings, and pair a mono 'HSP'
headset. In my case an old Jabra OTE-1.
Once the device is paired, make an incoming
Ok, thanks, here you are :)
** Attachment added: "application-click-com.ubuntu.music_music_2.4.1003.log"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604433/+attachment/4708875/+files/application-click-com.ubuntu.music_music_2.4.1003.log
--
You received this bug notification
Public bug reported:
Ubuntu 16.0.4
HP network printer
Prints document, except for last page, with this output:
ERROR:
undefined
OFFENDING COMMAND:
...Undefined
STACK:
{the rest of the error has varied; sometimes numbers like -699.95, -300.0,
-mark-, and others}
ProblemType: Bug
DistroRelease:
--- Comment From ru...@us.ibm.com 2016-07-28 12:47 EDT---
Pinging for status update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1602737
Title:
PCI RoCE
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
I don't know if this is the same bug or not but my laptop decided it was
critically low and shut itself off while the battery indicated it still
had about 3+ hours of life left. I couldn't power it back on until I
plugged in ac and at that point it was over 80% of battery life. I don't
think this
** Changed in: ubuntu-z-systems
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1602655
Title:
The openssl s390x assembly pack is
Public bug reported:
Hey,
I use M10 FHD tablet with OTA-12 and sometimes I use it with mouse. When I
scroll it down in my home scope it automatically goes untill the end of the
scope. So if I need an app that is in the middle of the list, I have to click,
hold and move mouse.
It could be like
** Changed in: openssl (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1602655
Title:
The openssl s390x assembly pack is
Public bug reported:
Hey,
I use M10 FHD tablet with OTA-12 and when I connect it to the external HD
monitor, the zoom is not correct. I cannot see the any of the border (top
panel, launcher,...). But this only happens with some of the monitors.
One of the monitors that doesn't work correct is
Public bug reported:
Hey
I use M10 FHD tablet with OTA-12 and bluetooth keyboard Logitech k810 and
special characters that comes from combining altgr and numbers are not working.
I use Slovenian layout
So I cannot get characters such as: ˝'˙` (combining altgr and 0,9,8,7).
Thanks
** Affects:
1 - 100 of 279 matches
Mail list logo