date:20151209

[Touch-packages] [Bug 1524234] [NEW] QML function trigger() with no argument doesn't override ActionItem.trigger

2015-12-09 Thread Christian Dywan

Public bug reported:

In QML it's only natural to declare

function trigger() { }

on an ActionItem (derived item) and expect it to override the trigger
slot.

This doesn't work - sometimes it works if the function is declared with
an argument, other times not at all.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Critical
 Assignee: Zsombor Egri (zsombi)
 Status: 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.
https://bugs.launchpad.net/bugs/1524234

Title:
  QML function trigger() with no argument doesn't override
  ActionItem.trigger

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In QML it's only natural to declare

  function trigger() { }

  on an ActionItem (derived item) and expect it to override the trigger
  slot.

  This doesn't work - sometimes it works if the function is declared
  with an argument, other times not at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1524234/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1524234] Re: QML function trigger() with no argument doesn't override ActionItem.trigger

2015-12-09 Thread Launchpad Bug Tracker

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/properTriggerCall

-- 
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/1524234

Title:
  QML function trigger() with no argument doesn't override
  ActionItem.trigger

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In QML it's only natural to declare

  function trigger() { }

  on an ActionItem (derived item) and expect it to override the trigger
  slot.

  This doesn't work - sometimes it works if the function is declared
  with an argument, other times not at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1524234/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1524130] Re: /usr/bin/unity8:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

2015-12-09 Thread Albert Astals Cid

** Also affects: dbus-cpp (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1524130

Title:
  
/usr/bin/unity8:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

Status in dbus-cpp package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.11+15.04.20151208-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/2ab45fb8f212225ec5c93d8fe917c1c82cda2839
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1524130/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1524234] Re: QML function trigger() with no argument doesn't override ActionItem.trigger

2015-12-09 Thread Zsombor Egri

This si valid also on Action itself.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

-- 
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/1524234

Title:
  QML function trigger() with no argument doesn't override
  ActionItem.trigger

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In QML it's only natural to declare

  function trigger() { }

  on an ActionItem (derived item) and expect it to override the trigger
  slot.

  This doesn't work - sometimes it works if the function is declared
  with an argument, other times not at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1524234/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2015-12-09 Thread Uranicus

Reporting on Bluetooth bug 1500242

I have send such a report on December, 6th 2015 where I have tested the
rc-proposed with my Jabra device. At that time the syslog-file was
missing which I have added later. I found out later, that syslog is a
rolling log, therefore maybe not all test logs are part of that syslog.

I have taken the time today to retest all that with the following
devices. I attach the log files:

Audi A3 car kit (2012 model)
Seat Alhambra car kit (2012 model)
Jabra BT250 head set
Logitech bluetooth mouse LogiLink ID0078 (Compatible to BT1.1/2.0/3.0+EDR)

Before testing I deleted all existing pairings with the devices and started 
from scratch.
System Information of the device
Detailed image information of the system used for testing
system-image-cli -i:

current build number: 196
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-12-05 18:28:01
version version: 196
version ubuntu: 20151204.1
version device: 20151028-869191d
version custom: 2015–36-46-vivid


hciconfig -a

hci0:   Type: BR/EDR  Bus: UART
BD Address: 4C:74:03:64:75:ED  ACL MTU: 1021:4  SCO MTU: 184:1
UP RUNNING 
RX bytes:8537 acl:181 sco:0 events:502 errors:0
TX bytes:221664 acl:460 sco:0 commands:72 errors:0
Features: 0xbf 0x3e 0x8d 0xfe 0xdb 0xff 0x5b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'Aquaris E4.5 Ubuntu Edition'
Class: 0x7e0110
Service Classes: Networking, Rendering, Capturing, Object Transfer, 
Audio, Telephony
Device Class: Computer, Handheld
HCI Version: 4.0 (0x6)  Revision: 0x0
LMP Version: 4.0 (0x6)  Subversion: 0x0
Manufacturer: MediaTek, Inc. (70)


bluetoothctl

[NEW] Controller 4C:74:03:64:75:ED Aquaris E4.5 Ubuntu Edition [default]


[bluetooth]# show
Controller 4C:74:03:64:75:ED
Name: Aquaris E4.5 Ubuntu Edition
Alias: Aquaris E4.5 Ubuntu Edition
Class: 0x7e0110
Powered: yes
Discoverable: no
Pairable: yes
UUIDs:
  Headset AG(1112--1000-8000-00805f9b34fb)
  Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
  A/V Remote Control(110e--1000-8000-00805f9b34fb)
  SIM Access(112d--1000-8000-00805f9b34fb)
  Generic Access Profile(1800--1000-8000-00805f9b34fb)
  PnP Information   (1200--1000-8000-00805f9b34fb)
  A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
  Handsfree (111e--1000-8000-00805f9b34fb)
  Audio Source  (110a--1000-8000-00805f9b34fb)
  Dialup Networking (1103--1000-8000-00805f9b34fb)
  Audio Sink(110b--1000-8000-00805f9b34fb)
  Handsfree Audio Gateway   (111f--1000-8000-00805f9b34fb)
  Message Notification Se.. (1133--1000-8000-00805f9b34fb)
  Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0523
Discovering: no
Modifications on the device (debugging information)
sudo mount -o remount,rw /
Since no bluetooth-override file was available I used:

sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' 
/etc/init/bluetooth.conf
sudo sed -i 's/--start/--start --log-level=debug/g' 
/usr/share/upstart/sessions/pulseaudio.conf
I was not 100% sure about the ofono modifications: “Add '-d' to the exec line 
in /etc/init/ofono.override”. I have modified the line in ofono.override to:

exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

Audi A3
[bluetooth]# devices

At this time devices shows no results (nothing paired yet).

Audi A3 in search mode and the two found each other:

[bluetooth]# devices
[CHG] Controller 4C:74:03:64:75:ED Discoverable: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[NEW] Device 00:0E:9F:E8:3A:24 Audi UHV 4272   
[CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 00:0E:9F:E8:3A:24 RSSI: -49
[CHG] Controller 4C:74:03:64:75:ED Discoverable: no

Connect Audi A3 with the phone (manually press the connect button in the
bluetooth menue):

[bluetooth]# 
[CHG] Device 00:0E:9F:E8:3A:24 RSSI: -67
[bluetooth]# 
[CHG] Device 00:0E:9F:E8:3A:24 RSSI: -52
[CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discoverable: yes

8:58 h: Enter the pairing code 1234 (nothing happens)

9:00 h: Enter pairing code a second time

[CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device

[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2015-12-09 Thread Uranicus

report in odt, pdf and log files

** Attachment added: "Bug 1500242 2015_12_09.7z"

https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4531794/+files/Bug%201500242%202015_12_09.7z

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1500242

Title:
Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
with BQ Aquaris 4.5

Status in Canonical System Image:
Confirmed
Status in bluez package in Ubuntu:
Incomplete
Status in ofono package in Ubuntu:
Incomplete

Bug description:
STEPS:
Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi
car kit (A3 2012 model)

1. Put Jabra BT250 into receiving mode
2. Phone searches automatically every 15 - 30 seconds for a new blue tooth
device
3. Phone finds Jabra BT250 and asks for pairing code
4. Enter code into phone
5. Jabra BT250 automatically exits the pairing mode (which is a sign that
pairing should have worked)
6. Phone looses connection to Jabra BT250
7. Manual reconnection via phone works (shows Jabra BT250 as being connected)
but ignores the device

Same behaviour with Audi car kit (Audi A3, 2012 model)

EXPECTED:
I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012
model) where the blue tooth pairing etc. works great (except some bugs which
are already filed).

ACTUAL:
No connection to the blue tooth device

VERSIONS:
OS-Build-Number: 25
Ubuntu-Image: 20150825.1

POSSIBLE ROOT CAUSE:
Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

1 2 >

1 - 100 of 166 matches

Mail list logo