DarkTrick | brainwash, interestingly enough, I could not start them via systemd | 00:18 |
---|---|---|
DarkTrick | brainwash, ah, so startup would only disable ./config/autostart/tracker* | 00:19 |
DarkTrick | ? | 00:19 |
=== brainwash_ is now known as brainwash | ||
=== ubott2 is now known as ubottu | ||
brainwash | DarkTrick: exactly | 09:08 |
brainwash | DarkTrick: therefore, it's not a bug in Xfce (unless you want Xfce to have an interface to configure systemd user services) | 09:10 |
DarkTrick | brainwash, then it's not an Xfce bug, but an xubuntu bug, where would I report an xubuntu bug? Or could it be a ubuntu bug saying that tracker* is configured as `autostart` AND service, where it should really be only either one? | 09:42 |
brainwash | DarkTrick: are you certain it is autostarted? | 09:43 |
brainwash | it could be some application (Nautilus) starting it | 09:43 |
DarkTrick | brainwash, I did not thoroughly analyze it, but they are getting started during bootup - even before logging in. I would guess nautilus is not yet present at that time (except there is some hidden feature of nautilus I'm not seeing) | 09:49 |
DarkTrick | Also, if I change /usr/lib/systemd/user/tracker*.service to /usr/lib/systemd/user/tracker*.service.disabled they don't get started anymore | 09:50 |
brainwash | you'll have to find out why they are enabled/activated by default | 09:54 |
brainwash | could be packaging or an upstream decision -> GNOME | 09:55 |
DarkTrick | by "they" you mean the services or the "autostarts"? | 09:55 |
DarkTrick | brainwash, ↑ | 09:56 |
brainwash | DarkTrick: tracker and its miners | 10:02 |
brainwash | you apparently don't want them to run | 10:04 |
DarkTrick | brainwash, well.. I think they are enabled because they are part of the system, I guess? | 10:04 |
DarkTrick | So having them autostarted by default is not the problem I see | 10:04 |
brainwash | ah okay | 10:05 |
DarkTrick | (sorry, miscommunication :/ ) | 10:05 |
DarkTrick | The problem is, that they are not easily disable-able | 10:05 |
brainwash | you can disable them via systemctl | 10:06 |
DarkTrick | because they apparently get autostarted from two different positions: ~/.config/autostart and through systemd | 10:06 |
DarkTrick | regarding xubuntu the problem arises, when using "session and startup", because the user *thinks* they have disabled it, while it is still started by systemd | 10:06 |
DarkTrick | so the system is not clear towards the user | 10:07 |
brainwash | isn't this true for pulseaudio too? | 10:08 |
brainwash | it has an autostart launcher I think | 10:08 |
brainwash | another example is xfsettingsd which has an autostart entry, but Xfce starts it anyway as part of the session | 10:10 |
brainwash | the entry is meant as fallback | 10:10 |
brainwash | maybe that's the case for tracker too | 10:11 |
DarkTrick | brainwash, this sounds to me, that the system is even more flawed in this area | 10:12 |
DarkTrick | If the user can turn something off, that gets started anyway, that's the system lying to the user | 10:13 |
DarkTrick | The question would then be: who is is charge (project) and what is to change... | 10:14 |
brainwash | the system isn't lying | 10:22 |
brainwash | I don't know how to solve this | 10:23 |
brainwash | https://docs.xfce.org/_media/xfce/xfce4-session/xfce4-session-preferences-autostart.png | 10:23 |
brainwash | that info text is gone in Xfce 4.16 | 10:24 |
brainwash | my idea was to add a hint to explain that autostart can be done through other ways also | 10:27 |
DarkTrick | brainwash, thank you for your input. I guess I'll go with a "config problem" for now. As it seems this also happens on ubuntu, I will move the bug there and see what happens. | 10:30 |
=== acheronuk is now known as RikMills | ||
=== CheeseEBoi_ is now known as CheeseEBoi | ||
=== sorinello1 is now known as sorinello |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!