vs220
veles16
ну можете свой конфиг скинуть
У меня нет самбы дома.
avahi и pcmanfm видят компы и с дефолтным конфигом
Дайте вывод

Запущен ли avahi-daemon?
systemctl status avahi-daemon .service
Открыт ли порт?
sudo netstat -anp |grep 5353
avachi и pcmanfm тоже не видят демоны запущены. Да и теперь в самбе дефолтного конфига нет, вообще нет ставил свой старый рабочий, скорее всего проблема в самом программном пакете самба

sudo netstat -anp |grep 5353
sudo: netstat: command not found
нет такой команды
vs220
veles16
но уведомления нет
Скорее всего не запущен notify-osd.

ps aux | grep notify-osd
покажет есть ли в процессах

В кде глюков побольше будет, хотя квин хорош. Удачи в настройке
как его запускать через что?
vs220
veles16
почему в этой ос все через одно место
Ну как бы
veles16
ничего не понял что там написано вставил строки
Да ну бросте есть старые конфиги ни один не работает, причина в не исправности самой программы самба, она не работает что в kde openbox gnome xfce, просто хотел разобраться, но похоже и вы сами не знаете, ну можете свой конфиг скинуть я посмотрю

Самба даже собственный комп не видит такого вообще никогда не было
vs220
Вы вроде на кде перешли не забыли для него настроить
https://wiki.archlinux.org/index.php/Samba#KDE
Нет сейчас самбы проверить.

Запустите авахи с ним проблем нет.
systemctl enable avahi-daemon.service
systemctl start avahi-daemon.service
перезагрузите фм должны быть видны компы, если нет то может точно что блочит

Если честно ничего не понял что там написано вставил строки

server multi channel support = yes
socket options = IPTOS_THROUGHPUT SO_KEEPALIVE
deadtime = 30
use sendfile = Yes
write cache size = 262144
min receivefile size = 16384
aio read size = 16384
aio write size = 16384
nt pipe support = no

load printers = No
printcap name = /dev/null
disable spoolss = Yes
Все перезагрузил результат прежний, avchi тоже запущен и тоже ничего не видит, рядом 2 компа на ubuntu все работает

Блин почему в этой ос все через одно место, за что не возьмись все не работает или работает с такими костылями, ну была нормальная самба сделал все по вики и работает а сейчас

Ради ржаки загрузился с загрузочной флешки линукс минт, самба все видит
vs220
browseable = no на yes
systemctl status nmbd.service
systemctl status smbd.service

Невозможно найти рабочие группы в вашей локальной сети. Возможно, этому препятствует брандмауэр.

