On 19 May 2015 at 16:00, David Edmundson wrote:
> Yes, it's only a problem on Kubuntu.
>
> It's also solvable by compiling Qt, but I don't really want to have to force
> new devs to do that unless I have to.
We should talk to the Kubuntu devs to see why its hardcoded that way,
and ask them to re
On Tue, May 19, 2015 at 12:30 PM, David Edmundson <
da...@davidedmundson.co.uk> wrote:
>
> But someone who wrote this must have been a Kubuntu user, there is a list
> of dependencies.
>
That was added by me about 2 weeks ago when I tried to follow
that setup as well on a clean system where I had
On Tue, May 19, 2015 at 2:10 AM, Siddhartha wrote:
> On 18 May 2015 at 22:58, David Edmundson
> wrote:
>
>> Just setting up on a new machine and thought I'd try following these
>> instructions exactly, the way a new developer would.
>>
>> I got stuck on something I don't know how to solve.
>>
>>
On 18 May 2015 at 22:58, David Edmundson wrote:
> Just setting up on a new machine and thought I'd try following these
> instructions exactly, the way a new developer would.
>
> I got stuck on something I don't know how to solve.
>
> Under Kubuntu because Qt is compiled with a hardcoded plugindir
On Mon, May 18, 2015 at 8:07 PM, David Edmundson
wrote:
>
>
> On Mon, May 18, 2015 at 7:05 PM, Aleix Pol wrote:
>>
>> On Mon, May 18, 2015 at 7:28 PM, David Edmundson
>> wrote:
>> > Just setting up on a new machine and thought I'd try following these
>> > instructions exactly, the way a new deve
On Mon, May 18, 2015 at 7:05 PM, Aleix Pol wrote:
> On Mon, May 18, 2015 at 7:28 PM, David Edmundson
> wrote:
> > Just setting up on a new machine and thought I'd try following these
> > instructions exactly, the way a new developer would.
> >
> > I got stuck on something I don't know how to sol
On Mon, May 18, 2015 at 7:28 PM, David Edmundson
wrote:
> Just setting up on a new machine and thought I'd try following these
> instructions exactly, the way a new developer would.
>
> I got stuck on something I don't know how to solve.
>
> Under Kubuntu because Qt is compiled with a hardcoded pl
Just setting up on a new machine and thought I'd try following these
instructions exactly, the way a new developer would.
I got stuck on something I don't know how to solve.
Under Kubuntu because Qt is compiled with a hardcoded plugindir for some
reason.
This means setting QT_PLUGIN_PATH env vari
On 1 April 2015 at 00:58, Bernhard Friedreich wrote:
> I finally found the problem - the instructions on the wiki were updated
> since my setup and I was lacking some lib64 directories in the runPlasma5.sh
> script..
Ah yes, sorry about that. I have some additional config which installs
all libra
I finally found the problem - the instructions on the wiki were updated
since my setup and I was lacking some lib64 directories in the
runPlasma5.sh script..
Thanks for the documentation and your help! :)
2015-03-31 20:44 GMT+02:00 Bernhard Friedreich :
> To me the XDG_DATA_DIRS path looks right
To me the XDG_DATA_DIRS path looks right..
[friedreb@pollux kde]$ awk -v 'RS=\0' -F= '$1=="XDG_DATA_DIRS" {print $2}'
/proc/3183/environ
/products/kde/install/share:/usr/share
[friedreb@pollux kde]$ ls -la /products/kde/install/share/ | wc -l
73
[friedreb@pollux kde]$ ls -la /products/kde/insta
>
> Any ideas? (attached the output/bt I got from gdb)
>
>
it's an assert in "could not find any theme"
At a guess you XDG_DATA_DIRS are wrong.
cat /proc/PIDOFPLASMASHELL/env will tell you the most
> Thanks :)
>
> Bye,
> Bernhard Friedreich
>
>
>
>
> 2015-03-28 19:23 GMT+01:00 Siddhartha :
>
>
Hey Martin,
Thanks for all the comments :)
On 30 March 2015 at 16:11, Martin Klapetek wrote:
>> sudo chown -R user:group /opt/kde
>
> I think this should either use $USER or `whoami` rather than "user" ?
Hmm good point. Also I learned that leaving the group empty after a
colon automatically set
Hi,
At first: thanks for the guide :) It's a nice addition to
https://community.kde.org/Frameworks/Building
I've got the following problems:
1.) on my fedora 23 (rawhide) I had to set selinux to permissive mode for
the custom dbus files to be read (otherwise it wouldn't let dbus access
them, mayb
Good stuff!
Here are my comments:
> sudo chown -R user:group /opt/kde
I think this should either use $USER or `whoami` rather than "user" ?
> Uncomment the last two lines if you also want to build the Applications
and PIM suite.
This should probably be inside the kdesrc-buildrc itself. Maybe
Hi David,
Thanks a lot for your comments!
On 28 March 2015 at 20:23, David Edmundson wrote:
> I don't think we should tell people to download's David Faure's
> kdesrc-buildrc file. It has "/d" hardcoded a lot.
>
> If we make our own we don't need people to change it and can have the same
> dire
Cool, definitely much needed .Thanks.
Review comments
--
I don't think we should tell people to download's David Faure's
kdesrc-buildrc file. It has "/d" hardcoded a lot.
If we make our own we don't need people to change it and can have the same
directories you use for the rest of this.
--
T
Hi everyone,
I shifted to Plasma 5 a while back. We all know how awesome it has become. :D
One particular moment I want to share was discovering "Require
password after locking" setting for Lock screen. I had been wishing
for something like this to quickly recover from unwanted screen
locking, an
18 matches
Mail list logo
