#550 removable disks aren't recogised

2.0
closed-works-for-me
PCMan
5
2012-10-28
2012-06-03
alister.hood
No

I build with --enable-udisks.
With current code from git, when I insert a removable disk it doesn't ask me if I want to open it. Also, if I mount it from the command line with udisks then it doesn't show up in the "Places" in the sidebar like it should.
Does this indicate --enable-udisks is broken in current Git? Or is the problem something else?

Discussion

    • milestone: --> 557433
     
  • alister.hood
    alister.hood
    2012-06-09

    Actually, I see something in the changelog about gvfs having preference over udisks, so I guess it is a problem with the gvfs support?

     
  • alister.hood
    alister.hood
    2012-06-10

    FWIW I have now built without udisks support, and when I insert a disk I don't get the dialogue asking me to mount it, but when I mount the drive manually it does show up in the sidebar. I have no idea if this is because of building it without udisks support, or because something has changed in git, or some other reason.

     
  • PCMan
    PCMan
    2012-06-10

    The udisks support is experimental and is not stable.
    The author of udisks already abandons udisks and is now making udisks2 which is very different.
    So I won't fix udisks support now since it's a waste of time.
    When I finally finish it, they drop udisks again and I need to do it again from scratch for udisks2.
    So sad. :-( Please turn off udisks support for now.

     
  • PCMan
    PCMan
    2012-06-10

    • milestone: 557433 --> 2.0
    • status: open --> open-later
     
  • alister.hood
    alister.hood
    2012-06-11

    So now that I have built without udisks support, how should I expect it to behave? When I plug a drive in is it supposed to ask if I want to mount the drive? Or is feature part of the udisks support?

     
  • alister.hood
    alister.hood
    2012-06-16

    > So now that I have built without udisks support, how should I expect it to
    behave? When I plug a drive in is it supposed to ask if I want to mount
    the drive? Or is feature part of the udisks support?

    I haven't looked at the code, but presumably it is not just part of the udisks support, as the pcmanfm settings still have all the auto-mount options under "volume management".

     
  • Even without udisks support, I am not able to see or mount removal devices in pcmanfm-1.0_rc1. However, pcmanfm-0.9.7 (with udisks support) works as expected

     
  • Sorry scratch that. pcmanfm-1.0_rc seems to work ok with gvfs

     
  • i compi9led this git pcmanfm and showme the dialog, but using older glib2 2.22/2.24 with gtk+ 2.20 ... in glib 2.2.6 the relationship with gvfs are change.. please note that for this bug fixed!

     
  • alister.hood
    alister.hood
    2012-08-10

    Sorry, are you saying that it works with an older glib and gtk, but not a newer one?
    Or that it works with a newer glib and gtk, but not an older one?

    I have gtk2.24.10 and glib2.32.3, and it does not work...

     
  • alister.hood
    alister.hood
    2012-08-19

    > So now that I have built without udisks support, how should I expect it to behave? When I plug a drive in is it supposed to ask if I want to mount the drive? Or is feature part of the udisks support?

    Ah, it is working for me now. My gvfs wasn't working - to make it work I need to start my desktop with `exec dbus-launch lxsession` rather than just `exec lxsession`.
    I see the Trash and stuff all work now too - I'd assumed they were not implemented yet :)

    This all makes me wonder how on earth we are supposed to know to start it like this, and why just starting the dbus session via /etc/X11/xinit/xinitrc.d/30-dbus isn't sufficient...

     
    • labels: 805537 --> isn't related to libfm or pcmanfm
    • status: open-later --> closed-works-for-me
     
  • > This all makes me wonder how on earth we are supposed to know to start it like this, and why just starting the dbus session via /etc/X11/xinit/xinitrc.d/30-dbus isn't sufficient...

    The most probably your /etc/X11/xinit/xinitrc.d/30-dbus just doesn't execute. Follow your comment I guess you have custom ~/.xinitrc but do you know in that case /etc/X11/xinitrc doesn't executed therefore /etc/X11/xinit/xinitrc.d/ isn't sourced by it?

     
  • alister.hood
    alister.hood
    2012-08-20

    No, it was executed, because this was in my .xinitrc

    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f" &
    done
    unset f
    fi

    > My gvfs wasn't working - to make it work I need to start my desktop with `exec dbus-launch lxsession` rather than just `exec lxsession`.

    No, sorry, I got confused. I meant to say that to make it work I need to start with `exec dbus-launch startlxde`. But that is wrong anyway - I just need to use `exec startlxde`.

     
  • alister.hood
    alister.hood
    2012-08-20

    • status: closed-works-for-me --> open-works-for-me
     
  • I think the lxsession isn't meant to run by Xinit but rather by Xsession instead and there are some differences in their execution.

     
    • status: open-works-for-me --> closed-works-for-me
     
  • I will comment on this bug because it is a little discussion on the gentoo bugzilla.
    https://bugs.gentoo.org/show_bug.cgi?id=438700
    https://bugs.gentoo.org/show_bug.cgi?id=438478
    and also because I get the same kind of troubles with policykit, a dependency of udisks, gdu and upower..

    When you install udisks or upower, this will install policykit at the same time. When this is done, you have to start lxde, and many other wm like fvwm, *box, ... with something like

    exec ck-launch-session startlxde

    or X won't start.

    This is because polkit is a daemon that take control of udev... (I hate that kind of things! And the recent inclusion of a JS interpreter into polkit are not making things better because 1) this is to open the door to a whole range of new issues, and 2) I have other things to do than to learn JS in order to make my system administration, especialy when the system was screwed up by this software. It is simpler to remove it, I can live without gnome -:)

    My system is completely *kit free. It only depend on udev for creating devices and mounting them. As exemple, gvfs is compiled against udev, but not against udisks or gdu.

    For me, polkit has several issues, and if I understand the big corporations need for this software, I just don't want it because it screw up my system. Without polikit (and udisks), the external devices and the CD/DVD get mounted whithout user intervention when I plug-in them.

    As soon polkit get installed, this and other things like X doesn't work anymore, and in the best case, I get an unneeded popup that ask me if I want to mount it (I want it to be automatic, when I plug-in something, this is because I want to access it, damned!). In the worst case (fvwm and other wm), I must mount them with mount, pmount or pmount-gui.

    When polkit is installed, the only possibility to get back the ancient begaviour is to uninstall it. That because it is a daemon without any possibility to desactivate it. When it is installed, it just work and screw up things.

    With my *kit free system, I can even define fixed mount points in /etc/fstab:

    # usb
    UUID=c5488d69-a86c-43b4-a70e-b6b12b0898f4 /mnt/usb ext2 user,noatime 0 2

    That way, this hdd will be mounted at any time. If at boot, it will be checjed by fsck. It later, it will just be mounted. The non defined devices will be mounted in /media/*. I get both the external stuffs and the cdrom updated in the left panel of pcman, that without any user intervention. (libfm-1.0.1 and lxsession-0.4.6.1). A very useful program to mount/unmount the external stuffs with just 2 clicks is pmount-gui. I use it to unmount the usb stuffs.

     
  • alister.hood
    alister.hood
    2012-10-20

    What are you actually trying to achieve by commenting on this ticket?

     
  • alister.hood
    alister.hood
    2012-10-20

    • status: closed-works-for-me --> open-works-for-me
     
    • status: open-works-for-me --> closed-works-for-me
     
  • dominique_libre: if you would like to write a tutorial how to setup a system without *kit you could do it at the Wiki.
    People will never find your comment here, you know.
    Thank you very much!