News

All news

The latest update to Raspbian

No exciting new hardware announcement to tie it to this time, but we’ve just released a new version of our Raspbian image with some (hopefully) useful features. Read on for all the details of what has changed…

Bluetooth

When the Pi 3 launched back in February, we’d not had time to do much in terms of getting access to the new onboard Bluetooth hardware. There was a working software stack, but the UI was non-existent.

I’d hoped to be able to use one of the existing Linux Bluetooth UIs, but on trying them all, none were really what I was looking for in terms of usability and integration with the look and feel of the desktop. I really didn’t want to write one from scratch, but that ended up being what I did, which meant a fun few weeks trying to make head or tail of the mysteries of BlueZ and D-Bus. After a few false starts, I finally got something I felt was usable, and so there is now a Bluetooth plugin for the lxpanel taskbar.

btmenu

On the taskbar, to the left of the network icon, there is now a Bluetooth icon. Clicking this opens a menu which allows you to make the Pi discoverable by other devices, or to add or remove a Bluetooth device. Selecting the ‘Add Device…’ option opens a window which will gradually populate with any discoverable Bluetooth devices which are in range – just select the one you want to pair with and press the ‘Pair’ button.

btdialog

You will then be guided through the pairing procedure, the nature of which depends on the device. With many devices (such as mice or speakers), pairing is entirely automatic and requires no user interaction; on others you may be asked to enter a code or to confirm that a code displayed on a remote device matches that shown on the Pi. Follow the prompts, and (all being well), you should be rewarded with a dialog telling you that pairing was successful.

Paired devices are listed at the end of the Bluetooth menu – these menu entries can be used to connect or disconnect a paired device. To remove a pairing completely, use the ‘Remove Device…’ option in the menu.

Bluetooth support is limited at this stage; you can pair with pretty much anything, but you can only usefully connect to devices which support either the Human Interface Device or Audio Sink services – in other words, mice, keyboards and other UI devices, and speakers and headsets.

Devices should reconnect after a reboot or on powering up your Pi, but bear in mind that keyboards and mice may need you to press a key or click the mouse button to wake them from sleep when first used after a power-up.

The Bluetooth UI should also work with an external Bluetooth dongle on platforms other than Pi 3 – I’ve successfully tested it with a Targus dongle on all the earlier platforms.

Bluetooth audio

The UI now supports the use of Bluetooth speakers and headsets for audio output, with a few caveats, about which more below.

To connect an audio device, you pair it as described above – it will then be listed in the audio device menu, accessible by right-clicking the speaker icon on the taskbar.

audiomen

Selecting a Bluetooth device from the audio device menu will cause it to be selected as the default audio output device – there will be a few seconds’ pause while the connection is established. You can then use the volume control on the taskbar to control it, as for standard wired audio devices.

There is one issue with the support for Bluetooth audio, however. Due to the way the Bluetooth stack has been written, Bluetooth devices do not appear to the system as standard ALSA audio devices – they require the use of an intermediate audio layer called PulseAudio. The PulseAudio magic is all built into the UI – you don’t need to worry about setting it up – but the problem is that not all applications are able to send audio to the PulseAudio interface, and therefore cannot output audio over Bluetooth.

Most applications work just fine – videos and music work in the Epiphany and Iceweasel browsers, as does the command-line mplayer music player and the vlc media player. But at present neither Scratch nor Sonic Pi can output audio over Bluetooth – we are working with the authors of these programs to address this and are hopeful that both can be made compatible, so please bear with us!

The use of PulseAudio has one other effect that may cause issues for a small number of users – specifically, if you are already using PulseAudio for anything other than interfacing with Bluetooth devices. This plugin will automatically stop the PulseAudio service whenever a standard ALSA device is selected. If you are using PulseAudio for your own purposes, it would be best to remove the volumealsa plugin from the taskbar completely to avoid this – just right-click anywhere on the taskbar, choose ‘Add/Remove Panel Items’, and remove the “Volume Control (ALSA)” item from the list.

SD card copier

One query which comes up a lot on the forums is about the best way to back up your Pi. People also want to know how to migrate their Raspbian install to a new SD card which is larger or smaller than the one they are using at the moment. This has been difficult with the command-line tools that we’ve recommended in the past, so there is now a new application to help with this, and you’ll find it in the menu under ‘Accessories’.

sdcc

The SD Card Copier application will copy Raspbian from one card to another – that’s pretty much all it does – but there are several useful things that you can do as a result. To use it, you will need a USB SD card writer.

To take a common example: what if you want to back up your existing Raspbian installation? Put a blank SD card in your USB card writer and plug it into your Pi, and then launch SD Card Copier. In the ‘Copy From Device’ box, select “Internal SD Card”, and then select the USB card writer in the ‘Copy To Device’ box (where it will probably be the only device listed). Press ‘Start’, watch the messages on the screen and wait – in ten or fifteen minutes, you should have a clone of your current installation on the new SD card. You can test it by putting the newly-copied card into the Pi’s SD card slot and booting it; it should boot and look exactly the same as your original installation, with all your data and applications intact.

You can run directly from the backup, but if you want to recover your original card from your backup, simply reverse the process – boot your Pi from the backup card, put the card to which you want to restore into the SD card writer, and repeat the process above.

The program does not restrict you to only copying to a card the same size as the source; you can copy to a larger card if you are running out of space on your existing one, or even to a smaller card (as long as it has enough space to store all your files – the program will warn you if there isn’t enough space). It has been designed to work with Raspbian and NOOBS images; it may work with other OSes or custom card formats, but this can’t be guaranteed.

The only restriction is that you cannot write to the internal SD card reader, as that would overwrite the OS you are actually running, which would cause bad things to happen.

Please also bear in mind that everything on the destination card will be overwritten by this program, so do make sure you’ve got nothing you want to keep on the destination card before you hit Start!

pigpio

This image includes the pigpio library from abyz.co.uk – this provides a unified way of accessing the Pi’s GPIO pins from Python, C and other languages. It removes the need to use sudo in programs which want to access the GPIOs, and as a result Scratch now runs sudo-less for everyone.

Geany

One of the tools which is really useful for professional programmers is a good text editor – the simple editor provided with LXDE is fine for small tasks, but not really suitable for serious work.

geany

The image now includes the Geany editor, which is much better suited to big projects – it offers features like syntax highlighting, automatic indentation and management of multiple files. There’s good online help built into the program itself, or have a look at the Geany website.

New versions of applications

There are new versions of many of the standard programs included in the image, including Scratch, Sonic Pi, Node-RED, BlueJ and PyPy. Please see the relevant individual websites or changelists for details of what has changed in each of these.

New kernel

The Linux kernel has been upgraded to version 4.4. This change should have no noticeable effect for most users, but it does force the use of device tree; if you’ve been hacking about with your Raspbian install, particularly in terms of installing new hardware, you may find reading this forum post useful.

Tweaks

There are a lot of small user interface tweaks throughout the system which you may notice. Some of these include:

• A new Shutdown Options dialog

shutdown

• The Mouse and Keyboard Settings dialog now allows you to set the delay between double-clicks of the mouse button

mandk

• The Raspberry Pi Configuration dialog now allows you to enable or disable the single-wire interface, and to enable or disable remote access to the pigpio daemon

rcgui

• Right-clicking the Wastebasket icon on the desktop now gives the option to empty the wastebasket

ewaste

• The keyboard shortcut Ctrl-Alt-T can now be used to open a Terminal window

Finally, there are a couple of setup-related features:

• When flashing a new Raspbian image, the file system will automatically be expanded to use all the space on the card when it is first booted.

• If a wpa_supplicant.conf file is placed into the /boot/ directory, this will be moved to the /etc/wpa_supplicant/ directory the next time the system is booted, overwriting the network settings; this allows a Wifi configuration to be preloaded onto a card from a Windows or other machine that can only see the boot partition.

There are also a host of fixes for minor bugs in various parts of the system, and some general cleaning-up of themes and text.

How do I get it?

A full image and a NOOBS installer are available from the Downloads page on this website.

If you are running the current Jessie image, it can be updated to the new version by running

sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install piclone geany usb-modeswitch pi-bluetooth
sudo apt-get install python-pigpio python3-pigpio

and then rebooting.

Edit – I’d omitted to show that the Python bindings for pigpio needed to be added as part of an upgrade – now added to the line above.

As ever, your feedback on the new release is very welcome – feel free to comment here or in the forums.

Updates

Some users who are using a remote desktop on the Pi have found that the taskbar keeps crashing. This has been traced to a security policy on the bus used to communicate with the Bluetooth hardware; to fix it, configure the Pi to autologin (using either the Raspberry Pi Configuration desktop application or raspi-config). Alternatively, update the security policy by editing /etc/dbus-1/system.d/bluetooth.conf – change the third line from the end from <deny send_destination="org.bluez"/> to <allow send_destination="org.bluez"/>.

Some users are also reporting that no Bluetooth controller is found on a Pi 3 after updating. This seems to be linked to the package which adds the Pi-specific Bluetooth support (which was added in the software release to support the Pi 3 earlier this year) somehow becoming uninstalled. The fix is to reinstall it – sudo apt-get install pi-bluetooth and reboot should enable the controller to be found.

324 comments

Awesome, thank you!

piclone doesn’t appear to be available yet

sudo apt-get install piclone
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package piclone

Give it a little while. The load balancers need to sync up.
Edit: Should be good now.

No I still get an error:

root@pi2:~# sudo apt-get install piclone geany usb-modeswitch
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package piclone

Exciting updates. Especially wpa_supplicant, Bluetooth GUI and pigpio are awesome!

This looks like the update that we’ve all been looking for – pigpio being included by default could be a massive boost

Great work, Simon. :-)

Does this include any updates to the opensource graphics stack?

No, no updates to that in this release.

The kernel has been updated, so there could be performance or stability fixes there. The user libraries are unchanged.

The kernel has been updated so there may be performance or stability fixes there. The user libraries are unchanged.

The base system is starting to become quite complete out-of-the-box just a shame we are still using Gtk2 on X11

Wow – so many useful new features – Raspbian is getting better and better! I especially like the SD card copier: Sometimes I had problems duplicating my Distro for workshops, because of the slightly different sizes of my 16 GB Micro SD-cards, I hope this tool fixes it.
Also good to hear that even you couldn’t get Sonic Pi to work woth bluetooth audio – I always thought I did something wrong. :)
Keep up the good work!

SD Card Copier – excellent.
By far the easiest way I have found to upgrade my 4GB card to a new 32GB card.
The old 4GB becomes my backup.

Is the /boot/wpa_supplicant trick compatible with the NOOBS Installer, or only with a direct .IMG installation?

(Because with a NOOBS Installation the /boot partition for Raspbian is not accessible from Windows.)

This will not work with NOOBS. However, if you connect to wifi in NOOBS before installing the OS, that will create a wpa_supplicant.conf file and install it.

Serge – you forgot https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=141270#p936532

If you put your wpa_supplicant.conf file on the NOOBS partition, NOOBS will use it for itself, but it will only work with the Broadcom wifi dongles that NOOBS supports.

Nevertheless, If you use the FULL NOOBS download (which includes Raspbian) you can add a single line to the /os/Raspbian/partition_setup.sh script to copy the file into Raspbian as well.

Re: wpa_supplicant. NOOBS documentation says it should work:

https://github.com/raspberrypi/noobs/blob/master/README.md#preconfiguring-a-wifi-network

“If you already know your WiFi details, you can preconfigure NOOBS to use it straight away. Put a copy of your wpa_supplicant.conf file on the NOOBS root partition and NOOBS will read it and store it in its settings for all future uses.”

Sorry: asked before reading. But reply is in conflict…

Yes, it will with the FULL NOOBS. Just add 1 line to partition_setup.sh. See https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=141270#p936532

Does this fix the problem with RS485 hats not working without all sorts of shenanigans on the Pi3?

Would this be the same problem I am seeing with the SPI clock speed changing with the cpu load (governor)?

I haven’t tried this yet: but the screenshots and description of the bluetooth tools looks great : I’ve found it difficult to get easy-to-use/understand/reliable bluetooth utils (cmdline or GUI) on Linux (of all types) – hopefully this will help pave the way for a better bluetooth stack/tools on Linux (beyond the Pi even….)

Nice one !

Simon is a little treasure, isn’t he?

Give him a hug from us ;-)

Is the source of the Bluetooth GUI available somewhere? I’ve got a headless project that would benefit from some of the functionality provided here so I’d really love to see how they got it work!

