Woody Gilk wrote:
> Johannes Held wrote:
>> Johannes Held wrote:
>>
>> That's strange.
>> It seems that every dockapp that works as systray is capable to kick openbox
>> up
>> to 100% cpu usage.
>>
>> But I simply start it after openbox..
>>
>>From my ~/.xinitrc:
>
> ### Openbox startup ##
Johannes Held wrote:
> Johannes Held wrote:
>
> That's strange.
> It seems that every dockapp that works as systray is capable to kick openbox
> up
> to 100% cpu usage.
>
> But I simply start it after openbox..
>
>From my ~/.xinitrc:
### Openbox startup
nitrogen --restore &
docker &
v
Johannes Held wrote:
> Woody Gilk wrote:
>> Johannes Held wrote:
>>> Do you know a altervative dockapp which acts like a systray?
>> pacman -Si docker
> Thank you very much.
That's strange.
It seems that every dockapp that works as systray is capable to kick openbox up
to 100% cpu usage.
But I sim
Woody Gilk wrote:
> Johannes Held wrote:
>> Do you know a altervative dockapp which acts like a systray?
> pacman -Si docker
Thank you very much.
--
Gruß, Johannes
http://www.hehejo.de
___
arch mailing list
arch@archlinux.org
http://www.archlinux.org/
Johannes Held wrote:
> I tried some things and I'm at the point, that wmdocker is the bad
> one.
>
> I excluded it from .xinitrc and everything seem to work properly.
>
> Do you know a altervative dockapp which acts like a systray?
pacman -Si docker
___
I tried some things and I'm at the point, that
wmdocker is the bad one.
I excluded it from .xinitrc and everything seem to work properly.
Do you know a altervative dockapp which acts like a systray?
Johannes Held wrote:
> Hello,
> I have still problems starting X using openbox 3.3.1-1.
> Sometim
Hello,
I have still problems starting X using openbox 3.3.1-1.
Sometimes my hack is working - but more and more I can't "X" because openbox
hangs with 100% CPU-usage.
Someone any ideas?
Johannes Held wrote:
> Hello,
>
> I have a problem starting openbox.
> It takes up to 100% of CPU-power and th
hi
> dbuslaunch="`which dbus-launch 2>/dev/null`"
> if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z
> "$DBUS_SESSION_BUS_ADDRESS" ]; then
> eval `$dbuslaunch --sh-syntax --exit-with-session`
> fi
>
> exec openbox
> That way dbus gets launched correctly, regardless of windowmanager o
Charles Mauch schrieb:
> Uhm, try this instead...
>
> dbuslaunch="`which dbus-launch 2>/dev/null`"
> if [ -n "$dbuslaunch" ] && [ -x "$dbuslaunch" ] && [ -z
> "$DBUS_SESSION_BUS_ADDRESS" ]; then
> eval `$dbuslaunch --sh-syntax --exit-with-session`
> fi
>
> exec openbox
>
> That way dbus gets
Greetings from Tacoma, WA, USA, Earth, Sol, Milky Way, Verse, Johannes!
On Thursday, October 19, in the 2006th year of our Lord, you wrote:
> Christian Schmidt schrieb:
>> On Thu, Oct 19, 2006 at 10:55:02AM +0200, Johannes Held wrote:
>> [...]
>>> and that's my .xinitrc (shortversion)
>>> #!/bin
Christian Schmidt schrieb:
> On Thu, Oct 19, 2006 at 10:55:02AM +0200, Johannes Held wrote:
> [...]
>> and that's my .xinitrc (shortversion)
>> #!/bin/sh
>> ~/t.sh &
>> openbox
>> exec dbus-launch --exit-with-session openbox
>
> Well, starting openbox twice is bound to fail. Just remove "openb
On Thu, Oct 19, 2006 at 10:55:02AM +0200, Johannes Held wrote:
[...]
> and that's my .xinitrc (shortversion)
> #!/bin/sh
> ~/t.sh &
> openbox
> exec dbus-launch --exit-with-session openbox
Well, starting openbox twice is bound to fail. Just remove "openbox" at like 3.
--
My Public GnuPG-Key:
Johannes Held wrote:
> Hello,
>
> I have a problem starting openbox.
> It takes up to 100% of CPU-power and then it hangs.
>
> and that's my .xinitrc (shortversion)
> #!/bin/sh
> ~/t.sh &
> openbox
> exec dbus-launch --exit-with-session openbo
You're starting openbox twice there. Try this:
# do
Hello,
I have a problem starting openbox.
It takes up to 100% of CPU-power and then it hangs.
I have a pretty bad workaround. Start openbox and kill it. Then it works.
This ist t.sh:
#!/bin/bash
sleep 5
killall -9 openbox
and that's my .xinitrc (shortversion)
#!/bin/sh
~/t.sh &
openbox
e
14 matches
Mail list logo
