Thank you, again, for taking the time to reply, Wolfi.
Yes, I was thinking that, and I was thinking the problems had to do with the changes.
As I wrote, you can file a bug report about the missing kdepim-runtime dependency (already fixed in Factory), but not for this.
Yes. I plan to file one when I finish checking what else is related.
I don’t think it makes sense to pull in the whole Plasma5 desktop just for KOrganizer, and as mentioned it won’t help anyway as that settings module will only configure the Plasma5 desktop and have no effect to your XFCE session.
I have to agree with this. But, I will be making a suggestion (I guess, upstream?) that an option to choose preferred local time or UTC, especially on import, might be possible without invoking the Date module.
It’s part of the package kdebase4-workspace-addons.
AFAICT this is only pulled in by kdebase4-workspace, the KDE4 desktop.
If this was an upgrade (from 13.2 or earlier), it won’t get uninstalled automatically though.
Neither system is upgrade. Both are clean install to emptied (reformatted) partitions.
kdebase4-workspace and kdebase4-workspace-addons are not installed on the 42.2 machine, but kdebase4-runtime is along with kdebase4-workspace-libs, both of which I presume were pulled in as dependencies for at least one of the several KDE applications I have installed on that machine.
Of course, those are not pulled in on the 42.3 machine, because of the changes moving up to Plasma5.
I would guess that also pulls in the Date/Time module.
[QUOTE]Yes, which I have set to Vancouver time in the Yast module. However, exchanging the ics file between the two machines, the 42.3 converts everything to UTC from Vancouver time, seriously messing up the Schedule. I find no setting to change that.
Might be a bug, yes.
I even remember a report at bugs.kde.org about some such problem, have to search for it.[/QUOTE]
Okay, I will do a search. Of course, I have the Yast module set to Local time, but also have checked to have System time as UTC. I presume that is playing a part, & I will see if that is the case when I find the bug.
Could you maybe provide the file?
Also, just to be sure, what’s the output of “locale”? (run as user)
I could provide the file, yes, but only if you want to spend that much time analyzing this. I know you are busy, and I am fine without a solution to this, as I am currently using Lightning in Thunderbird on the 42.3 machine and that is interoperating just fine. When I do my full install to replace 13.1 on this machine, then I will be wanting kOrganizer, but I possibly will be installing the KDE team’s Desktop when I do that, so all will probably be fine.
I am now just exploring this to see if things can be made smoother for any others who want to do the unusual thing of running kOrganizer on an Xfce desktop (or other Desktop, for that matter).
But, I just ran locale and see quite interesting output:
So it should silently fail if the config module is not installed?
I don’t think that’s a good idea either.
Oh, yes, I definitely agree with you on this! Instead, I wonder if it could not at least pull something up, or be replaced in the kOrganizer configuration file with another way of choosing the time-zone for the application. Probably something for me to suggest upstream, as I said.
And checking if it is installed (and disable or remove the option if not) is probably not easy to do either (in a distribution agnostic way, installation paths may be very different, if you compile from source you can freely choose them anyway…).
This I suspected.
… and, again, thanks.