It’s in a plugin called “bluetooth” for lxpanel. Make sure you can get source from apt by editing the files in /etc/apt and doing an apt-get update – then do apt-get source lxpanel. All the relevant code for discovery, pairing and connecting is in plugins/bluetooth, with the code for using audio devices in plugins/volumealsa.

Alternatively, all the source is in our GitHub repository – https://github.com/raspberrypi/lxpanel

Also the SD-backup looks like a great solution for a common requirement !

Really, well done !

This is fantastic and addresses so many of the little niggles and use cases I have with Raspbian.

Bluetooth – been having fun on Pi3 to get Bluetooth audio working. Hoping with this Bluetooth audio will be easy.

SD Copier – Brilliant. I’ve an old small SD with lots of customisation that I’d love to get on a bigger SD to continue using it. Now easy.

pigpio – Sudo Less everywhere.

Geany – It’s one of the first things I install. You can change the preference so that the [tab] key does 4 spaces. Making it easy to be consistent and gain the benefit of tabbing for python indents.

Excited to try the new applications.

New Kernel – Wonder if this will this help support 3D graphics in the future?

New shutdown menu. Update is worth it for this alone. I kept clicking on the words and not the radio button. Great it’s now nice big buttons.

Config Menu – great to see more control from the GUI

Wastebin – Every time I right click to empty. Now it will work!

Wifi set up on boot. Brilliant. At a recent event I needed to set up Wifi on a headless setup but couldn’t SSH in until it was on the network and couldn’t get it on the network until I could SSH in and update the config. Now really simple.

One other great thing about the new shutdown options menu is that if you open it and hit enter, it’ll shut the system down. I’ve been hoping for this feature for a while! (My MacOS habits are showing.) Thanks Simon!

The SHA-1 checksum for NOOBS_V1_9_1.zip is WRONG!
Downloads page says:
66a50545358e80229d77ebba89ab01f1c0fb4a02
but after downloading I get:
5bace3d2e1440ecb19bfa7760d299b5bb7c76981

I checked it twice. I guess the most likely explanation is that someone forgot to update the website info, rather than it being a hack…

Thanks, fixed.

Great release!

Will the SD Card Copier work from the common line?

If you’d like to copy your raspbian lite install for instanse.

No, it’s GUI-only. I did originally write a command-line script to test the functionality, though – I’ll look at including that in a future release.

Where is the source available for the SD card copier?
Is it guaranteed to backup a running system reliably?

Source is in the repo (http://archive.raspberrypi.org/debian/pool/ui/p/piclone/, it’s the xz archive). Pulling the source through apt-get source after uncommenting the deb-src in raspi.list should work too

“Guaranteed” is a very strong word! I’ve tested it on various running systems, and it has never yet failed to produce a working backup – that doesn’t mean I can offer a 100% guarantee though… It’s easy enough to test the backup it creates – just try and boot off the card it produces.

I recently wrote a bash script to shrink and backup sd card images, in which I took an approach to pop the sd card in another linux computer, after which I measure and calculate the minium size, after which I first shrink the partition, and than the filesystem. Than I write an image of the relevant blocks to create an image as small as possible. It works, and obviously avoids backup of live systems.
As this is about learning and sharing, I have posted it below. Let me know what could be improved upon.

#!/bin/bash -e
#######!/bin/bash -ex # The x is to be used for debugging.

#——————————————————————————
#
# 9 may 2016, backuPi.sh
#
#
# Calculates the minimum size of the sd card, and then resizes filesystem
# and partition.
# Subsequently creates an image of the relevant partitions space.
#
#
#
#——————————————————————————

function calcMiB()
{
# Calculate size in MiB, for easier reading.
local partsizeblocks=$1
local KBperblock=$2
local partsizeKiB=$(( ${partsizeblocks} * ${KBperblock} ))
local quotientMiB=”$(( (${partsizeblocks} * ${KBperblock}) / 1024 ))”
local modulusMiB=$(( ($partsizeKiB – ($quotientMiB * 1024))*1000/1024))
local modulusMiB2=”$(( (${partsizeblocks} % ${KBperblock}) / 1024))”
echo “${quotientMiB},${modulusMiB} MiB.”
}

# check which drive is the sd card:
echo “Please select the drive you want to format and write an image to.”
echo “The following filesystems have been found:”
lsblk
read -e -p “Which blockdevice: ” -i “sdc” myblkdev
read -e -p “Which partition do you want to shrink: ” -i “2” targetpartnr
targetpart=”${myblkdev}${targetpartnr}”

# Unmount directories, otherwise online shrinking from resize2fs would be
# required but this throws an error.
if grep -s “${myblkdev}” /proc/mounts
then
echo “Start unmounting partitions”
sudo umount -v “/dev/${myblkdev}”? # Questionmark is wildcard.
fi

# Check the filesystem/partition.
sudo e2fsck -fy “/dev/${targetpart}”

myblockcount=$(sudo tune2fs -l “/dev/${targetpart}” | grep ‘Block count’ | awk ‘{print $3}’)
myfreeblocks=$(sudo tune2fs -l “/dev/${targetpart}” | grep ‘Free blocks’ | awk ‘{print $3}’)
myblocksize=$(sudo tune2fs -l “/dev/${targetpart}” | grep ‘Block size’ | awk ‘{print $3}’)
mysectorsize=$(sudo sfdisk -l “/dev/${myblkdev}” | grep Units | awk ‘{print $8}’)
mystartsector=$(sudo fdisk -l “/dev/${myblkdev}” | grep “${targetpart}” | awk ‘{print $2}’)

# Calculate the smallest partition size, in blocks.
myusedblocks=$(( $myblockcount – $myfreeblocks ))
# Calculate target partion size, adding a bit of margin, about 8%.
mytargetblocks=$(( $myusedblocks + ($myusedblocks * 2 / 25) ))

# Calculate KiB per block to aid further calculation in KiB’s:
if (( “${myblocksize}” >= “1024” ))
then
KBperblock=$(( $myblocksize/1024 ))
else
echo “Blocksize is awkward: ${myblocksize}. Not sure what to do, stopping.”
exit
fi

# Round up new part size to multiple of blocksize to facilitate creation.
mynewpartsize=$(( (($mytargetblocks + $KBperblock-1) / $KBperblock) * $KBperblock ))

# Calculate and print the existing data and target partition size.
echo “”
echo “The size of the data on partion /dev/${targetpart} is \
$( calcMiB ${myusedblocks} ${KBperblock} )”
echo “”
echo “The new size of the data on partion /dev/${targetpart} will be \
$( calcMiB ${mytargetblocks} ${KBperblock} )”
echo “”

# Calculate multiplier from sector size to block size
sectorsperblock=$(( $myblocksize/$mysectorsize ))
# Calculate end point in sectors, that is what fdisk requires.
mynewendpoint=$(( $mystartsector + ($mynewpartsize * $sectorsperblock) ))

# Start execution:
# Resize the filesystem, values in 1024 bytes, see the “K” at the end.
# Example, if blocksize was 4096, nr of blocks x 4 is the resize value.
sudo resize2fs -fp “/dev/${targetpart}” $(( $mynewpartsize * $KBperblock ))K
# Resize partion, to make matters complicated values are in sector sizes.
# NB, the -s switch does not work, putting Yes after the command is the work around.
sudo parted “/dev/${myblkdev}” unit s resizepart “${targetpartnr}” “${mynewendpoint}” yes
sync

# Mounting the drives does not work: error looking up object with path ….
#udisksctl mount -p block_devices/sdc1
#udisksctl mount -p block_devices/sdc2
#udisksctl mount -b /dev/sdc1
#udisksctl mount -b /dev/sdc2

# Backup resized image
read -e -p “Backup the resized image? [Y/N] ” -i “Y” backupchoice

if [[ “${backupchoice}” =~ ^([yY][eE][sS]|[yY])$ ]]
then
mkdir -p ~/backups
read -e -p “Filename :” -i “$(date +%g%m%d)-raspbianbackup.img” Pibackupname
sudo dd if=”/dev/${myblkdev}” | pv | sudo dd of=~/backups/”${Pibackupname}” bs=512 count=”${mynewendpoint}”
echo “Backup succesfull.”
fi
exit

A WARNING about the script by
abracadabricx says: 23rd May 2016 at 5:40 pm

I foolishly cut & paste from firefox and tried to run this copy script on an Orange Pi PC.

firefox (or HTML5) changed the quotes and the minus sign ( hyphen) to unrecognized characters.
This results in the source SD card being resized to 0 sectors! Makes it unreadable, but it did succeed in a new dd to the card to start over.

Source is at https://github.com/raspberrypi/piclone and also as a source package in the apt repo.

It’s a file-level copy process, so it should be pretty safe on an idle desktop. Running it at the same time as an apt-get upgrade is definately a bad idea. Running it on a high-traffic database server will probablly end up with a corrupt DB in the backup.

> guaranteed to backup a running system reliably

Only shutting down the system, removing the card, and running a bit-level copy (and check the hashes) can guarantee this. Sometimes a best-effort attempt is helpful, though — and we should recognize it as such. (As both helpful and an attempt, not a perfect solution.)

> we should recognize it as such

Yes, I agree it is a very useful start and it will probably work fine in 99% of cases. But users should be aware its limitations and always check their backups.

It is also limited to copying the first 9 partitions, so it’s fine if you have a triple boot NOOBS card, but a quad boot (as recently seen in the forums) would not be fully copied.

I’m looking forward to the CLI version as the systems I most want to clone are cluster nodes without display, keyboard, or mouse.

isn’t that the command line verion you are looking for:
https://github.com/raspberrypi/piclone/blob/master/src/backup
the graphical front end is useing that script – so it should be possible to use that script without any GUI.

What are the Scratch updates, please, or where can I find details on them?

I’ll post some info to the Scratch forum shortly – it’s only just waking up time here on my island.

Thanks, Tim. Yes, I do always try to remember the time difference when ‘talking’ to you!

Can we have an updated Arduino IDE please.

Amazing :D now all I need is pi zero’s to be back in stock, and my life will be complete

See https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=147994

Great update, good work. I’m a big Geany user – I’m pleased to see it added.

Nice release, the OpenGL 2.1 update (mesa 11.1) works fine! Insignificant remark: a Geany entry in the context menu of PCManFM near the default Text Editor would be useful to quickly open files.

That SD Card Copier tool is epic! Must start using the desktop more.

Great to see Raspbian continuing to grow bigger and better, thank you!

Could you provide a link to the Scratch changelist please? The site search returns only this page for that query. Thank you!

Any news about PXE booting? You remember this: “Gordon rewrote the boot ROM for the chip and then provided an updated boot ROM to Broadcom, saying ‘shove this in the chip, it’ll work’,” Eben laughs. “And it does!”

Thanks for these updates!

A little finessing to do there yet – but keep an eye on this blog for more on the subject!

I periodically go to the office and shout at the developers implementing it and tell them to hurry up.

It’s not clear if this is helping or not.

You know that bit where sometimes you buy us beer? THAT helps.

Bummer about audio requiring PulseAudio. I’m running jack over alsa and it would have been nice to have the option of outputting to a BT device. Having PulseAudio disabled won’t affect the ability to pair BT keyboard/mice will it?

PulseAudio is only started when you connect to a bluetooth audio device (and stopped afterwards). It’s not used or required otherwise, so keyboards and mice will work without problems.

Are you able to provide a clue to enabling pulseaudio to work with CubicSDR? Here’s a link to the CubicSDR wiki: .

It’s amazing that CubicSDR runs so well on the RPi3 under jessie! Anyone wishing to build CubicSDR is welcome to request via e-mail the script I used/created.

I was surprised to find that CubicSDR would run on the Raspberry Pi3. Although a bit slow, and tending to overheat the Pi, it looks to be usable. It was necessary to reduce the Sample Rate to prevent buffer overflow.

The present issue is getting CubicSDR audio out. It appears to possibly be the result of the current (4.4.11-v7+) Debian Jessie release default configuration of PulseAudio. This is apparently currently under active development from the information here: https://www.raspberrypi.org/blog/another-update-raspbian/ . Killing and restarting the PulseAudio daemon successfully produced CubicSDR Audio: /bin/sh /usr/bin/start-pulseaudio-x11 .

When I access remotely using xrdp or nomachine I don’t get the taskbar. Please can someone tell me how to fix this.

I have the same problem.

No idea how to fix it, but I’m experiencing the same problem.

The same problem on my r-pi2. I tried autologin and install bluetooth package, but problem is still here

I have 4 Raspy’s 1xB 2xB2 1xB3 and I get 4 different results from the upgrade. Raspi-config is showing at least two different menus. I use rdesktop and xrdp on all. On one of the B2 I get correct X screen. On the B I get no indication of a taskbar at all. On the second B2 I get no indication of a taskbar. On the B3 I get no indication of a taskbar. In the past I have seen blank taskbars flashing (with associated icon movement) before all signs of the taskbar disappears. I usually access the pi’s via ssh but sometimes need X access. A fix for this would be greatly appreciated.
Using

Look at the section titled “Updates” at the bottom of the original blog post above – there are two possible fixes for this.

I solved problem by downgrade to 4.1.x kernel.

Great, can’t wait to get home and retest Full Minecraft with the latest OpenGL

I believe this should be fixed with the raspberrypi-sys-mods package.
It should have been auto installed, but can force most recent version with
sudo apt-get udpate && sudo apt-get install raspberrypi-sys-mods

Tried raspberrypi-sys-mod but this did not work.
The local HDMI output is fine but no toolbar with xrdp and nomachine remote access.
Thanks

Having same issue and not fix as of yet.

To clarify, this is in relation to a previous comment (which seems to have disappeared since) relating to issues with the changes with Pi 3 serial port name. It was fixed with raspberry-sys-mods package update.

Well done indeed . Many thanks for this important update.
I’ll be trying all of the new functions out.

This looks great cant wait to update.

Has the issue of right click on touch screens been addressed yet? this has been a bit of a sticking point for my with the official pi touch screen. :(

Great news! I especially like the SD card copier. For years I was doing regularly backups by shutting down the PI and copying the card in another computer. Not the best solution for heavily-used servers ;-)

I would be VERY happy if this tool would be useable from the command-line and not only via GUI. My most important PI-servers dont have GUI installed…

Agree. That was such a pain.

Have a look at our GitHub repo for piclone – https://github.com/raspberrypi/piclone There is a script in the src directory called backup – this is the original command-line prototype for SD Card Copier. It might need a bit of polishing, but it should be pretty close to what you need.

Great, I will check that! Thank you!

Just what I’ve been waiting for – I’d got a faster SD card to replace the one in my Pi3. The backup script worked perfectly first time.

If blueman is installed does it need to be removed? Will there be two bluetooth apps running if not?

You don’t need to remove blueman – it ought to coexist with the new GUI. (Although I can’t understand why you would *want* to keep it when there is a new shiny GUI that works properly and actually knows that people who are pairing with a device might also want to trust it and connect to it without being forced to do them all as separate steps… ;) )

