WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Fluxbox slow startup (~15 seconds)  (Read 946 times)

Offline hobophil

  • WikiUser
  • *
  • Posts: 24
Fluxbox slow startup (~15 seconds)
« on: September 28, 2018, 06:55:40 PM »
When booting up and using Fluxbox as window manager, it takes about 15 seconds to go from the command line (which briefly appears after extensions are loaded) to the desktop. I have a 2nd HDD with Fluxbox also installed with Tiny Core, and it takes about 3-4 seconds to start up. I have no idea what I did to make the 1st drive's start up so much slower. The 1st drive is an SSD which is like 25 times faster than the HDD. On the 1st drive with flwm_topside, it's about 2 seconds to get to the desktop. Haven't timed other window managers, but I think Fluxbox was slower than all of them. I want to use Fluxbox for aesthetic reasons.

Can someone please point me in the right direction to troubleshoot this? Any help is welcome, thanks.

onboot.lst:
Code: [Select]
Xorg-7.7.tcz
aterm.tcz
wbar.tcz
wifi.tcz
wl-modules-4.14.10-tinycore.tcz
iw.tcz
pci-utils.tcz
ndiswrapper.tcz
firmware-atheros.tcz
firmware-broadcom_bcm43xx.tcz
firmware-broadcom_bnx2.tcz
firmware-broadcom_bnx2x.tcz
firmware-getB43.tcz
firmware-ipw2100.tcz
firmware-ipw2200.tcz
firmware-iwimax.tcz
firmware-iwl8000.tcz
firmware-iwl9000.tcz
firmware-iwlwifi.tcz
firmware-marvel.tcz
firmware-myri10ge.tcz
firmware-netxen.tcz
firmware-openfwwf.tcz
firmware-ralinkwifi.tcz
firmware-rtl8192ce_se_de.tcz
firmware-rtlwifi.tcz
firmware-ti-connectivity.tcz
firmware-ueagle-atm.tcz
firmware-vxge.tcz
firmware-zd1211.tcz
firmware.tcz
tc-install-GUI.tcz
ezremaster.tcz
nano.tcz
alsa-config.tcz
xf86-video-ati.tcz
firmware-radeon.tcz
firmware-amd-ucode.tcz
graphics-4.14.10-tinycore.tcz
terminus-fonts.tcz
fluxbox.tcz
vlc2.tcz

.Xdefaults
Code: [Select]
Aterm*scrollBar: true
Aterm*transparent: true
Aterm*title: Terminal
Aterm*foreground: white
Aterm*background: black
Aterm*cursorColor: green
Aterm*fading: 70
Aterm*shading: 50
Aterm*color12: DodgerBlue1
Aterm*saveLines: 1000
fltk*scheme: plastic
Xft.dpi: 96.0
Aterm*font: -xos4-terminus-medium-r-normal--24-240-72-72-c-120-iso8859-1

.xsession
Code: [Select]
/usr/local/bin/Xorg -nolisten tcp &
export XPID=$!
waitforX || ! echo failed in waitforX || exit
"$DESKTOP" 2>/tmp/wm_errors &
export WM_PID=$!
[ -x $HOME/.setbackground ] && $HOME/.setbackground
[ -x $HOME/.mouse_config ] && $HOME/.mouse_config &
[ $(which "$ICONS".sh) ] && ${ICONS}.sh &
[ -d "$HOME/.X.d" ] && find "$HOME/.X.d" -type f -print | while read F; do . "$F"; done
xset +fp /usr/local/share/fonts/terminus/
xset +fp ~/.fonts/
xset -dpms
xset s off

.fluxbox/overlay
Code: [Select]
! The following line will prevent styles from setting the background.
background: none
! background: unset
*.font: '-adobe-noto sans cjk jp light-light-r-normal--0-0-0-0-p-0-iso8859-1'

