[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kwin] [Bug 337948] error on replacing kwin
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2014-08-01 7:21:53
Message-ID: bug-337948-17878-sDDLFxpjtB () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=337948

Thomas Lübking <thomas.luebking@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from Thomas Lübking <thomas.luebking@gmail.com> ---
> #!/bin/sh
> export DISPLAY=:0 2>&1
> killall kwin > /dev/null 2>&1
> kwin --replace  > /dev/null 2>&1
> ls -la > kwin.log > /dev/null 2>&1

a) you're probably doing this because of
https://forum.kde.org/viewtopic.php?f=111&t=121590 ?
b) there's no point in calling "killall kwin" (the way killall works this is
rather dangerous, because it applies to everything that has "kwin" in the
command) - "kwin --replace" shuts down any present windowmanager (ie. usually
kwin in your case)
c) The issue is "Session bus not found \nTo circumvent this problem try the
following command (with Linux and bash) \nexport $(dbus-launch)"

Basically your approach is wrong and you get an abort because
- there's no dbus session
- because you're not running this as user but as root and
- also some relevand environment variables of the session are not set

If the module loading parameter does not help you, check whether
suspnding/resuming the compositor alone helps to get rid of the corruption.

In case, you want a script that detects the users of all running kwin
processes, find their dbus session and as those users, check whether
qdbus org.kde.KWin /KWin compositingActive
and then
qdbus org.kde.KWin /KWin toggleCompositing
twice (with a little delay) - each addressing the proper DBUS (can be fetched
out of the /proc/$PID/environ)

The bug is invalid because your it's your script that is "buggy" ;-)

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]