Drive by posting while waiting on latest, greatest (to date) iso -

I ran it for a couple hours each in bspwm and fluxbox. No problems after decreasing the width of the conky window. Reminds me of the issues users would have with gnome2 desktop icons disappearing and/or blinking after doing a cut-and-paste of some conkyrc but not adjust for their screen aspect ratio.

Quote from: VastOne on February 02, 2014, 02:52:12 PM
Will test all day

I think you should go play golf or go fishing instead.

working fine in bspwm; going to let it sit and see if it stops:

The tint2 systray works in bspwm -



this is actually an interesting setup to get a launcher, system tray, and clock into bspwm. Windows don't iconify in bspwm so the taskbar is a bit superfluous - could probably be set up as a pager. Worth some tinkering later on.

back on topic, still working after typing all this.

@Vastone, do you know if the functionality of the tint2 systray come and go in fluxbox? I know it will if tint2 is restarted, but I never let it sit and checked it at a specified interval.

Where is the slit located in your fluxbox setup?  (there is just no good way to ask that question)

If it's at the top where your tint2 tray was located, move it to the botom and see if you lose functionality in the systray.

I have the upper right tint2 w/ systray working fine. But it's unpatched tint2 with slackware - openbox is already installed.

Edit - it's working in fvwm on VSIDO. Noticed something since my fvwm isn't using compositing. The width of the conky window is 1700 (your resolution?) by default (.conkyrc in /etc/skel); but the conky ouput isn't that wide. The conky window may be causing the interference. I'm thinking conky and tint2 are placed on the same layer when started. If conky is started after tint2, it will always be above tint2 and you're clicking the conky window not tint2 icons. If conky is started first, it will be below tint2 until it refreshes then upon restart it is above tint2 again and the problem returns.

Try decreasing the conky window to the minimum width required to display the information and see if the tint2 systray works in the upper right.



tried a couple logout/login and reboots. Systray working.

^ a first step on the path to awesomeness.

@digit - VSIDO + tabbed Xmonad; sounds like a good candidate for the quarterly oddball release you were talking about in the KDE build thread.

back on topic - tabbed is so much better than tiling (IMO, of course):

^ Still xmonad; is that tint2 along the top, or did you create something in haskel?

Fluxbox, current work in progress:

QuoteNOTES: my IT department wants only distros that pull sources directly from their approved list of Debian, Ubuntu, Arch, Suse, RHL, and CentOS (seems like there is another but cannot remember, and they are still debating Scientific ?!?!). They said #! was out of the question since it had modified packages and used an old insecure kernel; they recommend a vanilla Openbox Debian install if that's what I want. If I need to I can try that at some point, but I need to romp a bit with VSIDO first. It surprises me they approve *buntu though, what with all the user tracking. After the install I will check the sources list for VSIDO since that is one of the things they will ask me for. They are ok with pulling configuration files from various distros but leaving sources and packages unmodified.

Your IT doesn't allow #! but they allow Arch? That's downright comical. VSIDO I can understand since Sid is, by Debian's own admission, unstable so it wouldn't pass ant QA/QC you have going on.

Back on topic - I looked up the specs for the HP Envy 4 and it lists the drives as 500gb and 32gb. Hopefully jedi is correct and that 32gb Win7 drive is a hidden partition you can quickly deal with.

Also this from lwfitz -

QuoteAlso, on some machines its more than just setting to legacy boot. Double check that theres not a force bios option or anything enabled for windows 8.

be sure to double check that; I ran into that checking out a relative's new computer - doing a dummy install just to see what would be required.

Nice one jedi; I'll finish the month with something green(ish) -





revisiting bspwm.

It probably does not create a wm2.desktop file in /usr/share/xsessions/

You can use one that exists to create (as root) one for it. Copy an existing one to wm2.desktop and then edit it to change the name and the binary to execute.

Then it should show on the list of wm's in lightdm.

For slim, you'll need to add it to the list in the slim.conf you're using and make the appropriate entry in your ~/.xinitrc.

Wish we'd back into veggies too; have grone tomatoes, peppers, and radishes in the past. Mostly flowers now. Planted some peach and apple seeds a couple years back, but the deer got the shoots, I think.

^ Nice, I'm liking your green phase.

Pretty standard stuff today -



Window manager hopping this week. Dropped goomwwm, and went with subtle wm. Conky piped to dzen2 for the bottom bar. ; Edit got the sublets working for system info, thinned the window borders:

^ You are correct. Blackbox stopped being developed several years ago. Fluxbox, openbox, and a couple others that are no longer maintained were forked from blackbox.

If the OP really wants to decrease window manager resource usage, he can try using openbox without any 3rd party panels, or try another window manager like cwm, evilwm, flwm, or tinywm (default for Crux linux, I think) - none of which have native panels, but are EWMH compliant so you can use tint2, lxpanel etc ...; of course, there will be a decrease in features - like no window decorations - that he will need to deal with.

Jwm might suit your needs, Oday. It is similar in appearance to fluxbox, and has a native panel with systemtray - I posted a screenshot of the recent version in the screenshot thread. I think htop is running in that shot so you can see the resource usage.

@zbreaker thanks

messing around with a different window manager - goomwwm (get out of my way window manager) - written by the person who wrote musca. A floating wm with some tiling capability. Read more about it at the Arch wiki/forums -

@zbreaker, raphix - nice setups; welcome to the forum, raphix.

drive by posting: