tint2 strange issues and freezing

o9000 · 2016-02-26 19:43:17

If you compile from source, it will install all its files to /usr/local instead of /usr (except for /etc/xdg/tint2/tint2rc, there is a complete list of files here).
The package manager installs everything in /usr; thus there is no conflict between the two sets of files.

However if you have both of them installed at the same time, depending on your $PATH variable, one or the other may be started when you run 'tint2': if /usr/local/bin appears before /usr/bin, the one compiled from source is started. You can also use the full path '/usr/local/bin/tint2' to resolve the ambiguity.

Please let me know if things improve, or if you notice other problems.

Head_on_a_Stick · 2016-02-26 19:47:59

o9000 wrote:

However if you have both of them installed at the same time, depending on your $PATH variable, one or the other may be started when you run 'tint2'

In a stock BunsenLabs system, /usr/local/bin is searched before /usr/bin but after ~/bin

So if both are installed, the version compiled from source will be run.

Check with:

which tint2

ppk · 2016-02-27 08:25:50

which tint2

gave me ...

/usr/local/bin/tint2

As of now, the latest version 0.12.7 is stable for me. Till now, I've not faced any freezing issue. I will wait for two more days and post about my experience once again.

Also, the 0.12+ changelog is very impressive.

ppk · 2016-02-29 08:46:02

OK. I've used my laptop extensively for the last two days. There is not even a single freezing incident with the latest version (0.12.7) of tint2 panel. I feel the latest version is more stable than the stock 0.11 version in debian repos, at least in my case where I had frequent freezing issues with the 0.11 version.

Please consider it as my feedback and see if it's worth shipping the latest version in the final stable ISO.

KrunchTime · 2016-02-29 13:38:28

hhh wrote:

Our backport won't be the default. BL is going to stay with Debian stable OOTB wherever possible and then the user can do whatever they like...

+1

hhh wrote:

...we'll gladly help you break it.

cr0sh · 2016-09-03 15:26:16

This is my first-post on this forum, and I know this is a "dead thread" - I apologize for resurrecting it...

