There are a few things to note here:

• This does not invalidate the qmake project files and builds, these can still work in parallel.
• If ccache or sccache is detected in the system, it will automatically be used
• If a faster linker is supported, it will be used(LLD Linker on x86_64 with Clang, Gold Linker otherwise. If none supported, the default linker will be used)
• stacer-core is linked statically since it is a small codebase.
• Install Prefix was fixed(compared to the qmake version which always installs stacer-core in /usr/lib). You can use -DCMAKE_INSTALL_PREFIX=<path> or make DESTDIR=<path> install. Default prefix is /usr/local - that means, without passing anything, make install will put the binary here: /usr/local/bin/stacer
• make install will not install anything for Debug builds since no one should(probably by mistake) install unoptimized builds.
• Works in any IDE

OS: Ubuntu 16.04.2 LTS uname -a: Linux hostnamehere 4.8.0-54-generic #57~16.04.1-Ubuntu SMP Wed May 24 16:22:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Installed version: stacer_1.0.7_amd64.deb

I realize there is a TON of information being gathered on startup which I suspect has a lot to do with this. The application startup time from launching the window to seeing some output aside from "Loading" is very long, on the order of 2 minutes, 11 seconds.

When trying to clean anything from within Satcer an error message is shown: "System Cleaning Failed" (text in a red colored field).

Stacer version: 1.0.7 Linux: kubuntu 17.04

/Tomas Nilzon

Hi I've downloaded the Appimage version v1.0.8 but when I try to start it I get this message:

./Stacer-x64.AppImage 
This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".

Available platform plugins are: xcb.

Reinstalling the application may fix this problem.

The wrong message as follows: stacer

Translator could not load. ASSERT failure in QList::at: "index out of range", file /opt/qt59/include/QtCore/qlist.h, line 541 [1] 29618 abort (core dumped) stacer

set(CMAKE_CXX_STANDARD 11) has effect only starting with CMake 3.1, so the minimum requirement was lowered to 3.1(CMake 3.2 available in Ubuntu 14.04).

This also adds LTO for Release builds, which at the moment removes only 0.1 MB from the binary.

hello,i like the stacer

but i install stacer falied.

please help me ,how can solve the issue

[root@breap Documents]# yum localinstall stacer_1.0.9_x64.rpm Last metadata expiration check: 0:03:46 ago on Fri 16 Mar 2018 04:55:18 PM CST. Dependencies resolved.

Package Arch Version Repository Size

Installing: stacer x86_64 1.0.9-2 @commandline 29 M Installing dependencies: qt5-qtcharts x86_64 5.9.4-1.fc27 updates 575 k

Transaction Summary

Install 2 Packages

