WM corrupted after installation

realitymolder commented 2 years ago

Hey guys, it seems that after a clean install with the script the environment seems corrupted / missing some assets pictures and such.

realitymolder commented 2 years ago

Also I will add the the user folders are missing Nothing inside of the user folder only the cloned Debian Titus folder.

Pictures of the desktop (not colored and has artifacts ) :

nielsdrost7 commented 2 years ago

This is more troubleshooting than bugfixing, but ok... The artifacts are most likely, because the fontawesome font isn't installed yet.

Troubleshooting:

Install fontawesome font (check Chris's older video of him installing that font)
Bugfixing: make a pull-request adding the fontawesome font (and only that). Then refer that pull-request to this issue

fishd72 commented 2 years ago

Having the same issue running in a VM under VMware Fusion (Intel based Mac). I've installed the open-vm-tools-desktop package as a manual step prior to starting the sddm service.

Have confirmed that the fonts-font-awesome package is installed, and the .otf is present in /usr/share/fonts ...

aroumeliotis commented 2 years ago

It's an issue at the .Xresources configuration file. Find this line to edit #include "/home/titus/.Xnord" using your username instead of titus

nielsdrost7 commented 2 years ago

Find this line to edit #include "/home/titus/.Xnord" using your username instead of titus

Great find, man! It helps!

realitymolder commented 2 years ago

It's an issue at the .Xresources configuration file. Find this line to edit #include "/home/titus/.Xnord" using your username instead of titus

Should be located in my home folder ? Cause mine is empty

fishd72 commented 2 years ago

That's fixed it for me, thanks @aroumeliotis

@DanielToubul ... you don't have the file? As it starts with . it is hidden from view by default... use ls -la ~/ within Kitty to view all files, including hidden files and directories.

If it's definitely not there, you can run the user.sh script again from within the Debian-titus folder or copy the file manually from the Debian-titus directory using cp .Xresources ~.

realitymolder commented 2 years ago

That's fixed it for me, thanks @aroumeliotis

@DanielToubul ... you don't have the file? As it starts with . it is hidden from view by default... use ls -la ~/ within Kitty to view all files, including hidden files and directories.

If it's definitely not there, you can run the user.sh script again from within the Debian-titus folder or copy the file manually from the Debian-titus directory using cp .Xresources ~.

Thanks works like a charm And kudos to @aroumeliotis for helping out with this.

I wanted to create a pull request to add a dynamic variable of the username in the .Xresources file instead of the hard coded "titus" user name, but I've got no permission to do so. @ChrisTitusTech FYI

Now the only things which aren't working well are the ones that Chris is still working on. Thanks!

aphive commented 2 years ago

I wanted to create a pull request to add a dynamic variable of the username in the .Xresources file instead of the hard coded "titus" user name, but I've got no permission to do so.

You will need to fork the repo to your account then do a pull request with your changes.

aphive commented 2 years ago

I verified that I have the .Xnord and .Xresources files with no titus in the configs. I re-cloned the entire repo and replaced both .Xnord and .Xresources and I still have the issue.

However, when searching the .config directory I see these, not sure if they are of any importance

:~/.config$ grep -iR titus *
grep: rofi/bin/launcher_ribbon: No such file or directory
grep: rofi/bin/launcher_text: No such file or directory
grep: rofi/bin/launcher_slate: No such file or directory
grep: rofi/bin/launcher_colorful: No such file or directory
grep: rofi/bin/launcher_misc: No such file or directory

I verified fontawesome was installed:

sudo apt install fonts-font-awesome 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
fonts-font-awesome is already the newest version (5.0.10+really4.7.0~dfsg-4.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

and it's already part of the root.sh file here: https://github.com/ChrisTitusTech/Debian-titus/blob/e6d2ceffe318a37fc382f02807fb1a586535983e/root.sh#L19

2022-01-01_21-16

Update 1

I also re-ran the user.sh script just in case:

~/Debian-titus$ ./user.sh 
[sudo] password for squid: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ttf-mscorefonts-installer is already the newest version (3.8).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
fatal: destination path 'Layan-cursors' already exists and is not an empty directory.
Finished...

Update 2

Running xrdb -query I get this, in case it helps:

Xft.dpi:    96
Xft.antialias:  1
Xft.autohint:   1
Xft.hinting:    true
Xft.hintstyle:  hintslight
Xft.rgba:   rgb
Xft.lcdfilter:  lcddefault
URxvt.font: xft:FONT:style=Medium:size=9:antialias=true, xft:ICON:size=9:antialias=true, xft:NERD_FONT:size=9:antialias=true, xft:EMOJI:size=9:antialias=true
URxvt.boldFont: xft:FONT:style=Bold:size=9:antialias=true, xft:ICON:size=9:antialias=true, xft:NERD_FONT:size=9:antialias=true, xft:EMOJI:size=9:antialias=true
URxvt.italicFont:   xft:FONT:style=Italic:size=9:antialias=true, xft:ICON:size=9:antialias=true, xft:NERD_FONT:size=9:antialias=true, xft:EMOJI:size=9:antialias=true
URxvt.boldItalicFont:   xft:FONT:style=Bold Italic:size=9:antialias=true, xft:ICON:size=9:antialias=true, xft:NERD_FONT:size=9:antialias=true, xft:EMOJI:size=9:antialias=true
*.foreground:   #D8DEE9
*.background:   #2E3440
*.cursorColor:  #D8DEE9
*fading:    35
*fadeColor: #4C566A
*.color0:   #3B4252
*.color1:   #BF616A
*.color2:   #A3BE8C
*.color3:   #EBCB8B
*.color4:   #81A1C1
*.color5:   #B48EAD
*.color6:   #88C0D0
*.color7:   #E5E9F0
*.color8:   #4C566A
*.color9:   #BF616A
*.color10:  #A3BE8C
*.color11:  #EBCB8B
*.color12:  #81A1C1
*.color13:  #B48EAD
*.color14:  #8FBCBB
*.color15:  #ECEFF4
*.font: xft:FiraCode Nerd Font Mono:style=Medium:size=14:antialias=true
URxvt.depth:    32
URxvt*lineSpace:    0
URxvt*letterSpace:  -1
URxvt.iso14755: false
URxvt.iso14755_52:  false
URxvt*geometry: 184x44
URxvt.scrollBar:    false
URxvt*loginShell:   true
URxvt.internalBorder:   88
URxvt.perl-ext: default,matcher,resize-font
URxvt.url-launcher: linkhandler
URxvt.matcher.button:   1
URxvt.keysym.M-r:   perl:matcher:last
URxvt.keysym.M-l:   perl:matcher:list
URxvt.keysym.M-e:   perl:matcher:select
URxvt.saveLine: 10000
URxvt.cursorBlink:  true
URxvt.cursorUnderline:  true
URxvt*inheritPixmap:    false
URxvt*transparent:  false
URxvt*scrollTtyOutput:  false
URxvt*scrollWithBuffer: true
URxvt*scrollTtyKeypress:    true
URxvt.keysym.C-minus:   resize-font:smaller
URxvt.keysym.C-plus:    resize-font:bigger
URxvt.keysym.C-equal:   resize-font:reset
URxvt.keysym.C-question:    resize-font:show
URxvt.resize-font.step: 0.5
URxvt.keysym.Shift-Up:  command:\033]720;1\007
URxvt.keysym.Shift-Down:    command:\033]721;1\007
URxvt.secondaryScreen:  1
URxvt.secondaryScroll:  0
URxvt.secondaryWheel:   1
URxvt.keysym.Control-Meta-c:    builtin-string:
URxvt.keysym.Control-Meta-v:    builtin-string:
URxvt.keysym.Shift-Control-V:   eval:paste_clipboard
URxvt.keysym.Shift-Control-C:   eval:selection_to_clipboard
xterm.vt100.termName:   xterm-256color
xterm.vt100.scaleHeight:    1.0
XTerm.vt100.geometry:   80x32
xterm.vt100.internalBorder: 44
xterm.vt100.borderWidth:    0
XTerm*loginshell:   true
XTerm*savelines:    16384
XTerm*charClass:    33:48,36-47:48,58-59:48,61:48,63-64:48,95:48,126:48
xterm.vt100.utf8:   true
XTerm.vt100.locale: true
xterm.vt100.scrollBar:  false
xterm.vt100.cursorBlink:    true
xterm.vt100.selectToClipboard:  true
xterm.vt100.trimSelection:  true
xterm.vt100.renderFont: true
xterm.vt100.wideChars:  true
xterm.vt100.visualBell: false
xterm.vt100.forceBoxChars:  true
xterm.vt100.font-linedrawing:   true
*VT100*translations:    #override Shift <Btn1Up>: exec-formatted("linkhandler '%t'", PRIMARY)
xterm.vt100.translations:   #override \n Shift Ctrl <KeyPress> v:insert-selection(CLIPBOARD) \n Shift Ctrl <KeyPress> c:select-set(CLIPBOARD)
XTerm*faceSize: 10
xterm.vt100.faceName:   monospace
XTerm*scrollTtyOutput:  false
st.font:    monospace:pixelsize=20:antialias=true:autohint=true
st.alpha:   1
st.borderpx:    44
st.cursorshape: 3
st.disablebold: 0
st.disableitalics:  0
st.boxdraw: 1
st.boxdraw_bold:    1
st.boxdraw_braille: 1
st.chscale: 1.0
st.cwscale: 1.0

aphive commented 2 years ago

Bugfixing: make a pull-request adding the fontawesome font (and only that). Then refer that pull-request to this issue

it's already part of the root.sh file here: https://github.com/ChrisTitusTech/Debian-titus/blob/e6d2ceffe318a37fc382f02807fb1a586535983e/root.sh#L19

aphive commented 2 years ago

Ok, so I figured out part of the issue.. For some reason the colors are not being pulled from whatever xrdb is here:${xrdb:color0} I'm guessed that it's supposed to be pulling from .Xnord but is not, so, I mapped the colors and manually hard coded them into the .config/polybar/config file like so:

[colors]
#define color0:  #3B4252
#define color1:  #BF616A
#define color2:  #A3BEAD
#define color3:  #EBCB8B
#define color4:  #81A1C1
#define color5:  #B48EAD
#define color6:  #88C0D0
#define color7:  #E5E9F0
#define color8:  #4C566A
#define color9:  #BF616A
#define color10: #A3BE8C
#define color11: #EBCB8B
#define color12: #81A1C1
#define color13: #B48EAD
#define color14: #8FBCBB
#define color15: #ECEFF4

then did a search and replace in vim to change where it's mapped to:

:%s/xrdb/colors/g

Things look a little bit better now, however the coloring behind the icons between the half moon looking spacers are still missing and the spacers are solid white.

