On 2/25/22 17:34, Karel Gardas wrote:
hardware: amd64 + radeon R5? 230 + 2 monitors connected. One connected
to DVI, one to VGA. Monitor connected to VGA is on the left and rotated
to the portrait position.
- what I do to crash is:
- start Settings
- search for 'disp'
- select Display
Him
you could try to diable compositing to work around problems with the
graphics driver. And you can report a bug at bugs.debian.org (you should
first do some more investigation about which component causes the problem.)
On 2022-02-25 17:34 UTC+0100, Karel Gardas wrote:
>
> Hi Cindy,
>
> you h
Hi Cindy,
you helped a lot. Indeed, I've moved all dot files and folders into
backup and even problematic user is able to log in.
However, first configuration step brings X11 to the knees, crashing and
then I'm seeing login windows again. So I guess this is the real culprit
of what happene
On 2/25/22, Karel Gardas wrote:
> On 2/25/22 13:29, Christian Britz wrote:
>> Hello Karel,
>>
>> please try it with a temporary clean profile.
>>
>
> thanks for the idea, indeed after creating a random new and clean user
> and attempt to log into the Plasma (X11) session I went in well.
>
> On my
Hello Christian,
thanks for the idea, indeed after creating a random new and clean user
and attempt to log into the Plasma (X11) session I went in well.
On my problematic user I tried to rename some .cache and .config dirs to
remove possibility of corrupted config but this still does not he
Hello Karel,
please try it with a temporary clean profile.
Regards,
Christian
On 2022-02-25 13:12 UTC+0100, Karel Gardas wrote:
>
> Hello,
>
> I'm using debian testing so not sure if this is the right ML, but after
> Feb 24 update I'm no longer capable of logging into the X11/KDE-plasma.
> I
Hello,
I'm using debian testing so not sure if this is the right ML, but after
Feb 24 update I'm no longer capable of logging into the X11/KDE-plasma.
I simply log into, seeing KDE progress gear and then it returns back to
login. My .xsession errors shows that KDE complains about connection
On Fri Sep 4 12:07:23 2020 Greg Wooledge wrote:
> On Fri, Sep 04, 2020 at 11:09:45AM -0700, cgi...@surfnaked.ca
wrote:
>
>> OpenSSL version mismatch. Built against 1010104f, you have
1010006f
>
>> # find . -print | grep -i ssh [output abridged]
>> /etc/X11/Xsession.d/90x11-como
On Fri, Sep 04, 2020 at 11:09:45AM -0700, cgi...@surfnaked.ca wrote:
> OpenSSL version mismatch. Built against 1010104f, you have 1010006f
> # find . -print | grep -i ssh [output abridged]
> /etc/X11/Xsession.d/90x11-comon_ssh-agent
> /etc/xdg/autostart/gnome-keyring-ssh.desktop
> /usr/l
On Fri Sep 4 08:56:44 2020 Mike Kupfer
wrote:
> cgi...@surfnaked.ca wrote:
>
>> I'll continue puttering for a few more days - maybe others will
have
>> some ideas.
>
> So were there any errors or warnings in /var/log/Xorg.0.log?
Nothing there.
> I'd also check for error messages in $HOM
cgi...@surfnaked.ca wrote:
> I'll continue puttering for a few more days - maybe others will have
> some ideas.
So were there any errors or warnings in /var/log/Xorg.0.log?
I'd also check for error messages in $HOME/.xsession-errors.
regards,
mike
On Mi, 02 sep 20, 11:13:30, cgi...@surfnaked.ca wrote:
>
> I found instructions on the web for upgrading Stretch to Buster,
Do you mean these?
https://www.debian.org/releases/buster/releasenotes
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP s
On Wed Sep 2 21:32:55 2020 Andy Smith wrote:
> On Wed, Sep 02, 2020 at 11:13:30AM -0700, cgi...@surfnaked.ca
wrote:
>
>> The Buster upgrade seemed to work OK. I re-booted and got to my
>> xfce login screen. But when I entered my user ID and password,
>> the screen blanked for a second or
Hello,
On Wed, Sep 02, 2020 at 11:13:30AM -0700, cgi...@surfnaked.ca wrote:
> The Buster upgrade seemed to work OK. I re-booted and got to my
> xfce login screen. But when I entered my user ID and password,
> the screen blanked for a second or so, then came back to a blank
> login screen.
Use c
The scariest part of any system upgrade is that first re-boot.
Up until then, you're still running - but after that re-boot,
maybe the machine will come up, and maybe it won't.
Mine won't, and now I have to figure out how to fix it.
I found instructions on the web for upgrading Stretch to Buste
Same issue here.
I found 2 solutions:
1. Use lightdm as DM.
2. Revert the glx diversions with:
> sudo apt-get install -t testing glx-alternative-nvidia/testing glx
> -diversions/testing nvidia-kernel-dkms/testing nvidia-driver/testing
> libegl1-nvidia/testing
I didn't tried with today update
Lisi,
I like the idea of changing the display manager. I chose LXDE for sufficient
functionality and light weight and because I have read the Gnome did not
support remote desktop in jessie or stretch.
Do you have a suggestion for choices? Maybe it doesn't matter, I can always
change. That
I'm having a similar problem on a Jessie install. I don't think it's the
display manager. When I log in via the shell, I get an error message saying
the user has no home directory and starts with the home directory of "/".
Since I don't have permission to read anything on the root, it makes s
Thank you all for the input.
My 1.5 TB disk is not full; I only have Debian on it.
I found I can login with the shell. As Lisi points out, this is probably a
display manager issue.
I logged in as root so I could use the GUI to make it easier to follow
suggestions and record the results. Here
On Tuesday 22 September 2015 00:00:04 Facundo Aguilera wrote:
> Hi! I'm having a very similar problem. I can't login after today's
> upgrade. I tried from a console, but it's the same, it shows the
> welcome message and then the screen is "cleared", asking for the login
> name again. The is no diff
Hi! I'm having a very similar problem. I can't login after today's
upgrade. I tried from a console, but it's the same, it shows the
welcome message and then the screen is "cleared", asking for the login
name again. The is no difference if I try to login with root user.
I was able to login with su
Op Mon, 21 Sep 2015 02:31:08 -0700, schreef ray:
I have had this happen when my harddisk was at 100%.
I got as far as the graphical login, but it didn't accept my login.
I'm not sure but I believe I logged in via ssh or maybe I was still
connected. I don't recall that.
Anyway, on my end it was
On 21/09/15 22:49, ray wrote:
Sven
Thank you very much. I have installed LXDE and I don't know how to open a
console. Please suggest how I might learn to do that.
I had a similar problem with a version of ubuntu after making a lot of
changes. To fix the problem I created a new user and th
Opening a console is same for all sorts of linux distros... ctrl+alt+f4
do your job, and then try any of the combination of ctrl+alt+f*(*: 0-9), if
that doesn't work, you can reboot from console
sudo shutdown -r now
Regarding recovering password, you should read the following, which should
probabl
Sven
Thank you very much. I have installed LXDE and I don't know how to open a
console. Please suggest how I might learn to do that.
On Mon, 2015-09-21 at 02:31 -0700, ray wrote:
> Another approach I tried was to log in as root (I did not expect that
> to work). So I issued:
> passwd .
> I responded to the two password queries and received a success
> signal. I would expect that to solve the issue.
>
> After logging off, I a
Lisi
Thank you.
Another approach I tried was to log in as root (I did not expect that to work).
So I issued:
passwd .
I responded to the two password queries and received a success signal. I would
expect that to solve the issue.
After logging off, I attempted to log in with the updated pa
On Monday 21 September 2015 02:06:47 ray wrote:
> I cannot log on. I don't know if this is related, I was setting up for
> remote desktop, setup a password for the remote session. After rebooting,
> my normal user and password do not work and my rdp password does not work.
>
> What can I do to re
I cannot log on. I don't know if this is related, I was setting up for remote
desktop, setup a password for the remote session. After rebooting, my normal
user and password do not work and my rdp password does not work.
What can I do to recover?
This is Debian stretch with LXDE.
I am very sorry for reposting this, but adding the Solved tag might help
people in the future.
I'd like to confirm how I fixed this issue, which is the same that is
described in the bug report mentioned elsewhere in the thread. In
/etc/smb.conf, I had the line
kerberos method = secrets and key
I'd like to confirm how I fixed this issue, which is the same that is
described in the bug report mentioned elsewhere in the thread. In
/etc/smb.conf, I had the line
kerberos method = secrets and keytab
This didn't work because Samba didn't create the Kerberos keytab file when
I joined the dom
On 14.05.2015 23:47, Dalton D wrote:
> Hello!
>
> I'm trying to install Pykota on Debian Jessie. At the moment, I'm trying
> to get it so that I can log in to the system with Active Directory
> accounts. I set up Samba and Winbind correctly but still can't do this.
> From the syslog, it seems that
After a search of the bug tracker, this is a confirmed issue with the
Winbind package currently in Debian Jessie:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784656
Hello!
I'm trying to install Pykota on Debian Jessie. At the moment, I'm trying to
get it so that I can log in to the system with Active Directory accounts. I
set up Samba and Winbind correctly but still can't do this. From the
syslog, it seems that Winbind is crashing when I try to log in.
I can
Dr. Jennifer Nussbaum wrote:
> I experimented with every possible thing, and finally, i moved my
> .xsession file out of the way and that did it. It was a new file,
> but it contained only the line "xset b 0", and I dont know why this
> would cause the entire start to crash.
That explains everyth
be back in business!
Jen
- Original Message -
> From: Dr. Jennifer Nussbaum
> To: "debian-user@lists.debian.org"
> Cc:
> Sent: Friday, October 7, 2011 7:19 PM
> Subject: Help! Can't log in as self
>
> Im running Xfce4 on Debian testing. I recently reboote
Im running Xfce4 on Debian testing. I recently rebooted the machine, and i
didnt intentionally make any changes
to anything that i think would be relevant. On reboot, I was not able to log in
as my usual user; i get to the Xfce
"Welcome to [machine name]" screen, and enter my username/password, a
On Sun, 18 Apr 2010 10:58:49 -0400
Ryan Larrowe wrote:
> I would like to report a bug in Debian squeeze. After a fresg install
> I cannot log in to my system. I did use shadow passwords on my
> install. If you need more information you can contact me at
> rlarr...@gmail.com.
You should de
I would like to report a bug in Debian squeeze. After a fresg install
I cannot log in to my system. I did use shadow passwords on my
install. If you need more information you can contact me at
rlarr...@gmail.com.
Thank you,
Ryan Larrowe
--
To UNSUBSCRIBE, email to debian-user-requ...@li
Hi there,
This morning I noticed that my Etch box wouldn't let me start up a web
browser window. Odd I thought, so I took a look at the load average,
which was sitting at 210! Some processes such as vi or firefox can no
longer launch, but some simpler ones such as ps or top can still be run
In article <[EMAIL PROTECTED]>,
Bryan Donlan <[EMAIL PROTECTED]> wrote:
>On 8/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>> Can anyone suggest a tutorial on writing what I think are called init
>> scripts?
>
>Take a look at the files in /etc/init.d, just use one of them as a
>templat
On 8/30/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Bryan Donlan <[EMAIL PROTECTED]> wrote:
>
> >On 8/30/05, David W. Williams <[EMAIL PROTECTED]> wrote:
> >> I should have mentioned, I'm the:
> >>
> >>
> >> Re: I m
Bryan Donlan <[EMAIL PROTECTED]> wrote:
>On 8/30/05, David W. Williams <[EMAIL PROTECTED]> wrote:
>> I should have mentioned, I'm the:
>>
>>
>> Re: I messed up bootmisc.sh - now can't log in! guy
>>
>> from debian-user
>>
>
On 8/30/05, David W. Williams <[EMAIL PROTECTED]> wrote:
> I should have mentioned, I'm the:
>
>
> Re: I messed up bootmisc.sh - now can't log in! guy
>
> from debian-user
>
> I just tried this with vi, and when I went to save, got this message:
>
This did it!!! I had misunderstood the last lines of this post. (I stupidly
missed the "in either case".
I"m back in business.
Thank you Bryan! Thank you all!
A VERY grateful Dave Williams.
Bryan Donlan <[EMAIL PROTECTED]> wrote:
>On 8/29/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wr
On 8/29/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Can anyone recommend a good disk recovery company?
>
> Thanks in advance,
>
> Dave Williams
You don't need one for this. Which bootloader are you using, LILO or
GRUB? You can pass init=/bin/sh using it.
For grub, select the boot menu o
ff a cd-rom and mounting the disk, but I can't get
>>>>>>>>the disk to mount for some reason. I'm willing to try pretty much
>>>>>>>>anything at this point.
>>>>>>>>
>>>>>>>>
>>>>&g
nt for some reason. I'm willing to try pretty much
>>>>>>>anything at this point.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>My default grub menu list has a &q
there for some reason edit your grub boot command line and try adding
"single" to the end. I've never tried it manually before but I have used
the recovery mode a few times and I think that's the only difference.
Ah, but there's the problem. I can't
>>>>>
>>>>>
>>>>My default grub menu list has a "recovery" option. If that option isn't
>>>>there for some reason edit your grub boot command line and try adding
>>>>"single" to the end. I'
t manually before but I have used
the recovery mode a few times and I think that's the only difference.
Ah, but there's the problem. I can't log in to edit anything. Is there
a way to make a menu come up? (Am I missing something, besides a system
prompt of course ;-)
le" to the end. I've never tried it manually before but I have used
> > the recovery mode a few times and I think that's the only difference.
>
> Ah, but there's the problem. I can't log in to edit anything. Is there
> a way to make a menu come up? (Am
t;mode a few times and I think that's the only difference.
>
>
>--
>To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
Ah, but there's the problem. I can't
On Sat August 27 2005 05:28 pm, [EMAIL PROTECTED] wrote:
> I've tried booting off a cd-rom and mounting the disk, but I can't get the
> disk to mount for some reason. I'm willing to try pretty much anything at
> this point.
My default grub menu list has a "recovery" option. If that option isn't
I added a command to run mysqld to bootmisc.sh. Now everything boots
fine, but the command that I added to bootmisc.sh runs but doesn't exit,
leaving me with a system running mysql but at runlevel 2 (single user mode) .
It does not return a prompt so I can't log in and fix the problem
tervention necessary, there.)
i've got only two packages held back now (docbook-to-man and mc)
and most everything is working... except i can't log in at the X
window "display manager" prompt.
i've tried "/etc/init.d/wdm restart" and i get the login dialog;
i can ch
On Sunday 14 October 2001 11:13, Colin Watson wrote:
> Are you running unstable? Have you read debian-devel or debian-x
> recently?
I think so.. and yes I did
> http://lists.debian.org/debian-x/2001/debian-x-200110/msg4.html
'Twas one of the first things I did.
Ani
On Sun, Oct 14, 2001 at 08:15:08AM +, Aniartia wrote:
> okay I'm stuck on this one, xdm works great nice log in screen, but when I
> try to log in I'm just dumped at xdm again, the only error I can find is:
> /usr/X11R6/lib/X11/xdm/Xsession: /usr/bin/ssh-agent x-window-manager: No
> such fi
on Sun, Oct 14, 2001 at 08:15:08AM +, Aniartia ([EMAIL PROTECTED]) wrote:
> okay I'm stuck on this one, xdm works great nice log in screen, but when I
> try to log in I'm just dumped at xdm again, the only error I can find is:
> /usr/X11R6/lib/X11/xdm/Xsession: /usr/bin/ssh-agent x-window-ma
okay I'm stuck on this one, xdm works great nice log in screen, but when I
try to log in I'm just dumped at xdm again, the only error I can find is:
/usr/X11R6/lib/X11/xdm/Xsession: /usr/bin/ssh-agent x-window-manager: No
such file or directory
(I get a similar one if I use startx from the cons
wdm login
screen, however, I can't log in. I get the following message in
/var/log/daemon:
Aug 22 15:25:46 localhost wdm: wdm pipe read error with program
/usr/bin/X11/wdm Login, wdm terminating
I run wdm as my standard X display manager, and can log in from the
Ever since I ran apt-get upgrade and got the new XFree86 4.0.2-13 packages,
I can't log in to gdm as a normal user, though I can now as root since I
commented out the "use-ssh-agent" line in Xsession.options file.When I
try to use just startx from the command line, I'
The dependency is present in gnome-session 1.2.4-helix2, but not helix1.
Here's the before and after for the dist-upgrade I just did, which does seem to
have fixed the problem.
I filed a bug report with helix, since it's not clear to me that
helix2 actually fixed the problem, or if I fixed it as
On Wed, Dec 13, 2000 at 12:19:25AM -0800, Ross Boylan wrote:
> Definitely a similar problem here. Thanks to you and others for the
> ctl-atl-Fn trick.
>
> My .gnome-errors says
> /etc/gdm/Sessions//Gnome: checking /etc/login.defs for option UMASK
> /etc/gdm/Sessions//Gnome: /etc/login.defs: "UMA
Definitely a similar problem here. Thanks to you and others for the ctl-atl-Fn
trick.
My .gnome-errors says
/etc/gdm/Sessions//Gnome: checking /etc/login.defs for option UMASK
/etc/gdm/Sessions//Gnome: /etc/login.defs: "UMASK" is "022"
/etc/gdm/Sessions//Gnome: checking /etc/login.defs for optio
On Tue, 12 Dec 2000, J. Bruce Fields wrote:
> I had the identical systems. Logging in on a text console (alt-ctl-F1,
^^^err, meant to write "symptoms" there.
Sorry, I'll proofread more carefully next time)
> then log in), and examining the file .gnome-errors in my ho
I had the identical systems. Logging in on a text console (alt-ctl-F1,
then log in), and examining the file .gnome-errors in my home directory, I
found that gnome was complaining about not being able to find a certain
shared library file. (Can't remember the name--something with pixbuf in
it some
If you upgraded as shown below, you still need to install the packages
that have been kept back.
However I experienced a similar problem and it turned out that the rep
package didn't get installed.
HTH, Pascal Hos
[EMAIL PROTECTED]
Ross Boylan wrote:
I just did an apt-get upgrade, my first i
I just did an apt-get upgrade, my first in about 10 days. I'm now
unable to log in (except if I set my GDM session to Debian, which is
how I got on to send this message).
My system is potato with a little woody to support GNOME. I use Helix
gnome. After the upgrade the system locked up and star
> I can log in on Zope as superuser and create a new user. But I can
> not log in as that user although anything is correct as far as the
> login name and password is concerned.
i am new to zope as well but i just dealt with this the ohter day. it
appears that the admin user can log in from any
I am a newbie as far as apache and zope is concerned and would like to
get to know these two programs.
I can log in on Zope as superuser and create a new user. But I can
not log in as that user although anything is correct as far as the
login name and password is concerned.
I have removed apache
Debian
box is still off-limits. :-(
-Original Message-From: Matheson
[mailto:[EMAIL PROTECTED]Sent: Wednesday, October 11, 2000 4:42
PMTo: debian-user@lists.debian.orgSubject: I can't log
in to tty1-6!
Hey,
I turned on my computer today, and I can only log
in
Hey,
I turned on my computer today, and I can only log
in to X, not the normal tty's. I hanve no idea what could have
happened. When I try to log on it says
Last login: Wed Oct 11 00:23:41
2000 on tty1
Debian/GNU Linux 2.2 tux
tty1
tux login:
Any clues?
Thanks,
Camero
Bob,
np.
I intended to use -r. Below your post is a response to the same question
from another list member. All I can say is it seems to work for me. Next
time I'll try it again without the -r. I'm sure I'll have occasion to.
montefin
"Robert D. Hilliard" wrote:
>
> montefin <[EMAIL PROTECTE
montefin <[EMAIL PROTECTED]> writes:
> NOTE: If you get a large block of type that mentions a SUPERBLOCK error
> and tells you to do the '-b 8193' thing. Well, that's how you got that
> message, right? Instead I did this:
>
> e2fsck -r /dev/ (my /var looks like /dev/hda7
With e2fspro
On Tue, Apr 25, 2000 at 01:26:11PM +0200, Philip Lehman wrote:
>
> First thing I did when the machine came up again was upgrading from
> 2.2.9 to 2.2.14. This is scary.
>
> BTW: What's the best way to keep up with glitches like this if you
> don't follow devel and kernel lists?
I think probably
On Tue, 25 Apr 2000, Ethan Benson <[EMAIL PROTECTED]> wrote:
>On Mon, Apr 24, 2000 at 02:47:37PM -0700, montefin wrote:
>>
>> It seems the linux kernels from about 2.2.7 thru 2.2.13, and only on IDE
>> boxes, had a recurrent filesystem corruption problem. I was on kernel
>> 2.2.12 when I upgraded
On Mon, Apr 24, 2000 at 02:47:37PM -0700, montefin wrote:
> Philip,
>
> To follow up on Nathan's reply, and only because when I upgraded Red Hat
> from 6.0 to 6.1, I earned the dubious title Mr. Fsck-it, here's my 2
> cents:
>
> It seems the linux kernels from about 2.2.7 thru 2.2.13, and only on
Philip,
To follow up on Nathan's reply, and only because when I upgraded Red Hat
from 6.0 to 6.1, I earned the dubious title Mr. Fsck-it, here's my 2
cents:
It seems the linux kernels from about 2.2.7 thru 2.2.13, and only on IDE
boxes, had a recurrent filesystem corruption problem. I was on kern
On Mon, Apr 24, 2000 at 10:34:04PM +0200, Philip Lehman wrote:
[ snip ]
> I'm desperate because the same happens when I boot from a rescue
> disk. What can I do about that? Any help will definetly be very
> much appreciated...
Boot from the rescue disk (and root disk if you use potato) as if you
My potato workstation suffered from a power failure and it seems
like the partition holding the root filesystem was damaged. When
I boot, fsck forces a check and reports an error about duplicate
blocks (I'm sorry that I can't provide the precise error
messages, but there is no way to catch them).
On Sun, Jul 25, 1999 at 03:11:40PM -0500, Brad wrote:
> Now, the only question is "Which package did this?"...
Back in the 1.1 or 1.2 days there was this magic bug where the
permissions on /tmp would get screwed up -- they would become
-rwxr-xr-x or something like that. A lot of apps don't handle
On Sun, 25 Jul 1999, Jeremy Morgan wrote:
> > What're the permissions on /? (ls -ld /)
>
> THANK YOU! It never even occured to me to check the permissions on /. But
> when I did, I found that only root, the owner, had permission to execute.
> Well I fixed that! And now everything seems to be wo
>
> What're the permissions on /? (ls -ld /)
>
>
THANK YOU! It never even occured to me to check the permissions on /. But
when I did, I found that only root, the owner, had permission to execute.
Well I fixed that! And now everything seems to be working. Gosh, am I glad.
Again, thanks guys. Y
On Sun, 25 Jul 1999, Jeremy Morgan wrote:
> I'm not sure if this has been posted before (I've looked but can't find
> anything.) I recently reinstalled debian because the only user that my
> system could use was root. When I tried to su to any user except root I
> would get error messages:
>
>
I ran potato for a long time without any problems, but I built a new
computer recently so I reinstalled everything. Then the problem arised.
When I couldn't fix it, I just reinstalled again--from scratch, a nice,
clean hard drive. Everything was fine with my 2.1 install, but when I
upgraded to po
Exactly how did you reinstall? Did you recreate everything, or are you
trying to reuse parts of a previous installation (e.g. /home)? Many
people, including me, have upgraded from Slink to Potato without such a
problem. You're not trying to use passwd and group files or /home
directories left ov
>
> What are your permissions for /bin/login?
>
> --
> Andrew
I've check the permissions on many files. I may've overlooked one, but here
is /bin/login.
-rwsr-xr-x 1 root root40432 May 31 15:01 /bin/login
> Now this creates many problems except the obvious one (I have to use root
> always): no daemons or programs can run as another user--exim (mail), the
> cron.daily find (nobody), or any others. Before I continue, I'll list
> the
> permissions of certain files:
>
What are your permissions for
I'm not sure if this has been posted before (I've looked but can't find
anything.) I recently reinstalled debian because the only user that my
system could use was root. When I tried to su to any user except root I
would get error messages:
su: cannot run /bin/bash: Permission denied
When I
Sounds like a permissions problem. If you moved your 'dden' directory
while logged in as root, it is possible that it is now owned by root and
as user dden you dont have access to it.
Can you do an `ls -la /home` and email the result?
or alternatively you could try this...
1. log in as root
2. c
On Thu, 24 Jun 1999, David Densmore wrote:
> When I try to login to my normal user account I get this message:
>
> Unable to cd to "/home/dden"
>
> I can still log in as root, but I don't know how to fix the problem.
> I used the adduser command to create a new account and couldn't
> get into th
When I try to login to my normal user account I get this message:
Unable to cd to "/home/dden"
I can still log in as root, but I don't know how to fix the problem.
I used the adduser command to create a new account and couldn't
get into that one either.
Right before this happened I logged in as
> Yes. Most strange I can't log in as root or "su" I have just upgraded to
> "su:cannot execute exit no file or directory" then it just drops me back
> to the ansci login prompt?? it seems like a danferous feature can it be
> remidied ??
&g
On Wed, Mar 17, 1999 at 11:57:27AM +0100, E.L. Meijer Eric" wrote:
> >
> > Yes. Most strange I can't log in as root or "su" I have just upgraded to
> > slink from hamm. Everything went pretty well, for some reason sash became
> > my shell for root? (p
>
> Yes. Most strange I can't log in as root or "su" I have just upgraded to
> slink from hamm. Everything went pretty well, for some reason sash became my
> shell for root? (probably me using dselect - iused the multicd method. well
> not Knowing
> sash
Yes. Most strange I can't log in as root or "su" I have just upgraded to slink
from hamm. Everything went pretty well, for some reason sash became my shell
for root? (probably me using dselect - iused the multicd method. well not
Knowing
sash (well not at all axcept that its p
d then closing the connection!
|
|Even from the console i can't log in as root... same thing, it starts
| and says i have new mail and closes the connection.
|
|I'm trying not to panic. But how can i get back to my system?
Have you tried starting in single user mode? ("linux
s get as far as logging me in, telling me that i have
new mail and then closing the connection!
Even from the console i can't log in as root... same thing, it starts
and says i have new mail and closes the connection.
I'm trying not to panic. But how can i get back to my system?
console i can't log in as root... same thing, it starts
and says i have new mail and closes the connection.
I'm trying not to panic. But how can i get back to my system?
...
universero trio... [EMAIL PROTECTED] http://tio.net/~trio
Learn and use The International Language Esper
100 matches
Mail list logo