OK – so I removed the Blueman related stuff, and apparently a little extra. The remaining Bluetooth icon, the new one, it now says that there is no Bluetooth adapter found. I tried repeating the install steps on this page, but it fixed nothing so am assuming that the new Bluetooth software uses a common package with Bluemanz. Anyway idea of how I can get my Bluetooth back?

I am having the same problem to. Can someone fix this?

Really glad that the wifi config can now be read from /boot. This is a great time saver; thanks!s

Wow. Great work. Looking forward to playing with the new bells and whistles ! Already 56 comments – shows the interest we have in the subject and how it’s appreciated all these improvements ;o)

Did anyone find a fix for the toolbar missing with remote access. I ran the updates and sys-mode; no luck. Thanks.

Little question about piclone/sd card copier :
Is it not dangerous to raw copy the internal SD with the system running ?

It doesn’t do a raw copy; it copies individual files.

Thanks ! And perfect ;)
Shame on me, I didn’t browsed the code on the given Github repository.

Thanks man! Plus on the in-place upgrade notes.

No Menu bar when I RDP (using xrdp):
I will provide more structured feedback tonight when I get home:
1) I Did the update/upgrade
But after update, when I RDP (using xrdp) via Weaved, I see the top menu bar empy box flash few times, but does not appear.
So I end up with a display with all icons but no menu bar.
I did get a warning about config files being moved and preserved.
Dmesg does not show any interesting info.
will post info on forum later. (user blachanc)
No panic here.

I’ve just tried this here, and can’t repeat the problem. I’ve installed xrdp on my Pi with the latest image, and am using MS Remote Desktop to connect from my Mac – the taskbar is fine. It works equally well with a Pi booted from an SD card with a clean copy of the latest image, and from my NFS shared hacked-about development copy of the image.

I’ve now tried this with both a clean image, and an image upgraded from the previous Jessie image via apt, and both work fine with xrdp and Microsoft Remote Desktop on Mac.

One thing that does occur to me, though, is that it seems that xrdp creates a second desktop session. As the plugins for lxpanel are created on a per-session basis, this means you potentially have two copies of each plugin running, which will have separate copies of all the data associated with each. This might cause strange behaviour in some situations; it might be safer to boot the Pi to console only and thus not run a desktop locally on the Pi if you are then going to connect via xrdp.

Thanks Simon; I’m connecting to Pi via Tight VNC, over a VPN connection. Can you try and see if you get the same issue?
Thank you.

Sorry – I’m on a Mac and there is no Mac port of TightVNC; I’ve tried the Java version of their viewer, and it refuses to connect to my Pi.

I can confirm this issue, also using tightvnc.

Simon, I use the ipad client and have this issue as well. Only the raspi part is tightvncserver.

It’s likely a permissions problem. lxpanel exits with segmentation fault. When tightvncserver is run as root, no problems occur.

It works again when I edit out the bluetooth plugin in .config/lxpanel/LXDE-pi/panels/panel .

Sorry for the mant replies, hth!

Hi Simon,
I have been Windowzed a long time ago:
I always reboot between update/upgrades, no questions asked.

So I do not believe multiple seesions is the issue.
Maybe you could point me to what kind of info you would like to get, so when I switch tonight from “it does not work mode” to “here is the pertinent info”, you do get the pertinent info.

Ben

Unfortunately, I can’t tell you what the pertinent info is – all I can see is that it works for me, with both a clean install and with an upgrade of the previous Jessie image. There will be some difference between the system that you are running and a clean image which is causing the problem, but I can’t guess what that is, as I have no idea what changes you have made to your image.

Can I suggest that you try a clean install of the image on a new SD card and make sure that works for you?

On looking at the logs that some people have posted in the forums, it seems that lxsession (the session manager) is killing lxpanel for some reason.

One thing which might be interesting is to make sure that lxsession is being started with the correct parameters – if you open a terminal window (Ctrl-Alt-T on the new install, although I have no idea whether that will work across a remote connection) and type “export”, you can see the session variables.

These should include DESKTOP_SESSION=”LXDE-pi” – if that isn’t correct, things will break. Also try “ps ax | grep lxsession” to see the lxsession command line – this should be “/usr/bin/lxsession -s LXDE-pi -e LXDE” – if any of that is different, it will cause problems.

Logs /home/pi/.cache/lxsession/LXDE-pi/run.log shows lxpanel crashing. If I start lxpanel on a remote session I get a toolbar but does not look as nice.

Same problem here.

Same issue on a migrated/upgraded install.

I can call the panel just fine once my session is up using the terminal, but it fails to autostart.

I also do not have the Raspberry Pi shutdown menu, so I have a strong feeling that the OpenBox session is using the wrong profile.

Yes, I’d agree with your diagnosis – this sounds as if something in the session is not getting the right parameters at startup.

ps ax | grep lxsession should show /usr/bin/lxsession -s LXDE-pi -e LXDE

ps ax | grep openbox should show openbox –config-file /home/pi/.config/openbox/lxde-pi-rc.xml

If either of those are wrong, the desktop won’t behave properly.

Simon,
Thanks for the troubleshooting help.

Here’s what each returned:
$ ps ax | grep lxsession
793 pts/0 S+ 0:00 grep –color=auto lxsession

$ ps ax | grep openbox
795 pts/0 S+ 0:00 grep –color=auto openbox

Forgive the ignorance, but how do I address this?

Thanks so much.

Hmmm – that looks as if neither openbox nor lxsession is starting at all. That’ll probably be down to lxsession failing to launch – that is what starts up all the rest of the desktop components. lxsession should be started by a script in /usr/bin/ called startlxde-pi

Try running startlxde-pi at the command line and see if anything promising happens, or if you get a helpful error message.

Another thing to try is using raspi-config from the command line to enable and disable booting to desktop; if something has got changed in a startup file somewhere, this might sort it out.

I can’t reply to you directly, oddly enough.

Using raspi-config to change from Console, no login (which worked fine pre-updatea) to Desktop, Autologin seems to have fixed it for now.

Thanks!

Excellent – glad that’s sorted it. No idea what it can have been unhappy about though…

(BTW, the blog only allows a certain level of indentation; once you get past that, you can’t reply to a posts any more, and you have to reply to the ones with one fewer indent!)

Hey Simon,

I’ve checked the commands you provided and get the follow responds:
for lxsession
** Message: main.vala:99: Session is (null)
** Message: main.vala:100: DE is (null)
** Message: main.vala:104: No session set, fallback to LXDE session
** Message: main.vala:110: No desktop environnement set, fallback to LXDE
(lxsession:2372): Gtk-WARNING **: cannot open display:

but, what’s interesting, for ps ax | grep openbox
1388 ? S 0:00 openbox –config-file /home/pi/.config/openbox/lxde-pi-rc.xml
2406 pts/0 S+ 0:00 grep –color=auto openbox

and for startlxde-pi
** Message: main.vala:99: Session is LXDE-pi
** Message: main.vala:100: DE is LXDE

(lxsession:2407): Gtk-WARNING **: cannot open display:

Quickupdate:
I was able to get the toolbar running again buy running raspi-config and running it in cli mode. Once i startx the toolbar populated.
Thanks everyone for ideas.

Good news! No idea what was wrong there, but glad you’ve fixed it.

Is the USB Gadget mode in the new version of Raspbian? Can I use my piZero in Ethernet gadget mode?

Great. Thank you Bro.

After installing drivers for this screen http://www.waveshare.com/wiki/7inch_HDMI_LCD_(B) on RPi2 running the latest Raspbian, it doesn’t boot

I dist-upgraded from rpi-update, twice, and each time the Menu/Run seems to be non-responsive…

I updated the version on my Pi2 and all went well except the Bluetooth options failed since I don’t have a Bluetooth dongle installed.

One issue is that I don’t see the SD Copier in the accessories menu. Am I missing something?

Same problem here!
I opened Preferences -> Main Menu Editor -> Accessories and there it was, selected and well. By just guessing I de-selected and re-selected it, returned and there is was in the Accessories. Hopefully this works for you as well.

Thanks for the tip! Worked for me too.

nice :D

Nice one!

Like the automatic file system expand and sd card copier.

Keep Working on this Simon, You”re doing fantastic work!

This is great! Next time could you add UI support for 802.11x security? It’s something of a pain to have to do it manually.

Pig Pio?? …Oh right.

How about the SD card copier via command line?

There isn’t an official version, but if you go to https://github.com/raspberrypi/piclone, in the src directory you’ll find a script called backup – this is the command-line prototype I used when developing the GUI. It should work…

Is there away to connect to more than one bluetooth speaker simultaneously?

I was able to accomplish it using bluez 4 and the ALSA plugin on some different hardware, doesn’t seem like PulseAudio/Bluez 5 supports it though. I can’t connect to the second speaker via bluetoothctl or any bluetooth gui client.

Not to my knowledge – PulseAudio only allows a single output device to be selected, as far as I know.

It would have made my life a lot easier if BlueZ hadn’t discontinued the ALSA support in BlueZ 5…

Yeah… looks like I may have to downgrade to bluez 4.
I’m going to play around with it still. I know pulse supports multiple sinks, the issue is the bluetooth connection creates the sink dynamically and it disappears when the connection is gone.

However you can have a bluetooth sink and an analog sink active at the same time, and even load a combination module to combine the outputs and it will do it’s best to keep them synchronized.

I’m going to keep playing with it, will post on the forum if I can figure out how to do it.

Oh, and thanks for the response! This update is incredible and I know how much a pain in the ass it is to work with bluez, so thanks for the hard work!