.fluxbox/init
Code: [Select]
session.screen0.tabs.usePixmap: true
session.screen0.tabs.maxOver:   false
session.screen0.tabs.intitlebar:        true
session.screen0.slit.acceptKdeDockapps: true
session.screen0.slit.maxOver:   false
session.screen0.slit.onhead:    0
session.screen0.slit.placement: RightBottom
session.screen0.slit.autoHide:  false
session.screen0.slit.alpha:     255
session.screen0.slit.layer:     Dock
session.screen0.titlebar.left:  Stick
session.screen0.titlebar.right: Minimize Maximize Close
session.screen0.toolbar.onhead: 1
session.screen0.toolbar.tools:  prevworkspace, workspacename, nextworkspace, iconbar, systemtray, clock
session.screen0.toolbar.visible:        true
session.screen0.toolbar.alpha:  255
session.screen0.toolbar.autoHide:       false
session.screen0.toolbar.height: 0
session.screen0.toolbar.maxOver:        false
session.screen0.toolbar.layer:  Dock
session.screen0.toolbar.placement:      TopCenter
session.screen0.toolbar.widthPercent:   100
session.screen0.menu.alpha:     255
session.screen0.iconbar.alignment:      Relative
session.screen0.iconbar.iconTextPadding:        10
session.screen0.iconbar.usePixmap:      true
session.screen0.iconbar.mode:   {static groups} (workspace)
session.screen0.iconbar.iconWidth:      128
session.screen0.tab.placement:  TopLeft
session.screen0.tab.width:      64
session.screen0.clientMenu.usePixmap:   true
session.screen0.window.focus.alpha:     255
session.screen0.window.unfocus.alpha:   255
session.screen0.workspacewarping:       true
session.screen0.autoRaise:      true
session.screen0.workspaceNames: Workspace 1,Workspace 2,Workspace 3,Workspace 4,
session.screen0.focusSameHead:  false
session.screen0.strftimeFormat: %k:%M
session.screen0.tooltipDelay:   500
session.screen0.edgeSnapThreshold:      10
session.screen0.defaultDeco:    NORMAL
session.screen0.showwindowposition:     false
session.screen0.windowMenu:     /home/tc/.fluxbox/windowmenu
session.screen0.menuDelay:      200
session.screen0.focusNewWindows:        true
session.screen0.tabFocusModel:  ClickToTabFocus
session.screen0.windowPlacement:        RowMinOverlapPlacement
session.screen0.clickRaises:    true
session.screen0.allowRemoteActions:     false
session.screen0.colPlacementDirection:  TopToBottom
session.screen0.opaqueMove:     true
session.screen0.noFocusWhileTypingDelay:        0
session.screen0.maxDisableMove: false
session.screen0.rowPlacementDirection:  LeftToRight
session.screen0.fullMaximization:       false
session.screen0.maxDisableResize:       false
session.screen0.maxIgnoreIncrement:     true
session.screen0.workspaces:     4
session.screen0.focusModel:     ClickFocus
session.configVersion:  13
session.cacheLife:      5
session.slitlistFile:   ~/.fluxbox/slitlist
session.styleOverlay:   ~/.fluxbox/overlay
session.menuFile:       ~/.fluxbox/menu
session.forcePseudoTransparency:        false
session.styleFile:      /usr/local/share/fluxbox/styles/Artwiz
session.tabPadding:     0
session.autoRaiseDelay: 250
session.keyFile:        ~/.fluxbox/keys
session.doubleClickInterval:    250
session.colorsPerChannel:       4
session.cacheMax:       200
session.appsFile:       ~/.fluxbox/apps
session.tabsAttachArea: Window
session.ignoreBorder:   false

Entering "fluxbox -log ~fluxdir/log" into terminal from GUI desktop:
Code: [Select]
tc@box:~/.fluxbox$ fluxbox -log ~fluxdir/log
Warning: Failed to open file(/usr/local/share/fluxbox/nls/C/fluxbox.cat)
for translation, using default messages.
Keys: Invalid key/modifier on line 27): OnWindowBorder Move1 :StartMoving
Keys: Invalid key/modifier on line 30): OnLeftGrip Move1 :StartResizing bottomleft
Keys: Invalid key/modifier on line 31): OnRightGrip Move1 :StartResizing bottomright
BScreen::BScreen: an error occured while querying the X server.
        another window manager already running on display :0.0
