[SOLVED] Fluxbox no polkit? gparted not working due to ???
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
PulseAudio, and you say nw-applet too, so I should be able to remove that line from my startup file too, along with /usr/libexec/polkit-gnome-authentication-agent-1 &
looks like the bluesman-applet line in startup I can remove too.Yes.
Why not fix the exec path in /etc/xdg/autostart/dropbox.xdg, or copy this file to ~/.config autostart and fix the path there (will work as according to the specification the latter has priority over the former)
I thought about that but it needs a conditional to check to see what distro is running, as Void installs dropbox into /usr/bin and puts a dropbox.desktop file in ~/.config/autostart whereas Slack does not it puts everything to do with dropbox in /opt. Being that only one can use the desktop file in ~/.config/autostart due to both drop box installs going in two different places.
if I change the desktop file to reflect slackware then it fails again when starting Void.
hence the conditional to check to see what distro is starting.
if slack let it fail when fbautostart tries to start it, if Void let it Not fail when fbautostart starts it, and the conditional will not even try to start dropbox.
best case scenario I can come up with on short notice.
this looks interesting though
Quote:
Hidden Key
When the .desktop file has the Hidden key set to true, the .desktop file MUST be ignored. When multiple .desktop files with the same name exists in multiple directories then only the Hidden key in the most important .desktop file must be considered: If it is set to true all .desktop files with the same name in the other directories MUST be ignored as well.
let me reboot into void to check my theory on this first.
If that is the case adding a symlink to the executable in one of them will do.
Yes -- and --
that's an idea:
I just rebooted into Void and as luck has it void does not have
Code:
(userx@voider.org⚡️~)>>$ fbautostart
bash: fbautostart: command not found
so either one of two things can be done, I think, one: if else statement to deal with Void.
if slack do this else do that (being void) to start up what I need if I use fbautostart, which seems a nice add on in Slack or two: lots of soft links and editing files too?
As Void does not use or have actually fbautostart to start anything. That means I could try modding Slacks fbautostart to use in Void.
this all started because why? gparted, then dropbox now look what YOU got me doing. (that's called transferring blame see how I did that? )
the only two things that started up in Void-Fluxbox was volumeicon and dropbox, but my gparted still worked, only because Void does that differently, which took me to modding Slack to follow suit, that took me to dropbox that I do not worry about too much, but seeings how I was not starting it in Slack I figured why not?
Now look at the mess I am in.
In case of a re-install of one of the systems. Which method would be the easiest to recover from?
if else statement or softlinks?
your thoughts? (just because I'm checking your logic and reasoning)
thanks for that info on fbautostart I copied it over onto Void /usr/bin and it works there too. googled it afterwords and seen it is a github add on for fluxbox in general.
Even though fbautostart does not start dropbox in either distros due to I think that hidden key cluse in the docs. I fixed that with two lines of code in startup file.
What gives "grep ^Exec /etc/xdg/autostart/dropbox.desktop"? Please run the command in a shell and see what you get. Does the output actually start dropbox?
Also, I wouldn't share a whole $HOME among two distros as this directory contains a lot of (mostly hidden) file and directories whose content could have to differ from one distro to the other. My advice (if I am allowed to state one) would be to have two separate $HOME and symlink the files and sub-directories that you really want to share.
Last edited by Didier Spaier; 02-01-2017 at 03:30 PM.
Reason: s/dropbox.SlackBuild/dropbox.desktop/
What gives "grep ^Exec /etc/xdg/autostart/dropbox.SlackBuild"? Please run the command in a shell and see what you get. Does the output actually start dropbox?
I do not understand your complete thought.
your grep ^Exec /etc/xdg/autostart/dropbox.SlackBuild <--- is that a complete thought? slackbuild??
Code:
(userx@slacko⚡️~)>>$ grep ^Exec /etc/xdg/autostart/dropbox.SlackBuild
grep: /etc/xdg/autostart/dropbox.SlackBuild: No such file or directory
(userx@slacko⚡️~)>>$ ls /opt/dropbox
VERSION dropbox-lnx.x86_64-15.4.22 dropboxd
Code:
(userx@slacko⚡️~)>>$ cat /usr/share/applications/dropbox.desktop
[Desktop Entry]
Name=Dropbox
GenericName=Network Storage
Comment=Secure backup, sync and sharing made easy
Exec=dbus-launch /opt/dropbox/dropboxd
Icon=/usr/share/pixmaps/dropbox.png
Terminal=false
Type=Application
this is my void dropbox.desktop in ~/.config/autostart
Code:
Exec=dbus-launch /opt/dropbox/dropboxd
they have the same line to exec
for whatever reason they are not but it doesn't bother me in the least at this moment in time.
Quote:
Also, I wouldn't share a whole $HOME among two distros as this directory contains a lot of (mostly hidden) file and directories whose content could have to differ from one distro to the other. My advice (if I am allowed to state one) would be to have two separate $HOME and symlink the files and sub-directories that you really want to share.
that being my entire home with myself - nothing wrong with sharing that among oneself.
the word could being an operative word .. I've already been though this many times before .... hahaha that is what I am doing - breaking that stereo type thinking --- I'm living outside the box baby !!!! MHUuauhahahahahahhahahaha just need to know your systems. they are "clones" basically.
Im going to post this so I do not lose what I've written already, and double check this dropbox thing but at it is right now as I have it, this too works.
giving it a thought. I think I see what you're getting at, but neither distro places a dropbox.desktop in /etc/xdg/autostart.
think about it, it doesn't really matter one way or the other if I have it checked for which distro then start up dropbox by calling the dropbox start - that is a valid way to start it, or copying a dropbox.desktop into the /etc/xdg/autostart
to me not looking completely into all of the what nots about it they both work either way. it is still six one way and a half a dozen the other way.
shows that you have no /etc/xdg/autostart/dropbox.desktop so the grep command would have failed anyway.
Quote:
Originally Posted by BW-userx
this is my void dropbox.desktop in ~/.config/autostart
Code:
Exec=dbus-launch /opt/dropbox/dropboxd
they have the same line to exec
And the path is wrong for both distributions...
Just type "dbus-launch /opt/dropbox/dropboxd" in a shell to check the output
Quote:
that being my entire home with myself - nothing wrong with sharing that among oneself.
You just provided an example showing that this is wrong : If you have someapp.desktop in ~/.config/autostart but the command in the Exec field has to differ between distros, what will happen?
There would be no issue instead if you had one ~ for each distro.
But that's your systems so as long as you are happy the way it works, that's fine with me
Last edited by Didier Spaier; 02-01-2017 at 04:28 PM.
And the path is wrong for both distributions...
Just type "dbus-launch /opt/dropbox/dropboxd" in a shell to check the output
You just provided an example showing that this is wrong : If you have someapp.desktop in ~/.config/autostart but the command in the Exec field has to differ between distros, what will happen?
I do not have to that is where dropboxd is located in Slackware. in void it is located where that ones DB.Desktop says it is. they both have the right path to dropboxd.
Quote:
There would be no issue instead if you had one ~ for each distro.
But that's your systems so as long as you are happy the way it works, that's fine with me
Void puts its dropbox in ~/.config/autostart
Void dropbox -> /usr/
slack put its dropbox in /usr/share/applications
wait let me go look I seen a typo in my post for void
both desktop files point to their respective dropboxd exec
OK I was confused the one that is in my .config/autostart has to be for slackwares dropbox, I never really took in what it was saying, because dropbox was always starting per FB startup file - dropbox start & line I had which looks in the path /usr/bin/dropbox no desktop file what ever being used until I looked up in Slackware FB at the app area and seen dropbox was not there,
then this whole thing got started with me.
so being that dropbox start -- starts dropbox because it is looking in /usr/bin
where in slackware it is NOT in /usr/bin therefore it was NOT starting by just having that one line in FB startup file.
that is why I put this line in it to get it to start,
then you came along and showed me fbstartup and xdg and well here we are....
Looking at the tail of your post #1 I see that the way to start dropbox in not the same on both distributions.
You found a way to cope with this difference and that works, so that's fine.
But what I mean is that if /home was mounted on two different partitions in Slackware vs Void you would have two distinct files
/home/userx/.config/autostart/dropbox.desktop
Then, they could have:
Exec=/opt/dropbox/dropbox-lnx.x86_64-15.4.22/dropbox
and
Exec=dropbox start
respectively, thus dropbox be autostarted from both distros without needing to put anything in ~/.fluxbox/startup about that.
Another solution would be to put the files in the respective /etc/xdg/autostart directories, again with a distinct Exec line.
Oh well, as the saying goes, there's more than one way to skin a cat
One more thing to keep in mind with running two different distros with the same home directory, if one of those distros has a newer or older version of some program with incompatible settings in .config/, it could cause crashes. I've had it happen before. gtk was an issue a few years ago, and if one distro did a major upgrade, like KDE (I know you aren't using it, but it's just an example), the config files can change completely and you could break one or both installations.
As Didier said, it is your computer, and if you're happy with the setup, then that's all that matters
Looking at the tail of your post #1 I see that the way to start dropbox in not the same on both distributions.
You found a way to cope with this difference and that works, so that's fine.
But what I mean is that if /home was mounted on two different partitions in Slackware vs Void you would have two distinct files
/home/userx/.config/autostart/dropbox.desktop
Then, they could have:
Exec=/opt/dropbox/dropbox-lnx.x86_64-15.4.22/dropbox
and
Exec=dropbox start
respectively, thus dropbox be autostarted from both distros without needing to put anything in ~/.fluxbox/startup about that.
Another solution would be to put the files in the respective /etc/xdg/autostart directories, again with a distinct Exec line.
Oh well, as the saying goes, there's more than one way to skin a cat
Fluxbox 's startup file does not look in ~/.config/autostart or /etc/xdg/autostart it only uses the $PATH to start stuff by adding the commands within the startup file.
that I believe this is why the people at fluxbox came up with fbautostart to source the /etc/xdg/autostart and use desktop files to start up things.
so having two or more distros using Fluxbox all sharing the same $HOME it will all work itself out because each system is on its own partition even though the Home for everyone of the Linux systems are on the same partition.
either way having two or more using the same $HOME be it by the old way of adding just the apps exec to have startup file use the $PATH or have it using fbautostart it is still separated because fbautostart looks into /etc/xdg/autostart first then cancels out the rest of the dups
so it does not really matter, because it is fluxbox and Linux, Linux and fluxbox . the distros sharing it do not conflict as a result of it. Because each system has its own system and the $HOME is seperate of the two. sharing the same configs for the same wm that is how the cloning gets into it.
like I said and you judt did, their is more than one way to skin a cat, that is what I like aobut Linux.
one could not do this with two separate windows installs on one hdd.
but then again I bet it too can be done, just needed to edit the ini file and have two hard drives
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
