Bug 478851
Summary: | barry cannot connect to Blackberry Bold: -1, error sending control message: Operation not permitted): Probe: GetConfiguration failed | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nick Boldt <nickboldt+redhat> | ||||||
Component: | barry | Assignee: | Christopher D. Stover <quantumburnz> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 11 | CC: | awilliam, cochranb, john.ellson, jyuille5, pmachata, quantumburnz, sonarguy | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | 0.15-0.7.20090630git.fc9 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2009-07-03 19:32:30 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Nick Boldt
2009-01-05 16:48:11 UTC
chmod trick worked. As did simply running barrybackup as root. But since barrybackup is added to the user's Gnome menu under Accessories, shouldn't it at least be wrapped with ConsoleKit so the user's prompted to run it as root? Thanks for the bug report Nick. Upstream is aware of this issue. However when I tried Petr's trick I got this: Usb::Error caught in main: (-2, error submitting URB: No such file or directory): Error in usb_bulk_read Have you seen this on your end? I'm not familiar with ConsoleKit other than quickly looking at their website, but I'll pass it upstream and hopefully we can get it fixed soon. I haven't see the error you did. Running after chmod'ing (as myself or as root) worked as expected. Maybe you're missing one of the deps that are stated as requirements (but not resolved by yum when installing?): http://www.netdirect.ca/software/packages/barry/dependencies.php Or maybe you have a different version of libopensync? The docs state I should be using 0.22, but Fedora 10 (ie., yum) installed 0.36 for me. Seems there's another packaging requirement problem there too -- shouldn't yum know to backlevel to 0.22 instead of installing the latest, if the latest isn't supported? I'm still trying to figure out how to do all the other touted things I can supposedly do with barry. Perhaps because the tools aren't all named "barry*", I've only found the backup tool. How does one sync or install apps? BTW, running this seems to show that barry 0.14.4-fc10 does NOT actually declare its dependency on libopensync (or maybe I'm doing this wrong?) $ yum deplist barry | grep sync $ yum deplist barry-libs | grep sync Nope, I double checked and I have all the required deps. As for libopensync, I've filed a bug against it: https://bugzilla.redhat.com/show_bug.cgi?id=474070. The version of libopensync Fedora is using is not the stable version and barry is incompatible with it. Therefore, if you're using anything newer than F8, you will be unable to sync. To my knowledge, there's no program at the moment that will allow you to install things. My main reason for installing and packaging barry was the ability to charge my phone. When you plug in your phone, it automatically runs bcharge. However, you are able to tether your phone if you use your phone for the internet. I have the same issue with my Blackberry 8330 when using the usb interface. (-1, error sending control message: Operation not permitted): Probe: GetConfiguration failed I have tried the all the workarounds listed in this bug with no change in status: chmod a+rwx /dev/bus/usb/<bus>/<device> It still displays the same message, I have also check all the dependencies listed on page http://www.netdirect.ca/software/packages/barry/dependencies.php and have them installed. If you need further information let me know. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Created attachment 342029 [details]
Error message from barry on Fedora 11 Preview, x86_64, Blackberry 8830
I connected my Blackberry 8830 World Edition (provided by Sprint) while it was turned on and running, to my laptop over USB. Then I clicked Applications > Acessories > backup and got the error message shown in the png.
Output from the operation described in comment #7, in /var/log/messages: Apr 30 21:18:03 deafeng3 kernel: usb 6-1: new full speed USB device using uhci_hcd and address 2 Apr 30 21:18:03 deafeng3 kernel: usb 6-1: New USB device found, idVendor=0fca, idProduct=0006 Apr 30 21:18:03 deafeng3 kernel: usb 6-1: New USB device strings: Mfr=1, Product=4, SerialNumber=3 Apr 30 21:18:03 deafeng3 kernel: usb 6-1: Product: RIM Mass Storage Device Apr 30 21:18:03 deafeng3 kernel: usb 6-1: Manufacturer: Research In Motion Apr 30 21:18:03 deafeng3 kernel: usb 6-1: SerialNumber: 920DFBC8567158EE53A4FBEB560AB2B3F6045F66 Apr 30 21:18:03 deafeng3 kernel: usb 6-1: configuration #1 chosen from 1 choice Apr 30 21:18:03 deafeng3 kernel: usb 6-1: USB disconnect, address 2 Apr 30 21:18:03 deafeng3 kernel: usb 6-1: new full speed USB device using uhci_hcd and address 3 Apr 30 21:18:04 deafeng3 kernel: usb 6-1: New USB device found, idVendor=0fca, idProduct=0004 Apr 30 21:18:04 deafeng3 kernel: usb 6-1: New USB device strings: Mfr=1, Product=5, SerialNumber=3 Apr 30 21:18:04 deafeng3 kernel: usb 6-1: Product: RIM Composite Device Apr 30 21:18:04 deafeng3 kernel: usb 6-1: Manufacturer: Research In Motion Apr 30 21:18:04 deafeng3 kernel: usb 6-1: SerialNumber: 920DFBC8567158EE53A4FBEB560AB2B3F6045F66 Apr 30 21:18:04 deafeng3 kernel: usb 6-1: configuration #1 chosen from 1 choice Apr 30 21:18:04 deafeng3 kernel: Initializing USB Mass Storage driver... Apr 30 21:18:04 deafeng3 kernel: scsi6 : SCSI emulation for USB Mass Storage devices Apr 30 21:18:04 deafeng3 kernel: usbcore: registered new interface driver usb-storage Apr 30 21:18:04 deafeng3 kernel: USB Mass Storage support registered. Apr 30 21:18:09 deafeng3 kernel: scsi 6:0:0:0: Direct-Access RIM BlackBerry SD 0001 PQ: 0 ANSI: 4 CCS Apr 30 21:18:09 deafeng3 kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk Apr 30 21:18:09 deafeng3 kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0 Apr 30 21:21:08 deafeng3 kernel: usb 6-1: USB disconnect, address 3 Apr 30 21:21:35 deafeng3 kernel: usb 6-1: new full speed USB device using uhci_hcd and address 4 Apr 30 21:21:35 deafeng3 kernel: usb 6-1: New USB device found, idVendor=0fca, idProduct=0006 Apr 30 21:21:35 deafeng3 kernel: usb 6-1: New USB device strings: Mfr=1, Product=4, SerialNumber=3 Apr 30 21:21:35 deafeng3 kernel: usb 6-1: Product: RIM Mass Storage Device Apr 30 21:21:35 deafeng3 kernel: usb 6-1: Manufacturer: Research In Motion Apr 30 21:21:35 deafeng3 kernel: usb 6-1: SerialNumber: 920DFBC8567158EE53A4FBEB560AB2B3F6045F66 Apr 30 21:21:35 deafeng3 kernel: usb 6-1: configuration #1 chosen from 1 choice Apr 30 21:21:35 deafeng3 kernel: scsi7 : SCSI emulation for USB Mass Storage devices Apr 30 21:21:35 deafeng3 kernel: usb 6-1: usbfs: interface 0 claimed by usb-storage while 'bcharge' sets config #1 Apr 30 21:21:35 deafeng3 kernel: usb 6-1: USB disconnect, address 4 Apr 30 21:21:36 deafeng3 kernel: usb 6-1: new full speed USB device using uhci_hcd and address 5 Apr 30 21:21:36 deafeng3 kernel: usb 6-1: New USB device found, idVendor=0fca, idProduct=0004 Apr 30 21:21:36 deafeng3 kernel: usb 6-1: New USB device strings: Mfr=1, Product=5, SerialNumber=3 Apr 30 21:21:36 deafeng3 kernel: usb 6-1: Product: RIM Composite Device Apr 30 21:21:36 deafeng3 kernel: usb 6-1: Manufacturer: Research In Motion Apr 30 21:21:36 deafeng3 kernel: usb 6-1: SerialNumber: 920DFBC8567158EE53A4FBEB560AB2B3F6045F66 Apr 30 21:21:36 deafeng3 kernel: usb 6-1: configuration #1 chosen from 1 choice Apr 30 21:21:36 deafeng3 kernel: scsi8 : SCSI emulation for USB Mass Storage devices Apr 30 21:21:41 deafeng3 kernel: scsi 8:0:0:0: Direct-Access RIM BlackBerry SD 0001 PQ: 0 ANSI: 4 CCS Apr 30 21:21:41 deafeng3 kernel: sd 8:0:0:0: [sdb] Attached SCSI removable disk Apr 30 21:21:41 deafeng3 kernel: sd 8:0:0:0: Attached scsi generic sg2 type 0 Apr 30 21:22:29 deafeng3 kernel: usb 6-1: USB disconnect, address 5 I installed, on a Fedora 11 Preview on x86_64 laptop: libopensync libtar-devel then I ran /sbin/lsusb to find out which bus and device my Blackberry was assigned to. Turned out to be bus 006 device 003 then I ran the trick mentioned in the problem description, where chmod a+rwx /dev/bus/usb/<bus>/<device> was modified to chmod a+rwx /dev/bus/usb/006/003 and I tried using Barry again with the goal of performing a backup. It worked like a charm! So it looks like changing the barry package to include libopensync and libtar-devel as dependencies will help. Thanks Bob. I'm going to be building a new snapshot of Barry tomorrow hopefully. I'll be building with the libopensync dependency since Fedora downgraded it. Please keep your eye out for this and let me know how it works for you. It should be available on Rawhide in the next couple days. It looks like Blackberry devices can get assigned to different /dev/bus/usb/<bus>/<device>. Yesterday, my Blackberry was on /dev/bus/usb/006/003, today it looks like it is on /dev/bus/usb/006/005. The device number changed. This behavior can upset the barry software if the new device doesn't have rwx permissions on it. I went through the chmod routine once more and was able to get today's backup to work. Here is the output of /sbin/lsusb and the chmod action I took: # /sbin/lsusb Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 0c45:63f8 Microdia Bus 001 Device 011: ID 045e:0084 Microsoft Corp. Basic Optical Mouse Bus 001 Device 010: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard Bus 001 Device 009: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 012: ID 413c:8153 Dell Computer Corp. Bus 001 Device 013: ID 413c:8154 Dell Computer Corp. Bus 001 Device 003: ID 413c:2513 Dell Computer Corp. Bus 001 Device 007: ID 413c:8149 Dell Computer Corp. Bus 001 Device 008: ID 0a5c:4500 Broadcom Corp. Bus 001 Device 004: ID 413c:2513 Dell Computer Corp. Bus 001 Device 002: ID 0424:2512 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 005: ID 0fca:0004 Research In Motion, Ltd. Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub # chmod a+rwx /dev/bus/usb/006/005 [barry is able to find the Blackberry device at this point] [barry is able to back up the Blackberry device at this point] Each time you connect a Blackberry to a Fedora 11 system, the /dev/bus/usb/[bus]/[device] assigned to it has to have permissions freshly assigned through chmod. This means becoming root and doing the chmod as a preprequisite to doing the backup. I presume udev does all the work of creating the device entry, but doesn't assign friendly permissions to it. Perhaps barry can add an appropriate udev rule for me at install time? I'll also ask around on the Fedora-list to see if I can add a rule manually. Barry does ship with a /etc/security/console.perms.d/10-blackberry.perms file, with the contents: <blackberry>=/dev/bb-* <console> 0660 <blackberry> 0660 root which suggests that it expects the Blackberry device nodes to be /dev/bb-* ...maybe this needs updating? This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Bug still exists in Rawhide - fc12 barry-0.15-0.7.20090630git.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/barry-0.15-0.7.20090630git.fc9 barry-0.15-0.7.20090630git.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/barry-0.15-0.7.20090630git.fc10 barry-0.15-0.7.20090630git.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/barry-0.15-0.7.20090630git.fc11 barry-0.15-0.6.20090623git.fc11.x86_64, installed on my machine, no longer has an entry on my Gnome applications menu under "Accesories" where it once was. Running 'barrybackup' as an ordinary user gets an error: [rlc@deafeng3 ~]$ barrybackup Usb::Error caught in main: (-1, error sending control message: Operation not permitted): Probe: GetConfiguration failed (barrybackup:7936): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed I again had to follow this process as root: [root@deafeng3 ~]# lsusb Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 010: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard Bus 001 Device 011: ID 045e:0084 Microsoft Corp. Basic Optical Mouse Bus 001 Device 004: ID 413c:2513 Dell Computer Corp. Bus 001 Device 006: ID 0c45:63f8 Microdia Bus 001 Device 009: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 013: ID 413c:8154 Dell Computer Corp. Bus 001 Device 012: ID 413c:8153 Dell Computer Corp. Bus 001 Device 008: ID 0a5c:4500 Broadcom Corp. Bus 001 Device 007: ID 413c:8149 Dell Computer Corp. Bus 001 Device 003: ID 413c:2513 Dell Computer Corp. Bus 001 Device 002: ID 0424:2512 Standard Microsystems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 008: ID 0fca:0004 Research In Motion, Ltd. Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub [root@deafeng3 ~]# chmod a+rwx /dev/bus/usb/006/008 ...at which point `barrybackup` worked. Bob Thanks Bob. I temporarily removed the menu entry, but it will reappear in the next update with an icon instead of a blank spot where an icon should be. The permission issues have also been fixed if the next update. You're welcome to download the update from testing and give it a karma rating if you like. Thank you for taking the time to submit the additional info to this bug report. Chris barry-0.15-0.7.20090630git.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. barry-0.15-0.7.20090630git.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. barry-0.15-0.7.20090630git.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report. There is a huge improvement with barry-0.15-0.7.20090630git.fc11.x86_64. For the first time, it was able to back up my device just by my opening the appication from the Applications...Accessories graphical menu and clicking the backup button. Two clicks and no fooling with chmod. Well done, thanks! Now I just need to wait for my Blackberry to have a tough day and crash and see if barry can restore the data. Bob This problem is now occurring in Fedora 12. I just attempted to do a backup on Fedora 12, and it failed. I'm attaching a screenshot of the error message. I will be happy to reopen this bug under Fedora 12 if desired. Thanks, Bob Cochran Created attachment 376132 [details]
Error message on Barry Backup in Fedora 12 (release version)
As I have been able to Google over this permission issue, I have finally been able to backup my BlackBerry Curve 8310 with the Barry GUI as a root user using chmod. Will this problem be fixed in Fedora 12 anytime soon? Then again, I should be satisfied that I am able to backup my BlackBerry, period. |