Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - PackRat

Pages: [1] 2 3 ... 133
1
Download went smooth

Install was pretty smooth; had the usual glitch of grub not installing to /dev/sdc on this multi-boot machine. Easy enough to boot live session and install grub.
Everything working so far, NFS server setup no problem.

scrot in the screenshots page.

One other note - those themes I sent you use google fonts that you don't include, not too much an issue since you use the ~/.fluxbox/overlay file by default. good example of why that file exists, actually. If you're so inclined, you can edit those so the *font value is sans or something stadard. Or just keep that in mind if users start asking about font issues.

2
Artwork & Screenshots / Re: January 2018 Screenshot Thread
« on: January 20, 2018, 09:51:25 PM »
Clean install, 20 Jan 2018 build -


3
Flawless boot - no driver errors.

Code: [Select]
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @24.178s
└─lightdm.service @23.141s +1.035s
  └─systemd-user-sessions.service @22.743s +390ms
    └─network.target @22.741s
      └─wpa_supplicant.service @21.744s +995ms
        └─dbus.service @21.222s
          └─basic.target @21.218s
            └─live-config.service @8.917s +12.299s
              └─local-fs.target @8.908s
                └─tmp.mount @8.902s +5ms
                  └─local-fs-pre.target @8.901s
                    └─keyboard-setup.service @1.276s +7.624s
                      └─systemd-journald.socket @1.270s
                        └─system.slice @1.268s
                          └─-.slice @1.266s

 
Code: [Select]
       12.299s live-config.service
          7.624s keyboard-setup.service
          5.168s dev-loop0.device
          4.162s dev-sdb1.device
          2.131s ModemManager.service
          1.913s user@1000.service
          1.821s systemd-backlight@backlight:intel_backlight.service
          1.387s rsyslog.service
          1.319s lvm2-monitor.service
          1.035s lightdm.service

Just a brief pause at the live-config

I don't have any broadcom hardware, so I can't vouch for that.

And Firefox started up without issue.

4
Artwork & Screenshots / Re: January 2018 Screenshot Thread
« on: January 19, 2018, 10:49:39 PM »
Drive-by posting while I wait for some hot dogs to cook -


5
What would be the overhead / iso size increase to add these to the lite?

Code: [Select]
firmware-atheros
firmware-linux-free
firmware-linux-nonfree
firmware-realtek
firmware-b43-installer  <-- ?? not sure which driver is the general purpose broadcom driver

amd64-microcode
intel-microcode

bluetooth

Those would pretty much make all critical networking hardware work OOTB and eliminate a few error/warning messages at boot time.

6
General Support / Re: Live-Config issues on Stock ISO
« on: January 19, 2018, 09:52:47 PM »
Results for the lite iso -

Code: [Select]
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @22.760s
└─lightdm.service @21.873s +885ms
  └─systemd-user-sessions.service @21.750s +121ms
    └─network.target @21.749s
      └─wpa_supplicant.service @20.640s +1.108s
        └─dbus.service @20.190s
          └─basic.target @20.189s
            └─live-config.service @8.213s +11.974s
              └─local-fs.target @8.210s
                └─tmp.mount @8.204s +5ms
                  └─local-fs-pre.target @8.202s
                    └─keyboard-setup.service @1.259s +6.942s
                      └─systemd-journald.socket @1.099s
                        └─system.slice @1.095s
                          └─-.slice @1.094s[/b]

Code: [Select]
          11.974s live-config.service
          6.942s keyboard-setup.service
          4.288s dev-loop0.device
          4.287s dev-sdb1.device
          2.020s ModemManager.service
          1.616s user@1000.service
          1.310s rsyslog.service
          1.108s wpa_supplicant.service
           996ms systemd-tmpfiles-setup-dev.service
           981ms lvm2-monitor.service

7
General Support / Re: Live-Config issues on Stock ISO
« on: January 19, 2018, 09:41:01 PM »
Quote
On a wider scale, the live-config.service encompasses a mass amount of scripts that are run from /lib/live/config directory

Are the scripts different from the lite iso so that you can narrow it down? The 12 min 10 sec run time is awefully suspicious.

The only thing I can think of right now is that one of the applications in the list you posted in the other thread is related to the apparmor error. At first I thought it was something like pam looking to authenticate somehthing, but I didn't notice anything pam related in the logs/journals.

8
General Support / Re: Live-Config issues on Stock ISO
« on: January 19, 2018, 07:33:52 PM »
After booting the live session with the 12 min 12 sec wait, would it help you to run:

Code: [Select]
systemd-analyze critical-chain
and

Code: [Select]
systemd-analyze blame | head

Those commands give the start and total times for services to run don't they; maybe a comparrison to the lite version?

9
Conky / Re: Conky Support, Codes and Screenshots
« on: January 19, 2018, 02:37:02 AM »
Revamped the default conky for laptop; battery blinks when low - 15% - (needs acpi for the battery state):



Code: [Select]
conky.config = {
--#############################################
-- Settings
--#############################################
background = true,
use_xft = true,
font = 'Ubuntu:regular:size=10',
xftalpha = 1.0,
update_interval = 1.0,
-- update_interval_on_battery = 30.0,
total_run_times = 0,

own_window = true,
own_window_colour = '#141414',
own_window_transparent = true,
-- own_window_type = 'dock',
own_window_type = 'desktop' ,
own_window_hints = 'undecorated,below,sticky,skip_taskbar,skip_pager',
own_window_class = 'ConkyFB',
own_window_title = 'ConkyFB',
--#############################################
-- Compositing tips:
-- Conky can play strangely when used with
-- different compositors. I have found the
-- following to work well, but your mileage
-- may vary. Comment/uncomment to suit.
--#############################################
--#
-- own_window_argb_visual = true,
-- own_window_argb_value = 2,

--# xcompmgr
-- own_window_argb_visual yes
-- own_window_argb_value 120

--# cairo-compmgr
--own_window_type desktop
--own_window_argb_visual yes
--#############################################

no_buffers = true,
uppercase = true,
cpu_avg_samples = 2,
override_utf8_locale = true,
short_units = true,
imlib_cache_size = 0,
pad_percents = 1,
max_user_text = 3200,
text_buffer_size = 1024,
if_up_strictness = 'address',
double_buffer = true,
draw_shades = false,
draw_outline = false,
draw_borders = false,
draw_graph_borders = false,
border_inner_margin = 1,
border_outer_margin = 1,

default_color = '#D1BF64',
default_shade_color = '#000000',
default_outline_color = '#828282',
color0 = '#FFFFFF',
color1 = '#000000',
color2 = '#73AEB4',-- - blue titles
color3 = '#FFFF00',-- - yellow
color4 = '#0000FF',-- - blue
color5 = '#00FF00',-- - green
color6 = '#FFA500',-- - orange
color7 = '#D1BF64',-- - cyan3
color8 = '#DAA520',-- - gold
color9 = '#F00A11',-- - reddish

minimum_width = 256, minimum_height = 0,
maximum_width = 256,
alignment = 'top_left',
gap_x = 12,
gap_y = 12,

};

conky.text = [[
${image $HOME/images/vsidoorb_blk.png -s 48x48 -p 1,-1} \
${voffset 12}${goto 60}${color2}Kernel:${goto 128}${color}${kernel}
${voffset 16}${goto 12}${color2}Uptime:${goto 128}${color}${uptime_short}
${voffset 12}${goto 12}${color2}CPU:${goto 128}${if_match ${cpu}<=50}${color7}${else}${if_match ${cpu}<=70}${color8}${else}${if_match ${cpu}>70}${color9}${endif}${endif}${endif}${cpu cpu0}%${color}
${voffset 6}${goto 128}${loadavg 1}${offset 10}${loadavg 2}${offset 10}${loadavg 3}
${voffset 12}${goto 12}${color2}RAM:${goto 128}${if_match ${memperc}<=50}${color7}${else}${if_match ${memperc}<=70}${color8}${else}${if_match ${memperc}>70}${color9}${endif}${endif}${endif}${memperc}%${color}
${voffset 12}${goto 12}${color2}Batt:${color}${goto 128}${if_match ${battery_percent BAT0}<=15}${blink ${battery_percent BAT0}%}${else}${battery_percent BAT0}%${endif}${offset 12}${execpi 60 acpi | awk '/Battery 0/ {print $3}' | cut -c1-4}
${voffset 12}${goto 12}${color2}Up:${color}${goto 128}${upspeedgraph wlan0 16,112 666666 ff0000}
${voffset 16}${goto 12}${color2}Down:${color}${goto 128}${downspeedgraph wlan0 16,112 000000 00ff00}
]];

10
Artwork & Screenshots / Re: January 2018 Screenshot Thread
« on: January 19, 2018, 12:33:04 AM »
Pretty smooth; couple house cleaning items after boot (and I assume an install) - like upgrading the firefox addons - but all the mission critical stuff works OOTB as usual.