Error: Couldn't find screens to manage.
Make sure you don't have another window manager running.
« Last Edit: September 28, 2018, 07:11:19 PM by hobophil »

Offline hobophil

  • WikiUser
  • *
  • Posts: 24
Re: Fluxbox slow startup (~15 seconds)
« Reply #1 on: September 28, 2018, 07:34:27 PM »
More info: Once on the desktop, if I exit to command line and do startx, it's pretty fast to get back to the desktop. Only takes 2 seconds or so. Fluxbox is just slow during initial startup.
« Last Edit: September 28, 2018, 07:44:04 PM by hobophil »

Offline hobophil

  • WikiUser
  • *
  • Posts: 24
Re: Fluxbox slow startup (~15 seconds)
« Reply #2 on: September 28, 2018, 11:06:08 PM »
Tried JWM and it was also slow, around the same speed as Fluxbox.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 9879
Re: Fluxbox slow startup (~15 seconds)
« Reply #3 on: September 29, 2018, 12:51:09 AM »
First look in /var/log/Xorg.0.log, perhaps it has some clues. Otherwise you'd need to edit fluxbox source, add timed prints to see where it spends its time.
The only barriers that can stop you are the ones you create yourself.

Offline core-user

  • Full Member
  • ***
  • Posts: 144
  • Linux since 1999
Re: Fluxbox slow startup (~15 seconds)
« Reply #4 on: September 29, 2018, 02:28:17 AM »
Quote
BScreen::BScreen: an error occured while querying the X server.
        another window manager already running on display :0.0
Error: Couldn't find screens to manage.
Make sure you don't have another window manager running.
Quote
Tried JWM and it was also slow, around the same speed as Fluxbox.

Seems like a clue, is your system trying to run two WMs(?), did you check?
AMD, ARM, & Intel.

aus9

  • Guest
Re: Fluxbox slow startup (~15 seconds)
« Reply #5 on: September 29, 2018, 06:43:50 AM »
Quote
onboot.lst

You appear to load lots of firmware, forgive me, but have you checked that you need that many?

If you use a boot code like "syslog"  and check your log or dmesg or  you may find not all are required?

2) I suspect you don't need ezremaster.tcz each boot either. My 2 cents worth

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2756
Re: Fluxbox slow startup (~15 seconds)
« Reply #6 on: September 29, 2018, 09:46:03 AM »
Welcome hobophil

When you install TC from a CD image to a drive (HDD or USB) it's important to ensure the system is booting and is also loading extensions from the desired drive, which unfortunately is not intuitive for the new TC user.   This is particularly important when you have multiple installations, like a tinycore cd in the cd drive, a USB install, and various HDD installations.  Do not make the mistake of thinking tinycore is booting and loading extensions from the drive you selected, because that's not how it works.

The key to a successful and efficient installation is a boot config file which correctly specifies the drive and path to the selected extension store (tce).    Not forgetting the importance of making efficient use of both onboot.lst and ondemand features, Unlike the inept onboot.lst file listed in the first post.

Ideally,  an efficient onboot.lst file's contents will not include unused extensions or extensions which are dependencies of other extensions, there's a dep file for each extension listing required deps which are loaded when needed, they don't need loading twice...

Regarding the onboot.lst, start with the minimal list of required extensions then add only those extensions required for your hardware which can be found usually within the last 50 line of dmesg output

I'd bet that at least 60% of the extensions listed in your onboot.lst file are not needed