Total size: 30 M Installed size: 77 M Is this ok [y/N]: y Downloading Packages: [SKIPPED] qt5-qtcharts-5.9.4-1.fc27.x86_64.rpm: Already downloaded
Running transaction check Transaction check succeeded. Running transaction test The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Transaction check error: file /usr from install of stacer-1.0.9-2.x86_64 conflicts with file from package jdk1.8.0_144-2000:1.8.0_144-fcs.x86_64 file /usr/share/icons/hicolor from install of stacer-1.0.9-2.x86_64 conflicts with file from package teamviewer-12.0.76279-0.i686 file / from install of stacer-1.0.9-2.x86_64 conflicts with file from package filesystem-3.3-3.fc27.x86_64 file /usr from install of stacer-1.0.9-2.x86_64 conflicts with file from package filesystem-3.3-3.fc27.x86_64 file /usr/share from install of stacer-1.0.9-2.x86_64 conflicts with file from package filesystem-3.3-3.fc27.x86_64 file /usr/share/applications from install of stacer-1.0.9-2.x86_64 conflicts with file from package filesystem-3.3-3.fc27.x86_64 file /usr/share/icons from install of stacer-1.0.9-2.x86_64 conflicts with file from package filesystem-3.3-3.fc27.x86_64 file /usr/share/icons/hicolor/128x128 from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor/128x128/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor/16x16 from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor/16x16/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor/256x256 from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor/256x256/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor/32x32 from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor/32x32/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor/64x64 from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor/64x64/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package hicolor-icon-theme-0.17-1.fc27.noarch file /usr/share/icons/hicolor from install of stacer-1.0.9-2.x86_64 conflicts with file from package fedora-logos-28.0.2-1.fc27.x86_64 file /usr/share/icons/hicolor/16x16 from install of stacer-1.0.9-2.x86_64 conflicts with file from package fedora-logos-28.0.2-1.fc27.x86_64 file /usr/share/icons/hicolor/16x16/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package fedora-logos-28.0.2-1.fc27.x86_64 file /usr/share/icons/hicolor/256x256 from install of stacer-1.0.9-2.x86_64 conflicts with file from package fedora-logos-28.0.2-1.fc27.x86_64 file /usr/share/icons/hicolor/256x256/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package fedora-logos-28.0.2-1.fc27.x86_64 file /usr/share/icons/hicolor/32x32 from install of stacer-1.0.9-2.x86_64 conflicts with file from package fedora-logos-28.0.2-1.fc27.x86_64 file /usr/share/icons/hicolor/32x32/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package fedora-logos-28.0.2-1.fc27.x86_64 file /usr/share/icons/hicolor from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/128x128 from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/128x128/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/16x16 from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/16x16/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/256x256 from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/256x256/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/32x32 from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/32x32/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/64x64 from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file /usr/share/icons/hicolor/64x64/apps from install of stacer-1.0.9-2.x86_64 conflicts with file from package atom-1.23.3-0.1.x86_64 file / from install of stacer-1.0.9-2.x86_64 conflicts with file from package boostnote-0.10.0-2.x86_64 file /usr from install of stacer-1.0.9-2.x86_64 conflicts with file from package boostnote-0.10.0-2.x86_64 file /usr/share from install of stacer-1.0.9-2.x86_64 conflicts with file from package boostnote-0.10.0-2.x86_64 file /usr/share/applications from install of stacer-1.0.9-2.x86_64 conflicts with file from package boostnote-0.10.0-2.x86_64 file / from install of stacer-1.0.9-2.x86_64 conflicts with file from package netease-cloud-music-1.1.0-2.x86_64 file /usr from install of stacer-1.0.9-2.x86_64 conflicts with file from package netease-cloud-music-1.1.0-2.x86_64 file /usr/share from install of stacer-1.0.9-2.x86_64 conflicts with file from package netease-cloud-music-1.1.0-2.x86_64 file /usr/share/applications from install of stacer-1.0.9-2.x86_64 conflicts with file from package netease-cloud-music-1.1.0-2.x86_64 file /usr/share/icons from install of stacer-1.0.9-2.x86_64 conflicts with file from package netease-cloud-music-1.1.0-2.x86_64 file /usr/share/icons/hicolor from install of stacer-1.0.9-2.x86_64 conflicts with file from package netease-cloud-music-1.1.0-2.x86_64

Error Summary

[root@breap Documents]#

joseph@joseph-X541UJ:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04 LTS
Release:	20.04
Codename:	focal
joseph@joseph-X541UJ:~$ sudo apt install stacer 
[sudo] password for joseph: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
stacer is already the newest version (1.1.0-3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
joseph@joseph-X541UJ:~$ stacer

Command 'stacer' not found, but can be installed with:

sudo apt install stacer

joseph@joseph-X541UJ:~$ 

Hello,

what about adding a new feature, something like network limiter per application, here is screenshot:

https://www.netlimiter.com/files/imagegalleries/docs/client-full-new.png

Thank you

I installed the latest version (1.0.8) and noticed that the enabled/disabled System Startup Apps don't match the Startup apps for the system (refer to screenshot).

System Info:

• Ubuntu Budgie 17.04
• Kernel version: 4.10.0-30-generic #34-Ubuntu

I wanted to install from source but I wasn't able to do it. I followed these instructions :

git clone https://github.com/oguzhaninan/Stacer.git

cd Stacer

npm install && npm run build && npm start

Hi My screen has high definition 3800x2200 and when I zoom the display at 300x, it doesnt zoom your Stacer menus (too small). Cannot read. What to do? Am a newbee Cheers Serge

summary

Once I installed stacer from the deb package on github,it worked normally those days. Today I update it with apt package manager,it cannot start at that time. Then I remove the stacer complete,and reinstall it again.Finally it works.

details

In the Cinnamon Menu(like start menu),I can't find stacer. And in terminal,input "stacer", it alerts "No such file or directory". Then enter the applications directory:/usr/share/applications , double click the stacer,it alerts "the application launch failed". At last,I search "stacer" in Fsearch(a search utility),found that the stacer application directort had gone,just remaining the config and doc directory. So I complete remove the stacer ,and install again.Now it works now. So if you get stacer from github too,don't directly update it, you can remove it first,then reinstall it from apt package manager. With the command:

sudo apt autoremove stacer
sudo apt install stacer

Hi i have build on my ubuntu 22.04 stacer, but when i run: /app/Stacer/build/output/stacer tell me:

14:40:12 dacorsa@NanoKDE /home/dacorsa $ /app/Stacer/build/output/stacer Errore di segmentazione (core dump creato)

How can i solve it?

Hello!

Love Stacer!!! Was wondering if the app could possibly provide information about any Swap files on the system and provide a way to manage/resize/configure them.

Thanks!