Nice upgrade!
In the past I used rpi-clone (https://github.com/billw2/rpi-clone) to copy my SD card. This worked on destinations with different size than the source, too.

I am asking myself if the new “official” tool is better in any way (except gui vs. cli).
Any opinions on that?

Looking at rpi-clone, it looks as if it only works on standard Raspbian images; it looks to me as if it won’t clone a NOOBS card or anything else with more than 2 partitions. SD Card Copier is designed to duplicate the entire partition map of the source card on the destination, with the final partition expanded to fill the card completely – I’d say it is probably more flexible as a result, but rpi-clone looks to be fine as long as you just want to clone a simple Raspbian card.

Is /etc/network/interfaces now working as it should, or are we still forced to set things such as static IP addresses using /etc/dhcpcd.conf? It causes a ton of headaches as most online guides use and peoples own is used to /etc/network/interfaces file.

Setting static IPs using dhcpcd.conf has been the way people should have been doing this ever since we started using dhcpcd as standard in the image, which was well over a year ago now. There has been plenty of time for people who maintain online guides to update them – we’re not going to get rid of dhcpcd and go back to a less convenient UI just because some people’s documentation is out of date!

Yes, but the Raspberry Pi is 4 years old now, which means many of us started using /etc/network/interfaces, and not being closely tied in with the development team we’ve neither gotten the word to use dhcp.conf, nor been told how to, so we stick with what worked for us in the past. It’s a little dismissive to just say “you should have known”.

So what we should do is never change anything because people are used to the way things are now, and they might not like it?

You do realise that I don’t change things for the good of my health, or because I enjoy upsetting people – I do it to make things better. In the judgement of most Pi users, that’s what my work does – improves their experience. A small minority complain about every change, whether it is for better or for worse – I’m sorry, but for the benefit of everyone else, I intend to continue making improvements, and to do that, things are sometimes going to have to change from “the way they’ve always been”.

If you want to be informed about these changes, just read my blog posts; I write one every time there is a major GUI change, and they are all still available in the archive for anyone to read.

Hi Simon – great updates, lots to like that’s very useful and, as usual, things like SD Copier and the network boot configuration tools are about four years overdue ;)

However, I thought I was reading one of my own comments when I read this one, which means you’ve crossed waaaay over the line! I realize you’ve been busy, are tired, etc., but we all are, especially in the classrooms. I’m a little surprised that, as a fellow UX guy, it didn’t occur to you to put the URL for your blog anywhere in the post _or_ comments since you’ve been doing this gig, at least that I could easily find. The rule of information presentation is to tell them what you’re going to tell them, tell them what you want to tell them, and then remind them what you’ve told them. Bad UX engineer, bad! Sit! Lie down! Roll over! Play dead! OK, here’s a treat, good boy! :D

You should also realize that, depending on the search engine terms used, neither your blog nor the Foundation’s official instructions show up in search results for the “new” network configuration procedures (don’t feel bad, this is true for a lot of Pi info). A _lot_ of old cruft that isn’t in guides that are usually kept up-to-date can be returned in results well before the official and updated sites. There’s over four years of history from which results can come, and something that’s “only” a year old is in the vast minority.

I’m sure multiple someones at the Foundation know how to use search engine optimization (SEO) to get search results to display the most appropriate links to the official documentation as well as the kept-up-to-date guides. BTW, another big nit of mine about the Foundation documentation is that there don’t appear to be any dates-of-information on the pages. Again, this isn’t limited to you folks, most of the Web has this problem. Fortunately, I know how to send http requests to get ctime, mtime, atime, etc., but others are not so blessed :D

Oh, and one more thing, it _is_ possible to prevent corruption of any file if a multi-phase commit technique across multiple versions of files is used, along with checksums, etc., when writing files. Depending on only writing to one file on every write is a recipe for disaster – go read up on how ancient OSes such as DEC’s VMS wrote files with sequential integers at the end of each file name to provide automagic vermin, I mean version control. Github retains every version of a file whenever it’s updated, as do other configuration management systems, of course, so everyone there needs to think about how to incorporate this into Raspbian.

Otherwise, keep up the great hard work, along with everyone else there!

Errr, Jim – when I referred to “my blog posts”, I meant the ones like the one you are reading now! I don’t have a separate personal blog; when I make UI changes, I post to this blog here. Clicking on my name at the top of this post will link you to all the others – or just go to https://www.raspberrypi.org/blog/author/simon-long/

As for network configuration, the article in the help topics on this site describes how the dhcpcd GUI works – https://www.raspberrypi.org/documentation/configuration/wireless/README.md

It’s been like this for more than a year. “Nobody showed me how to do it” is something my 12 year old says when she hasn’t used common sense and she’s been called out on it. Are you, by any chance, my 12 year old?

“The needs of the many outweigh the needs of the few…or one.”

Spock

Prefer to use /etc/network/interfaces ..

Try and find an example showing static IPv6 example using that dhcpcd client ..

I agree with the sentiment, BUT it would be nice if the Foundation updated its own documentation much of which STILL has SysV instructions.

The official documentation page on wifi configuration is at https://www.raspberrypi.org/documentation/configuration/wireless/README.md – it describes how to use the GUI interface for dhcpcd. On a quick search around the site just now, I didn’t find anything in the help section describing the older networking setup – perhaps you could let us know where the outdated information is so we can update it?

Simon,

I have been travelling for the last week and haven’t had a chance to do anything on the Pi.

I was not referring to Networking per se, but often find folks on http://raspberrypi.stackexchange.com trying to follow old instructions.

One such example is:-
https://www.raspberrypi.org/documentation/remote-access/vnc/

I use a systemd service to run VNC (which incidentally is much simpler).

I will post any others if I run across them. Unfortunately there doesn’t seem to be a mechanism to notify things which need attention.

Really nice improvements.

Does this release support the new official V2 cam with the Sony sensor out of the box?

Yes, it does.

For those interested in what has changed in the new version of Scratch, a release note is now in the forums at https://www.raspberrypi.org/forums/viewtopic.php?f=77&t=148071

Thank you!

Very nice improvements.

Does this release support the new v2 cam with the Sony sensor out of the box?

This release, together with a Pi3, makes a really usable piece of kit; many thanks for all the hard work.

Exciting Stuff, Already Installing And Tinkering With It…

Luke

Great, especially all these tiny UI-fixes and things like the backup-tool…very good idea, many thanks!
Dont know if the reason that it works fine now is that I added the app-start-bar as a new panelentry – but now I also found my Kodi and Iceweasel-entries into the list where they belong, seems to be fixed, too…nice.

Now my only question remaining is – is there possibly an approximate date when we it will be possible to change the resolution of the new GL-driver?

The shutdown menu is still only in English.
Should be in the language of the country chosen.

Yes, something seems to be amiss with their language support.

I’ve generated the en_US UTF8 language and removed the en_GB UTF8 language, but all the localized strings in my UI are still British English. Really odd.

Same for the ‘Empty Trash Can’….

Unfortunately, my language skills are limited to good English and bad French; this does not qualify me to correctly translate all of the UI into the hundred or so languages Linux offers…

For some of the new packages I have added in the past, very helpful members of the community have submitted translation files, which have been incorporated into later releases (which is why the Raspberry Pi Configuration utility now works in Taiwanese and Dutch). Anyone can submit these – just go to the relevant repo in GitHub, create a language file in the correct format, and submit a pull request. All such contributions are very gratefully received – without them, the UI will only ever be in UK English, because that’s what I speak!

The “Empty Wastebasket” / “Empty Trash Can” confusion is slightly more complex, as some of those strings never had translation support included, and were hard coded to a mix of US English and UK English, using, I believe, three different terms for the same thing. They are now all consistently in UK English – I’ll look at making the strings translatable in a future update.

I teach 8 to 13 year old kids to code with Scratch on the Pi. Biggest problem we have is that the files get corrupted if the kids don’t shut down the Pi correctly. Even if they save and exit scratch the scratch file they saved is corrupted if they don’t shutdown. Has this been fixed ? Any plans to fix it?

Had to get kids excited about programming when their work get lost. HELP!

Surely, part of teaching them to code should also include how to shut the Pi down properly, and the consequences of not doing so?

Darren

It sure does but like adults, kids make mistakes. Parents arrive and the kid wants to leave quickly. They save their program, the start shutdown. Then get impatient and unplug before the shutdown is complete.

Then next week their work is lost. Much harder to get them to stay engaged.

Remember I’m talking about 8 year olds.

This really isn’t fixable – if you shut down a computer or pull a USB stick while writes are in progress, those writes will be corrupted. There’s nothing we can do stop someone physically pulling the power cable out in the middle of a write, and that situation is unrecoverable, just as it would be on any other computer.

Computers are sometimes unforgiving, and this is unfortunately one of those circumstances where there is nothing that can be done other than educating people not to do the thing that causes the problem.

Simon

thanks for the reply.

I get what you are saying but I would have thought that once the kid saves their Scratch file and exits scratch, the write would be complete. I’m surprised to see that the files gets written again as a zero size file after Scratch is closed when they don’t properly shut down the Pi.

Does that make sense?

Another idea: let them all save their work through some kind of network-connection on the ‘teachers’ harddisk…then you could control if everything is fine.

I’ve never used scratch…but I only hat 1 time a corrupted sd-card since I use the Pi – and that was caused by myself by pulling out power too early.

What is needed is for NuScratch to issue a sudo sync after a save (As the Pi only “remembers” file changes and doesn’t actually update the SD card until a proper powerdown/reboot – a sudo sync forces the SD card to be written to) I have a shortcut on the desktop and get the kids to run it as soon as they’ve exited Scratch – as long as they get to do that – then nothing is lost

Wow – I will try that. Thanks!

Wondering,is there a reason this can’t be addressed in Scratch. I’ve tried a lot of other programs including the Pi Office programs and they don’t corrupt if they are saved and the plug is pulled.

Couldn’t this be fixed by simply doing the save to the SD card when the user exits scratch rather than when the Pi is shut down? Does that not make more sense?

Is the GUI supposed to support the built in Bluetooth in the Pi3? I am getting “device not found”. It took me 3 tries to get bluez installed, are there other packages I need for Bluetooth?

Matt

I’m having the same issue where the “No Bluetooth adapter found” message is displayed in the GUI and the ‘Bluetoothctl’ ‘Show’ command in the shell returns “No default controller available”.
Bluetooth was previously fine and I’ve had a couple of reboots for luck – any suggestions on what to try would be welcomed.

NB – I also had the desktop issue sorted by
“Using raspi-config to change from Console, no login (which worked fine pre-update) to Desktop, Autologin”

The rest of the update looks great so far especially the SDcopier (Which only appeared after a second reboot for me)

Thanks

BGL

Update to my post not yet here – I disconnected a USB webcam and rebooted again and the bluetooth adapter is now available – I had a similar issue with WIFI I’d forgetten about.

Question – the Pi 3 is not syncing up with a Sony SRS-X33 speaker. Any clues on this issue.

Like the updates, the ability to clone is a big help for those of us who tinker and blow things up.

Thanks for great device.

It seems like a the new distro shipped with ssh disabled. I was able to reconfigure and run the previous one on headless systems. Not this time. Am I missing something?

Prior to the release, a lot of testing is done through ssh, so it’s something that would’ve been picked up. It’s most likely a networking issue elsewhere. Best to post a forum thread about it.

Slick, very slick upgrade.

hplip tool box does not work anymore. Any fix?

Thank you

Yes now I don’t have to use bluetooth bluez blueman anymore!

Would be great if you could fix the IPv6 interface within the GUI..

I had to dump the default network client for traditional /etc/network/interfaces, to get a static IPv6 address in place.

Nice! Specifically very happy with the wpa_supplicant in boot addon. Ideal for WiFi headless pi’s.

Yeah, v pleased with the wpa_supplicant.conf copy feature. In a similar vein, being able to copy dhcpcd.conf on 1st boot would be great to, especially for headless setups.

When I ran the sudo apt-get dist-upgrade halfway through the screen just went bland and the green light on the pi starts to blink. It boots bast the colour thing and then past the recovery bit and then it just stops as a blank screen can anyone help?

So…. dont upgrade the kernel if using an install via berryboot… breaks it.

My Berryboot Pi3 also got bricked – I assumed it was something I did !
[I add other images on the same berryboot install: like Kodi and Ubuntu Mate , these images also don’t boot after the upgrade]

I’m currently trying a ‘good old fashioned’ single-sd-card test of the upgrade now – just to make sure it isn’t something about my Pi (I doubt it is).

Just to say I retested with a single SD card upgrade on a Pi 3 – and everything seems to have worked very nicely this time (I previously tried upgrading my ‘berryboot’ version : but this broke my image)

(this is actually a follow-on post from my previous post: but my previous post hasn’t been approved/published yet)

The bluetooth scan even picks up Bluetooth LE devices as well (It saw my fitbit – I wasn’t able to pair – but I didn’t expect that to work – just nice to see it’s actually scanning LE as well as classic).

Hi. I have the same (or close to Matt Packwood above) problem with Bluetooth as well on pi3.
The icon is greyed out and reports “No Bluetooth adapter found”
Fwiw I had bluez installed before and it kinda worked with blueman. I have to enable the adapter in any way?
Thanks.