scrot or it never happened:


11
Good deal.

With the recent upgrades to firefox, all the addons you're using are obsolete/incompatable. Can those be upgraded before the [next] iso is built?

12
Download no issues
sha256sum checked out

rebooting .........

13
Artwork & Screenshots / Re: January 2018 Screenshot Thread
« on: January 16, 2018, 12:58:06 AM »
Going with a border only window decoration for a while -


14
WM Designs and Discussions / Fluxbox Deco Bitmasks
« on: January 15, 2018, 03:26:19 PM »
This was touched on in the fluxbox styles thread, but I'm separating it out.

This is a very hand thread to have bookmarked as a fluxbox HowTo

In the ~/.fluxbox/init file, there are three main lines to define the fluxbox window decorations:

Code: [Select]
session.screen0.titlebar.left: Shade Stick
session.screen0.titlebar.right: Minimize Maximize Close
session.screen0.defaultDeco: NORMAL

The first two lines define the position of the window buttons you want to use - so you can put them upper right/left, whatever you're comfortable with.

The last line deines the decor to use - NORMAL is the default, and note it's all caps and, I believe, case sensative.

Reading the man page for fluxbox-apps you'll come across this:

Code: [Select]
[Deco] {value}

           Specify the decoration state. There are several predefined value
           sets:

               NORMAL
                   Standard decorations

               NONE
                   No decorations

               BORDER
                   Like NONE except keep the X window border

               TAB
                   Like BORDER except keep external tabs (if enabled)

               TINY
                   Titlebar with only an iconify button

               TOOL
                   Titlebar only

               The value may also be a bitmask for finer-grained control. The
               bits are, from (1<<0) to (1<<10): Titlebar, Handle/Grips,
               Border, Iconify Button, Maximize Button, Close Button, Menu
               Button, Sticky Button, Shade Button, External Tabs, Focus
               Enabled.

Note there are several options other than NORMAL to use in the ~/.fluxbox/init file for the default decor; or you can override the default decor by setting decor on a per-app basis in the ~/.fluxbox/apps file.

But what exactly does this mean:

Code: [Select]
The value may also be a bitmask for finer-grained control. The
bits are, from (1<<0) to (1<<10): Titlebar, Handle/Grips,
Border, Iconify Button, Maximize Button, Close Button, Menu
Button, Sticky Button, Shade Button, External Tabs, Focus
Enabled.

That's where the above link comes in handy -

Code: [Select]
Each bit-property is given a value that's based on a power of 2 in ascending order:
Property                                            Value
titlebar                                                  1
handle/grips                                         2
border                                                   4
minimize button (called iconify)         8
maximize button                                 16
close button                                         32
enable window menu                          64
sticky button                                       128
shade button                                       256
enable tabbing                                    512
enable focus                                       1024

So the user can decide how a particular window shoud be decorated, adds up the values and uses it with [Deco] in the apps file. So if all you want is tab and borders: 512 + 4 = 516, in the ~/.fluxbox/apps file:

Code: [Select]
[Deco] {516}
Adding in some other window decor and per app settings yields an entry similar to:

Code: [Select]
[app] (name=win) (class=Xpdf)
  [Dimensions] {80% 90%}
  [Position] (UPPERLEFT) {10% 5%}
  [Deco] {1647}
  [Minimized] {no}
  [Maximized] {no}
  [Fullscreen] {no}
  [Layer] {8}
  [Alpha] {255}
[end]



Note than when you log out/in to fluxbox the deco bitmask gets converted to so code (hex?) so the apps entry changes to:

Code: [Select]
[app] (name=win) (class=Xpdf)
  [Dimensions] {80% 90%}
  [Position] (UPPERLEFT) {1% 2%}
  [Shaded] {no}
  [Deco] {0x66f}
  [Sticky] {no}
  [Minimized] {no}
  [Maximized] {no}
  [Fullscreen] {no}
  [Layer] {8}
  [Alpha] {255}
[end]

If the user has a preferred Deco it can be used as default in the ~/.fluxbox/init file

Code: [Select]
session.screen0.defaultDeco: 0x66f
instead of individually in the ~/.fluxbox/apps file.



 

15
Artwork & Screenshots / Re: January 2018 Screenshot Thread
« on: January 14, 2018, 12:23:59 AM »
screenshot day -


Pages: [1] 2 3 ... 133