Run script after resume from suspend
Hi, I would like to run xmodmap ~/.Xmodmap after resuming from suspend. Is there a hook which is called after resume from suspend in KDE? Thanks Rainer -- Rainer Dorsch http://bokomoko.de/
Re: Plasma 5: no more KDEHOME?
On Jessie, a "export" in a script within /usr/env would take care of the issue. What about stretch? Would a script called /usr/env/kdedirs.sh, containing: export XDG_DATA_HOME=~/.local.stretch/share export XDG_CONFIG_HOME=~/.config.stretch export XDG_CACHE_HOME=~/.cache.stretch ...would fit the bill? Would that be the proper way to go with stretch? João On Tue, Feb 27, 2018 at 6:23 AM, Christian Hilberg < hilb...@kernelconcepts.de> wrote: > Am Montag, 26. Februar 2018, 14:35:05 CET schrieb Joao Roscoe: > > Nice, good to know. > > > > Now, I suppose that in a few years, We'll be moving forward to a newer > > version of our distro of choice. Then we'll (again) face a transitory > > situation in which users will be able to login to different systems with > > different versions of KDE installed, what could result in some trouble, > due > > to different versions of the desktop environment and applications messing > > around with configuration files. In the past, we dealt with this by > > tweaking kde so that it would use "~/.kde. to store kde > > related data, instead of plainly "~/.kde". So, looking at > > https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html, > > from now on, I guess I could have the same result by tweaking the systems > > to replace "~/.config" wit "~/.config.". > > Don't forget about (at least, maybe there's more) ~/.cache/ and ~/.local/ > > > Is that right? > > > > Best regards, > > Joao > > > > On Sat, Feb 24, 2018 at 11:42 AM, Sune Vuorela > wrote: > > > On 2018-02-22, Joao Roscoe wrote: > > > > How could I avoid conflicts between different versions of kde from > now > > > > > > on? > > > > > > all kde and qt applications follows the XDG spec for this, and the > > > related set of environment variables. > > > > > > /Sune > > Best, > > Christian > > -- >
Re: Issues Setting Up KDE Development Environment in Stretch
Am Donnerstag, 1. März 2018, 10:23:25 CET schrieb Karsten Ladner: > Thanks so much for the good feedback! > > So I set up a chroot environment using debootstrap for sid. I have then > used the tool schroot to access the chroot environment. I am wanting to > work on Okular, so after installing all the dependencies for Okular with > "sudo apt-get build-dep okular" I used cmake to prepare all the build > files. Once that ran successfully, I used make to build Okular. However, > when I ran "make test" all of the tests failed except one. > > I am not sure why this is the case. I have included the output for "make > test" in this paste bin: https://pastebin.com/M88cr1X3 I'm neither much into KDE development and their testing methods nor in schroot usage... did you make sure schroot mounts /proc, /sys, /dev and /dev/pts into the chroot environment? Also the tests might be integration tests which need more of Sid's KDE environment up and running for passing successfully. It *might* be easier to do the actual testing run within a Sid VM with your build directory mounted into it (building, however, for me is quicker within a chroot than within a VM). HTH, Christian > I have also included the output for "ctest -R kimgiotest -VV" in this > pastebin: https://pastebin.com/CE5Qgxue > > Thanks > > > On Wed, Feb 28, 2018 at 6:10 AM, Christian Hilberg < > > hilb...@kernelconcepts.de> wrote: > > Am Mittwoch, 28. Februar 2018, 10:18:16 CET schrieb Christian Hilberg: > > > Am Dienstag, 27. Februar 2018, 23:33:09 CET schrieb Diederik de Haas: > > > > On maandag 26 februari 2018 10:14:39 CET Christian Hilberg wrote: > > > > > This even works with foreign architectures, as long as QEMU supports > > > > > them. For the Raspi, I set up a Raspbian-Lite chroot, copy > > > > > /usr/bin/qemu-arm-static into it, and am good to go for > > > > > cross-development > > > > > on my host. > > > > > > > > Do you have some more details you can share about this? (i.e. precise > > > > instructions) > > > > > > On Debian/Stretch, the dance is as follows: > > > [...] > > > > Just for the record, here's another one detailing the procedure: > > > > https://hblok.net/blog/posts/2014/02/06/chroot-to-arm/ > > > > (Bye)^2, > > > > Christian > > > > -- -- signature.asc Description: This is a digitally signed message part.