Hi, yes I’m getting this as well, on a Pi3, after doing an upgrade, I’m getting message ‘No bluetooth adapter found’ when I click on the grey Bluetooth icon in the task bar.
Regards, Kevin.

Can I run it in my Pi B first gen with only 256 MB RAM (one of the first batches)? Even Jessie lags a lot on this one.

It will run on any version of Pi, but performance won’t be great on the older models with small amounts of RAM. It’ll be no worse than your current version of Jessie, though.

Just got the upgrade all done and you all have done some really sweet work.

I did quite a bit of hacking on the UI on my Pi, but everything went smooth as far as I can tell.

Love the addition of Geany!! That’s a great choice. And the new “Backup” feature is great too. And YouTube video is running great in Epiphany.

It’s all Great!!!!

Thank you again!!

Wouldn’t it be great if we had a boot and OS partition that does not need to be adjusted by the user. And then have a third partition that takes up the rest of the SD card that will have all the user configs and files (everything else)?
That way upgrading would be a lot easier.

I followed the apt instructions but the new programs are not showing in my menu lists. Is there something I am missing

Simon, I just fully updated some previous Raspbian Jessie images and only 1 out of 4 were able to detect the Blue-Tooth on my Pi 3.

Any ideas of things to check for?

Hmmm. I’ve never seen the BT hardware not being detected, so I’m slightly at a loss! One suggestion – were you previously using an alternative BT manager (blueman or similar), and did you turn the BT hardware off in that? It’s possible that the power state of the BT hardware is a setting stored by the BlueZ stack which will persist across reboots, and my BT UI doesn’t know how to turn it back on.

If you did use blueman or similar, go back into blueman on those Pis where the BT hardware isn’t found, and make sure the BT is powered on.

If it isn’t that, I wonder if it might be an issue to do with the BT UART being used for something else, about which I will consult my colleagues in the kernel and hardware department on Monday!

I haven’t used any BT on any of these Jessie SD cards before.
The only thing different with the card that works is that it’s setup for SDR (Software Define Radio).

I guess when I was reading this post I expected a way in the Raspi-config or in the GUI version to turn the BT on and off.

No, there’s no way to power on or off the BT hardware via the GUI – it’s on the ‘to do’ list, but I haven’t got to it yet…

If you type “bluetoothctl” at the command-line prompt, that launches a command-line application which addresses the BlueZ stack. Once it is started, try typing “power on” – that should power up the BT hardware if it is off; see if that makes a difference.

I just shut down the SD card that the BT was working on,
then changed cards and tried your suggestion:

pi@raspberrypi:~ $ bluetoothctl
[bluetooth]# power on
No default controller available
[bluetooth]#

This seems really strange…

Hmmm. In that case, I’m slightly stumped – we’ll look into this in the office on Monday and see if we can think of anything else that might be going wrong. It’s clear that your hardware is working, as otherwise it wouldn’t work with the good card, so it must be something in the software configuration that is preventing it from being detected.

One thing that might be worth trying is forcing a reinstall of bluez (the BT stack) in case it somehow failed to update properly – try “sudo apt-get –reinstall install bluez” and see if it generates any error messages; there might be something on your system which is conflicting with bluez and preventing it from installing.

Alright, more weirdness…
I ran the ‘sudo apt-get install –reinstall bluez’
and still nothing shows up.

I’ll wait to hear back from you on Monday, about this issue.

Have a great weekend!

I have done some more testing.

First I plugged in a USB BT dongle and with bluetoothctl running it detected 2 different ones that I have, just fine.

Then burned a new image on to a blank card and it worked fine as well.

I think the upgrade process might be the cause of these issues, but I am still a Linux Noob.

I do have a background in Hardware and Windows troubleshooting though.

Just some more food for thought when Monday rolls around.

Hi Simon, Any further info on this issue?
Should I be posting elsewhere?

I would just like to get all the SD card to work the same way.

Look at the section titled “Updates” at the bottom of the original blog post above – the problem is the lack of the pi-bluetooth package. “sudo apt-get install pi-bluetooth” should fix it.

Re the “No Bluetooth Hardware Detected” – I have a 3 with the Official Display, no other hardware installed, if that helps.

The display shouldn’t make a difference as far as I know; try the advice above about the bluetoothctl command-line application and see if that shows any signs of life.

If bluetoothctl can’t see the hardware either, then there’s either a hardware fault (unlikely) or something else may be grabbing the UART used to connect to the BT module; I’ll consult with my colleagues on Monday about that.

Wouldn’t it be awfully nice if the SD-Card copier could write the image to a file (on a network share or USB stick of course)?

I downloaded the Lite version of Raspbian burned it into an SD card and copied a version of wpa_supplicant.conf to the / of the SD card with the necessary wifi configuration; however, when I rebooted the raspberry pi with the Lite image it failed to associate to the network.

Upon examination, found that the wpa_supplicant.conf file didn’t get copied to the /etc/wpa_supplicant folder. I manually copied the file from the /boot folder into /etc/wpa_supplicant folder, rebooted the raspberry pi, and it was able to associate correctly to the wife network.

Is this feature (automatically copy the wpa_supplicant.conf file) not available for the Lite version of Raspbian?

I’ve got the same question since I had a good look through the latest lite image and I can’t see where this is implemented. Can anyone shed any light on exactly how this mechanism works and is it present in the Lite image?

Seeing same behaviour with wpa_supplicant.conf and the lite image. Will download the full and retest.

Copying manually without any other changes works as expected.

tks folks – nice job… paired up my Kai mini-X2 BT speaker and Anker mini-BT keyboard – easier than doing it under OS X Yosemite!

my biggest problem was figuring out to RIGHT-CLICK the audio menu in order to select the BT output and then to leave my Audacious player settings ALONE… works well!
(range is not too good, but then my RPi3 is encased in a heavy, machined aluminum case w/a 2.2TFT)

Hi,
just made a distr-upgrade but SD card copier is missing from accessories
any suggestion?
thanks

same here. it does not appear in accessories even after restarting the pi!

I have the same problem – see earlier post as I can’t see either the sd-card copier or Geany in the menu lists. You can use Run option: ‘piclone’ , ‘geany’ will launch the applications. However, I have never been able to add new items to the menu.

no sd card copier under accessories after a distr-upgrade
any suggestion?
thanks

Hi I’m new to the pi and found these updates really easy to install and exiting especially the sd cloning as I have 8gb and wanted more space and don’t have a windows or Mac PC, keep up good work Simon long and thanks, and thanks everyone for comments been big help and pleasure to read.

Wonderful job, Simon! I really like the SD Card Copier!

Here’s my question: In the good old days, I used to be able to swap caps-lock and ctrl by adding “ctrl:swapcaps,” to the XKBOPTIONS in /etc/default/keyboard. This hasn’t worked for a while (although there’s a slightly tedious workaround).

What is the correct way to do this today?

Thanks in advance!

The bluetooth audio pair-process worked first go for me – I’m using a (mono) HMDX ‘Jam Classic’ (MODEL: HX-P230A).

Even better: ‘espeak’ works – so great potential for moderately funny practical jokes (voice appearing from under a cushion etc etc).

Shouldn’t PulseAudio start at boot?

After the upgrade it no longer does. I can however start it manually from a terminal with pulseaudio -D

There’s a clue here: https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/

My Pi3 Bluetooth is working as it detects both my laptops, but does not detect a Sony SRS-X33 BT speaker.

Any thoughts on the issue?

Thanks

I do Confirm pflipp fix for the No Panel VNC Problem:
If you comment out the Bluetooth plugin in “.config/lxpanel/LXDE-pi/panels/panel” the next time that you start the vnc service the panel will be back. Thanks a lot @Simon Long and if you have some time maybe you will be able to figure out what the problem is.
Thanks.

OK, I’ve found out what is going on here – there is what looks like a bug in the BlueZ stack (but it might be deliberate behaviour – not sure yet!) There is more information at https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=148030&p=975166#p975166

The quick fix is to make sure you set the Pi to autologin in either the CLI or the GUI – make the relevant setting in raspi-config or the desktop Raspberry Pi Configuration application; the Bluetooth plugin will then work fine over a remote connection.

SD card copying, in such a short time, and the enabling of bluetooth should be REALLY useful in schools, where there are often many Pi that need setting up and bluetooth Pi robot control might be needed. Surely worth a mention of this update in the next Education newsletter?

Hi all,
please help – I can see most of described new features after upgrading besides bluetooth icon, it does not appear. I am working through VNC-Viewer-5.3.1-Windows-64bit with Berryboot installation of Jessie Raspbian

After this upgrade, bluetooth stopped working: “No default controller available”.

When you say “stopped working” – was it working before the update? Had you successfully used the Bluetooth hardware before with blueman or another BT front end? In other words – did the update break a working BT configuration, or had you never tried to use BT before?

Simon, it looks like the latest bluetooth changes have broken RetroPie 3.7. Specifically, the Playstation 3 controllers used to work fine before via Bluetooth, but after the dist-upgrade no bluetooth hardware is found anymore. It looks like after the upgrade bluetoothctld is not marked as executable anymore, and even bringing it up manually doesn’t help. The only workaround I found is to downgrade bluetooth-pi from 0.1.1 to 0.1.0, that seems to fully restore the bluetooth functionality again.

Btw, I also noted that my Pi was running with powersave governor now. Did the default kernel governor change to powersave? I have to install cpufrequtils to switch it to ondemand.

Try removing the Bluetooth plugin from the taskbar and see if that makes a difference. It shouldn’t, but I don’t think we changed anything in the underlying Bluetooth stack for this release – if you still have a problem without the plugin, then it suggests we do have an issue somewhere in the stack / firmware / kernel.

RetroePie doesn’t have a desktop environment installed, it’s running EmulationStation as its frontend. Running `hcitool dev` with pi-bluetooth 0.1.1 gives a no device error, but after downgrading just pi-bluetooth to 0.1.0 it list hci0 correctly.

OK, thanks for that – looks like we have something wrong in the stack somewhere. We’ll investigate tomorrow!

Hi Simon,

To give you a little more information, someone on this thread here (https://www.raspberrypi.org/forums/viewtopic.php?t=148305&p=976259) has found out that by installing

apt-get install raspberrypi-sys-mods

the bluetooth on RetroPie gets fixed and it works even with pi-bluetooth 0.1.1 now. It seems to be related to /etc/udev/rules.d/99-com.rules, which gets replaced when installing raspberrypi-sys-mods.

Hope that helps.

> When you say “stopped working” – was it working before the update? Had you successfully used the Bluetooth hardware before with blueman or another BT front end? In other words – did the update break a working BT configuration, or had you never tried to use BT before?

It used to work. I don’t use graphical tools. I use `bluetoothctl`. Prior 3.7, I could pair a bluetooth device. Now, the bluetooth controller can’t be found.

Anyway, I re-installed, and now it works.

For anyone who is struggling with a crashing lxpanel over a remote desktop connection, I’ve found the problem.

There is more information at https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=148030&p=975166#p975166

The quick fix is to use either raspi-config or the desktop Raspberry Pi Configuration application to set the Pi to autologin on boot, either to the CLI or the GUI – the Bluetooth plugin will then work properly over a remote connection.

This looks to me like a bug in the BlueZ stack, but it might be a deliberate decision – I’ll talk to the BlueZ developers and see if there is a fix.

With the new kernel and Raspbian it seems more than one USB wireless card at bootup is a problem. Most of the time, only one gets recognized, the other is like non-existent. No dmesg messages, no nothing. Other USB port doesn’t work either, only way to make it work again is reboot. Happens with two different Wifi cards with different chipsets.

If I plug them after bootup they seem to work fine. Plugging in both at once (connected to a USB hub) also works.

Have tried on a Pi3 so far, wanted to try a Pi2 also to see if it’s model dependent.

Any other ideas how to further narrow this down?

Thank you for all the Coding!

Simplicity at last!
Installed latest Jessie to SDcard, attach WD PiDrive to Pi3B, boot from SD, piclone SD to WD drive, edit /boot/cmdline.txt, replacing root=…. by root=/dev/sda2, reboot and away we go.
Can’t wait for the day the final piece of bootcode is released and I can boot straight off the WD drive.

Hi Great update with realvnc it dragged me into using the gui
Also as to watch pi camera live just using command line. Found a problem on using the GUI for network setting up a static address on reboot ntpd did not update and I had the default date 1 Jan 1970. Daemon log then shows looking for RTC. After reboot,halt even switched off for the night the PI is still not getting any time from the web. Removed via GUI the static address so back to DNS and reboot still no NTPD service to update the time. Any help on this matter would be great.

Should this latest image work with the Pi Zero? Boots to GUI then mouse/keyboard don’t respond CPU % varies so somethings active. Tried 2 Zeros and images downloaded at different times on different machines

Yes, I tested it on Pi Zero as part of the release testing – it worked fine for me.

I did the update and it’s really great except for one thing. I have three RPI’s on my local network. Their hostname (as seen in config) are PiM3, PiM2 and PiZero. Prior to the update, I would access them from other machines on the local network as PiM3.local, PiM2.local and PiZero.local. I can access them by their IP addresses in VNC, Putty and Web Browser (those running apache). When I do log in, the appropriate name shows as part of the prompt and in the GUI. Apache reports its IP address, not the hostname, before it reported the hostname.

I’ve tried repeating procedures for establishing a hostname. The does not cause a change. Are these now name something other than .Local?

This seems to have resolved itself. It sorted when I did an Ipconfig /renew on windows and then killed all browser processes, restarted the browser. Another thing I did prior to all that was start an Rpi with a pre-update Sdcard. So the first thing that happened is that pi worked ok with it’s hostname. The second is that the updated pi worked right. I’m not quite sure what really solved this.

I now have sorted exactly what is happening and what the solution is. For some reason, some upgrades lead to invalidating the DNS cache on local network PCs. When this happens, the pi hostname can not be used to access the pie. I suspect that it’s during rpi-upgrade.

The remedy is to use ipconfig (the ifconfig of PC’s) start command prompt (best if admin / system prompt) and then ipconfig/registerdns

There is a minor problem where I have installed a second keyboard layout and a layout switch panel on the taskbar. Before the update clicking on the flag was switching from one language to another but after the update it doesn’t. Removing and readding the panel does not help. Actually I have to switch the layout with a keyboard shortcut and then clicking on flag works again… until the next boot. Also the done button on the keyboard layout settings does not do anything. I reckon it’s not much of a problem. Thanks for your work.

Re: Bluetooth. I’m deaf, and my hearing aids have a near-field link to a neck pendant that links through to bluetooth. I’ve been trying to get a workable system with this in my main Kubuntu workhorse, where I can use these at the same time as the headphone output (with an amplifier and ‘cans’). No luck so far – the audio mixer is a selector – it’s one or the other. Can we do any better here? This is to allow family/bystanders to hear at their comfort level while I crank up the volume through the ‘hairy maids’.

Question: I’ve read through the comments to ask what’s probably an obvious answer to everyone else’s. Is the Latest update to Raspbian compatible with versions lower than PI 3?

Yes, it runs on every Pi we’ve ever sold!

The same thing happened to me: after upgrading, bluetooth stopped working: “No default controller available”:

sudo bluetoothctl
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
No default controller available

However with hcitool the controller is there:

hcitool scan
Scanning …
A8:86:DD:AA:97:AE QR-MacMini
0C:BD:51:E0:4B:71 Alcatel OT871A
0C:FC:83:F6:46:85 BT-005:

Any idea on what is going on? Thanks!

Is there a chance for Raspbian to move from licensed h264 to its open and royaltee-free Cisco implementation – OpenH264?
Fedora Workstation has just replaced h264 codec with OpenH264 https://blogs.gnome.org/uraeus/2016/05/12/h264-in-fedora-workstation/ which supports H264 Baseline profile now.

Our H.264 codec is run on the VideoCore graphics accelerator, and is largely written in VideoCore-specific code. Unless an alternative codec was written to target the VideoCore, it would be significantly less efficient than the existing codec when run on Pi.

We need your help!

Several users have reported the Bluetooth controller being reported as not found after updating to the new release. We’ve been trying to replicate this at Pi Towers today, and have drawn a blank – we simply cannot see the failure on any of our systems; but there is clearly a problem as multiple people are seeing the issue.

We really need to examine an SD card with the problem – if some kind soul out there is UK-based and could post us their SD card (or a copy of it) which shows the problem, it would help a great deal in getting a fix. (You’d get your card back afterwards, promise!)

If you are able to help, please send us an email at info@raspberrypi.org and put “Simon Long – Bluetooth SD Card” in the subject line. Many thanks in advance!

My bluetooth controller not found issue was resolved by disconnecting my USB web cam and rebooting, pre update bluetooth was fine via the command line.

Thanks Simon.
Connecting my bluetooth speaker (Bose Soundlink) to in-built Raspberry BlueTooth using the GUI (latest Raspbian Jessie 2016-05-10) worked like a charm as per your post.

Since my Raspberry pi will work without screen, I then set the preferences to boot on CLI and then restart the raspberry pi.

Once reboot, I proceed to the needed commands (as CLI) to connect my bluetooth speaker as follows, but despite proper pairing/trust, the connection switch alternatively to yes and no:

pi@raspberrypi:~ $ sudo bluetoothctl -a
[NEW] Controller B8:27:EB:29:11:57 raspberrypi [default]
Agent registered
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller B8:27:EB:29:22:83 Discovering: yes
[NEW] Device 00:0C:8A:C2:5B:24 Bose Mini SoundLink
[bluetooth]# pair 00:0C:8A:C2:5B:24
Attempting to pair with 00:0C:8A:C2:5B:24
[CHG] Device 00:0C:8A:C2:5B:24 Connected: yes
[CHG] Device 00:0C:8A:C2:5B:24 UUIDs:
0000110b-0000-1000-8000-00805f9b34fb
0000110c-0000-1000-8000-00805f9b34fb
0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:0C:8A:C2:5B:24 Paired: yes
Pairing successful
[CHG] Device 00:0C:8A:C2:5B:24 Connected: no
[bluetooth]# trust 00:0C:8A:C2:5B:24
[CHG] Device 00:0C:8A:C2:5B:24 Trusted: yes
Changing 00:0C:8A:C2:5B:24 trust succeeded
[CHG] Device 00:0C:8A:C2:5B:24 Connected: yes
[CHG] Device 00:0C:8A:C2:5B:24 Connected: no
[CHG] Device 00:0C:8A:C2:5B:24 Connected: yes
[CHG] Device 00:0C:8A:C2:5B:24 Connected: no
[CHG] Device 00:0C:8A:C2:5B:24 Connected: yes
[bluetooth]# exit

I spent several hours looking for a solution everywhere on the internet and tried several ones but none could fix that issue (and still starting each time from scratch, by recreating a proper SD image but problem is still there.
I must say I am falling in a desperate mood.
Would you have any idea ?

Note: I am using the Raspbian Jessie 2016-05-10 without any change (except the initial apt-get update and upgrade)

The log above comes from bluetoothctl – I assume that means that you are running without the GUI? To connect an audio device, you need to be running PulseAudio, which is started along with the desktop; it has some inherent link to X (I’m not sure of the details) so is started as part of the desktop. The disconnection you see is probably due to the audio device connecting, finding there is no audio layer for it to talk to, and disconnecting. I’m not sure if PulseAudio will actually run from the command line, but you can try entering “pulseaudio -D” from the CLI to launch the daemon before trying to connect, and see if that helps.

Right, I am running without the GUI.
I thought that pulseaudio was already running because command pulseaudio –check did not return any value (so I though, wrongly, it was meaning value is 0, meaning pulseaudio already running) but finally, based on your suggestion, I ran pulseaudio -D then bluetoothctl command… and it works !! I can now connect my bluetooth speaker.
I will now need to add pulseaudio to start automatically at boot-up.
A very big thanks Simon !

I live outside and can’t help much especially since I did a fresh reinstall over the old raspbian of the new distro and now BT works.
If it helps, when adapter couldn’t found, I had bluez, blueman and a few dependencies of them I can’t recall of, along with hplip installed and possibly a few firmware updates I don’t remember through rpi-update.
Uninstalling and reinstalling any of the bluez or pi-bluetooth didn’t resolve the issue. Additionally bluetoothctl did not accept any (usb) keyboard input and at some attempts to fix through some command lines at some point I had and a D bus error report.

Sorry, it’s very generic I know but I don’t have any coding experience.

Also, over at Retropie forums, Retropie runs over a raspbian distro, some people managed to solve a Bluetooth PS3 pad pairing issue, where possibly BT stopped working, caused by raspbian update, by replacing the pi-Bluetooth deb with an older package.

https://retropie.org.uk/forum/topic/842/pi-3-ps3-bluetooth-controller-freeze-fix-updated/25

Does this allow us to use Bluetooth devices with audio input/output? I’ve got a Bluetooth speaker that I use for voice calls and would love to be able to use the input stream for some voice-activated stuff!

No, unfortunately we haven’t got around to sorting audio input yet. It’s on the to-do list!

Thanks! Looking forward to it.

Simon, I use SPI with my hardware under Python 2.7 and I am now getting “ImportError: No module named spidev” when I use “import spidev” in my program. I have verified that SPI is enabled in the Raspberry Pi configuration window and I even ensured that the dtparam=spi=on was uncommented in the config.txt file. What am I doing wrong?

You need to install the python-spidev module – sudo apt-get install python-spidev python3-spidev

OK, but why did you guys change it? It was much simpler in previous builds.

python-spidev was only previously included in the image as it was a dependency for another package that we no longer include; in order to keep the size of the image down, we don’t include packages that aren’t used.

You should manage dependencies of additional packages you build or install yourself. apt includes a mechanism to do this – “sudo apt-get build-dep package-name” should install everything needed to build a package.

Ugh! We’re going backwards to keep the image size down. Given the cost of memory, I for one would be more than happy if an image of greater than 4Gbytes was available with everything on it. And, I bet there are plenty of people who feel the same way about this. Instead of Jessie Lite you could call it Fat Jessie.

Actually, I’m afraid there aren’t that many people who feel the same way as you – one of the most common complaints we receive is that the image is too big. It’s already nearly a gigabyte and a half in size – unless you have very fast broadband, that is a download which will take hours rather than minutes. If there is anything we can do to reduce the download size that doesn’t impact functionality, we do it.

Are you kidding me? Have you been to the U.S.? WE WANT IT ALL.

How exactly does PulseAudio come into play now on older Pis without any bluetooth device? This update broke the volume display/control of mpd/mpc on my Pi 2 (set to auto-login to desktop, did a dist-upgrade & reboot via ssh, no rpi-update (yet)). How do I disable PulseAudio which seems to be useless to me anyway?

“mpc volume” reports: n/a
“amixer cget numid=1” reports: 65535 = 100% (used to be 85%, saved between reboots)
“amixer cset numid=1 — [value or percentage]” does seem to set the correct value but has no effect now.

I should add: I use this Pi as internet radio via hdmi, nothing connected except power, ethernet & hdmi cables.

Pulseaudio should automatically be stopped if you are not using a Bluetooth device – it will start when the desktop boots and immediately be terminated by the volumealsa plugin if the last audio device used was not a Bluetooth device. If you aren’t using the volumealsa plugin, you may as well just uninstall pulseaudio – “sudo apt-get remove pulseaudio”.

Thanks, but what you’re saying is, there shouldn’t be anything different? There most certainly is, though. CLI alsa volume control with amixer or mpd is broken.

I will try uninstalling pulseaudio, but there must be more to it than the mere presence of the package.

Before I try uninstalling, “apt-cache rdepends pulseaudio” gives a long list of packages:

xpra
veromix-common
speech-dispatcher
scratch
python-x2go
pulseaudio-utils
pulseaudio-module-zeroconf
pulseaudio-module-x11
pulseaudio-module-raop
pulseaudio-module-lirc
pulseaudio-module-jack
pulseaudio-module-gconf
pulseaudio-module-bluetooth
pulseaudio-module-bluetooth
pulseaudio-esound-compat
pulseaudio-esound-compat
pulseaudio-dbg
projectm-pulseaudio
pavucontrol
osspd-pulseaudio
mpg123
mpd
morse
minimodem
mate-settings-daemon-pulse
mate-media-pulse
ltsp-server
ltsp-client-core
ltsp-client
lives
lightspark-common
libpulse0
libcanberra-pulse
|kde-telepathy-call-ui
initramfs-tools-tcos
gnome-settings-daemon
gnome-media
gnome-core
education-thin-client-server
earcandy
cinnamon-settings-daemon
cairo-dock-impulse-plug-in

Will they all switch to using alsa by default..? In other words, was pulseaudio absent from the previous standard installation of Raspbian? I did not install it explicitly but can’t remember if it came as a dependency before the dist-upgrde today.

pulseaudio was not present on the previous image (unless you installed it yourself for some reason). Before uninstalling it, you could try just killing the process (sudo pkill pulseaudio) and see if that fixes your problem. It sounds to me, though, as if your problem is something being corrupted somewhere in your install, not the fact that pulseaudio has been installed; a non-running pulseaudio daemon has no effect on ALSA devices that I have seen.

“Something corrupt somewhere in my install” sounds quite vague for a very specific problem. I appreciate that you don’t know the exact source of the problem, neither do I obviously, but I also did nothing weird with my installation except install mpd/mpc/alsa-tools (the latter already present in later Raspbians I believe?) and lighttpd/php for my radio interface, and some more unrelated stuff like locate/dnsutils/bc etc. “amixer cset numid=1 [n]” has been the cli way of adjusting volume, has it not? In any case, it always worked for me but no longer after dist-upgrade & reboot.

So I removed pulseaudio which also removed: pulseaudio-module-bluetooth pulseaudio-module-x11. Then autoremove also removed: libwebrtc-audio-processing-0 rtkit. After a reboot, CLI alsa volume control was back in business. The volume even appeared back as 85%, my previous setting.

My problem is solved, thanks. But I do think there’s more to it than something unique to my install.

Simon’s great, but he can’t see your install and he’s not psychic. We love him just the same.

I tried with a completely fresh install of the new download (Raspbian not Noobs). Steps I followed:
– start up
– update & dist-upgrade & reboot
– install mpd, mpc, alsa-tools & reboot
Contrary to my old upgraded install, amixer then worked: both “amixer cget numid=1” and “amixer cset numid=1 — 85%” worked as expected. But mpd/mpc still had the same trouble not being able to read/write the sound volume. Like before, that was fixed after I apt-get removed pulseaudio.

Perhaps not what you expected: that it wouldn’t have had any influence at all? So I guess my original question stands: “How exactly does PulseAudio come into play now [on older Pis without any bluetooth device]?” Maybe some programs like mpd act differently at the mere presence of the pulseaudio package.

I cant pair wiimote…!!!

How to connect to hidden wifi network?
http://www.thehecklers.org/2015/02/27/how-to-connect-raspberry-pi-to-hidden-ssid/
does not seem to work anymore

It would have been really useful if you’d put a wpa_supplicant.conf.example file in the /boot/ folder (which doesn’t exist on Windows, it’s just the root of the microSD) and another file telling people about the functionality.

Simple things!

How long does it take to integrate kernel 4.5 or 4.6 in Raspbian?

The Raspbian distribution begins to look like a new pc with windows. A lot of useless software has to be removed before you can begin working seriously. The other way around the Lite version it takes too long to install all the needed tools. We need a developers distribution without f.ex. the office tools and games etc…

We’ve found a possible fix for the “no Bluetooth controller found” error – on a card we have examined with this problem, the Pi-specific Bluetooth support package had become uninstalled.

If your Pi is similarly afflicted, “sudo apt-get install pi-bluetooth” should fix it – please let us know if not!

Repeated SD Card Copier Failures.

I’m excited to see simplified SD Card Copier addition to latest Raspbian. So first thing I tried after the update installation and reboot was to duplicate my original but updated Raspbian OS card to two new OOB Samsung 16 EVO cards.

Both attempts failed and, somehow, the result is that the destination cards now boot as prior-version NOOBS installs!

Each installation appeared to be progressing normally. The progress bar advanced as expected and reported five partitions were installed without error. Then when the “All Finished!” prompt appeared, the “OK” button was inoperative. I had to issue a Shutdown command to regain control of the Pi.

In a re-do attempt, I’ve tried repeating the entire SD Card Copier procedure on these disks and get an “Insufficient space” error MSG.

My USB card reader is a several-years-old Targus device that uses a MINI (not MICRO) USB port. I use it infrequently – and, before today, entirely on Windows-based hardware.

MY QUESTIONS:

1. What’s wrong? Why can’t I make a mirror-image copy of my ONLY functioning OS card? Have I misunderstood the purpose of the SD Card Copier (i.e., it’s only designed to make NOOBS disks and NOT produce mirror copies of a functioning Raspian OS disk)? Etc.

2. How can I “erase” (low level format) these SD cards to their original 16gb state?

Many thanks! The RasPi is a blast!!

Rick

PS I’ve built and used “small” computers since 1979. Along the way, I have forgotten about all the head-banging a new user must endure to become facile with technology-from-scratch (example: look what I’m experiencing right now while attempting to replicate a DOS 2.0 DISKCOPY command…).

I started that journey with the promise that these things would “save you time.” According to recent spreadsheet analysis, somebody out there owes me about ten years! But I’m still enjoying the ride.

2. SDformater wiil do the full format.
https://www.sdcard.org/downloads/formatter_4/
(Win and Mac only)

Just set the format size adjustment to ON in options.
https://yvonnezoe.files.wordpress.com/2013/08/sd-card-format.jpg

SDFormatter works like a champ! No errors reported and the card has returned to its 16GB splendor. Many thanks!!

A follow-up for anyone else watching this thread:

Using the SDFormatted disk, I again tried to make a copy of my Raspian OS card via the new CardCopier app.

No dice.

Once again, the app seems to have completed its task. It built five partitions and then reported as it copied data into each one.

Then it presented a “Copy complete” message with an “OK” button. The button is inactive and didn’t respond either to clocking or simply pressing .

After about 5 minutes, the “Copy complete” message disappeared and was replaced by an error message saying CardCopier isn’t responding. If I leave THAT message up on the screen without responding, the message will eventually disappear and I’m returned to the Desktop.

I issue a Shutdown command and then turn off RasPi 3B.

Then I insert the “duplicated” card into RasPi and turn it back on.

It loads and immediately presents the NOOBS v1.8 installation screen. So I select and pull RasPi’s power (there is no apparent-elegant way to bail out).

Any ideas, anyone?

At least Canon brand digital camera can reformat your failed sd card to fat in few seconds. Other camera brands probably work as well.

I tried “Make Discoverable” and my Android phone could find it (and it had the computer name) and I tried PIN codes 1234 and 0000 and the password, but none worked. Is it possible to connect to the Pi from a phone, and e.g. use the phone as a remote controller? Can one connect from one Pi to another Pi? I tried it and it was discovered, but then I didn’t know the PIN. I tried the password, but it said Authentication Rejected.

I have a Pi 2 with a bluetooth dongle, and a Pi Zero with another BT-dongle, and I can e.g. connect a BT-keyboard to each — so they probably work well.

As I wrote in the original post, “Bluetooth support is limited at this stage; you can pair with pretty much anything, but you can only usefully connect to devices which support either the Human Interface Device or Audio Sink services – in other words, mice, keyboards and other UI devices, and speakers and headsets.”

I created a small tutorial on how to get geany to display both an option for running python2 or python3 programs, from the build menu.

http://zleap.net/geany-build-commands/

This should work for other languages too, but I mainly use python.

Hope it is helpful

Paul

Old case wont accept new Zero 1.3, Bugger!

For some bizarre reason the default for Pi3 using the latest 4.4.9 kernel is to DISABLE UART.

To enable it you need to change enable_uart=1 in /boot/config.txt.

PhilE (Raspberry Pi Engineer & Forum Moderator) explained why (although I think the reason was pretty lame) and seemed that anyone who uses the UART should look in the Forum troubleshooting section to find why a service they had been using suddenly didn’t work.

Very many people use UART (e.g. for data logging or GPS), and turning it off without notice or explaining how to turn it on seems rather cavalier.

Much was made of the changes in UART with the release of the Pi3 (although the fact that it didn’t work until the user discovered the need to fix core_freq). I assumed this was a bug or oversight which would be fixed in the next release.

https://github.com/RPi-Distro/repo/issues/22#issuecomment-213100587 explains why (for the Pi3B only) the UART is disabled by default.

https://www.raspberrypi.org/documentation/configuration/raspi-config.md#serial explains how to enable the UART (but perhaps this info could be made easier to find somehow?)

Is there any way to *not* autoexpand the filesystem on first boot? I want to take a downloaded image, boot it up, add some packages to it, and then create a new image from that I can use to replicate to my other pi. I’m sure for most people autoexpand is great and definitely lowers the bar for new users, but it’s a problem for me.

Very nice updates! Raspbian feels more and more polished. :) I wish it was just as simple to set up VNC remote control or even a real-time clock.

Great work, guys! :)

