Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1 2

#26 Other Issues » [SOLVED] <Ascii> Devuan Version » 2017-12-03 16:22:27

makh
Replies: 3

Hi

I run to get:

# cat /etc/devuan_version && cat /etc/debian_version
jessie
9.2

It doesnt return ascii.

Thankyou

#27 Devuan » [Closed] Devuan Repository ~ Suggestion » 2017-11-26 23:14:12

makh
Replies: 0

Hi

Theres a quite a good compression ratio of zipping of text files.

If the repository files are zipped then, the updating would take much smaller time, on both ends: server & client.
Plus ... lower bandwidth usage, and lesser network traffic.

Like right now:
http://packages.devuan.org/merged/dists/2.0/

ls -hls

112K -rw-r--r-- 1 user users 111K Nov 27 04:11 Release
 24K -rw-r--r-- 1 user users  22K Nov 27 04:11 Release.xz

Thankyou

Edit 2: The following download is too much consuming (29.4MB), today on 19-Dec-2017:

# apt update
Ign:1 http://linux.teamviewer.com/deb stable InRelease                         
Ign:2 http://linux.teamviewer.com/deb preview InRelease                        
Hit:3 http://linux.teamviewer.com/deb stable Release                           
Get:5 http://packages.devuan.org/merged ascii InRelease [113 kB]               
Get:6 http://auto.mirror.devuan.org/merged ascii InRelease [113 kB]          
Hit:7 http://linux.teamviewer.com/deb preview Release                          
Get:9 http://auto.mirror.devuan.org/merged ascii-updates InRelease [113 kB]    
Get:10 http://packages.devuan.org/merged ascii/main amd64 Packages [7136 kB]
Get:11 http://auto.mirror.devuan.org/merged ascii-security InRelease [112 kB]  
Get:12 http://auto.mirror.devuan.org/merged ascii/main amd64 Packages [7136 kB]
Get:13 http://auto.mirror.devuan.org/merged ascii/main i386 Packages [7116 kB] 
Get:14 http://packages.devuan.org/merged ascii/main i386 Packages [7116 kB]    
Get:15 http://auto.mirror.devuan.org/merged ascii-security/main amd64 Packages [226 kB]
Get:16 http://auto.mirror.devuan.org/merged ascii-security/main i386 Packages [226 kB]
Fetched 29.4 MB in 2min 41s (182 kB/s)

#28 Re: Desktop and Multimedia » [SOLVED] <Ascii> Conky ~ Errors in configuration file » 2017-11-25 22:06:13

makh

Thankyou Sir!

But I did forgot to look into: /etc/conky

Strangely, the versions are same, but Debian didnt made any issues on the use of the older configuration technique.

#29 Desktop and Multimedia » [SOLVED] <Ascii> Conky ~ Errors in configuration file » 2017-11-25 19:12:27

makh
Replies: 2

Hi

I have this configuration file running smooth on Stretch:

# For Xfce only, inside Virtualbox
#
# white backgoung with black fonts or colored

alignment top_right
background no
border_width 2
cpu_avg_samples 4
default_color black
default_outline_color tango
default_shade_color white
draw_borders yes
draw_graph_borders yes
draw_outline no
draw_shades no
use_xft yes
xftfont DejaVu Sans Mono:bold:size=10:black
gap_x 5
gap_y 50
# Play
minimum_size 120 483
maximum_width 140
net_avg_samples 1
no_buffers yes
out_to_console no
out_to_stderr no
extra_newline no
own_window yes
own_window_class Conky
own_window_type override
stippled_borders 0
uppercase no
use_spacer none
show_graph_scale no
show_graph_range no

double_buffer yes

# Opacity yes/no:
own_window_transparent no

own_window_colour light yellow

update_interval 1.0
update_interval_on_battery 4.0

TEXT
${color navy blue}   Remember
#
#
${color tango}uptime: ${color navy blue}$uptime_short 
#
#
${color }${execi 3600 uname -r}
#
#
$color${font Goudy Bookletter 1911:style=Bold:size=9}SYSTEM${font} ${hr 3}
#
#
${color}Cpu-1: ${color blue}${if_match ${cpu cpu1}>80}${color red}$endif${cpu cpu1}% ${color magneta}${freq_g cpu1}GHz
${color}Cpu-2: ${color blue}${if_match ${cpu cpu2}>80}${color red}$endif${cpu cpu2}% ${color magneta}${freq_g cpu2}GHz
${color}Cpu-3: ${color blue}${if_match ${cpu cpu3}>80}${color red}$endif${cpu cpu3}% ${color magneta}${freq_g cpu3}GHz
${color}Cpu-4: ${color blue}${if_match ${cpu cpu4}>80}${color red}$endif${cpu cpu4}% ${color magneta}${freq_g cpu4}GHz
${color }${hr 3}
#
#
${color}Mem: ${color magneta}$mem${color blue}/$memmax
#
#
${color}Swap:${color magneta} $swap${color blue}/$swapmax
#
#
${color }Procs/Run:${color blue}$processes${color }/${color magneta}$running_processes
${color }${hr 3}
#
#
${color navy blue}\
CPU %  PROCESS
${font Goudy Bookletter 1911:style=Bold:size=8}${color red}\
${top cpu 1}  ${top name 1}
${color tango}\
${top cpu 2}  ${top name 2}
${top cpu 3}  ${top name 3}
${top cpu 4}  ${top name 4}
${color blue}\
${top cpu 5}  ${top name 5}
${top cpu 6}  ${top name 6}
#${top cpu 7}  ${top name 7}
#${top cpu 8}  ${top name 8}
#${top cpu 9}  ${top name 9}
${color }${hr 3}
#
#
${color }MEMORY:
${color blue}${top_mem mem 1}  ${top_mem name 1}
${top_mem mem 2}  ${top_mem name 2}
${top_mem mem 3}  ${top_mem name 3}
${top_mem mem 4}  ${top_mem name 4}
${top_mem mem 4}  ${top_mem name 4}
${color }${hr 3}
#
#
${font arial:size=10:bold}${color }FILE SYSTEMS (~free):${font arial:size=10}
 ${color blue}ROOT ${color magneta}${fs_used /}${color }~${fs_free /}
${color }${hr 3}
#
#
${font arial:size=10:bold}${color}DISK WRITE/READ ${font Bullets:size=8:bold}
 ${color blue}sda: ${color dark tango}${diskio_write sda}/${diskio_read sda}
${if_existing /dev/cdrom}\
 ${color navy blue}cd:  ${color dark red}${font Bullets:size=8:bold}\
${diskio_write sr0}/${diskio_read sr0}$endif 
${if_existing /dev/sdb}\
 ${color blue}sdb: ${color dark tango}${font Bullets:size=8:bold}${diskio_write 
sdb}/${diskio_read sdb}$endif\

Dejavu fonts are installed. The versions of conky are same.

Conky doesnt execute, giving following non stop issues:

myuser@vmdev1r1:~$ conky -c 30_conky.conf 

conky: Syntax error (30_conky.conf:1: '=' expected near 'top_right') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: can't parse X color 'tango'
conky: desktop window (2e00003) is subwindow of root window (281)
conky: window type - override
conky: drawing to created window (0x3800001)
conky: drawing to double buffer
conky: can't parse X color 'tango'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'tango'
conky: can't parse X color 'magneta'
conky: can't parse X color 'dark tango'
conky: can't parse X color 'dark tango'
conky: diskio device 'sdb' does not exist
conky: diskio device 'sdb' does not exist
conky: obj->data.i 3 info.cpu_count 2
conky: attempting to use more CPUs than you have!
myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:2: '=' expected near 'no') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:2: '}' expected (to close '{' at line 1) near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf &
[1] 7898

myuser@vmdev1r1:~$ conky: Syntax error (30_conky.conf:2: '=' expected near 'no') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:2: '}' expected (to close '{' at line 1) near '='

[1]+  Exit 1                  conky -c 30_conky.conf

myuser@vmdev1r1:~$ conky -c 30_conky.conf &
[1] 7976

myuser@vmdev1r1:~$ conky: Syntax error (30_conky.conf:1: '=' expected near 'top_right') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: desktop window (2e00003) is subwindow of root window (281)
conky: window type - override
conky: drawing to created window (0x3800001)
conky: drawing to double buffer
conky: can't parse X color 'tango'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'tango'
conky: can't parse X color 'magneta'
conky: can't parse X color 'dark tango'
conky: can't parse X color 'dark tango'
conky: diskio device 'sdb' does not exist
conky: diskio device 'sdb' does not exist
conky: obj->data.i 3 info.cpu_count 2
conky: attempting to use more CPUs than you have!
conky -c 30_conky.conf &
[2] 8002
[1]   Exit 1                  conky -c 30_conky.conf

myuser@vmdev1r1:~$ conky: Syntax error (30_conky.conf:2: '=' expected near 'no') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: Invalid value '=top_right' for setting 'alignment'. Valid values are: 'top_left', 'top_right', 'top_middle', 'bottom_left', 'bottom_right', 'bottom_middle', 'middle_left', 'middle_middle', 'middle_right', 'tl', 'tr', 'tm', 'bl', 'br', 'bm', 'ml', 'mm', 'mr', 'none'.
conky: desktop window (2e00003) is subwindow of root window (281)
conky: window type - override
conky: drawing to created window (0x3800001)
conky: drawing to double buffer
conky: can't parse X color 'tango'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'tango'
conky: can't parse X color 'magneta'
conky: can't parse X color 'dark tango'
conky: can't parse X color 'dark tango'
conky: diskio device 'sdb' does not exist
conky: diskio device 'sdb' does not exist
conky: obj->data.i 3 info.cpu_count 2
conky: attempting to use more CPUs than you have!

[2]+  Exit 1                  conky -c 30_conky.conf

myuser@vmdev1r1:~$ conky -c 30_conky.conf  
conky: Syntax error (30_conky.conf:3: '=' expected near '2') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: Invalid value '=top_right' for setting 'alignment'. Valid values are: 'top_left', 'top_right', 'top_middle', 'bottom_left', 'bottom_right', 'bottom_middle', 'middle_left', 'middle_middle', 'middle_right', 'tl', 'tr', 'tm', 'bl', 'br', 'bm', 'ml', 'mm', 'mr', 'none'.
conky: desktop window (2e00003) is subwindow of root window (281)
conky: window type - override
conky: drawing to created window (0x3800001)
conky: drawing to double buffer
conky: can't parse X color 'tango'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'magneta'
conky: can't parse X color 'tango'
conky: can't parse X color 'magneta'
conky: can't parse X color 'dark tango'
conky: can't parse X color 'dark tango'
conky: diskio device 'sdb' does not exist
conky: diskio device 'sdb' does not exist
conky: obj->data.i 3 info.cpu_count 2
conky: attempting to use more CPUs than you have!

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:8: '=' expected near 'yes') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:13: '=' expected near 'DejaVu') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:13: '=' expected near 'Mono') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:13: function arguments expected near ':') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:13: function arguments expected near ':') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:13: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:13: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:13: function arguments expected near ':') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:14: unexpected symbol near '=') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:14: unexpected symbol near '10') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:18: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:18: '<name>' expected near '120') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:18: unexpected symbol near '483') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:18: malformed number near '120x') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:18: '=' expected near '120') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:18: unexpected symbol near '483') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:34: '=' expected near 'yes') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:36: unexpected symbol near '#') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:36: '=' expected near 'no') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:40: '=' expected near 'update_interval') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:40: '=' expected near 'update_interval') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:40: '=' expected near 'update_interval') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:40: '=' expected near 'update_interval') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:40: '=' expected near 'update_interval') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:40: '=' expected near 'TEXT') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

myuser@vmdev1r1:~$ conky -c 30_conky.conf 
conky: Syntax error (30_conky.conf:41: unexpected symbol near '$') while reading config file. 
conky: Assuming it's in old syntax and attempting conversion.
conky: [string "..."]:151: [string "converted config"]:4: unexpected symbol near '='

The last error came with following changes:

alignment =top_right
background =no
border_width =2
cpu_avg_samples =4
default_color =black
default_outline_color =red
default_shade_color =white
draw_borders =yes
draw_graph_borders =yes
draw_outline =no
draw_shades =no
use_xft =yes
xftfont =Arial
xftfont =fontsize10
xftfont =bold
gap_x =5
gap_y =50
minimum_size =120,483
maximum_width =140
net_avg_samples =1
no_buffers =yes
out_to_console =no
out_to_stderr =no
extra_newline =no
own_window =yes
own_window_class =Conky
own_window_type =override
stippled_borders =0
uppercase =no
use_spacer =none
show_graph_scale =no
show_graph_range =no

double_buffer =yes

own_window_transparent =no

own_window_colour =light yellow

=TEXT
${color navy blue}   Rem
#
#
${color tango}uptime: ${color navy blue}$uptime_short 
#
#
${color }${execi 3600 uname -r}
#
#
$color${font Goudy Bookletter 1911:style=Bold:size=9}SYSTEM${font} ${hr 3}
#
#
${color}Cpu-1: ${color blue}${if_match ${cpu cpu1}>80}${color red}$endif${cpu cpu1}% ${color magneta}${freq_g cpu1}GHz
${color}Cpu-2: ${color blue}${if_match ${cpu cpu2}>80}${color red}$endif${cpu cpu2}% ${color magneta}${freq_g cpu2}GHz
${color}Cpu-3: ${color blue}${if_match ${cpu cpu3}>80}${color red}$endif${cpu cpu3}% ${color magneta}${freq_g cpu3}GHz
${color}Cpu-4: ${color blue}${if_match ${cpu cpu4}>80}${color red}$endif${cpu cpu4}% ${color magneta}${freq_g cpu4}GHz
${color }${hr 3}
#
#
${color}Mem: ${color magneta}$mem${color blue}/$memmax
#
#
${color}Swap:${color magneta} $swap${color blue}/$swapmax
#
#
${color }Procs/Run:${color blue}$processes${color }/${color magneta}$running_processes
${color }${hr 3}
#
#
${color navy blue}\
CPU %  PROCESS
${font Goudy Bookletter 1911:style=Bold:size=8}${color red}\
${top cpu 1}  ${top name 1}
${color tango}\
${top cpu 2}  ${top name 2}
${top cpu 3}  ${top name 3}
${top cpu 4}  ${top name 4}
${color blue}\
${top cpu 5}  ${top name 5}
${top cpu 6}  ${top name 6}
#${top cpu 7}  ${top name 7}
#${top cpu 8}  ${top name 8}
#${top cpu 9}  ${top name 9}
${color }${hr 3}
#
#
${color }MEMORY:
${color blue}${top_mem mem 1}  ${top_mem name 1}
${top_mem mem 2}  ${top_mem name 2}
${top_mem mem 3}  ${top_mem name 3}
${top_mem mem 4}  ${top_mem name 4}
${top_mem mem 4}  ${top_mem name 4}
${color }${hr 3}
#
#
${font arial:size=10:bold}${color }FILE SYSTEMS (~free):${font arial:size=10}
 ${color blue}ROOT ${color magneta}${fs_used /}${color }~${fs_free /}
${color }${hr 3}
#
#
${font arial:size=10:bold}${color}DISK WRITE/READ ${font Bullets:size=8:bold}
 ${color blue}sda: ${color dark tango}${diskio_write sda}/${diskio_read sda}
${if_existing /dev/cdrom}\
 ${color navy blue}cd:  ${color dark red}${font Bullets:size=8:bold}\
${diskio_write sr0}/${diskio_read sr0}$endif 
${if_existing /dev/sdb}\
 ${color blue}sdb: ${color dark tango}${font Bullets:size=8:bold}${diskio_write 
sdb}/${diskio_read sdb}$endif\

But this changed and reformatted code doesnt seems right, to me.

Kindly advise.

Thankyou

#30 Re: Other Issues » [SOLVED] <Ascii> xfce4-terminal; No Scroll bar » 2017-11-22 06:29:33

makh

Hi

Checking into:

Applications > Settings > Appearance > Style

I solved it by choosing: 

Crux instead of "Clearlooks-Phenix-Purpy"

Strange there is no side bar for terminal in "crux", rest were working.

Thankyou

#31 Re: Other Issues » [SOLVED] <Ascii> xfce4-terminal; No Scroll bar » 2017-11-21 03:42:47

makh

Hi

Can anyone confirm, this issue is on his xfce also?

#32 Other Issues » [SOLVED] <Ascii> xfce4-terminal; No Scroll bar » 2017-11-20 15:58:06

makh
Replies: 7

Hi

Theres no scroll bar, to see the previous terminal display.

Kindly any fix?

Thankyou

#33 Re: Hardware & System Configuration » Sound disappeared after "touching" Audio Mixer panel » 2017-11-20 14:57:26

makh

Hi

As an additional cross check, always use unmute all options in alsamixer, if something is not working.

#34 Re: Desktop and Multimedia » (SOLVED) [Jessie] System keeping - how to undo package break of xfce4 » 2017-11-13 11:50:44

makh

Thankyou Sir!

#35 Re: Desktop and Multimedia » (SOLVED) [Jessie] System keeping - how to undo package break of xfce4 » 2017-11-12 04:48:54

makh

Hi

cat /var/log/apt/history.log
My try:

Start-Date: 2017-11-07  21:00:37
Commandline: apt remove hplip hplip-data quodlibet xfburn xsane xsane-common
Remove: hplip:amd64 (3.14.6-1+deb8u1), xfburn:amd64 (0.5.2-1), xsane-common:amd64 (0.998-6), printer-driver-postscript-hp:amd64 (3.14.6-1+deb8u1), xsane:amd64 (0.998-6+b1), quodlibet:amd64 (3.2.2-1), hplip-data:amd64 (3.14.6-1+deb8u1), xfce4-goodies:amd64 (4.10)
End-Date: 2017-11-07  21:00:51

Start-Date: 2017-11-07  21:07:02
Commandline: apt install hplip hplip-data quodlibet xfburn xsane xsane-common
Install: hplip:amd64 (3.14.6-1+deb8u1), xfburn:amd64 (0.5.2-1), xsane-common:amd64 (0.998-6), printer-driver-postscript-hp:amd64 (3.14.6-1+deb8u1, automatic), xsane:amd64 (0.998-6+b1), quodlibet:amd64 (3.2.2-1), hplip-data:amd64 (3.14.6-1+deb8u1)
End-Date: 2017-11-07  21:07:12

Start-Date: 2017-11-11  23:39:37
Commandline: apt-get install --reinstall xfce4
Reinstall: xfce4:amd64 (4.10.1)
End-Date: 2017-11-11  23:39:40

Start-Date: 2017-11-12  09:43:56
Commandline: apt-get install --reinstall xfce4 hplip hplip-data quodlibet xfburn xsane xsane-common
Reinstall: hplip:amd64 (3.14.6-1+deb8u1), xfburn:amd64 (0.5.2-1), xsane-common:amd64 (0.998-6), xfce4:amd64 (4.10.1), xsane:amd64 (0.998-6+b1), quodlibet:amd64 (3.2.2-1), hplip-data:amd64 (3.14.6-1+deb8u1)
End-Date: 2017-11-12  09:44:08

But still I get:

# apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and are no longer required:
  hddtemp libxfcegui4-4 ristretto xfce4-artwork xfce4-battery-plugin
  xfce4-clipman xfce4-clipman-plugin xfce4-cpufreq-plugin
  xfce4-cpugraph-plugin xfce4-datetime-plugin xfce4-dict xfce4-diskperf-plugin
  xfce4-fsguard-plugin xfce4-genmon-plugin xfce4-mailwatch-plugin
  xfce4-mount-plugin xfce4-netload-plugin xfce4-notes xfce4-notes-plugin
  xfce4-places-plugin xfce4-quicklauncher-plugin xfce4-screenshooter
  xfce4-sensors-plugin xfce4-smartbookmark-plugin xfce4-systemload-plugin
  xfce4-taskmanager xfce4-timer-plugin xfce4-verve-plugin xfce4-wavelan-plugin
  xfce4-weather-plugin xfce4-xkb-plugin

#36 Desktop and Multimedia » (SOLVED) [Jessie] System keeping - how to undo package break of xfce4 » 2017-11-11 07:27:53

makh
Replies: 4

Hi

I made a mistake trying to make my OS smaller. So I removed a few packages from the dependencies of meta package xfce4. But now I am getting this dependency issue, even though I reinstalled the earlier removed packages:

Calculating upgrade... The following packages were automatically installed and are no longer required:
  hddtemp libxfcegui4-4 ristretto xfce4-artwork xfce4-battery-plugin
  xfce4-clipman xfce4-clipman-plugin xfce4-cpufreq-plugin
  xfce4-cpugraph-plugin xfce4-datetime-plugin xfce4-dict xfce4-diskperf-plugin
  xfce4-fsguard-plugin xfce4-genmon-plugin xfce4-mailwatch-plugin
  xfce4-mount-plugin xfce4-netload-plugin xfce4-notes xfce4-notes-plugin
  xfce4-places-plugin xfce4-quicklauncher-plugin xfce4-screenshooter
  xfce4-sensors-plugin xfce4-smartbookmark-plugin xfce4-systemload-plugin
  xfce4-taskmanager xfce4-timer-plugin xfce4-verve-plugin xfce4-wavelan-plugin
  xfce4-weather-plugin xfce4-xkb-plugin
Use 'apt-get autoremove' to remove them.

But I want to keep these packages. ... Kindly guide.

Thankyou.

#37 Other Issues » [CLOSED] reportbug <Ascii> ~ cannot access the server » 2017-11-07 03:59:42

makh
Replies: 0

Hi

Please inform, is reportbug working in ascii.

Querying Devuan BTS for reports on xfce4-terminal (source)...
Unable to connect to Devuan BTS (error: "NoNetwork()"); continue [y|N|?]?

I have same settings for the debian stretch, and reportbug works there.

Thankyou.

#38 Re: Forum Feedback » [Discussed] Direct Search - site feature » 2017-11-06 13:09:30

makh

Thanks, for adding in the todo list. smile

#39 Forum Feedback » [Discussed] Direct Search - site feature » 2017-11-06 06:23:09

makh
Replies: 4

Hi

Dear Forum Admin

Usually all sites have a direct search option, here it is missing. First one has to click to go to next page and then use search options, which is more akin to be an advance search.

Kindly provide a small search right on top right, so it is fastly accessible.

Thankyou

#40 Re: Forum Feedback » [Discussed] Documentation Section » 2017-11-05 05:40:05

makh
fsmithred wrote:

.....

Right now Debian documentation and wiki are going slow, and not updated, even with 9.2 release.

2. It means that each Devuan will be actually following the release of each Debian, with same kernel version and packages, as is?

Thankyou

#41 Re: Forum Feedback » [Discussed] Documentation Section » 2017-11-04 21:08:43

makh

Hi

I assume; more than 60% would be a mere copy paste of debian jessie for stable.

For ascii, I cannot say, as the kernel has not yet been finalized, perhaps it will be 4.14 LTS ...

Thankyou

#42 Re: Other Issues » [Solved] Virtualbox guest additions - not working (Ascii) » 2017-11-04 17:38:58

makh

Thanks

#43 Re: Forum Feedback » [Discussed] Documentation Section » 2017-11-04 17:37:19

makh
golinux wrote:

...

Hi

I am suggesting to have these sub sections, in text format, in the Documents section, along with how tos:

1. Documentation
2. Wiki
3. Handbook
4. How tos

where members can contribute to devuan.

Thanks

Edit 1: Adding the name feature would be fun to use, if the forum admin allows. I hope server can manage some more space.

#44 Forum Feedback » [Discussed] Documentation Section » 2017-11-04 15:01:32

makh
Replies: 12

Hi

I tried to google, but didnt quite get some things like:

1. Documentation
2. Wiki
3. Handbook

except for:
https://dev1galaxy.org/viewtopic.php?id=1499

It shall be really kind of the admins of this forum to include these three sections under the Documentation, even as under construction or under edit (pointing to existing debian ones) or let the forum users contribute. I dont assume that it may be an overload for this website.

Just a suggestion...

Thankyou

#45 Re: Other Issues » [Solved] Virtualbox guest additions - not working (Ascii) » 2017-11-04 07:42:57

makh

Hello

But the version is not compatible to virtualbox 5.2. Any ways ...

Thankyou all for your kind help.

#46 Re: Other Issues » [Solved] Virtualbox guest additions - not working (Ascii) » 2017-11-04 02:24:18

makh

Hi @fog

cat /etc/apt/sources.list

## package repositories

# Compatible Debian 9:
#
deb http://auto.mirror.devuan.org/merged ascii main contrib non-free
deb http://auto.mirror.devuan.org/merged ascii-updates main contrib non-free
deb http://auto.mirror.devuan.org/merged ascii-security main contrib non-free

# Devuan repositories
deb http://packages.devuan.org/merged ascii main non-free contrib
#deb-src http://packages.devuan.org/merged ascii main non-free contrib

apt search virtualbox
shows no package for virtual box

also see:
http://devuanpackages.viralds.it/search … virtualbox
No ascii package.

Thankyou

#47 Re: Other Issues » [Solved] Virtualbox guest additions - not working (Ascii) » 2017-11-03 13:06:35

makh

Hi

I actually cloned the jessie, then upgraded to ascii. Then installed the guest cd after the upgrade.

I dont see any issue except that the guest addons arent working...

My folder creation was same as for jessie, no difference.

My host OS is Arch.

Edit 1: I reinstalled the guest additions:

# sh VBoxLinuxAdditions.run 
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.1.30 Guest Additions for Linux...........
VirtualBox Guest Additions installer
Removing installed version 5.1.30 of VirtualBox Guest Additions...
vboxadd.sh: Stopping VirtualBox Additions.
Copying additional installer modules ...
Installing additional modules ...
vboxadd.sh: Starting the VirtualBox Guest Additions.
Failed to set up service vboxadd, please check the log file
/var/log/VBoxGuestAdditions.log for details.

# cat /var/log/VBoxGuestAdditions.log

vboxadd.sh: failed: modprobe vboxguest failed.

Edit: Installing the dkms and the kernel header solved the issue.

Thankyou

#48 Re: Other Issues » (SOLVED) Systemd Library in Ascii » 2017-11-02 05:52:44

makh
golinux wrote:

Yes, libsystemd0 is passively there not doing anything (so far) but systemd is not.  There are other remnants of systemd libs etc, scattered here and there like dead barnacles on a boat.  Not ideal but not enough (wo)man power to clean out the cruft which requires it.   This has been discussed MANY times over the years. Search on irc and dng etc.

Thankyou

#49 Other Issues » [Solved] Virtualbox guest additions - not working (Ascii) » 2017-11-01 05:43:30

makh
Replies: 9

Hi

I have installed the guest cd components, but they are not working in ascii: like shared folder.

I am having devuan ascii installed inside virtualbox 5.1.30

also I get for:

cat /etc/debian_version
9.2
cat /etc/devuan_version
jessie

Thankyou

#50 Other Issues » (SOLVED) Systemd Library in Ascii » 2017-11-01 05:39:37

makh
Replies: 14

Hi

I have this library installed in Devuan Ascii.

libsystemd0:amd64

Are these components still in devuan?

Pages: 1 2

Board footer

Forum Software