Interestingly, the shades are mapped to the colors duplicating coloring profiles, why not just point the shades to the respective colors directly? I understand the naming factor tho.

; Active Shade 
shade0 = ${colors:color0}
shade1 = ${colors:color1}
shade2 = ${colors:color2}
shade3 = ${colors:color3}
shade4 = ${colors:color4}
shade5 = ${colors:color5}
shade6 = ${colors:color6}
shade7 = ${colors:color7}
shade8 = ${colors:color8}
shade9 = ${colors:color9}
shade10 = ${colors:color10}
shade11 = ${colors:color11}
shade12 = ${colors:color12}
shade13 = ${colors:color13}
shade14 = ${colors:color14}
shade15 = ${colors:color15}
shade16 = ${colors:color0}
shade17 = ${colors:color0}
shade18 = ${colors:color0}

aphive commented 2 years ago

So it seems there is something up with the rofi package 🤷🏻‍♂️, I removed it and installed the default package and it seems to make things a bit better. At least it brought the actual theme into place. Still not able to click on anything on the right side other than the power button.

sudo apt remove rofi && sudo apt install rofi

aphive commented 2 years ago

Update

I tried a whole fresh install and still borked.

Trials

I ended up rewriting the install scripts into one that uses the user account to do things, not run things as root, and left out that custom rofi_1.7.0-1_amd64.deb file as I have no idea what that's doing and it seems to be trying to delete usr/local for some reason when dpkg runs it, see issue 35.

What happened

That got me to 99% except for the powermenu and the fact that I can't interact with the bar items to the right (clock, battery, etc).

Assumptions

I think there may be something baked into the files that links between the different apps that is not working properly by default.

Moving forward

I'll try to build this thing out manually step by step and see if I can figure this out.

Notes

I'm running this on a ThinkPad X260 if that makes any difference.
Also, there doesn't seem to be anyway to interact with networking settings at all.

kssnagasinghe commented 2 years ago

@aphive What is your current problem? Your problem is that the polybar is blackened.

aphive commented 2 years ago

at the time, it was mainly that nothing on the right side functions as expected.

I ended up removing the full yes and no word options from the confirm file and the options started working when selecting power options now.

I'm wondering now if maybe hardware has some impact on the end result, also if maybe that custom rofi Deb file has something specific that does not work on some machines seeing that as soon as i removed it from use things worked just fine for the most part.

ChrisTitusTech / Debian-titus