Author Topic: bash-me-up (Bash Startup Files Setup Made Easy)  (Read 4504 times)

PackRat

  • Posts: 1913
    • View Profile
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #15 on: January 11, 2017, 02:19:01 PM »
Didn't catch this when proffing the script -

Code: [Select]
ln -sf /home/"$local_user"/.profile /root/.profile
ln -sf /home/"$local_user"/.bash_profile /root/.bash_profile
ln -sf /home/"$local_user"/.bashrc /root/.bashrc
ln -sf /home/"$local_user"/.bash_logout /root/.bash_logout
if [ -f /home/"$local_user"/.bash_aliases ] ; then
ln -sf /home/"$local_user"/.bash_aliases /root/.bash_aliases

Not too big an issue on this particular laptop where I'm the only user. On a multi-user machine those files would be linked to the last user setup.

Appears to me to be an inherent security flaw going on with this part. Does Debian even create those files for root? The default would be to just use the /etc/bashrc and /etc/profile, correct? Maybe just go that route.
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

hakerdefo

  • Posts: 520
    • View Profile
    • Looking at Linux through the Windows of Life
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #16 on: January 11, 2017, 03:41:47 PM »
$local_user is the user who ran this install script as sudo. On a multiuser machine this will be a bad thing. In the V2 of bash-me-up I'll make the soft-linking an optional feature. Thanks for pointing this out PackRat. As usual your observation is spot-on and valid.

Cheers!!!
You Can't Always Git What You Want

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #17 on: January 11, 2017, 04:21:35 PM »
Your fearless (dumbass?) leader went ahead and installed it.. I am now on another partition to restore the bup files but wanted to post what is going on

I installed with no issues.. I logged out and tried to log back in but got an endless loop back to the lightdm login. I also rebooted and same results

I use a separate /home partition that is also used on this partition I am on now.. just stating that whatever broke on the install partition is not affecting this login even though the files are the same

I can hold off for a while if you want to test anything.. Just let me know
 
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

PackRat

  • Posts: 1913
    • View Profile
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #18 on: January 11, 2017, 04:26:39 PM »
^ Is your lightdm login screen set to the "Default"

@hackerdefo - I stand corrected, for lxdm the default WM/DE is pulled from the /etc/lxdm/lxdm.conf file so I can use your .xsession file as is.

I will stand by statement that LightDM reads the .xsession file as evidenced by vastone being caught in a loop.

I think startx still defaults to .xinitrc, so that should work unless it is a symlink to .xsessionrc.

@vastone - add a window manager to your new .xsessionrc and see if you log in.
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #19 on: January 11, 2017, 04:39:22 PM »
Adding that did not change the issue.. Need to log out and back in to see if FluxBox is selected by LightDM

I still am verklemped by the fact that I can login on this partition using the same login and exact same files.. but will trace it down
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #20 on: January 11, 2017, 04:45:21 PM »
Was set to FluxBox and changing it to Default made no difference

If I change this login (working one) from FluxBox to Default it replicates the issue

I am going to go through each file now and look at what could be the issue and start a step by step restore and reboot to isolate
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

hakerdefo

  • Posts: 520
    • View Profile
    • Looking at Linux through the Windows of Life
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #21 on: January 11, 2017, 04:50:22 PM »
Can you post the ~/.xsession-errors file here?

Cheers!!!
You Can't Always Git What You Want

hakerdefo

  • Posts: 520
    • View Profile
    • Looking at Linux through the Windows of Life
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #22 on: January 11, 2017, 04:56:56 PM »
Also can you start the Fluxbox manually from a different tty, let's say tty2 by running this command,

Code: [Select]
startx /usr/bin/startfluxbox
Cheers!!!
You Can't Always Git What You Want

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #23 on: January 11, 2017, 04:57:07 PM »
Current xsessions-errors

