Your message dated Thu, 7 Jun 2012 19:39:54 -0400
with message-id <[email protected]>
and subject line Barry 0.18.3-3 contains mentioned fix
has caused the Debian Bug report #582195,
regarding barrybackup-gui: Cannot backup content as a regular user (permissions
issue)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
582195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582195
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: barrybackup-gui
Version: 0.15-1
Severity: important
Tags: upstream
Starting barrybackup-gui as a regular user in its default configuration does
not work
and barfs with a weird and useless error message.
When run as a normal user in my system it shows up the main window for backups,
waits
a few seconds and then shows up an error message saying (both in stderr and in
a window):
"Usb::Error caught in main:
(-1, error sending control message: Operation not permitted): Probe:
GetConfiguration failed"
When you click "OK" in the window with the error message the program quits.
Leaving you clueless as to what the root cause of the issue is.
Upon reviewing an strace of the program it looks like Barry Backup tries to
scan all
the devices in the USB bus, is not able to access them and barfs. I can see many
lines like this:
(...)
open("/dev/bus/usb/002/002", O_RDWR) = -1 EACCES (Permission denied)
open("/dev/bus/usb/002/002", O_RDONLY) = 8
ioctl(8, USBDEVFS_IOCTL, 0xbf9e39e4) = -1 EPERM (Operation not permitted)
(...)
I've looked at the files under /dev/bus/usb/ and have found that, even though
there are u-dev rules setup by barry-utils, these do not seem to be applied in
a proper manner:
$ lsusb |grep Research
Bus 001 Device 006: ID 0fca:8004 Research In Motion, Ltd.
$ ls -la /dev/bus/usb/001/006
crw-r--r-- 1 root plugdev 189, 5 may 19 01:05 /dev/bus/usb/001/006
^^^^
Notice the lack of write permissions for /dev/bus/usb/001/006.
Though the user I'm running with belongs to the plugdev group, the device
file permissions are not set up properly. Which is probably related to #561243
and easily fixed with the script below:
--------------------------------------------------------------------------
#!/bin/sh -e
# Find bus and device ID
usb_bus=`lsusb -d 0fca: | awk '{print $2 }'`
usb_device=`lsusb -d 0fca: | awk '{print $4 }' | sed -e 's/:$//'`
if [ -z "$usb_bus" ] || [ -z "$usb_device" ] ; then
echo "Cannot find a RIM device in the USB bus" >&2
exit 1
fi
if [ ! -e "/dev/bus/usb/${usb_bus}/${usb_device}" ] ; then
echo "Found RIM device at BUS ${usb_bus} DEVICE ${usb_device}.." >&2
echo " but cannot find a proper device file for it" >&2
exit 1
fi
echo "Changing device permissions for RIM device..."
sudo chmod g+w /dev/bus/usb/${usb_bus}/${usb_device}
echo "..done"
exit 0
--------------------------------------------------------------------------
However, it might be nice if the application instead of bailing out with such
an error presented a *useful* error message such as:
"I'm sorry, I am unable to access a RIM device in this system. Please review
the permissions for your USB devices."
Additionally, the strace dump shows that it tries to probe all the available
USB devices connected to the system. Since lsusb shows this:
Bus 004 Device 001: ID xxxx:xxxxx Not appliable...
Bus 002 Device 002: ID xxxx:xxxxx Not appliable...
Bus 002 Device 001: ID xxxx:xxxxx Not appliable...
Bus 003 Device 001: ID xxxx:xxxxx Not appliable...
Bus 005 Device 001: ID xxxx:xxxxx Not appliable...
Bus 001 Device 006: ID 0fca:8004 Research In Motion, Ltd.
Bus 001 Device 001: ID xxxx:xxxxx Not appliable...
Why doesn't it try to just prove bus 1 / device 6 ?
Regards
Javier
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Shell: /bin/sh linked to /bin/bash
Versions of packages barrybackup-gui depends on:
ii libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii libbarry0 0.15-1 Library for using the BlackBerry h
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libcairo2 1.8.10-3+b1 The Cairo 2D vector graphics libra
ii libcairomm-1.0-1 1.8.0-1 C++ wrappers for Cairo (shared lib
ii libfontconfig1 2.8.0-2 generic font configuration library
ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib
ii libgcc1 1:4.4.3-7 GCC support library
ii libglade2-0 1:2.6.4-1 library to load .glade files at ru
ii libglademm-2.4-1c2a 2.6.7-2 C++ wrappers for libglade2 (shared
ii libglib2.0-0 2.24.0-1 The GLib library of C routines
ii libglibmm-2.4-1c2a 2.24.0-1 C++ wrapper for the GLib toolkit (
ii libgtk2.0-0 2.20.0-2 The GTK+ graphical user interface
ii libgtkmm-2.4-1c2a 1:2.20.1-1 C++ wrappers for GTK+ (shared libr
ii libpango1.0-0 1.28.0-1 Layout and rendering of internatio
ii libpangomm-1.4-1 2.26.0-1 C++ Wrapper for pango (shared libr
ii libsigc++-2.0-0c2a 2.2.4.2-1 type-safe Signal Framework for C++
ii libstdc++6 4.4.3-7 The GNU Standard C++ Library v3
ii libtar 1.2.11-6 C library for manipulating tar arc
ii libusb-0.1-4 2:0.1.12-14 userspace USB programming library
ii libxml2 2.7.7.dfsg-2 GNOME XML library
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
barrybackup-gui recommends no packages.
barrybackup-gui suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: barry
Version: 0.18.3-3
My previous email on this, before I was maintainer, said:
> While the permissions issues have been long fixed in version
> 0.17.x and the upcoming 0.18.x, the user friendly error message was
> still a valid request.
>
> So I coded it up. The latest Barry git repo has this fixed. When
> version 0.18.x gets releasd, and makes it to the Debian repos,
> this bug can be closed.
These fixes are now available in sid.
- Chris
--- End Message ---
