Description of problem: It is no longer possible to send a file from a mobile phone to a computer under Mageia Linux since its fourth version (it's a regression) even when doing the pairing anew. Version-Release number of selected component (if applicable): Bluez 5-11 How reproducible: Always Steps to Reproduce: 1. Choose a file to send on your mobile phone 2. Activate the bluetooth on your mobile phone 3. Activate the bluetooth on your computer by right-clicking on the bluetooth icon in the bottom right corner in the task bar 4. Select the menu item "discoverable" to drive your computer discoverable 5. Select the computer as the device to which you'll try to send the file 6. It fails, journalctl indicates this error message: Dec 29 12:45:26 mercury obexd[5438]: open(/tmp/IMG_20131225_200111.jpg): Operation not permitted (1) The root cause is simple, bluez uses the root temporary folder instead of using the user's temporary folder, this patch fixes this bug: https://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=841896ae172c08c1652af88d0994f0349912ed14 This bug is already fixed in Cauldron as it uses Bluez 5-18. Reproducible: Steps to Reproduce:
CC: (none) => gouessej
Actually, switching to Bluez 5-18 doesn't fix this bug, I've just tested with the package available for Cauldron.
The commit you linked is already in 5.18, so if it fixes the problem, 5.18 should work. Did you reboot after upgrading to 5.18 to make sure all relevant services got restarted?
CC: (none) => guillomovitchAssignee: bugsquad => shlomif
Yes I rebooted to be sure to get a restarted service using Bluez 5.18. Actually, the patch that I linked to wouldn't have fixed the bug because ls -l /tmp shows that my user is allowed to read and write. Journalctl tells there is no journal now :( How can I help you? In the meantime, I'll install Mageia 4 on another computer with a build-in 6 in 1 memory card reader as I can't use the bluetooth. How can I reenable the journals?
Hardware: i586 => All
I installed Mageia Linux 4 on a bits machine, it's still reproducible: juin 07 18:08:08 localhost obexd[9873]: CONNECT(0x0), (null)(0xffffffff) juin 07 18:08:08 localhost obexd[9873]: CONNECT(0x0), (null)(0x0) juin 07 18:08:09 localhost obexd[9873]: PUT(0x2), (null)(0xffffffff) juin 07 18:08:09 localhost obexd[9873]: open(/tmp/20140525_193237.jpg1): Operation not permitted (1) juin 07 18:08:09 localhost obexd[9873]: PUT(0x2), FORBIDDEN(0x43) juin 07 18:08:09 localhost obexd[9873]: DISCONNECT(0x1), (null)(0xffffffff) juin 07 18:08:09 localhost obexd[9873]: DISCONNECT(0x1), SUCCESS(0x20) juin 07 18:08:09 localhost obexd[9873]: disconnected: Transport got disconnected
Sorry I meant "64 bits".
I get the same error when using Bluez 5.19.1 and Obex 0.48.2.
In VirtualBox, M3, KDE, 32-bit Package(s) under test: kernel-desktop-latest vboxadditions-kernel-desktop-latest default install of kernel-desktop-latest & vboxadditions-kernel-desktop-latest [root@localhost wilcal]# uname -a Linux localhost 3.10.40-desktop-1.mga3 #1 SMP Fri May 16 19:32:50 UTC 2014 i686 i686 i686 GNU/Linux [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-4.3.10-5.mga3.i586 is already installed M3 boots to a working desktop install kernel-desktop-latest & vboxadditions-kernel-desktop-latest from updates_testing [root@localhost wilcal]# uname -a Linux localhost 3.10.42-desktop-1.mga3 #1 SMP Fri Jun 6 21:34:34 UTC 2014 i686 i686 i686 GNU/Linux [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-4.3.10-6.mga3.i586 is already installed M3 boots to a working desktop Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
CC: (none) => wilcal.int
In VirtualBox, M3, KDE, 64-bit Package(s) under test: kernel-desktop-latest vboxadditions-kernel-desktop-latest default install of kernel-desktop-latest & vboxadditions-kernel-desktop-latest [root@localhost wilcal]# uname -a Linux localhost 3.10.40-desktop-1.mga3 #1 SMP Fri May 16 19:05:51 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-4.3.10-5.mga3.x86_64 is already installed M3 boots to a working desktop install kernel-desktop-latest & vboxadditions-kernel-desktop-latest from updates_testing [root@localhost wilcal]# uname -a Linux localhost 3.10.42-desktop-1.mga3 #1 SMP Fri Jun 6 21:08:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [root@localhost wilcal]# urpmi vboxadditions-kernel-desktop-latest Package vboxadditions-kernel-desktop-latest-4.3.10-6.mga3.x86_64 is already installed M3 boots to a working desktop Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64
sorry discard #7 & #8
Apparently, you need an application to control obex access, such as gnome-user-share for instance, not just bluez: http://www.spinics.net/lists/linux-bluetooth/msg46206.html
Status: NEW => ASSIGNED
Created attachment 5225 [details] KDE Setup module for Bluetooth
I already use the KDE setup module for Bluetooth to control obex access, isn't it enough?
Could it fix this bug? https://bugzilla.novell.com/show_bug.cgi?id=842688#c8
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD