[Bug 711561] Re: Compiz won't allow Desktop Cube plugin to load with unity

2011-03-07 Thread yoghurt_lx
"Wishlist" and "Opinion" is a loss of functions now called ?
The Cube is an important eye candy and feature which has brought many new users 
to Linux and Ubuntu.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711561

Title:
  Compiz won't allow Desktop Cube plugin to load with unity

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 495930] Re: Cambridge Silicon Radio Bluetooth Dongle gives permanent Connection timed out with Ubuntu 9.10

2010-01-18 Thread yoghurt_lx
First the bad news, it doesn't work with bluez 4.60-0ubuntu4.1
Same problem as with 4.570ubuntu1

I have not much idea of how to use 'git bisect', but thats only for now.
Have to take a closer look at it.

That this Dongle doesn't work with the latest bluez package is for my self not 
really a problem.
But I convinced several friends in Thailand to give up there illegal Windows 
copy's and use Ubuntu instead.
Now from the ~20 guys I moved to Ubuntu, most of them have this Dongle and 
would like to use it.
Hard to convince someone that Ubuntu is better if there Bluetooth Dongle 
doesn't work and hard to show them how they can make it work. They all have 
simply not much knowledge and that creates for me a lot extra work when I have 
to visit them to change the bluez package back, because the update did install 
the latest version.

-- 
Cambridge Silicon Radio Bluetooth Dongle gives permanent Connection timed out 
with Ubuntu 9.10
https://bugs.launchpad.net/bugs/495930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 495930] Re: Cambridge Silicon Radio Bluetooth Dongle gives permanent Connection timed out with Ubuntu 9.10

2010-01-15 Thread yoghurt_lx
Continuing of my self conversation.

Found out that changing only the package bluez from version 4.570ubuntu1
to version 4.32-0ubuntu4 is enough to make it work in that case.

How to:
Go to http://packages.ubuntu.com/jaunty/bluez, select your Architecture (amd64 
or i386) and download the package.
Open the Synaptic package administration, search for bluez and remove bluez 
there.
Removing bluez will also remove other packages, notice that because you have to 
reinstall them later.
After removing bluez close the Synaptic (only one instance can run) and install 
the downloaded package (bluez 4.32-0ubuntu4)
A double click in the folder where you downloaded the package 
bluez_4.32-0ubuntu4_i386.deb starts the Debian package installer and ignore the 
warning that a newer version is available.
Now open and reinstall in the Synaptic package administration all other 
packages which got former uninstalled with bluez.

Thats fairly easy once you know it and can even be done by someone without much 
knowledge.
Nevertheless, it would be fine to have a fix for that. Can't be that hard to 
compare this versions to see why this Dongle stopped working.
Well, maybe I start with that on my own too when I see the activity here which 
remembers me of a cemetery.

-- 
Cambridge Silicon Radio Bluetooth Dongle gives permanent Connection timed out 
with Ubuntu 9.10
https://bugs.launchpad.net/bugs/495930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 495930] Re: Cambridge Silicon Radio Bluetooth Dongle gives permanent Connection timed out with Ubuntu 9.10

2009-12-17 Thread yoghurt_lx
Reverted bluez packages back to the version that is used with the Ubuntu
9.04 Live CD (4.32-0ubuntu4) and now the Dongle works also with 9.10
perfectly.

Changing packages bluez, bluez-compat, bluez-utils, bluetooth from version 
4.570ubuntu1 to version 4.32-0ubuntu4 did do the job and that would indicate it 
is indeed a bluez bug and not related to something else.
I hope there will be a fix for this dongle in future and if they are any 
questions or something I can help with feel free to ask.
I will watch for updates at the bluez PPA and report back if this dongle starts 
working with a newer version.

-- 
Cambridge Silicon Radio Bluetooth Dongle gives permanent Connection timed out 
with Ubuntu 9.10
https://bugs.launchpad.net/bugs/495930
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 495930] [NEW] Cambridge Silicon Radio Bluetooth Dongle gives permanent Connection timed out with Ubuntu 9.10

2009-12-12 Thread yoghurt_lx
Public bug reported:

Binary package hint: bluez

---Ubuntu 9.10---
Description:Ubuntu 9.10
Release:9.10
:~$ uname -r
2.6.31-16-generic

Packages:
bluez 4.57-0ubuntu1
bluetooth 4.57-0ubuntu1

USB Devices:
:~$ lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 03f0:1712 Hewlett-Packard Printing Support
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 045e:0038 Microsoft Corp. SideWinder Precision 2
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
Bus 003 Device 006: ID 0a5c:3500 Broadcom Corp. 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

:~$ sudo hciconfig -a
hci0:   Type: USB
BD Address: 00:1B:10:00:06:75 ACL MTU: 377:10 SCO MTU: 16:0
UP RUNNING 
RX bytes:646 acl:0 sco:0 events:16 errors:0
TX bytes:67 acl:0 sco:0 commands:17 errors:0
Features: 0xff 0xff 0x0d 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: 
Link mode: SLAVE ACCEPT 
Can't read local name on hci0: Connection timed out (110)