I wanted to let everyone know that I was having the same problems as OP with tint2 (albeit I am not running BL - long story short: I have a customized system based on Ubuntu 14.04LTS minimal that I "built up" using Openbox, Tint2, XFCE, etc - plus old #! config files and my own magic to get a #! like experience after #! went belly up, but before BL was stable enough for me to consider using it, and before #!++ existed as well - I wanted my #!, I wanted something recent, so I rolled my own, so to speak).

Basically, every now-and-then tint2 (from the ubuntu repo) would lock up; it seemed to happen often when running Thunar - but occasionally other times it would die for no other apparent reason. Anyhow, I could get things re-started, but my system tray icons would never come back (even killing the processes and restarting them didn't help). For that, I had to completely logout/login again.

So - some searching 10 minutes ago brought me to this thread, and I thought "what the heck, what's one more custom piece of code on this already bodged-up system" - so I downloaded and built the latest stable from source as noted. So far, it is working - I'll see how stable it is over the next week or so, and let people know what happens.

In short - I want to thank everyone on this thread - even if this doesn't cure my ills, it was fun trying!

o9000 · 2016-09-03 21:57:35

Thanks for letting us know. If you find any issues with the latest version, don't hesitate to report them, either here or on https://gitlab.com/o9000/tint2/issues

Temetka · 2016-09-04 01:19:04

I"m glad someone bumped this thread. I just finished setting up my laptop with BL and was having the same issue as OP. Imagine my suprise to find myself posting in this thread earlier.

Anyway, I'm going to add the complile from source version to my system and report if anything breaks. Or heck just report if it works.

EDIT: Problems

So using the instructions from here:

https://gitlab.com/o9000/tint2

I get stuck at the cmake command. It appears to not be installed on my system (tried sudo cmake also). So I figured I would install it with a simple "sudo apt-get install cmake".

That worked fine. So now I have cmake installed. Cool, lets try this again

cmake ..

Nope. Figured since gcc is already installed I missed something. I re-ran bl-welcome and added in some of the development stuff.

Ran the command again and get this mess:

-- The CXX compiler identification is GNU 4.9.2
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Could NOT find PkgConfig (missing:  PKG_CONFIG_EXECUTABLE) 
CMake Error at /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:381 (message):
  pkg-config tool not found
Call Stack (most recent call first):
  /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:395 (_pkg_check_modules_internal)
  CMakeLists.txt:19 (pkg_check_modules)


CMake Error at /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:381 (message):
  pkg-config tool not found
Call Stack (most recent call first):
  /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:395 (_pkg_check_modules_internal)
  CMakeLists.txt:20 (pkg_check_modules)


CMake Error at /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:381 (message):
  pkg-config tool not found
Call Stack (most recent call first):
  /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:395 (_pkg_check_modules_internal)
  CMakeLists.txt:21 (pkg_check_modules)


CMake Error at /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:381 (message):
  pkg-config tool not found
Call Stack (most recent call first):
  /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:395 (_pkg_check_modules_internal)
  CMakeLists.txt:22 (pkg_check_modules)


CMake Error at /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:381 (message):
  pkg-config tool not found
Call Stack (most recent call first):
  /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:395 (_pkg_check_modules_internal)
  CMakeLists.txt:23 (pkg_check_modules)


CMake Error at /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:381 (message):
  pkg-config tool not found
Call Stack (most recent call first):
  /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:395 (_pkg_check_modules_internal)
  CMakeLists.txt:24 (pkg_check_modules)


CMake Error at /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:381 (message):
  pkg-config tool not found
Call Stack (most recent call first):
  /usr/share/cmake-3.0/Modules/FindPkgConfig.cmake:395 (_pkg_check_modules_internal)
  CMakeLists.txt:25 (pkg_check_modules)


CMake Error at CMakeLists.txt:67 (message):
  Not all dependencies fulfilled.  See
  https://gitlab.com/o9000/tint2/wikis/Install


-- Configuring incomplete, errors occurred!
See also "/home/temetka/tint2/build/CMakeFiles/CMakeOutput.log".
See also "/home/temetka/tint2/build/CMakeFiles/CMakeError.log".

So as of right now I am going to reboot and see if anything changes. I'll be back.

EDIT: Nope. Still the same mess as above. Now what?

Last edited by Temetka (2016-09-04 01:51:19)

cr0sh · 2016-09-04 05:17:03

Temetka wrote:

EDIT: Nope. Still the same mess as above. Now what?

Well - from what I can see you don't have pkg-config installed. But first - you have followed these instructions:

https://gitlab.com/o9000/tint2/wikis/Install

...and made sure you had all the dependencies installed?

You'll also want to make sure you have a full dev system installed - for Debian-based systems like BL - first make sure your system is up-to-date:

sudo apt-get update        # Fetches the list of available updates
sudo apt-get upgrade       # Strictly upgrades the current packages
sudo apt-get dist-upgrade  # Installs updates (new ones)

(note - the above is what I use on Ubuntu - but it should be the same or close for any debian-derived distro)

Then, install the development "essentials":

sudo apt-get install build-essential

Then re-run the build process for tint2 (remember to do it using sudo).

Usually that's all that is wrong - not having the full dev/compile system in place (and if you're compiling from source once, you'll likely do it again in the future - honestly, it should be part of the default install - and at one time it was a part of the default install on most distros up until the early-2000s or so).

nobody · 2016-09-04 06:26:36

We have the latest tint2 release in the BL repos, FYI. https://forums.bunsenlabs.org/viewtopic.php?id=1856.

o9000 · 2016-09-04 16:31:13

Indeed, if you are on BunsenLabs (not Ubuntu!) the easy way is to use the packaged version.

But for what it's worth, there is an easy way to install the dependencies required for building a program:

sudo apt-get build-dep tint2

This works as long as the dependencies of the packaged version and the version you want to compile are the same. From my experience, it is almost always the case. When it's not, it's usually a matter of finding a few new library dependencies, which should not be difficult with an apt-cache search, and looking for libWHATEVER-dev.

johnraff · 2016-09-05 02:18:49

There are also possible workrounds for the freezing that occurs with the BL default version of tint2. They work sometimes for some people:

*) If the freezes are infrequent, often just hitting Menu>Preferences>Tint2>Restart Tint2 will clear it. Obviously not a good option if it's happening all the time...
*) If you don't use the four launcher icons at the end of the panel, try disabling the launcher in tint2rc, ie remove the L from 'panel_items = LTSC'. (I understood the freezes were connected with startup notification, @o9000?)

o9000 · 2016-09-05 09:59:54

Indeed, it was a lockup caused by startup notifications.

Temetka · 2016-09-05 10:19:02

o9000 wrote:

Indeed, if you are on BunsenLabs (not Ubuntu!) the easy way is to use the packaged version.
But for what it's worth, there is an easy way to install the dependencies required for building a program:
sudo apt-get build-dep tint2
This works as long as the dependencies of the packaged version and the version you want to compile are the same. From my experience, it is almost always the case. When it's not, it's usually a matter of finding a few new library dependencies, which should not be difficult with an apt-cache search, and looking for libWHATEVER-dev.

Well hello there! I was unaware it was in the repo's. I'll give that a shot.

Tried and failed. I get this error:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: You must put some 'source' URIs in your sources.list

Here's my /etc/apt/sources.list file

# 

# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20160706-02:22]/ jessie contrib main non-free

# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20160706-02:22]/ jessie contrib main non-free

deb http://httpredir.debian.org/debian jessie main non-free contrib
#deb-src http://httpredir.debian.org/debian jessie main non-free contrib

deb http://security.debian.org/ jessie/updates main contrib non-free
#deb-src http://security.debian.org/ jessie/updates main contrib non-free

# jessie-updates, previously known as 'volatile'
deb http://httpredir.debian.org/debian jessie-updates main contrib non-free
#deb-src http://httpredir.debian.org/debian jessie-updates main contrib non-free

Thanks for any help in advance.

o9000 · 2016-09-05 10:23:05

You should just uncomment the deb-src lines (remove the #) and then run apt-get update to refresh the package index.

Last edited by o9000 (2016-09-05 10:24:45)

Temetka · 2016-09-05 23:42:21

That worked, thanks.

So silly question: How do I verify I am running the new version? I logged out and logged back in. Things look the same as they were before, but maybe it's the same config - or reading my tint2 config file and loading that.

v3g4n · 2016-09-06 03:41:54

logging out and back in should load you newest version of tint2 and you can verify your installed version with

apt-cache policy tint2

your newer version of tint2 will be looking at your tint2rc so that is why it looks the same.

o9000 · 2016-09-06 05:15:39

There is also

tint2 --version

.

martix · 2016-12-10 21:50:35

I'm wondering: In some posts above the "hovering"-feature was mentioned.

If I read correctly, since 0.12.3 it's possible to have changing icon colors and transparency while hovering over the icons (atm I have version 0.11+svn20121014).

Is it maybe possible to configure e.g. launching the browser while hovering over its icon in tint2?

o9000 · 2016-12-11 10:00:12

So you don't have to click? It's not possible at the moment. Why would you want this?

#21 2016-02-26 19:43:17

Re: tint2 strange issues and freezing

#22 2016-02-26 19:47:59

Re: tint2 strange issues and freezing

#23 2016-02-27 08:25:50

Re: tint2 strange issues and freezing

#24 2016-02-29 08:46:02

Re: tint2 strange issues and freezing

#25 2016-02-29 13:38:28

Re: tint2 strange issues and freezing

#26 2016-09-03 15:26:16

Re: tint2 strange issues and freezing

#27 2016-09-03 21:57:35

Re: tint2 strange issues and freezing

#28 2016-09-04 01:19:04

Re: tint2 strange issues and freezing

#29 2016-09-04 05:17:03

Re: tint2 strange issues and freezing

#30 2016-09-04 06:26:36

Re: tint2 strange issues and freezing

#31 2016-09-04 16:31:13

Re: tint2 strange issues and freezing

#32 2016-09-05 02:18:49

Re: tint2 strange issues and freezing

#33 2016-09-05 09:59:54

Re: tint2 strange issues and freezing

#34 2016-09-05 10:19:02

Re: tint2 strange issues and freezing

#35 2016-09-05 10:23:05

Re: tint2 strange issues and freezing

#36 2016-09-05 23:42:21

Re: tint2 strange issues and freezing

#37 2016-09-06 03:41:54

Re: tint2 strange issues and freezing

#38 2016-09-06 05:15:39

Re: tint2 strange issues and freezing

#39 2016-12-10 21:50:35

Re: tint2 strange issues and freezing

#40 2016-12-11 10:00:12

Re: tint2 strange issues and freezing

Board footer