On Thursday 15 October 2015 05:42:19 Sune Vuorela wrote:
> I think the plan is to push it to unstable soon after 5.5.1 is out.
Alright, thanks for the info.
> But note that the QScreen bug is not yet fixed.
Some fixes supposedly went into Qt 5.5 and in the bugreport they say they can't
reprodu
On 2015-10-14, Carsten Pfeiffer wrote:
> I'm wondering what's the status of Qt 5.5 (in experimental). I'm suffering
I think the plan is to push it to unstable soon after 5.5.1 is out.
But note that the QScreen bug is not yet fixed.
/Sune
Actually you are right, I just noticed that file in $HOME/.kde/share/config is
created again, even after I deleted it. I'm not sure if it's supposed to be
that way - you should probably file a bug for KDE: https://bugs.kde.org (for
Baloo component).
Regards,
Hillel Lubman.
On Thursday, Octobe
El 14/10/15 a las 16:21, Hillel Lubman escribió:
I think $HOME/.config/baloofilerc is used by baloo-kf5, while
$HOME/.kde/share/config/baloofilerc was used by older baloo [-]
Thank you for your reply.
What you said is what I thought but what confuses me is both files were
created at the
Hi,
I'm wondering what's the status of Qt 5.5 (in experimental). I'm suffering
badly from bug https://bugreports.qt.io/browse/QTBUG-42985 where all kinds of
applications crash when changing the monitor setup (use notebook standalone or
in dock with external monitors). The crashing applications
I think $HOME/.config/baloofilerc is used by baloo-kf5, while
$HOME/.kde/share/config/baloofilerc was used by older baloo (so if you switched
to baloo-kf5 you can remove the second one). In general, I noticed that quite a
number of KDE related config files moved to $HOME/.config from
$HOME/.kde
6 matches
Mail list logo