Code: [Select]
Xsession: X session started for vastone at Wed Jan 11 10:50:02 CST 2017
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/vastone/.Xauthority
localuser:vastone being added to access control list
gpgconf: warning: can not open config file /home/vastone/.gnupg/gpg-agent.conf: No such file or directory
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
OpenGL version: 3.
dbus-update-activation-environment: setting USER=vastone
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/vastone
dbus-update-activation-environment: setting DESKTOP_SESSION=fluxbox
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting LOGNAME=vastone
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting GDM_LANG=en_US.utf8
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=en_US.UTF-8
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=fluxbox
dbus-update-activation-environment: setting XAUTHORITY=/home/vastone/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/vastone
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting GDMSESSION=fluxbox
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/vastone
xmodmap:  unable to open file '~/.Xmodmap' for reading
xmodmap:  1 error encountered, aborting.
Keys: Invalid key/modifier on line 171): https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2Fstlwrkr4889%3Fcn%3DcmVwbHk%253D%26refsrc%3Demail&t=1&cn=cmVwbHk%3D&sig=f135617fa1ff0ae714c743b03fe906895295ce0f&iid=0e194376e99f4029bc4b5b7754686143&uid=31587023&nid=27+1262
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
xRandr: Found crtc's: 1
xRandr: Linking output HDMI-0 with crtc 0
No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
xRandr: Found crtc's: 1
xRandr: Linking output HDMI-0 with crtc 0
No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
real transparency off.... depth: 24
real transparency off.... depth: 24
panel items: LT
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2
panel items: FS
Systray composited rendering on
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2
Kernel uevent interface initialized...
systray window 10485767
tint2 : systray started
Kernel uevent interface initialized...
Loading icon theme cache...
libpng warning: iCCP: known incorrect sRGB profile
launcher.c 216: Using icon /usr/share/icons/LinuxLex-8/apps/chromium.png
launcher.c 216: Using icon /usr/local/bin/images/WoBD Terminal.png
launcher.c 216: Using icon /usr/local/bin/images/phoca_thumb_l_file-manager.png
launcher.c 216: Using icon /usr/local/bin/images/gmb.png
launcher.c 216: Using icon /usr/local/bin/images/vsidoorb_blk.png
Detected compositor, restarting tint2...
/tmp/buildd/tint2-0.12.12/src/tint.c 1988: restarting tint2...
xRandr: Found crtc's: 1
xRandr: Linking output HDMI-0 with crtc 0
No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
real transparency on... depth: 32
panel items: LT
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2
Kernel uevent interface initialized...
Loading icon theme cache...
launcher.c 216: Using icon /usr/share/icons/LinuxLex-8/apps/chromium.png
launcher.c 216: Using icon /usr/local/bin/images/WoBD Terminal.png
launcher.c 216: Using icon /usr/local/bin/images/phoca_thumb_l_file-manager.png
launcher.c 216: Using icon /usr/local/bin/images/gmb.png
launcher.c 216: Using icon /usr/local/bin/images/vsidoorb_blk.png
Detected compositor, restarting tint2...
/tmp/buildd/tint2-0.12.12/src/tint.c 1988: restarting tint2...
xRandr: Found crtc's: 1
xRandr: Linking output HDMI-0 with crtc 0
No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
real transparency on... depth: 32
panel items: FS
Systray composited rendering on
tint2 : nb monitor 1, nb monitor used 1, nb desktop 2
Kernel uevent interface initialized...
systray window 10485768
tint2 : systray started
conky: conky: Syntax error (/home/vastone/.conkyrc:2: unexpected symbol near '#') while reading config file.
conky: Assuming it's in old syntax and attempting conversion.
Syntax error (/home/vastone/.conkyrc2:2: unexpected symbol near '#') while reading config file.
conky: Assuming it's in old syntax and attempting conversion.
conky: desktop window (26a) is root window
conky: window type - normal
conky: drawing to created window (0x1000002)
conky: drawing to double buffer
conky: desktop window (26a) is root window
conky: window type - desktop
conky: drawing to created window (0x1200002)
conky: drawing to double buffer
[WARNING:flash/platform/pepper/pep_module.cpp(63)] SANDBOXED
[1688:1764:0111/105118.858210:ERROR:object_proxy.cc(583)] Failed to call method: org.freedesktop.NetworkManager.GetDevices: object_path= /org/freedesktop/NetworkManager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[1688:1764:0111/105118.858233:ERROR:networking_private_linux.cc(715)] Failed to enumerate network devices
[1688:1764:0111/105218.119368:ERROR:object_proxy.cc(583)] Failed to call method: org.freedesktop.NetworkManager.GetDevices: object_path= /org/freedesktop/NetworkManager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[1688:1764:0111/105218.119417:ERROR:networking_private_linux.cc(715)] Failed to enumerate network devices

xsessions-errors.old which is what happened on last login that does not work

Code: [Select]
Xsession: X session started for vastone at Wed Jan 11 10:48:47 CST 2017
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/vastone/.Xauthority
localuser:vastone being added to access control list
/etc/X11/Xsession: 28: export: Illegal option -f
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #24 on: January 11, 2017, 05:04:06 PM »
Also can you start the Fluxbox manually from a different tty, let's say tty2 by running this command,

Code: [Select]
startx /usr/bin/startfluxbox
Cheers!!!

Yes .. this worked and I am now logged into the original
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

hakerdefo

  • Posts: 520
    • View Profile
    • Looking at Linux through the Windows of Life
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #25 on: January 11, 2017, 05:24:23 PM »
I think I've got this one, perhaps ;)
VastOne can you edit the file .xsessionrc file provided by bash-me-up and change,

Code: [Select]
test -f /etc/profile && . /etc/profile
test -f $HOME/.profile && . $HOME/.profile

To

Code: [Select]
if [ -r ~/.profile ] ; then . ~/.profile ; fi
if [ -r /etc/profile ] ; then . /etc/profile ; fi

Save the file, log-out and try to log-in via LightDM. Hopefully you'll ;)

Cheers!!!
You Can't Always Git What You Want

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #26 on: January 11, 2017, 05:29:26 PM »
I think I've got this one, perhaps ;)
VastOne can you edit the file .xsessionrc file provided by bash-me-up and change,

Save the file, log-out and try to log-in via LightDM. Hopefully you'll ;)

Cheers!!!

Nope... same issue ... I cannot login on tty7 lightdm but I can login tty2 startx /usr/bin/startfluxbox

I also rebooted to be completely sure
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

hakerdefo

  • Posts: 520
    • View Profile
    • Looking at Linux through the Windows of Life
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #27 on: January 11, 2017, 05:32:13 PM »
Can you post the latest xsessions-errors file?

Cheers!!!
You Can't Always Git What You Want

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #28 on: January 11, 2017, 05:34:28 PM »
Here they are but I am not sure errors are being captured on a failed login because the latest and the old one are identical

Code: [Select]
Xsession: X session started for vastone at Wed Jan 11 11:30:59 CST 2017
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/vastone/.Xauthority
localuser:vastone being added to access control list
/etc/X11/Xsession: 28: export: Illegal option -f
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 3931
    • View Profile
    • VSIDO Community
Re: bash-me-up (Bash Startup Files Setup Made Easy)
« Reply #29 on: January 11, 2017, 05:37:18 PM »
This is behaving more like a permissions issue than anything.. But that makes no sense because I can login to another partition with the same login using the same /home files
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO