[kio] [Bug 336397] Getting "Unknown error code 150" when opening USB connected Android device in MTP mode

2016-10-08 Thread Fred via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=336397

Fred  changed:

   What|Removed |Added

 CC||frederic@laposte.net

--- Comment #5 from Fred  ---
Same behavior here, in mtp mode.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Bluedevil] [Bug 364223] Failure to connect bluetooth headphones

2016-06-11 Thread Fred via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364223

--- Comment #4 from Fred  ---
Perhaps this is a suitable bug for Neon?

-- 
You are receiving this mail because:
You are watching all bug changes.


[Bluedevil] [Bug 364223] Failure to connect bluetooth headphones

2016-06-11 Thread Fred via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364223

--- Comment #3 from Fred  ---
Actually I apologize... I recognize that if I'm having problems with
bluetoothctl it's not a bluedevil issue... I'm a little slow sometimes. If you
happen to be able to help I would appreciate it! If not, I understand.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Bluedevil] [Bug 364223] Failure to connect bluetooth headphones

2016-06-11 Thread Fred via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364223

--- Comment #2 from Fred  ---
Thanks for prompt reply.

I do not believe that this is a kernel issue since this was working in
kubuntu-16.04 LTS this morning, which as far as I know uses the same kernel
version as Neon (currently running 4.4.0-24-generic). I believe bluez should
also be the same version...

The reason this *might* be a bug for you is that I would guess that I'm running
a later bluedevil version than I was running this morning as I'm now on neon
"developer edition" (which I may be the underlying issue here afaik).

I have not been successful using bluetoothctl to connect... here's my current
status (device-id redacted):

[bluetooth]# info [device-id redacted]
Device [device-id redacted]
Name: Bose AE2 SoundLink
Alias: Bose AE2 SoundLink
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Bose Corporation (id redacted)

-- 
You are receiving this mail because:
You are watching all bug changes.


[Bluedevil] [Bug 364223] New: Failure to connect bluetooth headphones

2016-06-11 Thread Fred via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364223

Bug ID: 364223
   Summary: Failure to connect bluetooth headphones
   Product: Bluedevil
   Version: 5.6.4
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: fredisa4letterw...@gmail.com

When going through bluetooth "Add device" wizard, select my Bose AE2 SoundLink
headphones, which fail to install.



Reproducible: Always

Steps to Reproduce:
0. "Forget device" if listed
1. Turn on Bose AE2 SoundLink headphones 
2. Run "Add Device" wizard
3. select "Bose AE2 SoundLink"

Actual Results:  
Wizard takes a while (~10s) and then says "The setup of Bose AE2 SoundLink has
failed"

dmesg says: "Bluetooth: SMP security requested but not available."

bluetoothctl says: "Device [device id] Connected: yes"

>From KDE Control Module, device appears as connected, but displays "Type:
Unknown"

Audio does not work.

Expected Results:  
>From KDE Control Module, device should appear as "Type: Headphones" or "Type:
Audio" or something known.

Audio should work.

Don't want to be overly dramatic with the "Grave" severity, but bluetooth audio
is unusable for me today after doing a fresh install today... was working with
kubuntu 16.04 this morning so possibly an issue for Neon.

-- 
You are receiving this mail because:
You are watching all bug changes.