Advertising

QT 5.7.0 doesn’t support GTK theming

The QT 5.7.0 doesn’t support GTK theming, so after upgrade Qt related packages, the Qt based applications look… not really nice on GTK based desktops.

How to fix it:
sudo apt update
sudo apt install qt5-style-plugins

Then:
sudo echo "QT_QPA_PLATFORMTHEME=gtk2" >> /etc/environment
or
su
nano /etc/environment

and past into the file:
QT_QPA_PLATFORMTHEME=gtk2
then:
sudo reboot

That’s all. The first screen shows a Qt5 based application before, the second one after.

QMPlay2 before    QMPlay2 after

 

System upgrade 2015-07-21

 

The last system upgrade makes some changes in the system so be careful.
It wants to remove some packages:
Packages to be removed:
audacity avidemux avidemux-plugins avidemux-qt browser-plugin-vlc dvd95
gnome-control-center gstreamer0.10-plugins-ugly gstreamer1.0-plugins-bad
gstreamer1.0-plugins-ugly kadu libasound2-plugins:i386 libcheese-gtk23
libcheese7 libopencv-calib3d2.4 libopencv-contrib2.4 libopencv-features2d2.4
libopencv-highgui2.4 libopencv-legacy2.4 libopencv-objdetect2.4 mencoder
minitube ogmrip phonon phonon-backend-vlc skype:i386 twolame vlc vlc-nox
vlc-plugin-notify
New packages to be installed:
libavresample-ffmpeg2 libavresample-ffmpeg2:i386 libavutil-ffmpeg54
libavutil-ffmpeg54:i386 libswresample-ffmpeg1 libswscale-ffmpeg3
Hold packages:
libasound2-plugins
Packages to be upgraded:
libopencv-core2.4 libopencv-flann2.4 libopencv-imgproc2.4 libopencv-ml2.4
libopencv-video2.4

To fix that, remove ‘libasound2-plugins’ package before upgrading.
sudo apt-get remove libasound2-plugins
sudo apt-get autoremove

If you have ‘libasound2-plugins:i386’ package installed on 64bit system – remove it too.
sudo apt-get remove libasound2-plugins:i386
sudo apt-get autoremove

Then perform standard full upgrade:
sudo apt-get update
sudo apt-get dist-upgrade

The operations can remove ‘pulseaudio’, ‘pavucontrol’ and ‘skype’ packages so install them back after.

Edit:
Looks like ‘skype’ can’t be installed back – it depends on ‘libasound2-plugins’ which can’t be installed – broken dependencies.

 

Sparky rebranding

Last week me and MoroS have been working on Sparky rebranding.
The job is done now so you can get all the changes on yours present Sparky installations.

What does the Sparky rebranding mean?
Sparky iso image installs the system based on Debian testing with Sparky tools, touch and some additional elements. But the system is detected as Debian so it can make misunderstanding for some users.

All the system’s key elements have been rebuilt/replaced with Sparky ones and added a few new packages to improve Sparky “touch”.

If you’d like to turn your existing Sparky installation (up to version 3.6) or Debian testing installation into rebranded Sparky, follow the steps:
su
apt-get update
apt-get dist-upgrade
apt-get install -f

Then rebrand it:
apt-get install sparky-core
apt-get install -f

Then reboot:
reboot

SparkyLinux GRUB

To check it out, run:
lsb_release -a

If you find any problem, simply report it to our forums.

 
 
Back to -> FAQ main page
 

Sparky 3.4/3.4.1 tests

 

 

I have made my own test to find out how much power Sparky takes.
I used 32 bit iso images of Sparky 3.4 and 64 bit iso images of Sparky 3.4.1.

All tests have been made on VirtualBox with given the power:
– CPU 1 x 2.4 GHz for 32 bit systems
– CPU 2 x 2.4 GHz for 64 bit systems
– RAM memory 2024 MB
– SWAP 1024 MB – used: 0 in all tests

The results can be a little different on other machines.

Sparky installed on a hard drive:

CPU
32 bit
RAM
32 bit
CPU
64 bit
RAM
64 bit
CPU
64 bit EFI
RAM
64 bit EFI
Base 1-2 % 80 MB 2-3 % 118 MB
CLI 1-2 % 32 MB 1-2 % 52 MB
E18 1-3 % 104 MB 1-4 % 153 MB
GameOver 1-2 % 115 MB 1-4 % 185 MB
LXDE 1-2 % 123 MB 2-4 % 195 MB 2-4 % 196 MB
MATE 2-4 % 165 MB 2-4 % 266 MB
Razor-Qt 1-3 % 176 MB 1-3 % 240 MB
Xfce 1-3 % 139 MB 2-5 % 205 MB

Sparky Live system:

CPU
32 bit
RAM
32 bit
CPU
64 bit
RAM
64 bit
CPU
64 bit EFI
RAM
64 bit EFI
Base 1-2 % 93 MB 1-3 % 140 MB 1-3 % 139 MB
CLI 1-2 % 42 MB 1-2 % 66 MB
E18 1-2 % 122 MB 2-4 % 184 MB 2-5 % 178 MB
GameOver 1-2 % 131 MB 1-3 % 215 MB 1-3 % 207 MB
LXDE 1-2 % 135MB 2-4 % 216 MB 2-4 % 212 MB
MATE 2-4 % 190 MB 3-5 % 297 MB 2-5 % 295 MB
Razor-Qt 2-4 % 220 MB 2-4 % 337 MB 1-3 % 330 MB
Xfce 1-3 % 162 MB 2-5 % 250 MB 2-5 % 250 MB

The most hungry of power still is Razor-Qt desktop, the lightest one is Openbox.
64 bit Sparky consumes the same amout of power in BIOS and EFI mode.

 

Theme changing problem

 

Changing the default theme on Sparky LXDE, Ultra and Razor-Qt can make a problem.
To do that I used to use Lxappearance.
It saves new settings in 3 files:
/home/you/.gtkrc-2.0
/home/you/.config/gtk-3.0/setting.ini
/home/you/.config/lxsession/LXDE/desktop.conf

If Lxappearance changes the first two files well, it does not change the last one “desktop.conf”.
So edit the “desktop.conf” file with a text editor and change the line from:
sNet/ThemeName=Sparky3

to:
sNet/ThemeName=Your-Theme-Name

and save the file.
 
 
Back to -> FAQ main page
 

Sparky APTus 0.1.4

 

There is an update of Sparky APTus 0.1.4 available at our repository.

Changelog:
– Upgrade – this will run “apt-get upgrade”
– Dist_Upgrade – this will run “apt-get dist-upgrade” – recommended way to keep Sparky up to date
– Quick_Install – quick install a package/packages from the repository
– Quick_Install_DEB – quick install “.deb” package from a local disk with all the dependencies
– Quick_Remove – quick remove selected package/packages from the system with all the dependencies
– Old_Kernel_Remove – this will remove old, non-active system kernel (if any)

APTus

 

Sparky APTus

 

Sparky APTus is a small, simply and lightweight front-end for “apt-get” and “dpkg” tools.
It can be used for upgrading, installing, removing packages and cleaning up the system.

The application can do:

– Update – update package list
– Upgrade – safely system upgrading
– Dist_Upgrade – full system upgrading – recommended way to keep Sparky up to date

– Quick_Install – install a package/packages from the repository
– Quick_Install_DEB – install “.deb” package from a local disk with all the dependencies
– Language – install missing language packages

– Quick_Remove – remove selected package/packages from the system with all the dependencies
– Old_Kernel_Remove – this will remove old, non-active system kernel (if any)
– NonFree_Remove – this will remove Non-Free and Restricted packages from the system (if any)

– Fix_Broken_DPKG – Check by DPKG broken packages not installed/upgraded correctly
– Fix_Broken_APT – Check by APT broken packages not installed/upgraded correctly

– Autoremove – unnecessary packages removing
– Autoclean – old versions of “.deb” packages removing
– Clean – all downloaded “.deb” packages removing.

– Edit main (Debian testing) repository
– Edit other repositories

APTus

 

It can be installed from our repository.
For Debian and Ubuntu based distributions check: sparky-aptus-on-debian-and-ubuntu

 
Back to -> FAQ main page
 

Sparky repository

 
The configuration is deprecated, go to Sparky Wiki pages.

Log in to root account, then:
1. Create a new file:
nano /etc/apt/sources.list.d/sparky.list
2. Copy and past Sparky repo to the file.
## sparky
deb http://sparkylinux.org/repo testing main

3. Refresh packages list:
apt-get update
4. Install the Sparky public key:
apt-get install sparky-keyring
or
wget -O - http://sparkylinux.org/repo/sparkylinux.gpg.key | apt-key add -

then refresh package list again:
apt-get update
 
Back to -> FAQ main page
 