:~$ sudo hcitool inq
[sudo] password for tank: 
Inquiring ...
Inquiry failed.: Connection timed out


Log Files I got:

Messages:
Dec 12 21:56:15 kernel: [  683.120066] usb 3-1: new full speed USB device using 
uhci_hcd and address 6
Dec 12 21:56:15 kernel: [  683.280252] usb 3-1: configuration #1 chosen from 1 
choice
Dec 12 21:56:15 kernel: [  683.283122] hub 3-1:1.0: USB hub found
Dec 12 21:56:15 kernel: [  683.295061] hub 3-1:1.0: 3 ports detected
Dec 12 21:56:16 kernel: [  683.602220] usb 3-1.1: new full speed USB device 
using uhci_hcd and address 7
Dec 12 21:56:16 kernel: [  683.776189] usb 3-1.1: configuration #1 chosen from 
1 choice
Dec 12 21:56:16 kernel: [  683.867946] usb 3-1.2: new full speed USB device 
using uhci_hcd and address 8
Dec 12 21:56:21 kernel: [  689.073997] usb 3-1.2: new full speed USB device 
using uhci_hcd and address 9
Dec 12 21:56:21 kernel: [  689.196165] usb 3-1.2: configuration #1 chosen from 
1 choice
Dec 12 21:56:21 kernel: [  689.209110] input: HID 0a5c:3502 as 
/devices/pci:00/:00:04.3/usb3/3-1/3-1.2/3-1.2:1.0/input/input8
Dec 12 21:56:21 kernel: [  689.209345] generic-usb 0003:0A5C:3502.0004: 
input,hidraw1: USB HID v1.11 Keyboard [HID 0a5c:3502] on 
usb-:00:04.3-1.2/input0
Dec 12 21:56:21 kernel: [  689.282004] usb 3-1.3: new full speed USB device 
using uhci_hcd and address 10
Dec 12 21:56:22 kernel: [  689.434147] usb 3-1.3: configuration #1 chosen from 
1 choice
Dec 12 21:56:22 kernel: [  689.457110] input: HID 0a5c:3503 as 
/devices/pci:00/:00:04.3/usb3/3-1/3-1.3/3-1.3:1.0/input/input9
Dec 12 21:56:22 kernel: [  689.457364] generic-usb 0003:0A5C:3503.0005: 
input,hidraw2: USB HID v1.11 Mouse [HID 0a5c:3503] on 
usb-:00:04.3-1.3/input0

kern.log:
Dec 12 21:59:16 kernel: [  864.083825] hci_cmd_task: hci0 command tx timeout
Dec 12 22:01:10 kernel: [  978.278941] hci_cmd_task: hci0 command tx timeout

daemon.log:
Dec 12 21:56:16 bluetoothd[4125]: Bluetooth daemon 4.57
Dec 12 21:56:16 bluetoothd[4127]: Starting SDP server
Dec 12 21:56:16 bluetoothd[4127]: Can't load plugin 
/usr/lib/bluetooth/plugins/netlink.so: /usr/lib/bluetooth/plugins/netlink.so: 
undefined symbol: debug
Dec 12 21:56:16 NetworkManager:SCPlugin-Ifupdown: devices added (path: 
/sys/devices/virtual/net/pan0, iface: pan0)
Dec 12 21:56:16 NetworkManager:SCPlugin-Ifupdown: device added (path: 
/sys/devices/virtual/net/pan0, iface: pan0): no ifupdown configuration found.
Dec 12 21:56:16 NetworkManager:   device_creator(): 
/sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring...
Dec 12 21:56:16 bluetoothd[4127]: bridge pan0 created
Dec 12 21:56:16 bluetoothd[4127]: HCI dev 0 registered
Dec 12 21:56:16 bluetoothd[4127]: HCI dev 0 up
Dec 12 21:56:16 bluetoothd[4127]: Starting security manager 0
Dec 12 21:56:16 bluetoothd[4127]: Parsing /etc/bluetooth/serial.conf failed: No 
such file or directory
Dec 12 21:56:16 bluetoothd[4127]: Adapter /org/bluez/4125/hci0 has been enabled
Dec 12 21:59:16 bluetoothd[4127]: Discovery session 0x190e9e0 with :1.67 
activated
Dec 12 22:01:10 bluetoothd[4127]: Stopping discovery

syslog:
Dec 12 21:56:15 kernel: [  683.120066] usb 3-1: new full speed USB device using 
uhci_hcd and address 6
Dec 12 21:56:15 kernel: [  683.280252] usb 3-1: configuration #1 chosen from 1 
choice
Dec 12 21:56:15 kernel: [  683.283122] hub 3-1:1.0: USB hub found
Dec 12 21:56:15 kernel: [  683.295061] hub 3-1:1.0: 3 ports detected
Dec 12 21:56:16 kernel: [  683.602220] usb 3-1.1: new full speed USB device 
using uhci_hcd and address 7
Dec 12 21:56:16 kernel: [  683.776189] usb 3-1.1: configuration #1 chosen from 
1 choice
Dec 12 21:56:16 bluetoothd[4125]: Bluetoot