Bug 533397 - Podsleuth has no messagebus policy
Summary: Podsleuth has no messagebus policy
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: podsleuth
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christian Krause
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 495240
TreeView+ depends on / blocked
 
Reported: 2009-11-06 15:49 UTC by Tim Waugh
Modified: 2009-12-12 16:20 UTC (History)
2 users (show)

Fixed In Version: 0.6.5-2.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-11-25 15:29:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
podsleuth.conf (299 bytes, text/plain)
2009-11-06 15:49 UTC, Tim Waugh
no flags Details

Description Tim Waugh 2009-11-06 15:49:52 UTC
Created attachment 367835 [details]
podsleuth.conf

Description of problem:
One of the problems causing podsleuth not to work is that there is no messagebus policy for it.  The default has changed since Fedora 9 to deny all, so we need to explicitly allow messages through to org.podsleuth.

Version-Release number of selected component (if applicable):
podsleuth-0.6.5-1.fc12.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Plug in an iPod
2.podsleuth --rescan --debug
  
Actual results:
Rescanning device [/org/freedesktop/Hal/devices/volume_uuid_74FE_2EA5]

Unhandled Exception: System.Exception: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.238" (uid=500 pid=21103 comm="mono) interface="org.podsleuth" member="Scan" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=1551 comm="hald))
  at IPodSleuthProxy.Scan () [0x00000] 
  at PodSleuth.HalFrontend.HalClient.Run (System.String[] args) [0x00000] 
  at PodSleuth.HalFrontend.HalEntry.Main (System.String[] args) [0x00000]

Expected results:
Rescanning device [/org/freedesktop/Hal/devices/volume_uuid_74FE_2EA5]
iPod Found [/org/freedesktop/Hal/devices/volume_uuid_74FE_2EA5]
  * Generic Device Properties
    - Block Device:       /dev/sdc2
    - Mount Point:        /media/MY IPOD
    - Read Only:          False
    - Volume Size:        4 GiB
  * General iPod Properties
    - Serial Number:      
    - Firewire ID:        
    - Firmware Version:   
    - iPod_Control:       /iPod_Control
    - Extra Capabilities: none
    - Production Info:    Unknown
  * iPod Model Properties
    - Device Class:       
  * Image Types Supported
    - Photos:             False
    - Album Art:          False
    - Chapter Images:     False

(No serial number etc due to an SELinux denial, which I will file separately.)

Additional info:
Attached is an example policy file which lets me get as far as shown above.

Comment 1 Christian Krause 2009-11-11 23:40:00 UTC
Thanks for the bug report. Indeed it had a similar policy applied locally during all of the bug hunting... :-)

I've looked at your example and it looks like, that this policy would give each and every user on the system the right to:

- update the ipod database cache of podsleuth
- (re)-start a scan of the attached IPods

I think it would be the best to do the following:
- the service should be only allowed to be owned by root (IMHO effectively the interface is provided by hal and hal runs as root anyway)
- only users at a local console (<policy at_console="true">) are allowed to use the interface

Do you think that's reasonable?

Comment 2 Tim Waugh 2009-11-12 09:07:08 UTC
Sounds reasonable to me.

Comment 3 Fedora Update System 2009-11-12 23:04:19 UTC
podsleuth-0.6.5-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/podsleuth-0.6.5-2.fc12

Comment 4 Fedora Update System 2009-11-16 07:25:38 UTC
podsleuth-0.6.5-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update podsleuth'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-11495

Comment 5 Bug Zapper 2009-11-16 15:13:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 aedallan 2009-11-19 14:54:32 UTC
podsleuth-0.6.5-2.fc12.i686 still does not not identify ipod

Ipod mounts as storage device but podlseuth reports:

"No iPods were found in the HAL device tree"

