Re: [udisks] Can't automount disks
On Tue, 12 Mar 2013 15:10:14 +, Simon McVittie wrote: >If your chosen distribution requires you do things you "shouldn't have >to learn how" to do, may I suggest either opening feature/support >requests with that distribution (if it's one where you can do that), or >using a distribution that has everything set up "out of the box"? I'd rather use that distro because it's light, looks good, and is one the very few that offers official releases in languages other than English. For some reason, other distros seem to think users all speak English. Besides, since I can solve that problem by launching the two daemons manually, I'd rather dig deeper instead of giving up so close. ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On 12/03/13 16:41, Rex Dieter wrote: Stef Bon wrote: first ConsoleKit is not deadware as you call it. Do you have a better term for software that has no longer has any upstream development or maintainer? Yes, it's called mature. We have been keeping it working with the Debian maintainer, look at the git repo. There has been no changes because there is no need to change anything. - Samuli ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On 12/03/13 13:41, Gilles wrote: > Slax uses its own package system [...] > Currently, it doesn't mount all available partitions, and users > shouldn't have to learn how to open a terminal, and play with > fdisk/mount. If your chosen distribution requires you do things you "shouldn't have to learn how" to do, may I suggest either opening feature/support requests with that distribution (if it's one where you can do that), or using a distribution that has everything set up "out of the box"? Popular choices include Debian, Fedora, OpenSUSE or Ubuntu, with any of the GNOME, KDE, XFCE, LXDE or Unity desktops. Any advice given in this thread is essentially going to boil down to "Look at what $POPULAR_DISTRIBUTION does, and do that". S ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
Stef Bon wrote: > first ConsoleKit is not deadware as you call it. Do you have a better term for software that has no longer has any upstream development or maintainer? -- rex ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On Tue, 12 Mar 2013 14:41:42 +0100, Gilles wrote: >Looking around in /etc, it appears that distro relies on systemd, >udisks, and PolicyKit, and I noticed /etc/rc.d/rc.messagebus with >D-Bus stuff inside. Would I be correct in visualizing things thusly? KDE Dolphin file manager <- D-Bus -> udisks <- D-Bus -> polkit www.freedesktop.org/software/polkit/docs/latest/polkit.8.html ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On Tue, 12 Mar 2013 11:50:57 +0100, Stef Bon wrote: >But what distro do you have? The packagesystem of that should take >care of it, unless you use of course something like >LinuxFromScratch... Thanks for the infos. Slax uses its own package system, but it offers a utility to convert and install Slackware packages. Currently, it doesn't mount all available partitions, and users shouldn't have to learn how to open a terminal, and play with fdisk/mount. Looking around in /etc, it appears that distro relies on systemd, udisks, and PolicyKit, and I noticed /etc/rc.d/rc.messagebus with D-Bus stuff inside. Thank you. ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
Hi, first ConsoleKit is not deadware as you call it. It is still used on systems with upstart, but not anymore on systems using systemd. This is not good for development, having two different systems, they do not make life easier, but it is what it is. So it depends on your system what init system it's using. I beleive I saw you something wroting aboyt service files. Then ConsoleKit is replaced by systemd login daemon. HAL is not used anymore and was replaced bu udisks, which on his turn was replaced bu udisks2. So you have Policykit, udev, udisks2 and maybe ConsoleKit. Got the picture? Oh I forgot, Policykit has undergone also some transformations, make sure you have the latest version. But what distro do you have? The packagesystem of that should take care of it, unless you use of course something like LinuxFromScratch... Stef ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On 12/03/13 12:36, Gilles wrote: On Fri, 08 Mar 2013 21:41:02 +0200, Samuli Suominen wrote: You need to run your session with ConsoleKit/dbus in the start so you don't need to run the daemons like that afterwards Thanks for the links. Apparently, ConsoleKit is deadware and replaced with systemd (logind). At this point, I'm in the dark about what HAL, udev, udisks(1 and 2), ConsoleKit/PolicyKit/systemd, and D-Bus do and work together, and how to get whatever software is needed so that the right stuff is loaded at boot time and users can access mass storage devices, either internal or external. If someone knows of a good article that gives the big picture, I'm definitely interested. Right, if you use systemd-logind instead of ConsoleKit which is a full replacement for it (more or less) Then you should have the systemd-logind pam entry in /etc/pam.d instead so it gets picked up when you login to the system And then you should use a display manager that has the support for systemd-logind, preferably, but I guess text login works too, or should work somehow - You can forget HAL, ConsoleKit - UDisks1 can be co-installed with UDisks2, so use whatever your packages need So all the latest you need for this is: PolicyKit, systemd-logind, UDisks2, UPower It's all tied to logging correctly to the desktop session... No need for starting anything manually, it should just work ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On Fri, 08 Mar 2013 21:41:02 +0200, Samuli Suominen wrote: >You need to run your session with ConsoleKit/dbus in the start so you >don't need to run the daemons like that afterwards Thanks for the links. Apparently, ConsoleKit is deadware and replaced with systemd (logind). At this point, I'm in the dark about what HAL, udev, udisks(1 and 2), ConsoleKit/PolicyKit/systemd, and D-Bus do and work together, and how to get whatever software is needed so that the right stuff is loaded at boot time and users can access mass storage devices, either internal or external. If someone knows of a good article that gives the big picture, I'm definitely interested. Thank you. ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On 08/03/13 13:28, Gilles wrote: On Fri, 08 Mar 2013 12:20:02 +0100, Gilles wrote: How do I configure PolicyKit so I'm allowed at least read access to NTFS/FAT32 partitions? Without knowing what I'm doing, I just ran this... = # /usr/libexec/polkitd & # /usr/libexec/udisks-daemon & = ... and the KDE Dolphin filemanager automounted and granted me access to the two (ext4 and NTFS) partitions on the SATA drive. Cool :-) I'd still like to know a bit more about what applications are involved to allow users in Dolphin to access partitions on internal and external devices. Is there a good article somewhere that gives the big picture? You need to run your session with ConsoleKit/dbus in the start so you don't need to run the daemons like that afterwards For example, see https://wiki.archlinux.org/index.php/ConsoleKit or first post of this thread: http://forums.gentoo.org/viewtopic-t-858965-start-0.html If you read between the lines from that post, it'll apply to any Linux distro I for example have ~/.xinitrc of `exec startxfce4 --with-ck-launch` and use `startx` to run Xfce I might have there something like `exec ck-launch-session startkde4` too Then you need the pam_ck_connector.so module so that it runs when you log into the system, like $ grep pam_ck /etc/pam.d/* /etc/pam.d/system-login:-sessionoptionalpam_ck_connector.so nox11 But this should already be handled by your distro... Best if you just read those links I gave you, so I don't need to repeat it all here ;-) - Samuli ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On Fri, 08 Mar 2013 12:20:02 +0100, Gilles wrote: >How do I configure PolicyKit so I'm allowed at least read access to >NTFS/FAT32 partitions? Without knowing what I'm doing, I just ran this... = # /usr/libexec/polkitd & # /usr/libexec/udisks-daemon & = ... and the KDE Dolphin filemanager automounted and granted me access to the two (ext4 and NTFS) partitions on the SATA drive. Cool :-) I'd still like to know a bit more about what applications are involved to allow users in Dolphin to access partitions on internal and external devices. Is there a good article somewhere that gives the big picture? Thank you. ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On Thu, 7 Mar 2013 22:16:10 +0100, Stef Bon wrote: >policykit AND udisks are not started both. > >take care both are started. Thanks. I'm pretty much in the dark about what HAL, udisks, ConsoleKit, PolicyKit are. Apparently, HAL is now replaced with udisks to manage operations on hardware, while ConsoleKit and PolicyKit manage how non-root users are allowed to access priviledged processes (ConsoleKit = console-based access, PolicyKit = desktop-based access). FWIW, when I simply run "# /usr/libexec/polkitd", it says: === "Entering main event loop Connected to the system bus Registering null backend at priority -10 Error loading /var/run/ConsoleKit/database: Error statting file /var/run/ConsoleKit/database: No such file or directoryUsing authority class PolkitBackendLocalAuthority Acquired the name org.freedesktop.PolicyKit1" === Do I also need ConsoleKit, or is udisks + polkit enough to double-click and access a partition? How do I configure PolicyKit so I'm allowed at least read access to NTFS/FAT32 partitions? Thank you. ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
Hi, policykit AND udisks are not started both. take care both are started. Stef ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On Tue, 05 Mar 2013 08:08:17 -0800, Thiago Macieira wrote: >> But no trace of udisks-daemon mentioned elsewhere. Is it just another >> name for dbus-daemon? > >No. > >It looks like you don't have UDisks running. Progress: Just to see what'd happen, I simply ran this: # /usr/libexec/udisks-daemon & Next, launched Dolphin: The two partitions on the hard drive are listed :-) But when I click on either of them: "An error occured while accessing '48.8GiB Hard Drive' : the system responded: An unspecified error has occured : Not Authorized: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PolicyKit1 was not provided by any .service file" ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On Tue, 05 Mar 2013 08:08:17 -0800, Thiago Macieira wrote: >On terça-feira, 5 de março de 2013 14.23.59, Gilles wrote: >> /usr/bin/dbus-daemon --system >> dbus-launch --sh-syntax --exit-with-session >> /usr/bin/dbus-daemon --fork --print-pid 8 -- >> >> But no trace of udisks-daemon mentioned elsewhere. Is it just another >> name for dbus-daemon? > >No. > >It looks like you don't have UDisks running. Which binary should I start, and how? Thank you. ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On terça-feira, 5 de março de 2013 14.23.59, Gilles wrote: > /usr/bin/dbus-daemon --system > dbus-launch --sh-syntax --exit-with-session > /usr/bin/dbus-daemon --fork --print-pid 8 -- > > But no trace of udisks-daemon mentioned elsewhere. Is it just another > name for dbus-daemon? No. It looks like you don't have UDisks running. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 signature.asc Description: This is a digitally signed message part. ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
2013/3/5 Gilles : > At 14:58 05/03/2013, you wrote: > > I don't know what they are. Is autofs some Linux application while session > automounting provided by KDE? > Automounting is the process of automatically mounting when accessed, and only then. Very common is also the unmounting when not used for some period (timeout). In linux there is a daemon autofs which is taking care for this. Automatic mounting (when a session starts) is just what is says, and is something else. > >> I know that udev and udisks have changed a lot lately (especially udev). >> In my case I had also errors when I upgraded systemd (and thus also udev) >> and I had to upgrade udisks also. II'm also using KDE, and Solid did not >> find any devices. After upgrading udisks the problem was solved. > > > Good to know. I'll check if I can upgrade udisks and see how it goes. > Please let us/me know it solves your problem, Stef Bon the Netherlands ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
Re: [udisks] Can't automount disks
On Mon, 04 Mar 2013 17:05:53 +0100, Gilles wrote: >KDE seems unable to automount partitions because of this: > >#solid-hardware list > >QStringList >Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error: >"org.freedesktop.DBus.Error.ServiceUnknown" >virtual QStringList >Solid::Backends::UPower::UPowerManager::allDevices() error: >"org.freedesktop.DBus.Error.ServiceUnknown" > > >I was told "to ensure that UDisks is installed and being started >either before KDE startup (for manual starting of UDisks) or during >KDE startup (if using D-Bus automatic startup for UDisks)."... but >have no idea what to do. FWIW, "ps aux" shows the following entries that look familiar: /usr/bin/dbus-daemon --system dbus-launch --sh-syntax --exit-with-session /usr/bin/dbus-daemon --fork --print-pid 8 -- But no trace of udisks-daemon mentioned elsewhere. Is it just another name for dbus-daemon? Thank you. ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
[udisks] Can't automount disks
Hello I'm having a problem with the Slax distribution that no one seems to figure out. I posted here since it's apparently linked to udisks. To avoid requiring non-technical users to learn about fdisk and mount,I'd like all NTFS (and Linux) partitions to be automounted, both internal and external drives. KDE seems unable to automount partitions because of this: #solid-hardware list QStringList Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error: "org.freedesktop.DBus.Error.ServiceUnknown" virtual QStringList Solid::Backends::UPower::UPowerManager::allDevices() error: "org.freedesktop.DBus.Error.ServiceUnknown" I was told "to ensure that UDisks is installed and being started either before KDE startup (for manual starting of UDisks) or during KDE startup (if using D-Bus automatic startup for UDisks)."... but have no idea what to do. FWIW, I can mount the partitions manually through fdisk + mount. If you've seen this before and know how to solve it, any hint appreciated. Thanks for any help. ___ xdg mailing list xdg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xdg
