tint2 edit makes screen flicker

buckyballs · 2017-02-13 23:10:55

New guy here, no CL background since I installed Win95 with DOS (and DOS for dummies).
Fresh install of BL on a separate partition has run flawlessly for two weeks. I have managed to get several apps installed and working, and then -
Saw a mention of "hide taskbar" in a forum post re; tint2. I tried changing the value from 0 to 1 in the editor, saved (not "save as") and when I returned to desktop, taskbar was rapidly and irregularly opening and closing while any open window, including openbox menu, would flicker and show wallpaper as a flash.Not a comfortable environment.
Trie turning off tint2 with picker > deselect all > answer yes to prompt offering to kill all.
No tint, still flickers.
CPU in task man shows 5 to 12 percent usage with absolutely nothing visibly going on but blank wallpaper.
In task man;
usr/bin/x; -seat seat0 -auth/var/run/lightdm/root/0 - nolisten tcp vt7 noutswitch
possible error in that line, it's typed from napkin note as I am back in my win partition for now.
TMI or not enough?
I have made some other changes recently, but this is the one that set it off.
P.S. Tried un-editing change, no results.
Thank you so much for even offering this stuff, I will comment in the "introductions" thread when I'm up and running.

ohnonot · 2017-02-14 07:10:19

so you're saying it worked, then you did something, and now it flickers?
can you show us exactly what this something is?
preferably in code: commands executed, files edited (before - after) and so on.
if you made changes from the openbox menu, please recreate the exact path you took, e.g.
rootmenu => preferences => tint2 => restart tint2
and so on.

generally speaking and in my opinion bunsenlabs WILL require you to brush up on those command line skills, if you want to customize it that is.

Head_on_a_Stick · 2017-02-14 08:06:45

buckyballs wrote:

Tried un-editing change, no results.

To revert to the stock configuration, use:

cp /usr/share/bunsen/skel/.config/tint2/tint2rc ~/.config/tint2

buckyballs · 2017-02-17 02:03:10

ohnonot wrote:

bunsenlabs WILL require you to brush up on those command line skills

A very polite and extremely generous reading of my comments, Ohnonot.
The sad reality is I just don't have any. Like a kid taking apart a clock (yeah, I totally did that), the thing isn't going back together.
I would describe the exact steps I took if I could, but as I did more than one the path is shrouded in time now. It's also difficult to copy/paste over a partition and I'm on the Windows side just now because I haven't broken that.

head-on-a-stick wrote:

To revert to the stock configuration, use:
cp /usr/share/bunsen/skel/.config/tint2/tint2rc ~/.config/tint2

Tried that,got an error.
Thank you for your patience and clarity. I also remembered a "save" in the blob file, got an earlier version back,but the flickering and surprising memory usage continued.
I dont care to burn up anymore attention here when I have been fundamentally irresponsible, so I am going to employ the universal Microsoft repair protocol;
nuke it from orbit
I don't have much to lose, and I think I've learned a lesson.
Please mark this issue as "solved" and accept my thanks.
I have some additional comments that belong elsewhere, only wonder ;
Can I re-install BL over itself, or should I format first?
Also, will the grub boot loader allow two incidences of BL so that I can make leapfrog changes?
I'm keeping Windows as training wheels for a while.

damo · 2017-02-17 02:32:04

buckyballs wrote:

....
Can I re-install BL over itself, or should I format first?
Also, will the grub boot loader allow two incidences of BL so that I can make leapfrog changes?
I'm keeping Windows as training wheels for a while.

You can format the partition during the install process, although I tend to do it with gparted from the live disc first ( Main menu -> System);

You can only have 2 "instances" of BL if they are installed in different partitions. However, whichever was the latest to install grub will be the one that controls the boot process. It is actually quite useful to have a multi-boot setup, because you can use one to make archives (snapshots) of the other, for backing up ( - many other methods of doing this though).

BTW the default user configurations are in '/usr/share/bunsen/skel/', or you can get them from our github repository.

If you mess up your configuration, and don't know how to revert, then consider creating a new user and logging in to that - everything should be fresh defaults. [Try this before you reinstall?]

You really must get some familiarity with the commandline IMO! BL isn't windoze, and you are seriously restricting yourself if don't

buckyballs · 2017-02-17 05:21:05

BLenderer wrote:

consider creating a new user and logging in to that

Didn't think of that, good idea,but - I really did a lot wrong the first time and it's a recent install, so re-do feels right.
I had already set up three partitions (including the Windows on) before I started so I'm good to go.

BLenderer wrote:

You really must get some familiarity with the commandline

This is absolutely clear to me - although the OOB set up is totally useful by default and has been stable as a brick on my hardware. I could live well as-is.
The problem is where to begin?
It is not at all clear when starting from dead scratch what goes first.It feels like having to learn trig in Chinese in order to ride a bicycle.
Thought I'd post that in "Introductions" and take advice; I can't be the only one.I'm a retired old fart and up for "beginners mind" but at 69 I don't want to put in the same decade or two that I spent trying get competent with MS.
Sort of competent.
I'm busy smoking pastrami, roasting coffee, and mastering a new camera too.
Still, this distro has a sleekness that is wonderfully attractive to me, so I'll figure out a way - my retirement income doesn't allow for a c-note worth of upgrade from XP anyway.

hhh · 2017-02-17 06:03:22

Open a terminal...
sudo apt update && sudo apt upgrade

Occasionally...
sudo apt-get --purge autoremove && sudo apt-get clean

Be careful with autoremove though.

Head_on_a_Stick · 2017-02-17 07:58:53

For future reference:

buckyballs wrote:

head-on-a-stick wrote:
To revert to the stock configuration, use:
cp /usr/share/bunsen/skel/.config/tint2/tint2rc ~/.config/tint2
Tried that,got an error.

Please post the exact error message rather than a vague reference, "got an error" tells me *nothing* whereas the full, verbatim error message would have told me what had actually gone wrong

ohnonot · 2017-02-19 11:00:32

buckyballs wrote:

ohnonot wrote:
bunsenlabs WILL require you to brush up on those command line skills
A very polite and extremely generous reading of my comments, Ohnonot.
The sad reality is I just don't have any. Like a kid taking apart a clock (yeah, I totally did that), the thing isn't going back together.

i think that's how 99% of us got started with linux.

but you missed the second half of my quote:

, if you want to customize it that is.

people often miss that: linux is stable (enough), and usable even for a newbie (or however you want to call someone who won't touch the CLI). it's only if you insist on tinkering that things get a little tricky.

#1 2017-02-13 23:10:55

tint2 edit makes screen flicker

#2 2017-02-14 07:10:19

Re: tint2 edit makes screen flicker

#3 2017-02-14 08:06:45

Re: tint2 edit makes screen flicker

#4 2017-02-17 02:03:10

Re: tint2 edit makes screen flicker

#5 2017-02-17 02:32:04

Re: tint2 edit makes screen flicker

#6 2017-02-17 05:21:05

Re: tint2 edit makes screen flicker

#7 2017-02-17 06:03:22

Re: tint2 edit makes screen flicker

#8 2017-02-17 07:58:53

Re: tint2 edit makes screen flicker

#9 2017-02-19 11:00:32

Re: tint2 edit makes screen flicker

Board footer