Shell doesn't always come up

Dusty · 2005-07-26 23:53:08

This has been happening for quite a while, though it doesn't really bother me. Sometimes when I open an xterm, the bash prompt never comes up.

That's the problem. I don't really know how to expound on it. Anybody else get this?

Dusty

Snowman · 2005-07-26 23:58:26

Once I had similar problem. Check if your SHELL variable is set correctly.

Dusty · 2005-07-27 00:21:55

SHELL=/bin/bash

Dusty

phrakture · 2005-07-27 00:28:28

well, I've noticed that recently on occassion.... does it only happen in WMII?
did anything with the pseudo tty fs change recently?
is xterm set as a loginShell?

can't think of any other possibilities, but it has happened to me in WMII before... I just hit ctrl+alt+c,alt+t

Dusty · 2005-07-27 00:31:06

Phrak: I'm pretty sure its happened in other wms... wmi-10 for sure, as well as wmii, don't recall others.

I use alt-F4 Mod4-x... my keybindings are cooler than yours.

Dusty

phrakture · 2005-07-27 00:33:58

Dusty wrote:

I use alt-F4 Mod4-x... my keybindings are cooler than yours.

And very Windows-y! defaults are way better!

jackmetal · 2005-07-27 00:40:55

I had it happen recently. On fluxbox, bash shell. I tracked it down to something darn strange (didn't have dev/null permission, so it just hung on start). I changed /dev/null to 666 and it came up fine..

I tracked it down because I could log in with root fine, but a user login would hang..

Darn strange!

neri · 2005-07-27 14:54:39

It happend for me on xfce4 as well as on waimea-cvs a while ago. I dun remember if flux was affected, too.
I observed it mostly in xterm, but also remeber that it happened in mlterm as well.

/me has no clue why ...

-neri

FJ · 2005-07-28 00:00:58

This started happening to me on a Slax-TL LiveCD. It was working great for weeks and then one day it stopped bringing up the shell in Fluxbox. I loaded up KDE and it worked there. Very strange.

jackmetal · 2005-07-28 11:21:22

I've been too busy with clients to track it down further, but I was wondering if anyone else has noticed the issue with /dev/null?

That has been the cause of all of my term hangs. For me, it just started happening a few days ago. I'll have to see what has been updated over the weekend or the first of this week.

Maybe I'll have some time today to track it down, but what I've noticed is that once in a while starting a new term will hang. If I look @ /dev/null it's at rw------ only. If I change it to 666, my term starts back working but some time later (maybe a couple hours or so) it will do it again and /dev/null is back to 600.

jackmetal · 2005-07-29 00:21:09

OK, I had a little time to poke around for this issue that I'm having.

I reviewed all the logs and noticed in the syslog that it started on the 26th:

syslog.log:Jul 26 06:56:07 bigdog syslog-ng[2813]: Changing permissions on special file /dev/null
syslog.log:Jul 26 09:12:43 bigdog syslog-ng[2813]: Changing permissions on special file /dev/null
syslog.log:Jul 26 12:05:48 bigdog syslog-ng[2813]: Changing permissions on special file /dev/null
syslog.log:Jul 26 13:49:45 bigdog syslog-ng[2813]: Changing permissions on special file /dev/null
syslog.log:Jul 27 10:35:47 bigdog syslog-ng[2807]: Changing permissions on special file /dev/null
syslog.log:Jul 27 19:25:17 bigdog syslog-ng[2811]: Changing permissions on special file /dev/null
syslog.log:Jul 28 05:21:25 bigdog syslog-ng[2795]: Changing permissions on special file /dev/null
syslog.log:Jul 28 14:06:12 bigdog syslog-ng[2803]: Changing permissions on special file /dev/null
syslog.log:Jul 28 16:42:27 bigdog syslog-ng[2860]: Changing permissions on special file /dev/null
syslog.log:Jul 28 19:16:26 bigdog syslog-ng[3493]: Changing permissions on special file /dev/null

Any ideas what could be initiating this?

mr_echo · 2005-08-16 22:01:57

Sorry to bring up an old thread but I have experienced the same problem.

By an accident I found out that commenting out my

export LC_CTYPE="en_US.utf8"

in .bash_profile made things work out much better. I haven't experienced the same problem since I did that.

However I don't see how that would affect bash from starting. If anyone have found a solution please share. Archlinux is the only dist I've tried were this is happening for me which makes it even more weird, and I have tried a lot of dists. :?

jackmetal · 2005-08-19 08:30:18

mr_echo wrote:

Sorry to bring up an old thread but I have experienced the same problem.

Are you having the same problem I had (with /dev/null changing permissions)?

If so.....I'll poke back through my change-log and find my solution. I haven't had a problem since I fixed it a while back.

mr_echo · 2005-08-19 11:16:16

No, I haven't found anything indicating it's because of /dev/null. It works fine when I change my charset to anything else then utf-8 though.

Thanks anyway.

fluke · 2005-08-28 17:57:22

I meet the problem in fluxbox, and I cant find anything about /dev/null in my log

Arch Linux

#1 2005-07-26 23:53:08

Shell doesn't always come up

#2 2005-07-26 23:58:26

Re: Shell doesn't always come up

#3 2005-07-27 00:21:55

Re: Shell doesn't always come up

#4 2005-07-27 00:28:28

Re: Shell doesn't always come up

#5 2005-07-27 00:31:06

Re: Shell doesn't always come up

#6 2005-07-27 00:33:58

Re: Shell doesn't always come up

#7 2005-07-27 00:40:55

Re: Shell doesn't always come up

#8 2005-07-27 14:54:39

Re: Shell doesn't always come up

#9 2005-07-28 00:00:58

Re: Shell doesn't always come up

#10 2005-07-28 11:21:22

Re: Shell doesn't always come up

#11 2005-07-29 00:21:09

Re: Shell doesn't always come up

#12 2005-08-16 22:01:57

Re: Shell doesn't always come up

#13 2005-08-19 08:30:18

Re: Shell doesn't always come up

#14 2005-08-19 11:16:16

Re: Shell doesn't always come up

#15 2005-08-28 17:57:22

Re: Shell doesn't always come up

Board footer