nmbd.service - Samba NetBIOS name server
Loaded: loaded (/usr/lib/systemd/system/nmbd.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2018-02-25 19:48:19 MSK; 2min 18s ago
Process: 7566 ExecStart=/usr/bin/nmbd -D (code=exited, status=0/SUCCESS)
Main PID: 7572 (nmbd)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/nmbd.service
└─7572 /usr/bin/nmbd -D

фев 25 19:48:19 VELES systemd[1]: Starting Samba NetBIOS name server...
фев 25 19:48:19 VELES systemd[1]: Started Samba NetBIOS name server.
фев 25 19:48:19 VELES nmbd[7572]: [2018/02/25 19:48:19.256992, 0] ../lib/util/become_daemon.c:124(daemo
фев 25 19:48:19 VELES nmbd[7572]: STATUS=daemon 'nmbd' finished starting up and ready to serve connect
фев 25 19:48:42 VELES nmbd[7572]: [2018/02/25 19:48:42.002949, 0] ../source3/nmbd/nmbd_become_lmb.c:397
фев 25 19:48:42 VELES nmbd[7572]: *****
фев 25 19:48:42 VELES nmbd[7572]:
фев 25 19:48:42 VELES nmbd[7572]: Samba name server VELES is now a local master browser for workgroup
фев 25 19:48:42 VELES nmbd[7572]:
фев 25 19:48:42 VELES nmbd[7572]: *****
● smbd.service - Samba SMB/CIFS server
Loaded: loaded (/usr/lib/systemd/system/smbd.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2018-02-25 19:48:19 MSK; 3min 13s ago
Process: 7574 ExecStart=/usr/bin/smbd -D (code=exited, status=0/SUCCESS)
Main PID: 7575 (smbd)
Tasks: 4 (limit: 4915)
CGroup: /system.slice/smbd.service
├─7575 /usr/bin/smbd -D
├─7579 /usr/bin/smbd -D
├─7580 /usr/bin/smbd -D
└─7581 /usr/bin/smbd -D

фев 25 19:48:19 VELES systemd[1]: Starting Samba SMB/CIFS server...
фев 25 19:48:19 VELES systemd[1]: Started Samba SMB/CIFS server.
фев 25 19:48:19 VELES smbd[7575]: [2018/02/25 19:48:19.325375, 0] ../lib/util/become_daemon.c:124(daemo
фев 25 19:48:19 VELES smbd[7575]: STATUS=daemon 'smbd' finished starting up and ready to serve connect
lines 1-16/16 (END)

Рядом на компе стоит ubuntu все работает, как всегда с арчем все перемудрили
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
#  http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
#  http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

   usershare path = /var/lib/samba/usershare
   usershare max shares = 100
   usershare allow guests = yes
   usershare owner only = yes

# server string is the equivalent of the NT Description field
   server string = VELES

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /usr/local/samba/var/log.%m

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Specifies the Kerberos or Active Directory realm the host is part of
;   realm = MY_REALM

# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
;   passdb backend = tdbsam

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#	Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one	WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no

# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
#[homes]
#   comment = Home Directories
#   browseable = no
#  writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /usr/spool/samba
   browseable = no
# Set public = yes to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = no
;   printable = no
;   write list = @staff

# Other examples.
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

Раньше все делал по арче вики и все работало gvfs-smb установлен конфиг выше
vs220
veles16
+ notify-send ' ' -i notification-audio-volume-medium -h int:value:46 -h string:synchronous:volume
Скрипт нормально отрабатывает. Вы так и не сказали появляется ли надпись?
В терминале запустите , должно появиться уведомление значок с полоской
notify-send ' ' -i notification-audio-volume-medium -h int:value:46 -h string:synchronous:volume

Если уведомление не появляется, попробуйте на
notify-send "test"
Появляется или нет.

Если нет дайте вывод
ps aux | grep notify-osd
pacman -Qs notify-osd
pacman -Qs  libnotify

Звук убавляется, но уведомления нет, самого значка нет, библиотека libnotify установлена, решил проблему кардинально перешел на KDE
BigOrange
а volumeicon чем не устроил?
он всё это умеет
не устраивает
vs220
veles16
нет все норм
То есть надпись test появляется?
Попробуйте скрипт с отладкой запустить и вывод показать
 bash -xv '/home/oleg/bin/vol.sh' up

#!/bin/sh
# created by abarilla
usage="usage: $0 -c {up|down|mute} [-i increment] [-m mixer]"
+ usage='usage: /home/maxim/.scripts/vol.sh -c {up|down|mute} [-i increment] [-m mixer]'
command=
+ command=
increment=5%
+ increment=5%
mixer=Master
+ mixer=Master
while getopts i:m:h o
do case "$o" in
i) increment=$OPTARG;;
m) mixer=$OPTARG;;
h) echo "$usage"; exit 0;;
?) echo "$usage"; exit 0;;
esac
done
+ getopts i:m:h o
shift $(($OPTIND - 1))
+ shift 0
command=$1
+ command=down
if [ "$command" = "" ]; then
echo "usage: $0 {up|down|mute} [increment]"
exit 0;
fi
+ '[' down = '' ']'
display_volume=0
+ display_volume=0
if [ "$command" = "up" ]; then
display_volume=$(amixer set $mixer $increment+ unmute | grep -m 1 "%]" | cut -d "[" -f2|cut -d "%" -f1)
fi
+ '[' down = up ']'
if [ "$command" = "down" ]; then
display_volume=$(amixer set $mixer $increment- unmute | grep -m 1 "%]" | cut -d "[" -f2|cut -d "%" -f1)
fi
+ '[' down = down ']'
++ amixer set Master 5%- unmute
++ grep -m 1 '%]'
++ cut -d '[' -f2
++ cut -d % -f1
+ display_volume=46
icon_name=""
+ icon_name=
if [ "$command" = "mute" ]; then
if amixer get Master | grep "\[on\]"; then
display_volume=0
icon_name="notification-audio-volume-muted"
amixer set $mixer mute
else
display_volume=$(amixer set $mixer unmute | grep -m 1 "%]" | cut -d "[" -f2|cut -d "%" -f1)
fi
fi
+ '[' down = mute ']'
if [ "$icon_name" = "" ]; then
if [ "$display_volume" = "0" ]; then
icon_name="notification-audio-volume-off"
else
if [ "$display_volume" -lt "33" ]; then
icon_name="notification-audio-volume-low"
else
if [ "$display_volume" -lt "67" ]; then
icon_name="notification-audio-volume-medium"
else
icon_name="notification-audio-volume-high"
fi
fi
fi
fi
+ '[' '' = '' ']'
+ '[' 46 = 0 ']'
+ '[' 46 -lt 33 ']'
+ '[' 46 -lt 67 ']'
+ icon_name=notification-audio-volume-medium
notify-send " " -i $icon_name -h int:value:$display_volume -h string:synchronous:volume
+ notify-send ' ' -i notification-audio-volume-medium -h int:value:46 -h string:synchronous:volume
vs220
veles16
а вот самого индикатора нет
В терминале
notify-send "test"

Надпись test появляется, ругани нет?
нет все норм