Quote
Code: [Select]
Xorg-7.7.tcz
aterm.tcz
wbar.tcz
wifi.tcz
wl-modules-4.14.10-tinycore.tcz
iw.tcz
pci-utils.tcz
ndiswrapper.tcz
firmware-atheros.tcz
firmware-broadcom_bcm43xx.tcz
firmware-broadcom_bnx2.tcz
firmware-broadcom_bnx2x.tcz
firmware-getB43.tcz
firmware-ipw2100.tcz
firmware-ipw2200.tcz
firmware-iwimax.tcz
firmware-iwl8000.tcz
firmware-iwl9000.tcz
firmware-iwlwifi.tcz
firmware-marvel.tcz
firmware-myri10ge.tcz
firmware-netxen.tcz
firmware-openfwwf.tcz
firmware-ralinkwifi.tcz
firmware-rtl8192ce_se_de.tcz
firmware-rtlwifi.tcz
firmware-ti-connectivity.tcz
firmware-ueagle-atm.tcz
firmware-vxge.tcz
firmware-zd1211.tcz
firmware.tcz
tc-install-GUI.tcz
ezremaster.tcz
nano.tcz
alsa-config.tcz
xf86-video-ati.tcz
firmware-radeon.tcz
firmware-amd-ucode.tcz
graphics-4.14.10-tinycore.tcz
terminus-fonts.tcz
fluxbox.tcz
vlc2.tcz
the above should be reduced tremendously

Start with this, assuming you need the AMD and wl support then check dmesg until all hardware and wifi is working
Code: [Select]
Xorg-7.7.tcz
aterm.tcz
wbar.tcz
Xlibs.tcz
Xprogs.tcz
fluxbox.tcz
wifi.tcz
wl-modules-4.14.10-tinycore.tcz
pci-utils.tcz
xf86-video-ati.tcz
firmware-radeon.tcz
firmware-amd-ucode.tcz
graphics-4.14.10-tinycore.tcz
alsa.tcz
terminus-fonts.tcz
nano.tcz

you can add vlc2  via ondemand

if you really need wl-modules for a broadcom device don't forget to blacklist the bcma, ssb and b43 modules.  then temporarily load firmware-getB43.tcz and run it to install your wifi firmware (if needed)
« Last Edit: September 29, 2018, 10:16:05 AM by coreplayer2 »

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2756
Re: Fluxbox slow startup (~15 seconds)
« Reply #7 on: September 29, 2018, 11:20:23 AM »
On reflection, you might find this example a more efficient and functional onboot.lst for your system.
remember to add wifi drivers if necessary and only firmware specific for your wifi hardware

Code: [Select]
wbar.tcz
aterm.tcz
imlib2-bin.tcz
libxcb.tcz
libXfont.tcz
libXi.tcz
libXmu.tcz
libXpm.tcz
libXrandr.tcz
graphics-4.14.10-tinycore.tcz
xf86-video-ati.tcz
firmware-radeon.tcz
firmware-amd-ucode.tcz
Xorg-7.7.tcz
fluxbox.tcz
alsa.tcz
wifi.tcz

unless you like nano, tc comes with editor already..
« Last Edit: September 29, 2018, 11:24:06 AM by coreplayer2 »

Offline hobophil

  • WikiUser
  • *
  • Posts: 24
Re: Fluxbox slow startup (~15 seconds)
« Reply #8 on: September 29, 2018, 02:10:43 PM »

Seems like a clue, is your system trying to run two WMs(?), did you check?

No I'm not, but I agree this is weird. I'm not using the bootcode desktop=flwm or anything. I don't think I have any other WM's in the onboot.lst or anywhere else. I do have other WM's in my optional TCE folder.

First look in /var/log/Xorg.0.log, perhaps it has some clues. Otherwise you'd need to edit fluxbox source, add timed prints to see where it spends its time.

I did look in there, I don't think there was anything relevant in there other than what is in the fluxbox log. I will check again later.

On reflection, you might find this example a more efficient and functional onboot.lst for your system.
remember to add wifi drivers if necessary and only firmware specific for your wifi hardware

unless you like nano, tc comes with editor already..


Thanks for the tips. Yeah, I haven't trimmed stuff away from what was bundled with my default Core Plus iso. I will try reducing it later (away from my PC right now). I will also check that TCEs are loading from the right spot. Do you think that the long onboot.lst is slowing down the window manager startup though? My "fast" booting HDD has a pretty long onboot.lst too, not very much different.  Also, why does flwm_topside load fast but Fluxbox is slow, on the same SSD with the same bootcodes? Also please note I am talking about the speed as timed from when after all extensions are loaded and the TC command line appears, to when the desktop shows up. Thanks again.