Comment 7 Christian Krause 2009-11-20 21:00:26 UTC
(In reply to comment #6)
> podsleuth-0.6.5-2.fc12.i686 still does not not identify ipod
> Ipod mounts as storage device but podlseuth reports:
> "No iPods were found in the HAL device tree"  

Yes, that's correct. Unfortunately the overall problem is not solved yet since the problem requires some bigger changes upstream and according to the bug report in gnome bugzilla this has not finished yet.

This specific bug was to just a prerequisite to get at least the workaround working which I've described here:

https://bugzilla.redhat.com/show_bug.cgi?id=495240#c20

Comment 8 aedallan 2009-11-21 10:33:46 UTC
Thanks Christian. Whatever is going on with nautilus, unsetting the automount option via gconf-editor does not stop automounting taking place.



(In reply to comment #7)
> (In reply to comment #6)
> > podsleuth-0.6.5-2.fc12.i686 still does not not identify ipod
> > Ipod mounts as storage device but podlseuth reports:
> > "No iPods were found in the HAL device tree"  
> 
> Yes, that's correct. Unfortunately the overall problem is not solved yet since
> the problem requires some bigger changes upstream and according to the bug
> report in gnome bugzilla this has not finished yet.
> 
> This specific bug was to just a prerequisite to get at least the workaround
> working which I've described here:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=495240#c20

Comment 9 Christian Krause 2009-11-22 16:51:51 UTC
(In reply to comment #8)
> Thanks Christian. Whatever is going on with nautilus, unsetting the automount
> option via gconf-editor does not stop automounting taking place.

Sorry for the question, but just to be on the safe side: Your are using gnome and not KDE? So far I don't know (and I don't believe) that the my workaround would work in KDE....

Please verify with
gconftool-2 -g /apps/nautilus/preferences/media_automount
that the option is really set to false.
If the automounting still happens, please try to logout and login again and if this also doesn't help, please try to reboot.

Comment 10 aedallan 2009-11-22 20:45:10 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > Thanks Christian. Whatever is going on with nautilus, unsetting the automount
> > option via gconf-editor does not stop automounting taking place.
> 
> Sorry for the question, but just to be on the safe side: Your are using gnome
> and not KDE? So far I don't know (and I don't believe) that the my workaround
> would work in KDE....
> 
> Please verify with
> gconftool-2 -g /apps/nautilus/preferences/media_automount
> that the option is really set to false.
> If the automounting still happens, please try to logout and login again and if
> this also doesn't help, please try to reboot.  

Thanks for the assistance with this.

I am using gnome and it does appear automount is disabled:

# gconftool-2 -g /apps/nautilus/preferences/media_automount
false

Tried logging out/rebooting same issue.

Here is the dmesg output for the mounting of the device, I don't know if it indicates who is doing the mounting:

usb 2-2: new high speed USB device using ehci_hcd and address 6
usb 2-2: New USB device found, idVendor=05ac, idProduct=1261
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-2: Product: iPod
usb 2-2: Manufacturer: Apple Inc.
usb 2-2: SerialNumber: 000A2700137ED9E9
usb 2-2: configuration #1 chosen from 2 choices
scsi8 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi 8:0:0:0: Direct-Access     Apple    iPod             1.62 PQ: 0 ANSI: 0
sd 8:0:0:0: Attached scsi generic sg2 type 0
sd 8:0:0:0: [sdb] 29255991 4096-byte logical blocks: (119 GB/111 GiB)
sd 8:0:0:0: [sdb] Write Protect is off
sd 8:0:0:0: [sdb] Mode Sense: 68 00 00 08
sd 8:0:0:0: [sdb] Assuming drive cache: write through
sd 8:0:0:0: [sdb] 29255991 4096-byte logical blocks: (119 GB/111 GiB)
sd 8:0:0:0: [sdb] Assuming drive cache: write through
 sdb: sdb1
sd 8:0:0:0: [sdb] 29255991 4096-byte logical blocks: (119 GB/111 GiB)
sd 8:0:0:0: [sdb] Assuming drive cache: write through
sd 8:0:0:0: [sdb] Attached SCSI removable disk

Comment 11 Fedora Update System 2009-11-25 15:29:01 UTC
podsleuth-0.6.5-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 aedallan 2009-12-07 17:26:31 UTC
Problem persists. Details in post #10

Another case of stuff-that-used-to-work being broken. I know the software is free, but jeez, surely an e-hippocratic oath should apply. I'm giving up on banshee, nice as it is.

Comment 13 Christian Krause 2009-12-12 16:20:07 UTC
(In reply to comment #12)
> Problem persists. Details in post #10

I am sorry, but I don't have an idea what is causing the auto-mounting on your side.

Sure, podsleuth will itself mount the ipod for a short period of time, but it will also umount it.

So unfortunately I have only two suggestions for you:

- determine what's causing the automount in you case (probably ask on http://fedoraforum.org/ or file a but report against nautilus)

- wait for the next update of podsleuth and banshee: upstream has implemented native devicekit support and I'll try to package the most recent git version - please follow bug #495240 for details.


Note You need to log in before you can comment on or make changes to this bug.