Hi
I am on Fedora 22, fully updated.
When I start KOrganizer manually, it works fine and there's a systray entry for the reminder daemon. The setting "start reminder daemon at login" is enabled in its right-click menu.
But at next login, it does not start. I have to manually start KOrganizer.
In system settings, I've configured for "Start with an empty session", but that's how it has always been and KOrganizer used to auto-start. In 'Autostart' tab, KOrganizer is not included, but again, I never had to add it manually in previous versions.
Is this a bug? Or am I missing something?
Thanks and regards,
Syam Krishnan C.R.
Syam Krishnan wrote:
Hi
I am on Fedora 22, fully updated.
When I start KOrganizer manually, it works fine and there's a systray entry for the reminder daemon. The setting "start reminder daemon at login" is enabled in its right-click menu.
But at next login, it does not start. I have to manually start KOrganizer.
In system settings, I've configured for "Start with an empty session", but that's how it has always been and KOrganizer used to auto-start. In 'Autostart' tab, KOrganizer is not included, but again, I never had to add it manually in previous versions.
Is this a bug? Or am I missing something?
It's a bug, but I think there's an easy fix, mind filing a bug @ bugzilla.redhat.com against kdepim for tracking purposes?
In short, it's autostart file lives under /usr/share/autostart (used only by kde4) and not /etc/xdg/autostart
(and korgac.desktop is not the only one, others include kgpg.desktop and konqy_preload.desktop)
-- Rex
On 10/02/2015 07:52 AM, Rex Dieter wrote:
Syam Krishnan wrote:
Hi
I am on Fedora 22, fully updated.
When I start KOrganizer manually, it works fine and there's a systray entry for the reminder daemon. The setting "start reminder daemon at login" is enabled in its right-click menu.
But at next login, it does not start. I have to manually start KOrganizer.
In system settings, I've configured for "Start with an empty session", but that's how it has always been and KOrganizer used to auto-start. In 'Autostart' tab, KOrganizer is not included, but again, I never had to add it manually in previous versions.
Is this a bug? Or am I missing something?
It's a bug, but I think there's an easy fix, mind filing a bug @ bugzilla.redhat.com against kdepim for tracking purposes?
In short, it's autostart file lives under /usr/share/autostart (used only by kde4) and not /etc/xdg/autostart
(and korgac.desktop is not the only one, others include kgpg.desktop and konqy_preload.desktop)
-- Rex
I noticed the same issue, but was never bothered enough to track it down. Thanks for the motivation. I filed the bug this morning at
https://bugzilla.redhat.com/show_bug.cgi?id=1268342
On Friday 02 October 2015 06:22 PM, Rex Dieter wrote:
Syam Krishnan wrote:
Is this a bug? Or am I missing something?
It's a bug, but I think there's an easy fix, mind filing a bug @ bugzilla.redhat.com against kdepim for tracking purposes?
In short, it's autostart file lives under /usr/share/autostart (used only by kde4) and not /etc/xdg/autostart
Thanks for the confirmation.
But can I ask a basic layman question..
How come the autostart file is in a root-only location like /usr/share/autostart or /etc/xdg/autostart? Shouldn't it be in a ordinary-user-writable location instead? Otherwise, how come an ordinary user starting KOrganizer gets permissions to install an auto-start file in these root-only locations? And if one user chooses to autostart KOrganizer, won't it be enabled for other users too?
Thanks and regards,
Syam
Syam Krishnan wrote:
But can I ask a basic layman question..
How come the autostart file is in a root-only location like /usr/share/autostart or /etc/xdg/autostart? Shouldn't it be in a ordinary-user-writable location instead? Otherwise, how come an ordinary user starting KOrganizer gets permissions to install an auto-start file in these root-only locations? And if one user chooses to autostart KOrganizer, won't it be enabled for other users too?
Your suggestion is one possible implementation, but ...
the way it currently works is that the autostart .desktop file includes a special key to conditionally start or not.
for example, korganizer's korgac.desktop includes:
X-KDE-autostart-condition=korgacrc:General:Autostart:true
which means it'll only start if ~/.kde/share/config/korgacrc [General] section includes a key Autostart=true
-- Rex
On Saturday 03 October 2015 07:27 AM, Rex Dieter wrote:
Syam Krishnan wrote:
But can I ask a basic layman question..
How come the autostart file is in a root-only location like /usr/share/autostart or /etc/xdg/autostart? Shouldn't it be in a ordinary-user-writable location instead? Otherwise, how come an ordinary user starting KOrganizer gets permissions to install an auto-start file in these root-only locations? And if one user chooses to autostart KOrganizer, won't it be enabled for other users too?
Your suggestion is one possible implementation, but ...
the way it currently works is that the autostart .desktop file includes a special key to conditionally start or not.
for example, korganizer's korgac.desktop includes:
X-KDE-autostart-condition=korgacrc:General:Autostart:true
which means it'll only start if ~/.kde/share/config/korgacrc [General] section includes a key Autostart=true
Oh. OK. So the application at the time of install creates a global autostart file in those root-only locations. Then there is a per-user file which actually enables autostart for that user.
Interesting.. Never knew this. Thanks for the info.
Regards,
Syam
Rex Dieter wrote:
Your suggestion is one possible implementation, but ...
the way it currently works is that the autostart .desktop file includes a special key to conditionally start or not.
for example, korganizer's korgac.desktop includes:
X-KDE-autostart-condition=korgacrc:General:Autostart:true
which means it'll only start if ~/.kde/share/config/korgacrc [General] section includes a key Autostart=true
The problem is that X-KDE-autostart-condition will NOT work on all the non- Plasma desktops that read /etc/xdg/autostart! Heck, it won't even work in Plasma 5 because Plasma 5 does not use ~/.kde. This was fine while the file was in /usr/share/autostart, but now this feature won't work anymore.
Kevin Kofler
Kevin Kofler wrote:
Rex Dieter wrote:
Your suggestion is one possible implementation, but ...
the way it currently works is that the autostart .desktop file includes a special key to conditionally start or not.
for example, korganizer's korgac.desktop includes:
X-KDE-autostart-condition=korgacrc:General:Autostart:true
which means it'll only start if ~/.kde/share/config/korgacrc [General] section includes a key Autostart=true
The problem is that X-KDE-autostart-condition will NOT work on all the non- Plasma desktops that read /etc/xdg/autostart! Heck, it won't even work in Plasma 5 because Plasma 5 does not use ~/.kde. This was fine while the file was in /usr/share/autostart, but now this feature won't work
Hrm, I was assuming that plasma5 (still) supported X-KDE-autostart- condition. Do you have evidence to the contrary?
I can look closer if you're uncertain.
As far as non-plasma desktops, they never worked for this before, and they still won't (due to OnlyShowIn=KDE; ) so there's no loss in functionality there.
-- Rex
Rex Dieter wrote:
Hrm, I was assuming that plasma5 (still) supported X-KDE-autostart- condition. Do you have evidence to the contrary?
Sure, it supports it (I think), but that won't do any help because KOrganizer is a KDE 4 application and writes to the old settings location (.kde/share/config) whereas Plasma 5 only looks in .config.
Kevin Kofler
Syam Krishnan wrote:
I am on Fedora 22, fully updated.
When I start KOrganizer manually, it works fine and
there's a systray
entry for the reminder daemon. The setting "start reminder daemon at login" is
enabled in its
right-click menu.
But at next login, it does not start. I have to
manually start KOrganizer.
This problem is also present on F23ß.