« Last Edit: September 29, 2018, 02:12:59 PM by hobophil »

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2756
Re: Fluxbox slow startup (~15 seconds)
« Reply #9 on: September 29, 2018, 02:35:16 PM »
...
On reflection, you might find this example a more efficient and functional onboot.lst for your system.
remember to add wifi drivers if necessary and only firmware specific for your wifi hardware

unless you like nano, tc comes with editor already..

Thanks for the tips. Yeah, I haven't trimmed stuff away from what was bundled with my default Core Plus iso. I will try reducing it later (away from my PC right now). I will also check that TCEs are loading from the right spot. Do you think that the long onboot.lst is slowing down the window manager startup though? My "fast" booting HDD has a pretty long onboot.lst too, not very much different.  Also, why does flwm_topside load fast but Fluxbox is slow, on the same SSD with the same bootcodes? Also please note I am talking about the speed as timed from when after all extensions are loaded and the TC command line appears, to when the desktop shows up. Thanks again.

1. Please show the contents of your boot config file

:)
« Last Edit: September 29, 2018, 02:39:18 PM by coreplayer2 »

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2756
Re: Fluxbox slow startup (~15 seconds)
« Reply #10 on: September 29, 2018, 03:09:35 PM »
after cleaning up your base install, you can try removing Xorg, xf86-video-ati, graphics-4.14.10-tinycore and fluxbox from your onboot.lst

then at the command line, enter:

tce-load -i graphics-4.14.10-tinycore xf86-video-ati Xorg-7.7 fluxbox
check for errors, then enter
Code: [Select]
startxand time with stopwatch to the Desktop

In my tests both fluxbox and hackedbox with Xorg-7.7 and Nvidia drivers take approximately 6 seconds (which allows for a 2 second human reaction element)

It takes this long to load because of Xorg and the Nvidia drivers

check /var/log/Xorg.0.log for Errors and Warnings

I suspect Xvesa produces considerably faster results
« Last Edit: September 29, 2018, 03:12:04 PM by coreplayer2 »

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 2756
Re: Fluxbox slow startup (~15 seconds)
« Reply #11 on: September 29, 2018, 06:25:14 PM »
Ok, to test this further..
I setup a  boot menu item which represented a minimalist TC9 x86 system with syslog bootcode enabled and set to load the onboot.lst file as previously suggested specific to my test system (Xorg + Nvidia drivers + sample Window Manager + other hardware drivers).

I rebooted three times each with a different Window Manager;  fluxbox, hackedbox and flwm_topside

Syslog reported no more than 9 seconds from installing extensions to desktop with each window manager.  So, put another way;  all Wm's booted in equal time.

Syslog also showed that approximately 6 of those 9 seconds to desktop was consumed by building icons for the desktop wbar and loading of the Xorg/Nvidia driver

In other words, I can't reproduce this issue as IMO each window manager loaded within a second or two..




« Last Edit: September 29, 2018, 06:32:01 PM by coreplayer2 »

Offline hobophil

  • WikiUser
  • *
  • Posts: 24
Re: Fluxbox slow startup (~15 seconds)
« Reply #12 on: October 05, 2018, 10:58:02 PM »
1. Please show the contents of your boot config file

:)

Current bootcodes:
Quote
tc@box:~$ showbootcodes
BOOT_IMAGE=/tce/boot/vmlinuz quiet nodhcp tce=sda1/tce home=sda1 initrd=/tce/boot/core.gz

I did the timing test you suggested above, with this onboot.lst below. I forgot to remove vlc2, but I don't really want to remove it anyways because that is one of the main things I'm using this PC for and I want it on the wbar on login.
Code: [Select]
aterm.tcz
wbar.tcz
ezremaster.tcz
nano.tcz
alsa-config.tcz
firmware-radeon.tcz
terminus-fonts.tcz
vlc2.tcz

Loaded the graphics extensions and then did "startx" as you directed. Time was about 14 seconds per stopwatch.