How to SparkyLinux CLI

 

For Sparky CLI 3.4 and above go to the newer guide.

 

 

This quick quide will let you know about SparkyLinux CLI up to version 3.2.
All the applications presented above have been preinstalled in SparkyLinux up to version 3.2.
 
I. What does the CLI mean?
Command Line Interface is an interface which works with no a graphic interface.
All the work has to be managed in two ways:
1. having a command
   or
2. using an additional interface working in text mode as well (but much easier)

II. What is the SparkyLinux CLI?
SparkyLinux CLI works as a Live CD/USB distro and features Debian “testing” branch base system with a few tools.
It has a set of drivers for wireless network devices, the same as rest of the SparkyLinux editions have.
Sparky CLI is designed to be used in two cases:
1. to make an installation of Debian testing base and to build own desktop based on it
  or
2. to be used on machines which can’t run the graphics server

Sparky CLI can be used as Live CD/USB system or can be installed on a hard or USB drive.
Live edition of Sparky CLI needs CD media or 1 GB of flash drive.
It requires 2 GB of a hard or USB drive to make full system installation.

III. What does the SparkyLinux CLI have?
1. The base system of Debian testing
2. Set of drivers for wireless network devices (Wifi)
3. Sparky Live Installer, which can be run with command:
sudo sparkylinux-installer
4. Cfdisk – partitioning tool.

Cfdisk

5. Networking tools:
a. Ceni – network manager, can be run with command:
sudo ceni

Ceni

Some of wireless cards needs an exact module to be loaded. It has to be done if Ceni will not find your network device. Check your card type with command:
lspci
 or
lsusb

Load the module (for example: my wifi card works on “zydas” chipset):
modprobe -r zd1211rw

If the command will not display any problem, just load it:

modprobe zd1211rw
Then start Ceni again.

b. Ping
This tool let you check has the connection with internet been done well (any address):

ping -c 2 sparkylinux.org
c. ELinks – web browser.

ELinks

d. CenterIM – instant messenger, it supports the protocols: Gadu-Gadu, Jabber, ICQ, Yahoo!, AOL, IRC and MSN.

CenterIM

e. UFW (Uncomplicated Firewall) lets you configure the firewall in easy way.
The firewall activation (all the commands as root):
ufw enable
To disable it:
ufw disable
The firewall status check in:
ufw status
f.  Wget – download manager, can be run:
wget file-address

g. Midnight Commander – FTP (& SFTP) file transfer. “Left” or “Right” tab -> ftp (sftp) link.
Connect to a server with command:
user-name@ftp.server-address
Then type your password.

MC FTP

h. rTorrent – BitTorrent client, start downloading with command:
rtorrent file.torrent

rTorrent

6. Multimedia
a. Alsamixer – the sound mixer – lets you configure sound devices.
Run it with command:
alsamixer
Usage:
– upper cursor – makes the sound louder
– bottom cursor – makes the sound quieter
– left and right cursor – changing between sound devices
– the “m” key switch on/turn off sound device, “MM” – a device is on, “OO” – a device is off.

Alsamixer

b. MOC (Music on Console) – music player, works with “ncurses” interface.
Run it with command:
mocp

MOC

c. VLC (VideoLAN Client) – multimedia player, it supports many popular audio and video file formats and streaming. VLC can be run in two ways:
cvlc /patch-to-local-or-network-file
or using “ncurses” interface (recommended) – lets you browse local disks and partitions:
vlc -I ncurses
Press “Shift” + “b” to browse files and directories.

VLC

7. Others
a. Midnight Commander – file manager and text editor, can be run with command:
mc
b. Nano – text editor, can be run with command:
nano
c. Htop – an interactive system-monitor process-viewer:
htop
d. Fbi – graphics viewer:
fbi /patch-to-file
e. DF – lets you check how much space a file system is using (%), the file system type, which partition it is on, and its mount point:
df
With “h” option – in MB:
df -h
f. Mount – lets you mount partitions, disk and removable storage devices.
Checking all devices:
fdisk -l
Mounting a partition:
mount -t file_system_type /dev/partition_number /mounting_point
for example.:
mount -t vfat /dev/sda8 /mnt
Type exact file system type (“ext2”, “ext3”, “ext4”, “ntfs-3g”, etc.) instead of “vfat”.
Unmounting partitions:
umount /dev/partition_number
for example.:
umount /dev/sda8

 
Back to -> FAQ main page
 

Advertising