I installed the latest update to Raspbian, and all looks good except there is no SC Card Copier app in the Accessories menu.

I am the only one that did this i guess. I typed my password with one finger and very slowly. Now, I cannot login. After spending 4 days perfecting my Pi3. I hate the world right now. Any jumpers. Anything at all. Please dont say I have to start over. It was so damn perfect. And, it was running at 1400 Mhz. And, it was never even warm. Im going to die.

http://www.raspberrypi-spy.co.uk/2014/08/how-to-reset-a-forgotten-raspberry-pi-password/ – you’re welcome!

Hi,

I raised the rdesktop/xrdp problem some time ago and have only just got back here to check progress. I am very pleased to say that the updates at the end of the document above have solved the problem. Thank you very much. I just don’t understand how the bluetooth setting affected the menu in X. Thank you again.

Peter

Should I be able to get these improvements via apt-get etc?

Since starting with Raspian Jessie I have added all sorts, and wouldn’t want to start again…

From the dates in the comments this happened just before or on 13th May, would be good to see a date associated with the post? Also, would be good to see the new version number quoted ;-)

I am trying to do this with a Noobs installation but am not getting things to work well. Pigpio daemon doesn’t work and the sd card copier isn’t available. I assume this is due to my Noobs vs Raspian install. Is there an instruction set anywhere with instructions to use this with a Noobs installation?

Thanks,
Jon

After dist-upgrade I get the new apps piclone and geany, but neither appear on the menus, even though there can be seen as selected on the Main Menu Editor in preferences. How do I sort this? I tried deselecting and reselecting them but to no avail.

Hello,
Just a quick note. I love playing with the Pi’s I have (2 2’s and a 3). There seem to be a fair amount of negativity in some of the comments. Since this a hobby I wonder why.
It’s should be fun and a chance to learn. I had been lazy and I used BerryBoot to add a USB drive for the file system. This broke with this update (see above) which forced me to do it the right way and along the way pick up a few new tricks.
Keep up the great work Simon.

Hi,
SD Copier: cloning a 8GB (NOOBS image) SD card to a 16GB one works, however it doesn’t expand the filesystem. I also can’t expand it with the Raspberry pi Configuration.

