Debian stretch amd64 XFCE. HW System running Debian without problems for c. 3 years, apart from HDD crash 3 months ago; HDD replaced with SSD.
Since about 2 weeks I have 2 strange repeatable symptoms:
(1) To logout or shutdown, I have to perform the complete action two times: click on 'applications-logout-logout'; the two instances of logout or shutdown can be separated by any length of time, as if a latch is being set.
(2) On boot and login, .bashrc is not executed. Normally .bashrc is run when .profile is executed, so that after login, certain actions such character composing and sound settings are carried out. But .bashrc is now only executed when I open a console.
These 2 consistent faults are a minor nuisance, but are possibly indicative of a more serious problem. I cannot say if the 2 problems started at the same time or not, nor can I recall any causative specific action. Seems unlikely that the 2 symptoms are linked, but....
I played around trying to run fsck, but this was not possible - 'init 1' just freezes the system, after a some screen output. fsck is also not part of the installation image. Anyway, it seems that fsck is run during boot.
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Strange behaviour [SOLVED]
Re: Strange behaviour
I've been confused by .profile and .bashrc myself, and noticed that ~/.profile is not read when booting to lightdm then login to plasma desktop. If I boot my fluxbox installation without a display manager all the way to login prompt and login, then .profile is read as before.consufed wrote:(2) On boot and login, .bashrc is not executed. Normally .bashrc is run when .profile is executed, so that after login, certain actions such character composing and sound settings are carried out. But .bashrc is now only executed when I open a console.
The reason I noticed is that ~/.profile is what adds ~/bin to the users path, and this situation breaks that path in any terminals opened under plasma desktop. I don't know what the answer is, or whether it's related to your problem, but it has been this way ever since I installed stretch about a yr ago.
resigned by AI ChatGPT
- oswaldkelso
- df -h | grep > 20TiB
- Posts: 1490
- Joined: 2005-07-26 23:20
- Location: UK
- Has thanked: 1 time
- Been thanked: 58 times
Re: Strange behaviour
Your not the only one.I've been confused by .profile and .bashrc myself
https://blog.flowblok.id.au/2013-02/she ... ripts.html
Free Software Matters
Ash init durbatulûk, ash init gimbatul,
Ash init thrakatulûk agh burzum-ishi krimpatul.
My oldest used PC: 1999 imac 333Mhz 256MB PPC abandoned by Debian
Ash init durbatulûk, ash init gimbatul,
Ash init thrakatulûk agh burzum-ishi krimpatul.
My oldest used PC: 1999 imac 333Mhz 256MB PPC abandoned by Debian
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: Strange behaviour
That is not true, ~/.bashrc is run if you open any interactive shell whereas ~/.profile is only sourced for login shells.consufed wrote:Normally .bashrc is run when .profile is executed
What makes you think this?confused wrote:.bashrc is not executed
What doesn't happen that you think should happen, exactly?
I don't use bash myself (mksh ftw!) but I can assure you that ~/.bashrc works exactly as expected in Debian 9 because I have been testing our BunsenLabs Helium desktop extensively recently (based on stretch) and we need ~/.bashrc to work properly.
Use ~/.xsessionrc insteadbw123 wrote:~/.profile is not read when booting to lightdm
deadbang
Re: Strange behaviour
I wrote: 'Normally .bashrc is run when .profile is executed'
This statement is true by default in Debian 9.
Head_on_a_stick wrote that 'Normally .bashrc is run when .profile is executed' is not true.
Head_on_a_stick meant to write: 'Normally .bashrc is run when .profile is executed' and 'when you login' in the default installation of Debian 9.
Head_on_a_stick implied that my .bashrc is not working.
This statement is true by default in Debian 9.
Head_on_a_stick wrote that 'Normally .bashrc is run when .profile is executed' is not true.
Head_on_a_stick meant to write: 'Normally .bashrc is run when .profile is executed' and 'when you login' in the default installation of Debian 9.
Head_on_a_stick implied that my .bashrc is not working.
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: Strange behaviour
No, I didn't. My statement is completely correct.consufed wrote:Head_on_a_stick meant to write: 'Normally .bashrc is run when .profile is executed' and 'when you login' in the default installation of Debian 9.
It is certainly true that the stock Debian /etc/skel/.profile sources ~/.bashrc but we cannot be sure that applies to your system until you post the content of your ~/.profile
No, I didn't.confused wrote:Head_on_a_stick implied that my .bashrc is not working.
You stated that your ~/.bashrc doesn't work, I am doubting that assertion.
What, exactly, doesn't work for you?
What do you think should happen? What actually happens?
deadbang
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: Strange behaviour [SOLVED]
Why has this thread been marked [SOLVED]?
Please share your solution with the community so that others can benefit.
Please share your solution with the community so that others can benefit.
deadbang
Re: Strange behaviour
Use .xessionrc instead of .profile to add ~/bin to path? Not sure I'd want that, what about ssh, or logins that don't start an x session?Head_on_a_Stick wrote:Use ~/.xsessionrc insteadbw123 wrote:~/.profile is not read when booting to lightdm
If I use .xsessionrc to source .profile it would have potential to source .profile twice, depending on whether login or dm starts the x session. Also, what if X session is started under ssh? I really like keeping things simple and as close to defaults as possible.
This whole thing is confusing. I know most people use only one setup, but I use my computers quite a few different ways.
sheesh, give me a break.Head_on_a_Stick wrote:
can assure you that ~/.bashrc works exactly as expected in Debian 9 because I have been testing our BunsenLabs Helium desktop
resigned by AI ChatGPT
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: Strange behaviour
I was just pointing out that if LightDM is used then ~/.xsessionrc fills the same role that ~/.profile does for a console login.bw123 wrote:Use .xessionrc instead of .profile to add ~/bin to path?
Anything that you would add to ~/.profile for a console-based login can be added to ~/.xsessionrc to produce the same effect for a login under LightDM.
I wasn't talking to yousheesh, give me a break.
deadbang