screenfetch apresentando erro! [RESOLVIDO]

Frank_Supremo
(usa Arch Linux)

Enviado em 10/05/2019 - 19:42h

Boa noite a todos!

Eu instalei o Debian 9.9 xfce em um notebook acer, ai instalei a funcao do screenfetch como root e depois de instalado ao usar o mesmo como usuario normal ele apresenta a informaçao correta como exibe abaixo:

frank@debian:~$ screenfetch
_,met$$$$$gg. frank@debian
,g$$$$$$$$$$$$$$$P. OS: Debian 9.9 stretch
,g$$P"" """Y$$.". Kernel: x86_64 Linux 4.9.0-9-amd64
,$$P' `$$$. Uptime: 10h 54m
',$$P ,ggs. `$$b: Packages: 1793
`d$$' ,$P"' . $$$ Shell: bash 4.4.12
$$P d$' , $$P Resolution: 1366x768
$$: $$. - ,d$$' DE: XFCE
$$\; Y$b._ _,d$P' WM: Xfwm4
Y$$. `.`"Y$$$$P"' WM Theme: Default
`$$b "-.__ GTK Theme: Xfce-dusk [GTK2]
`Y$$ Icon Theme: Tango
`Y$$. Font: Sans 10
`$$b. CPU: Intel Core i5-2310 CPU @ 3.2GHz
`Y$$b. GPU: Mesa DRI Intel(R) Sandybridge Desktop
`"Y$b._ RAM: 1047MiB / 5865MiB
`""""

Mas ao usar o mesmo comando como root, o mesmo apresenta a informação abaixo:

frank@debian:~$ su
Senha:
root@debian:/home/frank# cd Downloads/
root@debian:/home/frank/Downloads# screenfetch
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
_,met$$$$$gg. root@debian
,g$$$$$$$$$$$$$$$P. OS: Debian 9.9 stretch
,g$$P"" """Y$$.". Kernel: x86_64 Linux 4.9.0-9-amd64
,$$P' `$$$. Uptime: 10h 54m
',$$P ,ggs. `$$b: Packages: 1793
`d$$' ,$P"' . $$$ Shell: bash 4.4.12
$$P d$' , $$P Resolution: 1366x768
$$: $$. - ,d$$' DE: XFCE
$$\; Y$b._ _,d$P' WM: Xfwm4
Y$$. `.`"Y$$$$P"' GTK Theme:
`$$b "-.__ CPU: Intel Core i5-2310 CPU @ 3.2GHz
`Y$$ GPU: Mesa DRI Intel(R) Sandybridge Desktop
`Y$$. RAM: 1580MiB / 5865MiB
`$$b.
`Y$$b.
`"Y$b._
`""""

Se eu atualizo não acontece nenhum erro como informar abaixo:

root@debian:/home/frank/Downloads# apt update && apt upgrade
Ign:1 http://deb.debian.org/debian stable InRelease
Obter:2 http://deb.debian.org/debian stable-updates InRelease [91,0 kB]
Atingido:3 http://deb.debian.org/debian-security stable/updates InRelease
Atingido:4 http://deb.debian.org/debian stable Release
Baixados 91,0 kB em 0s (131 kB/s)
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
All packages are up to date.
Lendo listas de pacotes... Pronto
Construindo árvore de dependências
Lendo informação de estado... Pronto
Calculando atualização... Pronto
0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.

E agora o que fazer, alguém pode mim dar uma forca ou uma ajudinha neste criterio.

Grato desde já.

edps
(usa Slackware)

Enviado em 10/05/2019 - 22:32h

Provavelmente porque você está chamando uma ferramenta em modo-cli, mas usando um aplicativo gráfico (sobre o X, Wayland ou outra joça) e usando login de root, o que geralmente não é permitido, para ver se é mesmo isso você pode tentar:

$ xhost +

$ su <entra com a senha de root>

# screenfetch 

* eu prefiro o neofetch.

Se rolar, beleza! basta sair do login de root e fechar o host:

# exit

$ xhost - 

Frank_Supremo
(usa Arch Linux)

Enviado em 10/05/2019 - 22:43h

Boa noite edps!

Eu segui a sua recomendação e veja o resultado abaixo:

frank@debian:~$ xhost +
access control disabled, clients can connect from any host
frank@debian:~$ su
Senha:
root@debian:/home/frank# screenfetch
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
_,met$$$$$gg. root@debian
,g$$$$$$$$$$$$$$$P. OS: Debian 9.9 stretch
,g$$P"" """Y$$.". Kernel: x86_64 Linux 4.9.0-9-amd64
,$$P' `$$$. Uptime: 23h 22m
',$$P ,ggs. `$$b: Packages: 1800
`d$$' ,$P"' . $$$ Shell: bash 4.4.12
$$P d$' , $$P Resolution: 1366x768
$$: $$. - ,d$$' DE: XFCE
$$\; Y$b._ _,d$P' WM: Xfwm4
Y$$. `.`"Y$$$$P"' GTK Theme:
`$$b "-.__ CPU: Intel Core i5-2310 CPU @ 3.2GHz
`Y$$ GPU: Mesa DRI Intel(R) Sandybridge Desktop
`Y$$. RAM: 1251MiB / 5865MiB
`$$b.
`Y$$b.
`"Y$b._
`""""

root@debian:/home/frank# exit
exit
frank@debian:~$ xhost -
access control enabled, only authorized clients can connect
frank@debian:~$ su
Senha:
root@debian:/home/frank# screenfetch
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
_,met$$$$$gg. root@debian
,g$$$$$$$$$$$$$$$P. OS: Debian 9.9 stretch
,g$$P"" """Y$$.". Kernel: x86_64 Linux 4.9.0-9-amd64
,$$P' `$$$. Uptime: 23h 23m
',$$P ,ggs. `$$b: Packages: 1800
`d$$' ,$P"' . $$$ Shell: bash 4.4.12
$$P d$' , $$P Resolution: 1366x768
$$: $$. - ,d$$' DE: XFCE
$$\; Y$b._ _,d$P' WM: Xfwm4
Y$$. `.`"Y$$$$P"' GTK Theme:
`$$b "-.__ CPU: Intel Core i5-2310 CPU @ 3.2GHz
`Y$$ GPU: Mesa DRI Intel(R) Sandybridge Desktop
`Y$$. RAM: 1262MiB / 5865MiB
`$$b.
`Y$$b.
`"Y$b._
`""""

root@debian:/home/frank# exit
exit
frank@debian:~$

edps
(usa Slackware)

Enviado em 10/05/2019 - 22:49h

Bom ao que parece é coisa do XFCE mesmo, verifique se o pacote está instalado com:

$ dpkg -l | grep libxconf

O pacote chama-se na Stable, Testing e Unstable: libxfconf-0-2 com a mesma versão, a 4.12.1-1, no Jessie/OldStable é a 4.10.0-3

Frank_Supremo
(usa Arch Linux)

Enviado em 10/05/2019 - 22:57h

Segue resultado da sua recomendação:

frank@debian:~$ dpkg -l | grep libxconf
frank@debian:~$ su
Senha:
root@debian:/home/frank# screenfetch
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
[[ ! ]] Failed to init libxfconf: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken..
_,met$$$$$gg. root@debian
,g$$$$$$$$$$$$$$$P. OS: Debian 9.9 stretch
,g$$P"" """Y$$.". Kernel: x86_64 Linux 4.9.0-9-amd64
,$$P' `$$$. Uptime: 23h 38m
',$$P ,ggs. `$$b: Packages: 1800
`d$$' ,$P"' . $$$ Shell: bash 4.4.12
$$P d$' , $$P Resolution: 1366x768
$$: $$. - ,d$$' DE: XFCE
$$\; Y$b._ _,d$P' WM: Xfwm4
Y$$. `.`"Y$$$$P"' GTK Theme:
`$$b "-.__ CPU: Intel Core i5-2310 CPU @ 3.2GHz
`Y$$ GPU: Mesa DRI Intel(R) Sandybridge Desktop
`Y$$. RAM: 1318MiB / 5865MiB
`$$b.
`Y$$b.
`"Y$b._
`""""

root@debian:/home/frank# dpkg -l | grep libxconf

edps
(usa Slackware)

Enviado em 10/05/2019 - 22:58h

Sei que o pedido é referente ao screenfetch, mas porque não tenta o neofetch:

$ sudo apt-get update

$ sudo apt-get install neofetch 

Acho esse mais completo, tem um post antigo no meu blog:

https://edpsblog.wordpress.com/2017/07/09/dica-informacoes-do-sistema-com-neofetch/

Outro que acho legal é o inxi:

* dica jurássica no VOL:

https://www.vivaolinux.com.br/dica/Obtendo-informacoes-do-sistema-com-o-script-INXI/

$ sudo apt-get update

$ sudo apt-get install inxi 

Exemplo:

$ inxi -Fxz

System:    Host: gentoo Kernel: 5.0.12-gentoo x86_64 bits: 64 gcc: 8.2.0

           Desktop: Openbox 3.6.1 Distro: Gentoo Base System release 2.6

Machine:   Device: desktop Mobo: ASUSTeK model: PRIME H310M-E v: Rev X.0x serial: N/A

           UEFI: American Megatrends v: 0223 date: 02/27/2018

CPU:       6 core Intel Core i5-8400 (-MCP-) 

           arch: Skylake rev.10 cache: 9216 KB

           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 33696

           clock speeds: max: 4000 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz

           4: 800 MHz 5: 800 MHz 6: 800 MHz

Graphics:  Card: Intel UHD Graphics 630 (Desktop) bus-ID: 00:02.0

           Display Server: X.Org 1.20.4 driver: modesetting

           Resolution: 1920x1080@60.00hz

           OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2)

           version: 4.5 Mesa 18.3.6 Direct Render: Yes

Audio:     Card Intel Cannon Lake PCH cAVS

           driver: snd_hda_intel bus-ID: 00:1f.3

           Sound: Advanced Linux Sound Architecture v: k5.0.12-gentoo

Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller

           driver: r8169 port: 3000 bus-ID: 02:00.0

           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>

Drives:    HDD Total Size: 2660.6GB (35.8% used)

           ID-1: /dev/sda model: ST500DM002 size: 500.1GB

           ID-2: /dev/sdc model: ST1000DM010 size: 1000.2GB

           ID-3: /dev/sdb model: SAMSUNG_HD161GJ size: 160.0GB

           ID-4: USB /dev/sdd model: 025_HN size: 1000.2GB

Partition: ID-1: / size: 99G used: 14G (15%) fs: ext4 dev: /dev/root

           ID-2: swap-1 size: 2.77GB used: 0.00GB (0%)

           fs: swap dev: /dev/zram0

           ID-3: swap-2 size: 2.77GB used: 0.00GB (0%)

           fs: swap dev: /dev/zram1

           ID-4: swap-3 size: 2.77GB used: 0.00GB (0%)

           fs: swap dev: /dev/zram2

           ID-5: swap-4 size: 2.77GB used: 0.00GB (0%)

           fs: swap dev: /dev/zram3

           ID-6: swap-5 size: 2.77GB used: 0.00GB (0%)

           fs: swap dev: /dev/zram4

           ID-7: swap-6 size: 2.77GB used: 0.00GB (0%)

           fs: swap dev: /dev/zram5

RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present

Sensors:   System Temperatures: cpu: 34.0C mobo: N/A

           Fan Speeds (in rpm): cpu: 0

Info:      Processes: 223 Uptime: 58 min Memory: 1875.7/15872.1MB

           Init: SysVinit rc: OpenRC runlevel: default Gcc sys: 8.2.0

 

edps
(usa Slackware)

Enviado em 10/05/2019 - 22:59h

Ao que parece o pacote não está instalado, tente então:

$ sudo apt-get install xfconf libxfconf-0-2 

Frank_Supremo
(usa Arch Linux)

Enviado em 10/05/2019 - 23:04h

Ola eu removi o screenfetch com o comando

# apt remove screenfetch

e instalei o neofetch como voce mim recomendou e o resultado é esse abaixo:

root@debian:/home/frank/Downloads# neofetch
_,met$$$$$gg. root@debian
,g$$$$$$$$$$$$$$$P. -----------
,g$$P" """Y$$.". OS: Debian GNU/Linux 9.9 (stretch) x86_64
,$$P' `$$$. Kernel: 4.9.0-9-amd64
',$$P ,ggs. `$$b: Uptime: 23 hours, 43 minutes
`d$$' ,$P"' . $$$ Packages: 1800
$$P d$' , $$P Shell: bash 4.4.12
$$: $$. - ,d$$' Resolution: 1366x768
$$; Y$b._ _,d$P' DE: XFCE
Y$$. `.`"Y$$$$P"' WM: Xfwm4
`$$b "-.__ Theme: Adwaita [GTK3]
`Y$$ Icons: Adwaita [GTK3]
`Y$$. CPU: Intel i5-2310 (4) @ 3.2GHz
`$$b. GPU: Intel Integrated Graphics
`Y$$b. Memory: 1398MB / 5865MB
`"Y$b._
`""" ████████████████████████


root@debian:/home/frank/Downloads# exit
exit
frank@debian:~$ neofetch
_,met$$$$$gg. frank@debian
,g$$$$$$$$$$$$$$$P. ------------
,g$$P" """Y$$.". OS: Debian GNU/Linux 9.9 (stretch) x86_64
,$$P' `$$$. Kernel: 4.9.0-9-amd64
',$$P ,ggs. `$$b: Uptime: 23 hours, 43 minutes
`d$$' ,$P"' . $$$ Packages: 1800
$$P d$' , $$P Shell: bash 4.4.12
$$: $$. - ,d$$' Resolution: 1366x768
$$; Y$b._ _,d$P' DE: XFCE
Y$$. `.`"Y$$$$P"' WM: Xfwm4
`$$b "-.__ WM Theme: Default
`Y$$ Theme: Xfce-dusk [GTK2], Adwaita [GTK3]
`Y$$. Icons: Tango [GTK2], Adwaita [GTK3]
`$$b. Terminal: xfce4-terminal
`Y$$b. CPU: Intel i5-2310 (4) @ 3.2GHz
`"Y$b._ GPU: Intel Integrated Graphics
`""" Memory: 1397MB / 5865MB

████████████████████████


frank@debian:~$

Obtive sucesso, obrigado.

edps
(usa Slackware)

Enviado em 10/05/2019 - 23:06h

É não foi um suceeeesso, mas serve.

Mas se quiser tentar, fiquei curioso e fui checar no pai dos burros (o google kkk) e lá me disseram que parece ser problema no su e que se você executá-lo com a opção --login ou pura e simplesmente -l, rola:

https://forum.manjaro.org/t/terminal-su-failed-to-init-libxfconf/43724

Logo, se quiser tentar:

$ sudo apt-get install screenfetch

$ su -l

# screenfetch

# exit 

Frank_Supremo
(usa Arch Linux)

Enviado em 10/05/2019 - 23:12h

Eu acabo de testa e funcionar, veja abaixo o resultado:

frank@debian:~$ su -l
Senha:
root@debian:~# screenfetch
_,met$$$$$gg. root@debian
,g$$$$$$$$$$$$$$$P. OS: Debian 9.9 stretch
,g$$P"" """Y$$.". Kernel: x86_64 Linux 4.9.0-9-amd64
,$$P' `$$$. Uptime: 23h 53m
',$$P ,ggs. `$$b: Packages: 1801
`d$$' ,$P"' . $$$ Shell: su
$$P d$' , $$P Resolution: 1366x768
$$: $$. - ,d$$' WM: Xfwm4
$$\; Y$b._ _,d$P' CPU: Intel Core i5-2310 CPU @ 3.2GHz
Y$$. `.`"Y$$$$P"' GPU: Mesa DRI Intel(R) Sandybridge Desktop
`$$b "-.__ RAM: 1420MiB / 5865MiB
`Y$$
`Y$$.
`$$b.
`Y$$b.
`"Y$b._
`""""

root@debian:~#

Frank_Supremo
(usa Arch Linux)

Enviado em 10/05/2019 - 23:13h

Obrigado mesmo vou ficar com o neofetch, porque parece esta mais completo!
Só tenho mas uma duvida este recurso funcionar em todas as ditribuiçoes Linux?