Hi,
mine might of worked but it said errors for both last 2 commands.This is what it said:sudo apt-get install piclone geany usb-modeswitch pi-bluetooth
Reading package lists… Done
Building dependency tree
Reading state information… Done
geany is already the newest version.
usb-modeswitch is already the newest version.
usb-modeswitch set to manually installed.
pi-bluetooth is already the newest version.
pi-bluetooth set to manually installed.
The following packages were automatically installed and are no longer required:
libasn1-8-heimdal libgssapi3-heimdal libhcrypto4-heimdal
libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal
libkrb5-26-heimdal libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5
libqt5qml5 libqt5quick5 libqt5widgets5 libroken18-heimdal libwind0-heimdal
libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-randr0
libxcb-render-util0 libxcb-xkb1 libxfce4ui-1-0 libxkbcommon-x11-0
qml-module-qtquick-controls qml-module-qtquick-dialogs
qml-module-qtquick-layouts qml-module-qtquick-privatewidgets
qml-module-qtquick-window2 qml-module-qtquick2 wiringpi
xfce-keyboard-shortcuts
Use ‘apt-get autoremove’ to remove them.
The following NEW packages will be installed:
piclone
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 12.7 kB of archives.
After this operation, 98.3 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.raspberrypi.org/debian/ jessie/ui piclone armhf 0.2 [12.7 kB]
Fetched 12.7 kB in 0s (115 kB/s)
Selecting previously unselected package piclone.
(Reading database … 120893 files and directories currently installed.)
Preparing to unpack …/archives/piclone_0.2_armhf.deb …
Unpacking piclone (0.2) …
Processing triggers for gnome-menus (3.13.3-6) …
Processing triggers for desktop-file-utils (0.22-1) …
Processing triggers for mime-support (3.58) …
Setting up bluez (5.23-2+rpi2) …
Job for bluetooth.service failed. See ‘systemctl status bluetooth.service’ and ‘journalctl -xn’ for details.
invoke-rc.d: initscript bluetooth, action “start” failed.
dpkg: error processing package bluez (–configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of pi-bluetooth:
pi-bluetooth depends on bluez; however:
Package bluez is not configured yet.

dpkg: error processing package pi-bluetooth (–configure):
dependency problems – leaving unconfigured
dpkg: dependency problems prevent configuration of pulseaudio-module-bluetooth:
pulseaudio-module-bluetooth depends on bluez (>= 4.40); however:
Package bluez is not configured yet.

dpkg: error processing package pulseaudio-module-bluetooth (–configure):
dependency problems – leaving unconfigured
Setting up piclone (0.2) …
Errors were encountered while processing:
bluez
pi-bluetooth
pulseaudio-module-bluetooth
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is what the other said:
sudo apt-get install python-pigpio python3-pigpio
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
libasn1-8-heimdal libgssapi3-heimdal libhcrypto4-heimdal
libheimbase1-heimdal libheimntlm0-heimdal libhx509-5-heimdal
libkrb5-26-heimdal libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5
libqt5qml5 libqt5quick5 libqt5widgets5 libroken18-heimdal libwind0-heimdal
libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-randr0
libxcb-render-util0 libxcb-xkb1 libxfce4ui-1-0 libxkbcommon-x11-0
qml-module-qtquick-controls qml-module-qtquick-dialogs
qml-module-qtquick-layouts qml-module-qtquick-privatewidgets
qml-module-qtquick-window2 qml-module-qtquick2 wiringpi
xfce-keyboard-shortcuts
Use ‘apt-get autoremove’ to remove them.
The following NEW packages will be installed:
python-pigpio python3-pigpio
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
Need to get 53.4 kB of archives.
After this operation, 319 kB of additional disk space will be used.
Get:1 http://archive.raspberrypi.org/debian/ jessie/main python-pigpio armhf 1.30-1 [26.7 kB]
Get:2 http://archive.raspberrypi.org/debian/ jessie/main python3-pigpio armhf 1.30-1 [26.7 kB]
Fetched 53.4 kB in 0s (336 kB/s)
Selecting previously unselected package python-pigpio.
(Reading database … 120902 files and directories currently installed.)
Preparing to unpack …/python-pigpio_1.30-1_armhf.deb …
Unpacking python-pigpio (1.30-1) …
Selecting previously unselected package python3-pigpio.
Preparing to unpack …/python3-pigpio_1.30-1_armhf.deb …
Unpacking python3-pigpio (1.30-1) …
Setting up bluez (5.23-2+rpi2) …
Job for bluetooth.service failed. See ‘systemctl status bluetooth.service’ and ‘journalctl -xn’ for details.
invoke-rc.d: initscript bluetooth, action “start” failed.
dpkg: error processing package bluez (–configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of pi-bluetooth:
pi-bluetooth depends on bluez; however:
Package bluez is not configured yet.

dpkg: error processing package pulseaudio-module-bluetooth (–configure):
dependency problems – leaving unconfigured
Setting up python-pigpio (1.30-1) …
Setting up python3-pigpio (1.30-1) …
Errors were encountered while processing:
bluez
pi-bluetooth
pulseaudio-module-bluetooth
E: Sub-process /usr/bin/dpkg returned an error code (1)

The game maker games for the pi don’t seem to work with the new update

The Ctrl-Alt-T doesn’t launch the terminal for me.
Any idea one? Anyone ran into this?

Would there be a way (simpler than bluetoothctl) to start the new Bluetooth GUI from a USB keyboard only?

This time I still had an old USB mouse around but since I no longer have any regular use for them, it could be given away without a second thought at any time.

On the Documentation part of the website, you have instructions to backup the SD card using command line prompts for Linux and Mac. I have Windows and it would be great if you would add a command line tool for Windows.

Hi,

I am using a RaspberryPi3 with the latetst Raspian Wheezy installed on it.
I encounter the problem that the clock will not sync if the RaspberryPi3 is connected with the internet over Wifi. When I use a LAN connection than the synchronization of the clock works. I solved the problem by adding at the end of the .bashrc file the line ‘sudo dpkg-reconfigure npt’. May you have a better solution for the problem or pindown what the real problem is?

Regards

Jean

1. I am running jessie 4.4 on a Rpi3. I can connect my BT speaker, via the Desktop method. I am running mopidy and can then have the audio play thru the BT speaker.

But the audio stops after ~ one hour or so. (I haven’t timed it). Is there a timeout setting in pulseaudio? Using the cli – top, show pulseaudio not running. bluetoothctl shows my speaker still connected.

2. I am trying to use a bash script to start pulseaudio and connect the BT speaker and start mopidy :
{ pulseaudio –start
echo -e ‘power on\nconnect 88:C6:26:07:B1:73 \nquit’ | bluetoothctl
mopidy
} –this is the commands in the script -not the script itself —
This works, but times out, stops playing music after ~ one hour.

Any thoughts.

Has anyone got the latest update version to work in cloning an SD card using a Pi 2 yet ?
When I try, it reports that it can’t create partitions……

Anyone have any ideas on how to get it to work???

Thanks

It is informative blog.SD card copier is the best for me.It is the easiest way.This gives the helpful information to me that i need it.I am waiting to get more information from your site.
Thanks for sharing this..

Hi Guys just wondering if you can give me some direction.
I am using a 32 G microsd card. when I put the latest image on the card. It shows up as 64Mb image. how can I fully use the size of the card? even though I do a raspi-config and select expand sdcard. Image is still like 64mb. Also when I do a sudo apt-get dist-upgrade. It always end up with error E: drive and stopped. It was better with the Aug 27 date image went farther. I can see the speed of the Pi after the update. Thanks.

I am having a problem with the Main Menu Editor. I change things and they show up OK in the menu editor, but the menu itself doesn’t change. Moving things up and down and unchecking things has no affect on the menu itself. This just started happening in the last few day.
On another note, I’m new to Linux and Raspberry Pi and find it to be an amazing piece of hardware and Raspbian has been amazing as well!

Just wanted to say “Thanks” for all the great work you’ve done Simon.

I spent time setting up a Pi3 for a friend today to surf the web and get email. It was easier than ever before to configure it for her and it looks great!

I bought a RPi3 last month. Initially both bluetooth and wifi worked but now i can’t use it. Is says no adapter found. How to fix it?

the raspbian-wheezy was working grate why change it!?
i hate this jessie crap!. i cant update or upgrade. dnsmasq squid everything more or less fails! nothing is working.

bring back raspbian wheezy plz!

Please do not resize the file system at first boot!

I want a seperate /home partition, this is no longer possible without a lot of work, that was not necessary in the previous release.

It is too late to make any changes after the initial boot, the resizing is done during the first boot, no questions asked, it is not necessary and not desired. A quite surprising change. What’s wrong with running raspi-config at first login? This gives the user a chance to choose something.

Now it’s up to me to clean up this mess, caused by a script, that simply shouldn’t have run.

Please fix auto-resizing-no-questions-asked isssue this in the next release.

It’s not a feature, it’s a bug :-)

This feature was introduced in the previous release, not in this one. It’s a deliberate decision – too many people were having problems with running out of space and their Pis becoming unusable due to forgetting to resize the file system. While there are a few people like you who don’t want to resize the partition, the vast majority of users do, and with all the changes we make to Raspbian, the intention is to make the life of the majority as easy as possible.

Here is a workaround for this issue – I found it on another page, so I won’t take credit for it. But I tried it, and it worked. In short: Mount the boot partition from the image file, find the kernel command line (/boot/cmdline.txt) and obliterate the last part (init=/usr/lib/raspi-config/init_resize.sh). And please – could you just ask a question about it – you can have a default choice and a timeout, but please leave the choice to the user. The other thing is called Windows and MacIntosh :-)

(http://raspberrypi.stackexchange.com/questions/47773/disable-auto-file-system-expansion-in-new-jessie-image-2016-05-10)

Here is an example using 2016-05-10-raspbian-jessie-lite.img.

Try this:

fdisk -lu ./2016-05-10-raspbian-jessie-lite.img

You’ll get this information:

Device Boot Start End Blocks Id System

2016-05-10-raspbian-jessie-lite.img1 8192 137215 64512 c W95 FAT32 (LBA)

2016-05-10-raspbian-jessie-lite.img2 137216 2707455 1285120 83 Linux

So for the boot section your offset is (Start*512) = 8192 * 512 = 4194304

For the Raspbian filesystem your offset is (Start*512) = 137216 * 512 = 70254592

mkdir boot
sudo mount -t vfat -o loop,offset=4194304 2016-05-10-raspbian-jessie-lite.img boot

If you want to view/edit the Raspbian Filesystem. Not needed though.

mkdir test
sudo mount -t ext4 -o loop,offset=70254592 2016-05-10-raspbian-jessie-lite.img test

Then you need to modify the ./boot/cmdline.txt file.

sudo gedit ./boot/cmdline.txt

From:

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet init=/usr/lib/raspi-config/init_resize.sh

To:

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet

sudo umount ./boot

If you mounted the Raspbian filesystem:

sudo umount ./test

Now flash the new image to your SD card.

2016-05-10-raspbian-jessie-lite.img

It won’t automatically expand after booting up on your Pi.

I am kinda screwed. I misunderstood the application and was backing up my sd card to a USB stick. I was hoping it will create an image file…but it doesnt :(

I have the backup on an external USB drive. My sd card is now corrupted. Is there nay means that I could recover my files (if possible every thing, configuration bla bla..) from the USB drive??

I look forward to your comments

Similar situation here
please help

Yes – you’ll need to be able to boot a Pi to do so, though. You’ll also need a USB SD card reader. Put a blank SD card into the USB card reader and connect it to a USB port on your Pi; connect your USB stick with the backup to another USB port on your Pi. Run SD Card Copier, and choose your USB stick as the source and the USB card reader as the target – run the copy. You should then have the contents of your original SD card on the new card.

Thanks for the help.

Unfortunately, I did not get it working. The back up is on a USB drive (1TB size) with some other files. Using the raspberry pi sd card copier software I am unable to locate to the back up file in the USB drive. It selects the drive as a whole. I put the destination sd card in the usb writer and tried to copy. But it gets interrupted, saying ‘cannot create partition …’

Any thought?

There is no backup file on the USB drive – the entire drive is the backup! This tool copies one entire drive onto another. If you are getting partition creation errors, try a different SD card, or try reformatting the card on a PC or Mac to erase all the partitions and start from scratch.

I downloaded and installed the latest Raspbian image file on a 32GB SD card and installed it in my Raspi3B yesterday. Raspbian booted up fine using my TV as the display. (The new look and features are great by the way). I attempted to enable the VNCServer option in the configuration menu, but it does not seem to start-up during the boot process. It works if I go in through SSH and then run VNCServer. I tried several other methods (rc.local and another option I found on another forum), but neither seem to work. there methods worked on my previous installation. What do I need to do to get VNCServer to start at boot?

I have lates Raspian (Raspbian Jessie with PIXEL). I made successful pairing with some USB-devices in the bluetooth plugin. Problems is that when I try to connect from RPi to some device (phone or JY-MCU) RPi informs “connection failed – no usable services on this device”. I haven’t found any explanation for this. Does someone knows what is wrong?

Where is raspberry-Pi3 Bluetooth icon path??
(Add DEvice.. & Remove Device.. )
Is this used Python code??
Thanks.

Comments are closed

News

Related posts

Another new Raspbian release

Another Raspbian Desktop User Interface Update

Latest Raspbian update

Next Post

Zero grows a camera connector

Previous Post

Gesture control for your TV

Share this post

324 comments

Anton

Giles

Giles

Serge Schneider

Stuart Hunter

Matthew

sam

Raspberry Pi Staff Simon Long — post author

dom

dom

Alexander Brown

Stuart Hunter

B.Goode

Serge Schneider

procount

B.Goode

procount

KeithB

JPW

Cancelor

elParaguayo

Raspberry Pi Staff Simon Long — post author

JPW

Laurence Tyler

Serge Schneider

Jens

Raspberry Pi Staff Simon Long — post author

procount

DirkS

Raspberry Pi Staff Simon Long — post author

Peter Green

procount

Clark Wierda

beta-tester

Darren Townsend

tim Rowledge

Darren Townsend

Cancelor

dan3008

DirkS

Tom Fotherby

Clinton Morse

Serge Schneider

Larry Dighera

Larry Dighera

Trevor Harris

graycrow

Saijin_Naib

Jam_Alex

Peter Rich

Raspberry Pi Staff Simon Long — post author

Jam_Alex

rpiMike

Trevor Harris

vlad

Bonzadog

BbMech7

Stefan

Raspberry Pi Staff Simon Long — post author

Stefan

Matt

Jeffrey F

Raspberry Pi Staff Simon Long — post author

Jeffrey F.

Isaac LastName

vlad

laurent

Raspberry Pi Staff Simon Long — post author

laurent