By the way, when I tried adding these extensions to onboot.lst through Apps, it didn't do anything to onboot.lst. Maybe because they are already depended on by Xorg?
Code: [Select]
imlib2-bin.tcz
libxcb.tcz
libXfont.tcz
libXi.tcz
libXmu.tcz
libXpm.tcz
libXrandr.tcz

Offline hobophil

  • WikiUser
  • *
  • Posts: 24
Re: Fluxbox slow startup (~15 seconds)
« Reply #13 on: October 05, 2018, 11:17:14 PM »
Bottom part of syslog output (syslog bootcode enabled):
Code: [Select]
Oct  5 23:04:24 box user.info kernel: [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor 0
Oct  5 23:04:26 box authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/chown -R root.staff /usr/local/tce.installed
Oct  5 23:04:26 box authpriv.notice sudo:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/chmod -R 775 /usr/local/tce.installed
Oct  5 23:04:26 box authpriv.notice sudo:     root : TTY=console ; PWD=/ ; USER=root ; COMMAND=/bin/tar -C / -zxf /mnt/sda1/tce/mydata.tgz
Oct  5 23:04:26 box daemon.info init: starting pid 3425, tty '/dev/tty1': '/sbin/getty -nl /sbin/autologin 38400 tty1'
Oct  5 23:04:26 box auth.info login[3425]: root login on 'tty1'
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=unknown ; PWD=/home/tc ; USER=root ; COMMAND=/usr/bin/tee /etc/sysconfig/backup
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/rm -rf /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/cp /usr/local/share/wbar/dot.wbar /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chown root.staff /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3486 /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3501 /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3509 /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3524 /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/rm -rf /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/cp /usr/local/share/wbar/dot.wbar /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chown root.staff /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3556 /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3571 /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3579 /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3594 /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/usr/local/bin/fluxbox_initmenu
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/newmenu /usr/local/tce.fluxbox
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3707 /usr/local/tce.icons
Oct  5 23:04:26 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:27 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/newmenu /usr/local/tce.fluxbox
Oct  5 23:04:27 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/wbar.3744 /usr/local/tce.icons
Oct  5 23:04:27 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/chmod g+w /usr/local/tce.icons
Oct  5 23:04:27 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/work3752 /usr/local/tce.icons
Oct  5 23:04:43 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/work3991 /usr/local/tce.icons
Oct  5 23:04:43 box authpriv.notice sudo:       tc : TTY=tty1 ; PWD=/home/tc ; USER=root ; COMMAND=/bin/mv /tmp/work4009 /usr/local/tce.icons
Oct  5 23:04:46 box user.notice kernel: random: crng init done

Offline hobophil

  • WikiUser
  • *
  • Posts: 24
Re: Fluxbox slow startup (~15 seconds)
« Reply #14 on: October 05, 2018, 11:20:13 PM »
Xorg.0.log errors:

Quote
tc@box:/var/log$ cat Xorg.0.log | grep EE
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    15.223] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    15.251] (EE) RADEON(0): glamor detected, failed to initialize EGL.
[    15.399] (II) Initializing extension MIT-SCREEN-SAVER
[    15.399] (EE) AIGLX error: dlopen of /usr/local/lib/dri/r600_dri.so failed (/usr/local/lib/dri/r600_dri.so: cannot open shared object file: No such file or directory)
[    15.399] (EE) AIGLX error: unable to load driver r600
[    15.399] (EE) AIGLX error: dlopen of /usr/local/lib/dri/swrast_dri.so failed (/usr/local/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
[    15.399] (EE) AIGLX error: unable to load driver swrast
[    15.399] (EE) GLX: could not load software renderer
[    15.689] (II) Initializing extension MIT-SCREEN-SAVER
[    15.689] (EE) AIGLX error: dlopen of /usr/local/lib/dri/r600_dri.so failed (/usr/local/lib/dri/r600_dri.so: cannot open shared object file: No such file or directory)
[    15.689] (EE) AIGLX error: unable to load driver r600
[    15.689] (EE) AIGLX error: dlopen of /usr/local/lib/dri/swrast_dri.so failed (/usr/local/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
[    15.689] (EE) AIGLX error: unable to load driver swrast
[    15.689] (EE) GLX: could not load software renderer