Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)

[Karel Gardas]

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 Configuration node
  - move VGA monitor from right to left
  - select rotation on left monitor (rotate 90 clockwise)
  - hit 'Apply' button

^ and right after hitting Apply I get crash.

IMPORTANT: if I do *NOT* rotate left monitor, if I just move it from 
right to left, X11 are able to survive! If I do *NOT* move VGA monitor 
from right to left, but just rotate it, I will get again immediate crash.


Conclusion: my X11 crashes since Feb 24 update on monitor rotation on R5 
230 GPU.


I've also verified that while being logged into KDE following command:

$ xrandr --output VGA-0 --rotate left

crashes X11 server and I'm back into SDDM login window. I tested this to 
remove any doubt if KDE framework here (thorough display config) is the 
culprit or not.


Now, I'm pretty confident that this issue happened last week (7 days) or 
so since this is my debian testing and I've been using it more recently 
hence also updating every using day. The question is: where to report 
that to get some fix?


Thanks,
Karel

Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)

[Christian Britz]

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 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 happened on problematic user. The step to duplicate is this:
> 
> 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 Configuration node
>   - move VGA monitor from right to left
>   - select rotation on left monitor (rotate 90 clockwise)
>   - hit 'Apply' button
> 
> ^ and right after hitting Apply I get crash.
> 
> IMPORTANT: if I do *NOT* rotate left monitor, if I just move it from 
> right to left, X11 are able to survive! If I do *NOT* move VGA monitor 
> from right to left, but just rotate it, I will get again immediate crash.
> 
> Conclusion: my X11 crashes since Feb 24 update on monitor rotation on R5 
> 230 GPU.
> 
> Question: is there any forum where should I report this conclusion to 
> get attention of the X11 packagers/developers?
> 
> Thanks!
> Karel
> 
> 
> 
> On 2/25/22 16:56, Cindy Sue Causey wrote:
>> 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 problematic user I tried to rename some .cache and .config dirs to
>>> remove possibility of corrupted config but this still does not help.
>>>
>>> Do you have any idea where everywhere KDE stores its bits of data? Ref
>>> to web page describing this will be enough so I can debug the issue and
>>> find the culprit behind this issue...
>>
>>
>> When I'd encounter something like this, one of the things that worked
>> for me was to rename (dot)Xauthority in the user's home directory. My
>> memory is that the file would be recreated during a (FINALLY)
>> successful login.
>>
>> If that doesn't work, how I tripped over that was by going into the
>> file manager (Thunar in XFCE4) and sorting files by newest modified
>> dates. That hinted at what files might have been most recently touched
>> and thus might be a possible culprit.
>>
>> Good luck!
>>
>> Cindy :)
> 

-- 
http://www.cb-fraggle.de

Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)

[Karel Gardas]

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 happened on problematic user. The step to duplicate is this:


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 Configuration node
 - move VGA monitor from right to left
 - select rotation on left monitor (rotate 90 clockwise)
 - hit 'Apply' button

^ and right after hitting Apply I get crash.

IMPORTANT: if I do *NOT* rotate left monitor, if I just move it from 
right to left, X11 are able to survive! If I do *NOT* move VGA monitor 
from right to left, but just rotate it, I will get again immediate crash.


Conclusion: my X11 crashes since Feb 24 update on monitor rotation on R5 
230 GPU.


Question: is there any forum where should I report this conclusion to 
get attention of the X11 packagers/developers?


Thanks!
Karel



On 2/25/22 16:56, Cindy Sue Causey wrote:

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 problematic user I tried to rename some .cache and .config dirs to
remove possibility of corrupted config but this still does not help.

Do you have any idea where everywhere KDE stores its bits of data? Ref
to web page describing this will be enough so I can debug the issue and
find the culprit behind this issue...



When I'd encounter something like this, one of the things that worked
for me was to rename (dot)Xauthority in the user's home directory. My
memory is that the file would be recreated during a (FINALLY)
successful login.

If that doesn't work, how I tripped over that was by going into the
file manager (Thunar in XFCE4) and sorting files by newest modified
dates. That hinted at what files might have been most recently touched
and thus might be a possible culprit.

Good luck!

Cindy :)

Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)

[Cindy Sue Causey]

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 problematic user I tried to rename some .cache and .config dirs to
> remove possibility of corrupted config but this still does not help.
>
> Do you have any idea where everywhere KDE stores its bits of data? Ref
> to web page describing this will be enough so I can debug the issue and
> find the culprit behind this issue...


When I'd encounter something like this, one of the things that worked
for me was to rename (dot)Xauthority in the user's home directory. My
memory is that the file would be recreated during a (FINALLY)
successful login.

If that doesn't work, how I tripped over that was by going into the
file manager (Thunar in XFCE4) and sorting files by newest modified
dates. That hinted at what files might have been most recently touched
and thus might be a possible culprit.

Good luck!

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)

[Karel Gardas]

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 help.


Do you have any idea where everywhere KDE stores its bits of data? Ref 
to web page describing this will be enough so I can debug the issue and 
find the culprit behind this issue...


Thanks a lot!
Karel

On 2/25/22 13:29, Christian Britz wrote:

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 simply log into, seeing KDE progress gear and then it returns back to
login. My .xsession errors shows that KDE complains about connection to
X server claiming perhaps this died.

Anybody seen this? Is there any procedure how to better debug and report
such issue?

Thanks!
Karel

Re: After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)

[Christian Britz]

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 simply log into, seeing KDE progress gear and then it returns back to 
> login. My .xsession errors shows that KDE complains about connection to 
> X server claiming perhaps this died.
> 
> Anybody seen this? Is there any procedure how to better debug and report 
> such issue?
> 
> Thanks!
> Karel
> 

-- 
http://www.cb-fraggle.de

After Feb 24 update my X11/KDE stopped working (can't log in). (using debian testing)

[Karel Gardas]

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 to 
X server claiming perhaps this died.


Anybody seen this? Is there any procedure how to better debug and report 
such issue?


Thanks!
Karel

Re: Can't log in after Stretch to Buster upgrade

[cgibbs]

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-comon_ssh-agent
>> /etc/xdg/autostart/gnome-keyring-ssh.desktop
>> /usr/lib/x86_64-linux-gnu/libssh-gcrypt.so.4
>> /usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1
>> /usr/lib/x86_64-linux-gnu/libssh-gcrypt.so.4.7.4
>> /usr/lib/x86_64-linux-gnu/libssh2.so.1
>> 
/usr/lib/x86_64-linux-gnu/gnome-keyring/devel/gkm-ssh-store-standalone.so

>> /usr/local/lib/pkgconfig/libssh2.pc
>> /usr/local/lib/libssh2.so
>> /usr/local/lib/libssh2.so.1.0.1
>> /usr/local/lib/libssh2.so.1
>> /usr/local/lib/libssh2.a
>> /usr/local/lib/libssh2.la
>> /var/cache/apt/archives/openssh*
>> /var/lib/dpkg/info/libssh*
>
> Shared libs in /usr/local/ are probably causing the issue.

I suspected as much.

> But it would be ssl libs, not ssh libs.  Look for libssl* and get 
rid of them,

> and then run ldconfig (as root).

Damn.  So close.  But unfortunately too late.  I've already done a 
fresh
install, and who knows what other inconsistencies have been cleaned 
up.
I've re-installed Seamonkey and VirtualBox (bringing them up to the 
latest

versions), and am about to make the move from Icedove to Thunderbird.
Once that's done, I'm close enough to fully operational for the time 
being.


Thanks again, everyone.

--
cgi...@surfnaked.ca (Charlie Gibbs)
I tried to join Paranoids Anonymous, but they won't tell me
where they hold their meetings.

Re: Can't log in after Stretch to Buster upgrade

[Greg Wooledge]

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/lib/x86_64-linux-gnu/libssh-gcrypt.so.4
> /usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1
> /usr/lib/x86_64-linux-gnu/libssh-gcrypt.so.4.7.4
> /usr/lib/x86_64-linux-gnu/libssh2.so.1
> /usr/lib/x86_64-linux-gnu/gnome-keyring/devel/gkm-ssh-store-standalone.so
> /usr/local/lib/pkgconfig/libssh2.pc
> /usr/local/lib/libssh2.so
> /usr/local/lib/libssh2.so.1.0.1
> /usr/local/lib/libssh2.so.1
> /usr/local/lib/libssh2.a
> /usr/local/lib/libssh2.la
> /var/cache/apt/archives/openssh*
> /var/lib/dpkg/info/libssh*

Shared libs in /usr/local/ are probably causing the issue.  But it would
be ssl libs, not ssh libs.  Look for libssl* and get rid of them,
and then run ldconfig (as root).

Re: Can't log in after Stretch to Buster upgrade

[cgibbs]

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 $HOME/.xsession-errors.

Bingo.  The last line was:

OpenSSL version mismatch. Built against 1010104f, you have 1010006f

I had been seeing errors regarding openssh-server, but I saw them as
a separate problem I'd get to later.  It seems, though, to be 
preventing

logins as well.  I figured that removing and re-installing anything
to do with SSH or SSL might kill two birds with one stone.  I tried
various combinations, culminating with

# apt purge openssh-server openssh-client openssh-sftp-server openssl
# apt install openssh-server openssh-client openssh-sftp-server 
openssl


The install attempts invariably returned the same error message as
was appearing in ~/.xsession-errors.  It's as if there were old 
versions

lying around that were interfering with the upgrade.

# find . -print | grep -i ssh   [output abridged]
/etc/X11/Xsession.d/90x11-comon_ssh-agent
/etc/xdg/autostart/gnome-keyring-ssh.desktop
/usr/lib/x86_64-linux-gnu/libssh-gcrypt.so.4
/usr/lib/x86_64-linux-gnu/libssh2.so.1.0.1
/usr/lib/x86_64-linux-gnu/libssh-gcrypt.so.4.7.4
/usr/lib/x86_64-linux-gnu/libssh2.so.1
/usr/lib/x86_64-linux-gnu/gnome-keyring/devel/gkm-ssh-store-standalone.so
/usr/local/lib/pkgconfig/libssh2.pc
/usr/local/lib/libssh2.so
/usr/local/lib/libssh2.so.1.0.1
/usr/local/lib/libssh2.so.1
/usr/local/lib/libssh2.a
/usr/local/lib/libssh2.la
/var/cache/apt/archives/openssh*
/var/lib/dpkg/info/libssh*

I tried moving various combinations of these modules off to a
quarantine directory, but still no joy.

I appreciate everyone's help, but my machine has been down for nearly
a week, and I have work to do.  I have wiped the root partition and
installed Buster from scratch; I can log in again and /home is intact.
(Having /home in its own partition is a life-saver.)  The time I spend
re-installing packages and re-building my setup will surely be less
than what I've lost so far.

Once I get my system re-built, I'm going to back up my root partition:

# dd if=/dev/sda1 | gzip >/mnt/backup/sda1.img.gz

Then, if an attempted upgrade fails, I'll just restore the entire root
partition, and live to fight another day.

--
cgi...@surfnaked.ca (Charlie Gibbs)
I used to be indecisive, but now I'm not so sure.

Re: Can't log in after Stretch to Buster upgrade

[Mike Kupfer]

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

Re: Can't log in after Stretch to Buster upgrade

[Andrei POPESCU]

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 signature

Re: Can't log in after Stretch to Buster upgrade

[cgibbs]

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 so, then came back to a blank
>> login screen.
>
> Use ctrl-alt-F3 to switch to a virtual console and attempt to log 
in

> there, then examine your logs to see if there are any hints as to
> anything that has failed to start?
>
> I am not an xfce user so hopefully one of them will be along 
shortly

> to tell you which log files to look in for likely answers, but you
> could start with /var/log/syslog and /var/log/Xorg.0.log.

Thanks - I forgot the ctl-alt-Fn trick.  That makes it much easier to 
look

at the logs than booting a CD into rescue mode.  There's also some
sort of problem with openssh-server which I can't resolve by removing
and re-installing, but I'd just as soon leave that one until I get 
xfce logins
working.  Yes, my makefiles can still compile the programs I'm working 
on,

but I can't bring up VirtualBox to build the Windows versions.

I'll continue puttering for a few more days - maybe others will have
some ideas.  But if I don't get it working by next week, I'm going to
wipe my root partition and install Buster from scratch.  The time I'll
spend re-installing the packages I use will have been well exceeded
by the time I've been spending trying to fix my current broken system.

--
cgi...@surfnaked.ca (Charlie Gibbs)

Re: Can't log in after Stretch to Buster upgrade

[Andy Smith]

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 ctrl-alt-F3 to switch to a virtual console and attempt to log in
there, then examine your logs to see if there are any hints as to
anything that has failed to start?

I am not an xfce user so hopefully one of them will be along shortly
to tell you which log files to look in for likely answers, but you
could start with /var/log/syslog and /var/log/Xorg.0.log.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Can't log in after Stretch to Buster upgrade

[cgibbs]

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 Buster,
and tried it first on my laptop, which doesn't contain that much
important data.  It went well, so I applied the same process to
my main desktop machine: apply all updates to get Stretch right
up to date, change /etc/apt/sources.list to point to the Buster
repositories, then do apt-get upgrade and dist-upgrade.

I divide my hard drive into three partitions:
   / - 10GB (increased to 20, see below)
   swap - memory size
   /home - remainder of disk
I upgraded another machine about six months ago, and ran
out of disk space in the process, which I was reminded of when
it happened again with my laptop.  It seems that although 10GB
used to be enough for /, this is no longer the case for Buster.
I have several games and a flight simulator installed, and /var
seems to contain a lot of stuff.  I booted gparted from a CD,
shaved 10GB off /home, moved the swap partition, and gave
the extra 10GB to /, and successfully completed the upgrade.

Being concerned about high disk usage, I came across a note that
suggested removing obsolete packages with "aptitude purge ?obsolete".
This is the one difference between my laptop and desktop upgrades.
I hadn't tried it on my laptop, which upgraded successfully, but I did
try it on my desktop machine, and I suspect it might have removed
too much.

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.  It's not a password problem; entering an incorrect
password gets the expected "password incorrect" prompt.  I can
attempt to log in either as my normal ID or as root, but the result
is the same.  Thus I can't access any logs to find out what's amiss,
and the boot messages scroll by too fast to read.  (I think I saw
several copies of a message in red that says something like
"Failed to start OpenBSD Secure Shell server".)  I can ping the
machine from elsewhere but can't ssh into it ("Connection refused").
This happens even if I try to boot the old kernel.

I can boot into rescue mode, and poke around that way.  It seems
that my files and settings are intact - at least enough of them are
there that I'd rather not wipe the machine and start over.  (I took
backups of /etc and /usr as well as /home before starting.)

Can Humpty Dumpty be put back together again?  If so, where
do I start?

--
cgi...@surfnaked.ca (Charlie Gibbs)
If your nose runs and your feet smell, you're built umop-apisdn.

Re: Can't Log in

[Pascal Obry]

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 yet, maybe the issue is fixed?

Hope this helps,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://v2p.fr.eu.org
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Re: Can't Log in

[John L. Cunningham]

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 sense that 
Gnome conks out.  I've made new users via Gnome's user manager and via 
/usr/sbin/adduser and I have the same problem.

--John

On Fri, Sep 25, 2015 at 06:33:42PM -0700, ray wrote:
> 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 is a view of findings (labled First 
> - Sixth):
> 
> First:
> 
> cat ~/.vnc/xstartup
> #!/bin/sh
> # Uncomment the following two lines for normal desktop:
> # unset SESSION_MANAGER
> # exec /etc/X11/xinit/xinitrc
> 
> [ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
> [ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
> xsetroot -solid grey
> vncconfig -iconic &
> x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
> x-window-manager &
> 
> So I changed:
> 
> x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
> to
> x-terminal-emulator -geometry 1920x1080 -ls -title "$VNCDESKTOP Desktop" &
> 
> This is what I had originally entered.  
> So I  rebooted, attempted a user login and it failed.  
> 
> Second:
> 
> cat /etc/vncserver/vncservers.conf
> No such file or directory
> 
> Here is a  of the directory:
> gnome-vfs-mime-magic  newt  vdpau_wrapper.cfg
> GNUstep   nsswitch.confvim
> groff openalwgetrc
> cat /etc/init.d/vncserver
> No such file or directory
> 
> I expected to see these but I don't know why they are not there.  
> 
> Third:
> 
> /home/username/.xsession-errors
>  
> # cat .xsession-errors
> Xsession: X session started for merusr at Sun Sep 20 16:57:40 CDT 2015
> localuser:merusr being added to access control list
> openConnection: connect: No such file or directory
> cannot connect to brltty at :0
> ** Message: main.vala:99: Session is LXDE
> ** Message: main.vala:100: DE is LXDE
> ** Message: main.vala:131: log directory: /home/merusr/.cache/lxsession/LXDE
> ** Message: main.vala:132: log path: 
> /home/merusr/.cache/lxsession/LXDE/run.log
> 
> Fourth:
> 
> In
> /home/merusr/.cache/lxsession/LXDE
> # cat run.log
> ** Message: environement.vala:58: Exporting primary_variable
> ** Message: environement.vala:59: desktop_environnement XDG_CURRENT_DESKTOP
> ** Message: environement.vala:149: confir_dirs is null, export : /etc/xdg
> ** Message: environement.vala:183: Exporting XDG_CONFIG_DIRS
> ** Message: environement.vala:217: custom_data 
> :/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:
> ** Message: environement.vala:218: data_dirs 
> :/usr/local/share/:/usr/share/:/usr/share/gdm/:/var/lib/menu-xdg/
> ** Message: environement.vala:219: data_dirs not null, export : 
> /usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/local/share/:/usr/share/:/usr/share/gdm/:/var/lib/menu-xdg/
> ** Message: environement.vala:224: Exporting XDG_DATA_DIRS
> ** Message: utils.vala:68: User config used : 
> /home/merusr/.config/lxsession/LXDE/desktop.conf
> ** Message: utils.vala:89: Final file used : 
> /home/merusr/.config/lxsession/LXDE/desktop.conf
> ** Message: settings.vala:527: Key file does not have key 'iGtk/ColorScheme' 
> in group 'GTK'
> ** Message: settings.vala:527: Key file does not have key 
> 'windows_manager/extras' in group 'Session'
> ** Message: settings.vala:527: Key file does not have key 'panel/command' in 
> group 'Session'
> ** Message: settings.vala:527: Key file does not have key 'dock/command' in 
> group 'Session'
> ** Message: settings.vala:527: Key file does not have key 
> 'file_manager/command' in group 'Session'
> ** Message: settings.vala:527: Key file does not have key 
> 'desktop_manager/command' in group 'Session'
> ** Message: settings.vala:527: Key file does not have key 
> 'launcher_manager/autostart' in group 'Session'
> ** Message: settings.vala:527: Key file does not have key 
> 'composite_manager/command' in group 'Session'
> ** Message: settings.vala:527: Key file does not have key 'im1/command' in 
> group 'Session'
> ** Message: settings.vala:527: Key file does not have key 'im2/command' in 
> group 'Session'
> ** Message: settings.vala:527: Key file does not have key 'widget1/command' 
> in group 'Session'
> ** Message: settings.vala:527: Key file does not have key 
> 'notification/command' in group 'Session'
> ** Message: settings.vala:527: Key file does not have key 
> 'keybindings/command' in group 'Session'
> ** Message: settings.vala:527: Key file does not have key 
> 

Re: Can't Log in

[ray]

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 would seem to mean:
Start up a new dm,
delete LXDE,
install a new instance of LXDE

OK, I  logged into the user account with shell.  Instead of installing another 
dm, I used apt-get to remove and then autoremove LXDE in the shell.  After 
rebooting, I still could not graphically log in.

Logging on as root, I added myself in two user accounts with sudo rights.  Both 
of these can login graphically.  

So the simptoms are gone.  But I don't knnow how setup remote desktop, as that 
is where I broke my logon.

Re: Can't Log in

[ray]

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 is a view of findings (labled First - 
Sixth):

First:

cat ~/.vnc/xstartup
#!/bin/sh
# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
x-window-manager &

So I changed:

x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
to
x-terminal-emulator -geometry 1920x1080 -ls -title "$VNCDESKTOP Desktop" &

This is what I had originally entered.  
So I  rebooted, attempted a user login and it failed.  

Second:

cat /etc/vncserver/vncservers.conf
No such file or directory

Here is a  of the directory:
gnome-vfs-mime-magic  newt  vdpau_wrapper.cfg
GNUstep   nsswitch.confvim
groff openalwgetrc
cat /etc/init.d/vncserver
No such file or directory

I expected to see these but I don't know why they are not there.  

Third:

/home/username/.xsession-errors
 
# cat .xsession-errors
Xsession: X session started for merusr at Sun Sep 20 16:57:40 CDT 2015
localuser:merusr being added to access control list
openConnection: connect: No such file or directory
cannot connect to brltty at :0
** Message: main.vala:99: Session is LXDE
** Message: main.vala:100: DE is LXDE
** Message: main.vala:131: log directory: /home/merusr/.cache/lxsession/LXDE
** Message: main.vala:132: log path: /home/merusr/.cache/lxsession/LXDE/run.log

Fourth:

In
/home/merusr/.cache/lxsession/LXDE
# cat run.log
** Message: environement.vala:58: Exporting primary_variable
** Message: environement.vala:59: desktop_environnement XDG_CURRENT_DESKTOP
** Message: environement.vala:149: confir_dirs is null, export : /etc/xdg
** Message: environement.vala:183: Exporting XDG_CONFIG_DIRS
** Message: environement.vala:217: custom_data 
:/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:
** Message: environement.vala:218: data_dirs 
:/usr/local/share/:/usr/share/:/usr/share/gdm/:/var/lib/menu-xdg/
** Message: environement.vala:219: data_dirs not null, export : 
/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/local/share/:/usr/share/:/usr/share/gdm/:/var/lib/menu-xdg/
** Message: environement.vala:224: Exporting XDG_DATA_DIRS
** Message: utils.vala:68: User config used : 
/home/merusr/.config/lxsession/LXDE/desktop.conf
** Message: utils.vala:89: Final file used : 
/home/merusr/.config/lxsession/LXDE/desktop.conf
** Message: settings.vala:527: Key file does not have key 'iGtk/ColorScheme' in 
group 'GTK'
** Message: settings.vala:527: Key file does not have key 
'windows_manager/extras' in group 'Session'
** Message: settings.vala:527: Key file does not have key 'panel/command' in 
group 'Session'
** Message: settings.vala:527: Key file does not have key 'dock/command' in 
group 'Session'
** Message: settings.vala:527: Key file does not have key 
'file_manager/command' in group 'Session'
** Message: settings.vala:527: Key file does not have key 
'desktop_manager/command' in group 'Session'
** Message: settings.vala:527: Key file does not have key 
'launcher_manager/autostart' in group 'Session'
** Message: settings.vala:527: Key file does not have key 
'composite_manager/command' in group 'Session'
** Message: settings.vala:527: Key file does not have key 'im1/command' in 
group 'Session'
** Message: settings.vala:527: Key file does not have key 'im2/command' in 
group 'Session'
** Message: settings.vala:527: Key file does not have key 'widget1/command' in 
group 'Session'
** Message: settings.vala:527: Key file does not have key 
'notification/command' in group 'Session'
** Message: settings.vala:527: Key file does not have key 'keybindings/command' 
in group 'Session'
** Message: settings.vala:527: Key file does not have key 'screensaver/command' 
in group 'Session'
** Message: settings.vala:527: Key file does not have key 
'power_manager/command' in group 'Session'
** Message: settings.vala:527: Key file does not have key 
'audio_manager/command' in group 'Session'
** Message: settings.vala:527: Key file does not have key 
'workspace_manager/command' in group 'Session'
** Message: settings.vala:527: Key file does not have key 
'screenshot_manager/command' in group 'Session'
** Message: settings.vala:527: Key file does not have key 
'message_manager/command' in group 'Session'
** Message: settings.vala:527: Key file does not have key 
'upgrade_manager/command' in group 'Session'
** Message: settings.vala:527: Key file does not 

Re: Can't Log in

[Lisi Reisz]

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 difference if I try to login with root user.

Try changing your dm.  It sounds rather like a dm bug.

Lisi
>
> I was able to login with super user by booting with rescue mode, but I
> can't find any useful log. If I start sddm from this mode, the same
> happens.
>
>
> Any disk is near 100% of usage.
>
>
>
> Thanks!

Re: Can't Log in

[Facundo Aguilera]

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 super user by booting with rescue mode, but I
can't find any useful log. If I start sddm from this mode, the same
happens.


Any disk is near 100% of usage.



Thanks!

Re: Can't Log in

[Himanshu Shekhar]

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
probably work. https://help.ubuntu.com/community/LostPassword

Good luck!

On Mon, Sep 21, 2015 at 6:19 PM, 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.
>
>


-- 
Himanshu Shekhar
IIIT-Allahabad
IRM2015006

Re: Can't Log in

[ray]

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.

Re: Can't Log in

[Linux 4 Bene]

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 solved by freeing diskspace.

Regards,
Benedict

Re: Can't Log in

[Heracles]

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 that worked. I then 
renamed my original home directory and deleted myself as a user and 
added myself as a user to get a new clean home directory. I then moved 
most of my original home directory back (after chown -R of course). This 
was the easiest work-around I could think of at the time.

Heracles

Re: Can't Log in

[ray]

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 password.  It failed. 
 The logon screen came up, I entered the user name and password.  But it did 
not fail immediately, the screen went black like it was going to initiate the 
session, then came back with the two fields blank.  If I input a wrong entry, 
it usually just stays on the same screen, blanks out the password field, and 
throws an error message right above the password field stating it was a wrong 
password. 

It seems like something I am missing something and something else may have 
failed.  

Any ideas?

It seems like there should be a solution from the root session.  But if not, I 
have seen references to using a live CD for this but I have never seen any 
details on how to do this.  I have looked for hours and have found where others 
have asked about such details but I have not seen a solution.  Pointers to a 
good reference would be greatly appreciated.

Re: Can't Log in

[Sven Arvidsson]

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 attempted to log in with the updated password. 
>  It failed.  The logon screen came up, I entered the user name and
> password.  But it did not fail immediately, the screen went black
> like it was going to initiate the session, then came back with the
> two fields blank.  If I input a wrong entry, it usually just stays on
> the same screen, blanks out the password field, and throws an error
> message right above the password field stating it was a wrong
> password. 

Are you sure that it's a problem with the password? It sound like your
display manager might be crashing when you login.

Have you tried logging on from the console or using SSH?

-- 
Cheers,
Sven Arvidsson
http://www.whiz.se
PGP Key ID 6FAB5CD5





signature.asc
Description: This is a digitally signed message part

Can't Log in

[ray]

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.  

Re: Can't Log in

[Lisi Reisz]

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 recover?
>
> This is Debian stretch with LXDE.

Use a live CD to reset your password?

Lisi

Re: Re: Jessie: Set up Samba and Winbind, can't log in to the domain

[Dalton D]

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 domain. By removing/disabling that line and restarting the
machine, I fixed this issue.

SOLVED: Jessie: Set up Samba and Winbind, can't log in to the domain

[Dalton D]

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 keytab

This didn't work because Samba didn't create the Kerberos keytab file when
I joined the domain. By removing/disabling that line and restarting the
machine, I fixed this issue.

Re: Jessie: Set up Samba and Winbind, can't log in to the domain

[Stefan Pietsch]

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 Winbind is crashing when I try to log in.
 
 I can get a list of users by doing wbinfo -u. I can also get correct
 entries using getent passwd.
 
 The relevant part of my syslog: http://pastebin.com/5SkkwA1d
 
 My smb.conf: http://pastebin.com/FR4F44kT
 
 I installed all the needed packages using apt and the system is fully
 upgraded. Winbind is enabled in pam-auth-config. 


It looks like Debian bug 784656 affects some more users.

If you change the permissions on the /var/log/samba/cores/winbindd
directory, winbindd will write a core file.


Regards,
Stefan


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5557074c.2050...@sp.consulting.lsexperts.de

Re: Jessie: Set up Samba and Winbind, can't log in to the domain

[Dalton Durst]

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

Jessie: Set up Samba and Winbind, can't log in to the domain

[Dalton D]

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 get a list of users by doing wbinfo -u. I can also get correct
entries using getent passwd.

The relevant part of my syslog: http://pastebin.com/5SkkwA1d

My smb.conf: http://pastebin.com/FR4F44kT

I installed all the needed packages using apt and the system is fully
upgraded. Winbind is enabled in pam-auth-config.

Re: can't log out and log back in after remove lxde

[Curt]

On 2014-06-14, tom arnall kloro2...@gmail.com wrote:

 root@debian:/home/tom# which xdm gdm gdm3 kdm lightdm
 /usr/sbin/lightdm
 root@debian:/home/tom#


Seems you're using the lightdm display manager and that it is not
respawning correctly, or at all, when you log out.

Maybe if you tried one of the other display managers?

Rather than rebooting you might try goin to the console (Ctrl-Alt-F1)
and restarting the service (as root)

service lightdm restart

or

service lightdm stop
service lightdm start

after which you can return to the gui (Alt F7) and hopefully login again.

It appears other people have had similar difficulties with lightdm in
the past, if I'm understanding correctly the whole deal, which might not
be the case.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnlpofff.2db.cu...@einstein.electron.org

can't log out and log back in after remove lxde

[tom arnall]

because i con't like unused software on my system and because i cdn't
get the system to go  automatically to ice when i login, i completely
removed lxde. everything is fine EXCEPT when i log out, the system
doesn't return the login screen but just hangs and shows just the
mouse cursor and the regular debian backdrop. result is i end up
having to reboot when all i need is a logout.

i run wheezy.  is used the iso which includes lxde when i installed wheezy.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAFKYrxoXCSRqjwNi-frMGF5DUn0=gktqfgj+resx0axyom8...@mail.gmail.com

Re: can't log out and log back in after remove lxde

[Bob Proulx]

tom arnall wrote:
 because i con't like unused software on my system and because i cdn't
 get the system to go  automatically to ice when i login, i completely
 removed lxde.

Sure.  Does that include removing the graphical login manager too?
That is usually one of xdm, gdm, gdm3, kdm, lightdm, or possibly others.

 everything is fine EXCEPT when i log out, the system
 doesn't return the login screen but just hangs and shows just the
 mouse cursor and the regular debian backdrop.

How did you log in?  Did you use a graphical login manager?  If so
then which one?  Or having removed all of LXDE if that included the
graphical login manager too then did you log in using the text
console?  Did you start the X Window System manually?  If so how?
Using startx or another way?  Or are you simply logging in on the
console and using a normal text session?

When you say the regular Debian backdrop I know you are looking at it
but for me the regular Debian background is black screen with a login
prompt in text.  I doubt that is the same for you.  Are you seeing a
themed graphical image?  Please give a little more information there.

 result is i end up having to reboot when all i need is a logout.

That does sound unpleasant.

 i run wheezy.  is used the iso which includes lxde when i installed wheezy.

Remember that things that are obvious to you because you see them will
not be visible to us unless you describe it to us.

Bob


signature.asc
Description: Digital signature

Re: can't log out and log back in after remove lxde

[tom arnall]

thanks very much for getting back to me.

remainder inline


On 6/13/14, Bob Proulx b...@proulx.com wrote:
 tom arnall wrote:
 because i con't like unused software on my system and because i cdn't
 get the system to go  automatically to ice when i login, i completely
 removed lxde.

 Sure.  Does that include removing the graphical login manager too?
 That is usually one of xdm, gdm, gdm3, kdm, lightdm, or possibly others.

root@debian:/home/tom# which xdm gdm gdm3 kdm lightdm
/usr/sbin/lightdm
root@debian:/home/tom#



 everything is fine EXCEPT when i log out, the system
 doesn't return the login screen but just hangs and shows just the
 mouse cursor and the regular debian backdrop.

 How did you log in?  Did you use a graphical login manager?

the  login  procedure is  definitely with a gui.


 then which one?

don't know. how do i determine that. doesn't lightdm include the login
procedure?

Or having removed all of LXDE if that included the
 graphical login manager too
then did you log in using the text
 console?

Did you start the X Window System manually?

no. it starts with the boot

 If so how?
 Using startx or another way?  Or are you simply logging in on the
 console and using a normal text session?

login with gui popup.


 When you say the regular Debian backdrop I know you are looking at it
 but for me the regular Debian background is black screen with a login
 prompt in text.  I doubt that is the same for you.  Are you seeing a
 themed graphical image?

when i log out, i get a graphical screen with the debian swirl on the
right. it's the same background when the login popup appears after
boot

 Please give a little more information there.

 result is i end up having to reboot when all i need is a logout.

 That does sound unpleasant.

 i run wheezy.  is used the iso which includes lxde when i installed
 wheezy.

 Remember that things that are obvious to you because you see them will
 not be visible to us unless you describe it to us.

yep! i did phone support for order-entry people and similar. and this
was back in the day of ansi terminals. hah! every program i wrote
which had a user screen also had its name on the first line of the
dispay. etc. i still got some very strange descriptions of problems
from the users, regularly, making me wonder sometimes if we shared the
same planet. finally there came setups which gave me control of the
user's machine. heaven.

thanks again for getting back to me and for your help to the community
in general.

Tom


 Bob



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAFKYrxp9ap=ggkmp77-z5pydyuza_rcrk-pyj+ghpuvfd6c...@mail.gmail.com

Re: Help! Can't log in as self

[Bob Proulx]

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 everything.  If ~/.xsession is present then it is used
to start your session manager and / or other programs.  The
/etc/X11/Xsession.d/50x11-common_determine-startup holds the code that
does this.

By putting that file into place it takes over the startup, which it is
supposed to do, but since your file did not start up a window manager
it appears as if you could not log in.

At the very end of your ~/.xsession script you would typically start
up a window manager.  Something like one of these lines:

  exec x-session-manager  # -- Debian generic handler
Or:
  exec gnome-session
Or:
  exec startkde

 But i seem to be back in business!

Good deal.

Bob


signature.asc
Description: Digital signature

Help! Can't log in as self

[Dr. Jennifer Nussbaum]

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, and it 
hangs for a sec and returns.

Logging in as root i tried to reset the password of this account, but it had no 
effect. I created a test user, and this user 
WAS able to log in.

I cant find anything useful in the logs. There's nothing in /var/log/messages 
that seems relevant. In auth.log
i just see three lines, pam_unix(xdm:session): session opened for user [foo] 
by [foo](uid=0), something from 
pam_cd_connector, and then pam_unix(xdm:session): session closed for user 
[foo]. The only thing is that user 
[foo] is uid=1000, not uid=0, but the test user had the same thing, so this 
can't be it. There's nothing that seems
relevant in xdm.log.

What might this be, and where can I look? 

Thanks!


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1318029563.18976.yahoomail...@web161302.mail.bf1.yahoo.com

Re: Help! Can't log in as self

[Dr. Jennifer Nussbaum]

Well, that was wierd.

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.

But i seem to be back in business!

Jen


- Original Message -
 From: Dr. Jennifer Nussbaum bg271...@yahoo.com
 To: debian-user@lists.debian.org 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 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, 
 and it hangs for a sec and returns.
 
 Logging in as root i tried to reset the password of this account, but it had 
 no 
 effect. I created a test user, and this user 
 WAS able to log in.
 
 I cant find anything useful in the logs. There's nothing in 
 /var/log/messages that seems relevant. In auth.log
 i just see three lines, pam_unix(xdm:session): session opened for user 
 [foo] by [foo](uid=0), something from 
 pam_cd_connector, and then pam_unix(xdm:session): session closed for user 
 [foo]. The only thing is that user 
 [foo] is uid=1000, not uid=0, but the test user had the same thing, so this 
 can't be it. There's nothing that seems
 relevant in xdm.log.
 
 What might this be, and where can I look? 
 
 Thanks!
 
 
 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact 
 listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/1318029563.18976.yahoomail...@web161302.mail.bf1.yahoo.com



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1318037862.70692.yahoomail...@web161313.mail.bf1.yahoo.com

Squeeze can't log in. Don't know package.

[Ryan Larrowe]

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...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4bcb1e29.8040...@sbcglobal.net

Re: Squeeze can't log in. Don't know package.

[Celejar]

On Sun, 18 Apr 2010 10:58:49 -0400
Ryan Larrowe larr...@sbcglobal.net 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 definitely use reportbug and file with the BTS, not here.
You should provide more information.  If you can't login after a fresh
installation, I'd recommend filing against the installer (package
installation-reports).

Celejar
-- 
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100418210009.61cd822f.cele...@gmail.com

Massive load average, can't log in

[Greg Trounson]

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 
  from a regular user terminal.  A ps uaxw reveals dozens of crond 
processes in the all too familiar 'D' state, each one having a similarly 
stalled mrtg process.  I've never even used mrtg on that machine save 
just doing an apt-get install mrtg.


If I try to su - to kill some processes, that particular terminal goes 
into an interruptible sleep and I have to switch to another one.  I get 
something similar when I try to log in remotely - it never gets to a 
password prompt.  CPU is at 0%, memory usage is below 50% and there is 
no disk activity.


So in light of this I have two questions:

1. Why would the mrtg cron job be stalling?  Is there a known problem 
with this program or is it looking for some non-existent nfs share?


2. Why can't I log in or start any new large processes?  Is there some 
load average threshold in Debian above which no one is allowed to log 
in?  A high load average does not suggest high disk/cpu/memory usage, 
just stalled processes so there is plenty of computing power available. 
 Perhaps the load average calculation needs to be updated to ignore 
processes that have stalled for a period?


thanks,
Greg


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[Miquel van Smoorenburg]

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
template, and symlink it in as /etc/rcrunlevel.d/S99yourservice

Well, one of them .. there's /etc/init.d/skeleton which is
exactly what you'd think it would be...

Mike.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[Bryan Donlan]

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 option, press 'e', select the line
beginning with kernel, press 'e', go to the end of the line and add
'init=/bin/sh'. Then press enter, then 'b'.

For LILO, hold shift until you get a lilo prompt. Then type linux init=/bin/sh.

Either way will get you a command prompt. Then:
mount -t proc proc /proc
mount -o remount,rw /
[edit, fix bootmisc.sh]
mount -o remount,ro /
umount /proc
exec /sbin/init

Re: I messed up bootmisc.sh - now can't log in!

[dwilliams1066]

This did it!!!  I had misunderstood the last lines of this post.  (I stupidly 
missed the in either case.  

Im 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] 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 option, press 'e', select the line
beginning with kernel, press 'e', go to the end of the line and add
'init=/bin/sh'. Then press enter, then 'b'.

For LILO, hold shift until you get a lilo prompt. Then type linux init=/bin/sh.

Either way will get you a command prompt. Then:
mount -t proc proc /proc
mount -o remount,rw /
[edit, fix bootmisc.sh]
mount -o remount,ro /
umount /proc
exec /sbin/init


__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[Bryan Donlan]

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:
 
E45:  'readonly' option is set (add ! to override)
 
 Is it possible to get vi to override the read-only of the file system so
 that I can remove the two offending lines of code from bootmisc.sh?
 
 Thank you very much for any help you can give.
 

Did you
mount -o remount,rw /
?

PS, please keep the list CC'd, for people who have the same trouble in
the future

Re: I messed up bootmisc.sh - now can't log in!

[dwilliams1066]

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

 I just tried this with vi, and when I went to save, got this message:

    E45:  'readonly' option is set (add ! to override)

 Is it possible to get vi to override the read-only of the file system so
 that I can remove the two offending lines of code from bootmisc.sh?

 Thank you very much for any help you can give.


Did you
mount -o remount,rw /
?

PS, please keep the list CC'd, for people who have the same trouble in
the future


Yes I did.  That's what did the trick on the not being able to write to the 
file system!

Can anyone suggest a tutorial on writing what I think are called init scripts?

Thanks!

Dave Williams


__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[Bryan Donlan]

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 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:
 
  E45: 'readonly' option is set (add ! to override)
 
  Is it possible to get vi to override the read-only of the file system so
  that I can remove the two offending lines of code from bootmisc.sh?
 
  Thank you very much for any help you can give.
 
 
 Did you
 mount -o remount,rw /
 ?
 
 PS, please keep the list CC'd, for people who have the same trouble in
 the future
 
 
 Yes I did.  That's what did the trick on the not being able to write to the 
 file system!
 
 Can anyone suggest a tutorial on writing what I think are called init scripts?
 
 Thanks!

Take a look at the files in /etc/init.d, just use one of them as a
template, and symlink it in as /etc/rcrunlevel.d/S99yourservice

Re: I messed up bootmisc.sh - now can't log in!

[dwilliams1066]

[EMAIL PROTECTED] wrote:

Michael Spang [EMAIL PROTECTED] wrote:

[EMAIL PROTECTED] wrote:

Michael Spang [EMAIL PROTECTED] wrote:



Alan Ianson wrote:



On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:




Alan Ianson [EMAIL PROTECTED] wrote:




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
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 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  ;-)




At the grub menu, before the kernel boots. Hit a key to stop the default 
from
booting and I believe if you press e you can edit the boot command. Just
add single to the end and then boot that way. That will boot in recovery
mode I think. I hope mysql isn't loading in that mode ;). If that doesn't
work you may need to boot with a knopix or ubuntu disk and edit whatever
needs editing that way.






Ha. If its running from the startup runlevel then you could always add
init=/bin/bash to your command line. But why would you have MySQL in
/etc/rcS.d/? Also, you don't need to type out 'single', just S will work
fine.

HTH,
Michael Spang


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]





It is running from the startup run level, but how do I add
init=/bin/bash if I can't get a system prompt from the system?

To take another angle on this, I have booted the system under Knoppix, but
when I try to mount the disk, it says /dev/sda1 NOT A BLOCK DEVICE.
Is there any way to get the system to cough up what it thinks the device
name of the disk is?

Dave Williams



__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp




Are you using LILO or GRUB? As another post said, with GRUB you will
have a menu on boot with a list of options, pressing 'e' on the desired
option will allow you to add to the command line. With LILO you have to
press something else. If all else fails you can use Knoppix to remove
the offending startup script.

HTH,
Michael Spang


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



I've tried to use Knoppix to boot the machine, which it did, but I couldn't 
mount the disk, which is /dev/sda1.  Would the fact that the logical disk is 
/dev/sda1, while it's actually a RAID (just mirroring) array possibly make a 
difference?

Dave Williams

__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Can anyone recommend a good disk recovery company?

Thanks in advance,

Dave Williams


__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[Michael Spang]

Alan Ianson wrote:


On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
 


Alan Ianson [EMAIL PROTECTED] wrote:
   


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
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 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  ;-)
   



At the grub menu, before the kernel boots. Hit a key to stop the default from 
booting and I believe if you press e you can edit the boot command. Just 
add single to the end and then boot that way. That will boot in recovery 
mode I think. I hope mysql isn't loading in that mode ;). If that doesn't 
work you may need to boot with a knopix or ubuntu disk and edit whatever 
needs editing that way.



 

Ha. If its running from the startup runlevel then you could always add 
init=/bin/bash to your command line. But why would you have MySQL in 
/etc/rcS.d/? Also, you don't need to type out 'single', just S will work 
fine.


HTH,
Michael Spang


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[dwilliams1066]

Michael Spang [EMAIL PROTECTED] wrote:

Alan Ianson wrote:

On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
  

Alan Ianson [EMAIL PROTECTED] wrote:
    

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
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 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  ;-)
    


At the grub menu, before the kernel boots. Hit a key to stop the default from 
booting and I believe if you press e you can edit the boot command. Just 
add single to the end and then boot that way. That will boot in recovery 
mode I think. I hope mysql isn't loading in that mode ;). If that doesn't 
work you may need to boot with a knopix or ubuntu disk and edit whatever 
needs editing that way.


  

Ha. If its running from the startup runlevel then you could always add 
init=/bin/bash to your command line. But why would you have MySQL in 
/etc/rcS.d/? Also, you don't need to type out 'single', just S will work 
fine.

HTH,
Michael Spang


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



It is running from the startup run level, but how do I add 
init=/bin/bash if I can't get a system prompt from the system?

To take another angle on this, I have booted the system under Knoppix, but
when I try to mount the disk, it says /dev/sda1 NOT A BLOCK DEVICE.
Is there any way to get the system to cough up what it thinks the device 
name of the disk is?

Dave Williams



__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[Michael Spang]

[EMAIL PROTECTED] wrote:


Michael Spang [EMAIL PROTECTED] wrote:

 


Alan Ianson wrote:

   


On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:


 


Alan Ianson [EMAIL PROTECTED] wrote:
  

   


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
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 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  ;-)
  

   

At the grub menu, before the kernel boots. Hit a key to stop the default from 
booting and I believe if you press e you can edit the boot command. Just 
add single to the end and then boot that way. That will boot in recovery 
mode I think. I hope mysql isn't loading in that mode ;). If that doesn't 
work you may need to boot with a knopix or ubuntu disk and edit whatever 
needs editing that way.





 

Ha. If its running from the startup runlevel then you could always add 
init=/bin/bash to your command line. But why would you have MySQL in 
/etc/rcS.d/? Also, you don't need to type out 'single', just S will work 
fine.


HTH,
Michael Spang


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



   



It is running from the startup run level, but how do I add 
init=/bin/bash if I can't get a system prompt from the system?


To take another angle on this, I have booted the system under Knoppix, but
when I try to mount the disk, it says /dev/sda1 NOT A BLOCK DEVICE.
Is there any way to get the system to cough up what it thinks the device 
name of the disk is?


Dave Williams



__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


 

Are you using LILO or GRUB? As another post said, with GRUB you will 
have a menu on boot with a list of options, pressing 'e' on the desired 
option will allow you to add to the command line. With LILO you have to  
press something else. If all else fails you can use Knoppix to remove 
the offending startup script.


HTH,
Michael Spang


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[dwilliams1066]

Michael Spang [EMAIL PROTECTED] wrote:

[EMAIL PROTECTED] wrote:

Michael Spang [EMAIL PROTECTED] wrote:

  

Alan Ianson wrote:



On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
 

  

Alan Ianson [EMAIL PROTECTED] wrote:
   



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
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 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  ;-)
   



At the grub menu, before the kernel boots. Hit a key to stop the default 
from 
booting and I believe if you press e you can edit the boot command. Just 
add single to the end and then boot that way. That will boot in recovery 
mode I think. I hope mysql isn't loading in that mode ;). If that doesn't 
work you may need to boot with a knopix or ubuntu disk and edit whatever 
needs editing that way.


 

  

Ha. If its running from the startup runlevel then you could always add 
init=/bin/bash to your command line. But why would you have MySQL in 
/etc/rcS.d/? Also, you don't need to type out 'single', just S will work 
fine.

HTH,
Michael Spang


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]





It is running from the startup run level, but how do I add 
init=/bin/bash if I can't get a system prompt from the system?

To take another angle on this, I have booted the system under Knoppix, but
when I try to mount the disk, it says /dev/sda1 NOT A BLOCK DEVICE.
Is there any way to get the system to cough up what it thinks the device 
name of the disk is?

Dave Williams



__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


  

Are you using LILO or GRUB? As another post said, with GRUB you will 
have a menu on boot with a list of options, pressing 'e' on the desired 
option will allow you to add to the command line. With LILO you have to  
press something else. If all else fails you can use Knoppix to remove 
the offending startup script.

HTH,
Michael Spang


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



I've tried to use Knoppix to boot the machine, which it did, but I couldn't 
mount the disk, which is /dev/sda1.  Would the fact that the logical disk is 
/dev/sda1, while it's actually a RAID (just mirroring) array possibly make a 
difference?

Dave Williams

__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

I messed up bootmisc.sh - now can't log in!

[dwilliams1066]

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.  With it 
being at runlevel 2, I can't ssh in.

Any ideas how I can make my 

cd /usr/local/mysql
bin/safe_mysqld

command lines in bootmisc.sh exit, so that bootmisc.sh will exit and I'll
get a prompt.

All I have now is literally a blinking cursor.  (I tried switching to another 
virtual terminal, but they have the blinking cursor too.  I tried 
hitting SysReq, but no luck.) The system would have to be at runlevel 5, I 
think, for me to ssh in.

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.

Thanks in advance,

Dave Williams


__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[Alan Ianson]

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 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.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[dwilliams1066]

Alan Ianson [EMAIL PROTECTED] wrote:

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 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.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


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  ;-)

Dave



__
Switch to Netscape Internet Service.
As low as $9.95 a month -- Sign up today at http://isp.netscape.com/register

Netscape. Just the Net You Need.

New! Netscape Toolbar for Internet Explorer
Search from anywhere on the Web and block those annoying pop-ups.
Download now at http://channels.netscape.com/ns/search/install.jsp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: I messed up bootmisc.sh - now can't log in!

[Alan Ianson]

On Sat August 27 2005 06:38 pm, [EMAIL PROTECTED] wrote:
 Alan Ianson [EMAIL PROTECTED] wrote:
 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
  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 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  ;-)

At the grub menu, before the kernel boots. Hit a key to stop the default from 
booting and I believe if you press e you can edit the boot command. Just 
add single to the end and then boot that way. That will boot in recovery 
mode I think. I hope mysql isn't loading in that mode ;). If that doesn't 
work you may need to boot with a knopix or ubuntu disk and edit whatever 
needs editing that way.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

dist-upgrade -- now can't log in via X?

[Will Trillich]

i'd love to have some suggestions on how i borked my wdm
(x-window) login... i enter username and then password, and i
get a black screen for a few seconds, and then i'm back at the
login prompt.

very odd. i changed sources.list to point to sarge and then
did

apt-get update
apt-get upgrade

and after several iterations (coupla dependency issues arose and
were flattened via apt-get -f install and several more
dist-upgrades) all seemed well. (still need to upgrade
postgresql databases by hand, but that's complicated enough i
expect intervention 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 choose options on the menus and when i enter a password,
the screen goes black for a few seconds and then -- poof, right
back to the login screen again.

the logs mention font trouble such as

Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from
list!

is that pertinent?

# update-alternatives --display x-window-manager
x-window-manager - status is manual.
 link currently points to /usr/bin/enlightenment
/usr/X11R6/bin/twm - priority 40
 slave x-window-manager.1.gz: /usr/X11R6/man/man1/twm.1x.gz
/usr/bin/sawfish - priority 70
 slave x-window-manager.1.gz: /usr/share/man/man1/sawfish.1.gz
/usr/bin/blackbox - priority 50
 slave x-window-manager.1.gz:
/usr/share/man/man1/blackbox.1.gz
/usr/bin/enlightenment - priority 50
 slave x-window-manager.1.gz:
/usr/share/man/man1/enlightenment.1.gz
Current `best' version is /usr/bin/sawfish.

# update-alternatives --display x-session-manager
x-session-manager - status is manual.
 link currently points to /usr/bin/gnome-session
/usr/bin/gnome-session - priority 20
 slave x-session-manager.1.gz:
/usr/share/man/man1/gnome-session.1.gz
Current `best' version is /usr/bin/gnome-session.

how do i go about tracking this down?

-- 
I use Debian/GNU Linux version 3.0;
Linux boss 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i586 unknown
 
DEBIAN NEWBIE TIP #40 from Will Trillich [EMAIL PROTECTED]
:
Why are ROOT LOGINS EVIL? The main problem is this: if you have
a handful of (trusted) people who know the root password, you
can't tell -- not just by looking in the logs -- which one
logged in as root! But if you have them log in as themselves
first, they can su or sudo to get root privileges, and then
the logs will reflect who they actually are. To facilitate
this, empty out /etc/securetty (see /etc/pam.d/login for info).

Also see http://newbieDoc.sourceForge.net/ ...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

X server working but I can't log in (unstable)

[Aniartia]

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 console) but everything 
exists.. so what's going on, can someone please tell me what's going on and 
how to fix it.

TIA
   Ani

Re: X server working but I can't log in (unstable)

[Karsten M. Self]

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-manager: No 
 such file or directory
 (I get a similar one if I use startx from the console) but everything 
 exists.. so what's going on, can someone please tell me what's going on and 
 how to fix it.

$ man update-alternatives
$ update-alternatives --display x-window-manager

You have a window manager installed?  

Peace.

-- 
Karsten M. Self kmself@ix.netcom.com   http://kmself.home.netcom.com/
 What part of Gestalt don't you understand? Home of the brave
  http://gestalt-system.sourceforge.net/   Land of the free
   Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org
Geek for Hire http://kmself.home.netcom.com/resume.html


pgpNODQwYsC6Z.pgp
Description: PGP signature

Re: X server working but I can't log in (unstable)

[Colin Watson]

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 file or directory

Are you running unstable? Have you read debian-devel or debian-x
recently?

  http://lists.debian.org/debian-x/2001/debian-x-200110/msg4.html

-- 
Colin Watson  [EMAIL PROTECTED]

Re: X server working but I can't log in (unstable)

[Aniartia]

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

vnc, wdm, xinetd, and pam: can't log in

[Karsten M. Self]

I'm using a trick I've just learned to try triggering VNC sessions from
xinetd.  See for more info:

http://z.iwethey.org/forums/render/content/show?contentid=6286


My own configuration is included below.

The problem:

Launching xvncviewer :50 gives me an X session and a 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
   console via X.

Anyone else have any luck with this, or ideas on how to proceed?


from /etc/services

vnc 5950/tcp# VNC
vnc-1   5951/tcp# VNC
vnc-2   5952/tcp# VNC
vnc-3   5953/tcp# VNC
vnc-4   5954/tcp# VNC
vnc-5   5955/tcp# VNC
vnc-6   5956/tcp# VNC
vnc-7   5957/tcp# VNC


/etc/xinetd.d/vnc:

service vnc
{
disable= no
socket_type= stream
protocol   = tcp
wait   = no
user   = nobody
server = /usr/bin/X11/Xvnc 
server_args= -inetd -query ego -once -geometry 800x600 -depth 16
log_on_failur  += USERID
}


/etc/X11/wdm/Xservers (non-comment, nonblank lines only):

:0 local /usr/bin/X11/X vt7 -deferglyphs 32 -dpi 100 -nolisten tcp


/etc/pam.d/wdm

#%PAM-1.0
authrequiredpam_nologin.so
authrequiredpam_env.so
authrequiredpam_unix.so
account requiredpam_unix.so
passwordrequiredpam_unix.so
session requiredpam_unix.so


-- 
Karsten M. Self kmself@ix.netcom.com  http://kmself.home.netcom.com/
 What part of Gestalt don't you understand? There is no K5 cabal
  http://gestalt-system.sourceforge.net/   http://www.kuro5hin.org
   Free Dmitry! Boycott Adobe! Repeal the DMCA!http://www.freesklyarov.org
Geek for Hirehttp://kmself.home.netcom.com/resume.html



pgpVDA5IMect9.pgp
Description: PGP signature

can't log in as normal user

[Bart Himel]

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'm told "user doesn't have 
authority to start X server". Can someone tell me which file permissions 
have been changed and what I should do to change this back to norma? 

Re: Can't log in after apt-get upgrade

[Ross Boylan]

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 option ULIMIT
/etc/gdm/Sessions//Gnome: checking /etc/login.defs for option MAIL_DIR
/etc/gdm/Sessions//Gnome: /etc/login.defs: MAIL_DIR is /var/spool/mail
/etc/gdm/Sessions//Gnome: using /etc/X11/Xsession.options for options
/etc/gdm/Sessions//Gnome: checking /etc/X11/Xsession.options for option 
allow-user-resources
/etc/gdm/Sessions//Gnome: checking /etc/X11/Xsession.options for option 
allow-user-modmap
/usr/bin/gnome-session: error in loading shared libraries: 
libgnomecanvaspixbuf.so.1: cannot open shared object file: No such file or 
directory

However, dpkg -S shows no packages owning the file.

This appears to be an error in Helix's gnome-session package.  I'll file a bug 
if I ever get my gui back!  

I'm going to try the dist upgrade; I notice that gnome-session is one of the 
packages that operation would affect.

On Tue, Dec 12, 2000 at 04:10:06PM -0500, J. Bruce Fields wrote:
 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 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 somewhere.)  I did dpkg -S name of the file it couldn't find, it
  turned out that file was provided by a package that it claimed was
  installed (can't remember the name of the package, either, sorry).  But
  the file didn't seem to be there. So, I apt-get remove'd that package (in
  the process, it ended up removing a large chunk of my gnome installation I
  think), then apt-get install'ed task-helix-gnome.  All is now well.  Don't
  ask me---Bruce Fields
  
  On Tue, 12 Dec 2000, Ross Boylan wrote:
  
   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 started
   beeping--this seems to be standard when updating sawfish.
   Unfortunately, when I restarted I had the problem described above.
   When I enter a user name and password the login screen disappears, and
   the monitor makes a click as if resyncing.  The login screen then
   comes back on.
   
   I'd appreciate any advice on where to look for the source of the
   problem.
   
   Thanks.
   
   System info:
   Linux wheat 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown
   
   Here's the start of the upgrade session, and then my apt.sources:
   
   Script started on Tue Dec 12 01:03:09 2000
   wheat:/usr/local/rootlog# date
   Tue Dec 12 01:03:11 PST 2000
   wheat:/usr/local/rootlog# apt-get -qu upgrade
   Reading Package Lists...
   Building Dependency Tree...
   The following packages have been kept back
 gnome-core gnome-help gnome-panel gnome-panel-data gnome-session
 gnome-terminal libgnomeprint11 
   The following packages will be upgraded
 cpp-doc cron dnsutils ed elvis-tiny gcc-doc gnome-bin 
   gnome-control-center
 gnome-dev-doc gnome-faq gnome-help-data gnome-libs-data gs libart-dev
 libart2 libcapplet0 libgdk-pixbuf2 libgnome-dev libgnome32 
   libgnomesupport0
 libgnomeui32 libgnorba-dev libgnorba27 libgnorbagtk0 libgtkxmhtml1
 libncurses5 libncurses5-dev liborbit-dev liborbit0 libpanel-applet0
 libreadlineg2 librep9 libzvt2 modutils ncurses-base ncurses-bin 
   ncurses-term
 netscape-base-4 netscape-base-4-libc5 orbit rep rep-gtk rstart rstartd
 sawfish sawfish-gnome sgml-tools ssh ssh-askpass-gnome xbase-clients 
   xext
 xf86setup xfree86-common xfs xlib6 xlib6g xlib6g-dev xmms xnest xproxy 
   xprt
 xserver-common xserver-svga xserver-vga16 xsm xterm xvfb 
   67 packages upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
   Need to get 24.9MB of archives. After unpacking 945kB will be used.
   
   
   [Nothing unusual in the rest of the log]
   
   [sources.list]
   deb-src cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/source/
   deb cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/binary-i386/
   deb cdrom:[Debian beta #2 bf 2.2.3]/ 
   Debian/dists/potato/non-free/binary-i386/
   deb cdrom:[beta Debian 2.2.3]/ Debian/dists/potato/main/binary-i386/
   deb file:/ms/k/download/debian potato main
   #deb http://http.us.debian.org/debian woody main contrib non-free
   deb http://http.us.debian.org/debian potato main contrib non-free
   deb 

Re: Can't log in after apt-get upgrade

[Eric G . Miller]

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: UMASK is 022
 /etc/gdm/Sessions//Gnome: checking /etc/login.defs for option ULIMIT
 /etc/gdm/Sessions//Gnome: checking /etc/login.defs for option MAIL_DIR
 /etc/gdm/Sessions//Gnome: /etc/login.defs: MAIL_DIR is /var/spool/mail
 /etc/gdm/Sessions//Gnome: using /etc/X11/Xsession.options for options
 /etc/gdm/Sessions//Gnome: checking /etc/X11/Xsession.options for option 
 allow-user-resources
 /etc/gdm/Sessions//Gnome: checking /etc/X11/Xsession.options for option 
 allow-user-modmap
 /usr/bin/gnome-session: error in loading shared libraries: 
 libgnomecanvaspixbuf.so.1: cannot open shared object file: No such file or 
 directory
 
 However, dpkg -S shows no packages owning the file.

It wouldn't. You don't have it installed.  Guess GDM is missing a
dependency? 

# apt-get install libgdk-pixbuf-gnome2

Ahh, but it is shown as a dependency for gnome-session.  Wonder why you
don't have it...

-- 
Eric G. Miller egm2@jps.net

Re: Can't log in after apt-get upgrade

[Ross Boylan]

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 a side effect
of doing a dist-upgrade. 

Before (based on yesterdays apt-get upgrade):

Package: gnome-session
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 184
Maintainer: Helix Code, Inc. [EMAIL PROTECTED]
Source: gnome-core
Version: 1.2.4-helix1
Depends: gdk-imlib1 (= 1.9.8), libart2 (= 1.2.0), libaudiofile0, libc6 (= 
2.1.2), libdb2 (= 1:2.4.14-7), libesd0 (= 0.2.16) | libesd-alsa0 (= 0.2.16), 
libgdk-pixbuf2 (= 0.9.0), libglib1.2 (= 1.2.0), libgnome32 (= 1.2.0), 
libgnomesupport0 (= 1.2.0), libgnomeui32 (= 1.2.0), libgtk1.2 (= 1.2.0), 
libjpeg62, libpng2, libtiff3g, libz1, xlib6g (= 3.3.6-4), gnome-core (= 
1.2.4-helix1), gnome-panel
Recommends: gmc


After:

Package: gnome-session
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 184
Maintainer: Helix Code, Inc. [EMAIL PROTECTED]
Source: gnome-core
Version: 1.2.4-helix2
Depends: gdk-imlib1 (= 1.9.8), libart2 (= 1.2.0), libaudiofile0, libc6 (= 
2.1.2), libdb2 (= 1:2.4.14-7), libesd0 (= 0.2.16) | libesd-alsa0 (= 0.2.16), 
libgdk-pixbuf-gnome2 (= 0.9.0), libgdk-pixbuf2 (= 0.9.0), libglib1.2 (= 
1.2.0), libgnome32 (= 1.2.0), libgnomesupport0 (= 1.2.0), libgnomeui32 (= 
1.2.0), libgtk1.2 (= 1.2.0), libjpeg62, libpng2, libtiff3g, libz1, xlib6g (= 
3.3.6-4), gnome-core (= 1.2.4-helix2), gnome-panel
Recommends: gmc

Note libgdk-pixbug-gnome2 appears only in the 2nd version.

On Wed, Dec 13, 2000 at 12:29:36AM -0800, Eric G . Miller wrote:
 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: UMASK is 022
  /etc/gdm/Sessions//Gnome: checking /etc/login.defs for option ULIMIT
  /etc/gdm/Sessions//Gnome: checking /etc/login.defs for option MAIL_DIR
  /etc/gdm/Sessions//Gnome: /etc/login.defs: MAIL_DIR is /var/spool/mail
  /etc/gdm/Sessions//Gnome: using /etc/X11/Xsession.options for options
  /etc/gdm/Sessions//Gnome: checking /etc/X11/Xsession.options for option 
  allow-user-resources
  /etc/gdm/Sessions//Gnome: checking /etc/X11/Xsession.options for option 
  allow-user-modmap
  /usr/bin/gnome-session: error in loading shared libraries: 
  libgnomecanvaspixbuf.so.1: cannot open shared object file: No such file or 
  directory
  
  However, dpkg -S shows no packages owning the file.
 
 It wouldn't. You don't have it installed.  Guess GDM is missing a
 dependency? 
 
 # apt-get install libgdk-pixbuf-gnome2
 
 Ahh, but it is shown as a dependency for gnome-session.  Wonder why you
 don't have it...
 
 -- 
 Eric G. Miller egm2@jps.net

Can't log in after apt-get upgrade

[Ross Boylan]

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 started
beeping--this seems to be standard when updating sawfish.
Unfortunately, when I restarted I had the problem described above.
When I enter a user name and password the login screen disappears, and
the monitor makes a click as if resyncing.  The login screen then
comes back on.

I'd appreciate any advice on where to look for the source of the
problem.

Thanks.

System info:
Linux wheat 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown

Here's the start of the upgrade session, and then my apt.sources:

Script started on Tue Dec 12 01:03:09 2000
wheat:/usr/local/rootlog# date
Tue Dec 12 01:03:11 PST 2000
wheat:/usr/local/rootlog# apt-get -qu upgrade
Reading Package Lists...
Building Dependency Tree...
The following packages have been kept back
  gnome-core gnome-help gnome-panel gnome-panel-data gnome-session
  gnome-terminal libgnomeprint11 
The following packages will be upgraded
  cpp-doc cron dnsutils ed elvis-tiny gcc-doc gnome-bin gnome-control-center
  gnome-dev-doc gnome-faq gnome-help-data gnome-libs-data gs libart-dev
  libart2 libcapplet0 libgdk-pixbuf2 libgnome-dev libgnome32 libgnomesupport0
  libgnomeui32 libgnorba-dev libgnorba27 libgnorbagtk0 libgtkxmhtml1
  libncurses5 libncurses5-dev liborbit-dev liborbit0 libpanel-applet0
  libreadlineg2 librep9 libzvt2 modutils ncurses-base ncurses-bin ncurses-term
  netscape-base-4 netscape-base-4-libc5 orbit rep rep-gtk rstart rstartd
  sawfish sawfish-gnome sgml-tools ssh ssh-askpass-gnome xbase-clients xext
  xf86setup xfree86-common xfs xlib6 xlib6g xlib6g-dev xmms xnest xproxy xprt
  xserver-common xserver-svga xserver-vga16 xsm xterm xvfb 
67 packages upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 24.9MB of archives. After unpacking 945kB will be used.


[Nothing unusual in the rest of the log]

[sources.list]
deb-src cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/source/
deb cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/binary-i386/
deb cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/non-free/binary-i386/
deb cdrom:[beta Debian 2.2.3]/ Debian/dists/potato/main/binary-i386/
deb file:/ms/k/download/debian potato main
#deb http://http.us.debian.org/debian woody main contrib non-free
deb http://http.us.debian.org/debian potato main contrib non-free
deb http://non-us.debian.org/ potato/non-US main non-free contrib
#deb http://security.debian.org potato updates

# Uncomment if you want the apt-get source function to work
deb-src http://http.us.debian.org/debian potato main contrib non-free
deb-src http://non-us.debian.org/  potato/non-US main non-free contrib

#Helix
deb file:/usr/local/download/Helix woody main
deb-src file:/usr/local/download/Helix woody main
deb http://spidermonkey.helixcode.com/distributions/debian unstable main
deb-src http://spidermonkey.helixcode.com/distributions/debian unstable main

Re: Can't log in after apt-get upgrade

[Pascal Hos]

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 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 started
beeping--this seems to be standard when updating sawfish.
Unfortunately, when I restarted I had the problem described above.
When I enter a user name and password the login screen disappears, and
the monitor makes a click as if resyncing.  The login screen then
comes back on.

I'd appreciate any advice on where to look for the source of the
problem.

Thanks.

System info:
Linux wheat 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown

Here's the start of the upgrade session, and then my apt.sources:

Script started on Tue Dec 12 01:03:09 2000
wheat:/usr/local/rootlog# date
Tue Dec 12 01:03:11 PST 2000
wheat:/usr/local/rootlog# apt-get -qu upgrade
Reading Package Lists...
Building Dependency Tree...
The following packages have been kept back
  gnome-core gnome-help gnome-panel gnome-panel-data gnome-session
  gnome-terminal libgnomeprint11 
The following packages will be upgraded

  cpp-doc cron dnsutils ed elvis-tiny gcc-doc gnome-bin gnome-control-center
  gnome-dev-doc gnome-faq gnome-help-data gnome-libs-data gs libart-dev
  libart2 libcapplet0 libgdk-pixbuf2 libgnome-dev libgnome32 libgnomesupport0
  libgnomeui32 libgnorba-dev libgnorba27 libgnorbagtk0 libgtkxmhtml1
  libncurses5 libncurses5-dev liborbit-dev liborbit0 libpanel-applet0
  libreadlineg2 librep9 libzvt2 modutils ncurses-base ncurses-bin ncurses-term
  netscape-base-4 netscape-base-4-libc5 orbit rep rep-gtk rstart rstartd
  sawfish sawfish-gnome sgml-tools ssh ssh-askpass-gnome xbase-clients xext
  xf86setup xfree86-common xfs xlib6 xlib6g xlib6g-dev xmms xnest xproxy xprt
  xserver-common xserver-svga xserver-vga16 xsm xterm xvfb 
67 packages upgraded, 0 newly installed, 0 to remove and 7 not upgraded.

Need to get 24.9MB of archives. After unpacking 945kB will be used.


[Nothing unusual in the rest of the log]

[sources.list]
deb-src cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/source/
deb cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/binary-i386/
deb cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/non-free/binary-i386/
deb cdrom:[beta Debian 2.2.3]/ Debian/dists/potato/main/binary-i386/
deb file:/ms/k/download/debian potato main
#deb http://http.us.debian.org/debian woody main contrib non-free
deb http://http.us.debian.org/debian potato main contrib non-free
deb http://non-us.debian.org/ potato/non-US main non-free contrib
#deb http://security.debian.org potato updates

# Uncomment if you want the apt-get source function to work
deb-src http://http.us.debian.org/debian potato main contrib non-free
deb-src http://non-us.debian.org/  potato/non-US main non-free contrib

#Helix
deb file:/usr/local/download/Helix woody main
deb-src file:/usr/local/download/Helix woody main
deb http://spidermonkey.helixcode.com/distributions/debian unstable main
deb-src http://spidermonkey.helixcode.com/distributions/debian unstable main

Re: Can't log in after apt-get upgrade

[J. Bruce Fields]

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 somewhere.)  I did dpkg -S name of the file it couldn't find, it
turned out that file was provided by a package that it claimed was
installed (can't remember the name of the package, either, sorry).  But
the file didn't seem to be there. So, I apt-get remove'd that package (in
the process, it ended up removing a large chunk of my gnome installation I
think), then apt-get install'ed task-helix-gnome.  All is now well.  Don't
ask me---Bruce Fields

On Tue, 12 Dec 2000, Ross Boylan wrote:

 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 started
 beeping--this seems to be standard when updating sawfish.
 Unfortunately, when I restarted I had the problem described above.
 When I enter a user name and password the login screen disappears, and
 the monitor makes a click as if resyncing.  The login screen then
 comes back on.
 
 I'd appreciate any advice on where to look for the source of the
 problem.
 
 Thanks.
 
 System info:
 Linux wheat 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown
 
 Here's the start of the upgrade session, and then my apt.sources:
 
 Script started on Tue Dec 12 01:03:09 2000
 wheat:/usr/local/rootlog# date
 Tue Dec 12 01:03:11 PST 2000
 wheat:/usr/local/rootlog# apt-get -qu upgrade
 Reading Package Lists...
 Building Dependency Tree...
 The following packages have been kept back
   gnome-core gnome-help gnome-panel gnome-panel-data gnome-session
   gnome-terminal libgnomeprint11 
 The following packages will be upgraded
   cpp-doc cron dnsutils ed elvis-tiny gcc-doc gnome-bin gnome-control-center
   gnome-dev-doc gnome-faq gnome-help-data gnome-libs-data gs libart-dev
   libart2 libcapplet0 libgdk-pixbuf2 libgnome-dev libgnome32 libgnomesupport0
   libgnomeui32 libgnorba-dev libgnorba27 libgnorbagtk0 libgtkxmhtml1
   libncurses5 libncurses5-dev liborbit-dev liborbit0 libpanel-applet0
   libreadlineg2 librep9 libzvt2 modutils ncurses-base ncurses-bin ncurses-term
   netscape-base-4 netscape-base-4-libc5 orbit rep rep-gtk rstart rstartd
   sawfish sawfish-gnome sgml-tools ssh ssh-askpass-gnome xbase-clients xext
   xf86setup xfree86-common xfs xlib6 xlib6g xlib6g-dev xmms xnest xproxy xprt
   xserver-common xserver-svga xserver-vga16 xsm xterm xvfb 
 67 packages upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
 Need to get 24.9MB of archives. After unpacking 945kB will be used.
 
 
 [Nothing unusual in the rest of the log]
 
 [sources.list]
 deb-src cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/source/
 deb cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/binary-i386/
 deb cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/non-free/binary-i386/
 deb cdrom:[beta Debian 2.2.3]/ Debian/dists/potato/main/binary-i386/
 deb file:/ms/k/download/debian potato main
 #deb http://http.us.debian.org/debian woody main contrib non-free
 deb http://http.us.debian.org/debian potato main contrib non-free
 deb http://non-us.debian.org/ potato/non-US main non-free contrib
 #deb http://security.debian.org potato updates
 
 # Uncomment if you want the apt-get source function to work
 deb-src http://http.us.debian.org/debian potato main contrib non-free
 deb-src http://non-us.debian.org/  potato/non-US main non-free contrib
 
 #Helix
 deb file:/usr/local/download/Helix woody main
 deb-src file:/usr/local/download/Helix woody main
 deb http://spidermonkey.helixcode.com/distributions/debian unstable main
 deb-src http://spidermonkey.helixcode.com/distributions/debian unstable main
 

Re: Can't log in after apt-get upgrade

[J. Bruce Fields]

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 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 somewhere.)  I did dpkg -S name of the file it couldn't find, it
 turned out that file was provided by a package that it claimed was
 installed (can't remember the name of the package, either, sorry).  But
 the file didn't seem to be there. So, I apt-get remove'd that package (in
 the process, it ended up removing a large chunk of my gnome installation I
 think), then apt-get install'ed task-helix-gnome.  All is now well.  Don't
 ask me---Bruce Fields
 
 On Tue, 12 Dec 2000, Ross Boylan wrote:
 
  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 started
  beeping--this seems to be standard when updating sawfish.
  Unfortunately, when I restarted I had the problem described above.
  When I enter a user name and password the login screen disappears, and
  the monitor makes a click as if resyncing.  The login screen then
  comes back on.
  
  I'd appreciate any advice on where to look for the source of the
  problem.
  
  Thanks.
  
  System info:
  Linux wheat 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown
  
  Here's the start of the upgrade session, and then my apt.sources:
  
  Script started on Tue Dec 12 01:03:09 2000
  wheat:/usr/local/rootlog# date
  Tue Dec 12 01:03:11 PST 2000
  wheat:/usr/local/rootlog# apt-get -qu upgrade
  Reading Package Lists...
  Building Dependency Tree...
  The following packages have been kept back
gnome-core gnome-help gnome-panel gnome-panel-data gnome-session
gnome-terminal libgnomeprint11 
  The following packages will be upgraded
cpp-doc cron dnsutils ed elvis-tiny gcc-doc gnome-bin gnome-control-center
gnome-dev-doc gnome-faq gnome-help-data gnome-libs-data gs libart-dev
libart2 libcapplet0 libgdk-pixbuf2 libgnome-dev libgnome32 
  libgnomesupport0
libgnomeui32 libgnorba-dev libgnorba27 libgnorbagtk0 libgtkxmhtml1
libncurses5 libncurses5-dev liborbit-dev liborbit0 libpanel-applet0
libreadlineg2 librep9 libzvt2 modutils ncurses-base ncurses-bin 
  ncurses-term
netscape-base-4 netscape-base-4-libc5 orbit rep rep-gtk rstart rstartd
sawfish sawfish-gnome sgml-tools ssh ssh-askpass-gnome xbase-clients xext
xf86setup xfree86-common xfs xlib6 xlib6g xlib6g-dev xmms xnest xproxy 
  xprt
xserver-common xserver-svga xserver-vga16 xsm xterm xvfb 
  67 packages upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
  Need to get 24.9MB of archives. After unpacking 945kB will be used.
  
  
  [Nothing unusual in the rest of the log]
  
  [sources.list]
  deb-src cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/source/
  deb cdrom:[Debian beta #2 bf 2.2.3]/ Debian/dists/potato/main/binary-i386/
  deb cdrom:[Debian beta #2 bf 2.2.3]/ 
  Debian/dists/potato/non-free/binary-i386/
  deb cdrom:[beta Debian 2.2.3]/ Debian/dists/potato/main/binary-i386/
  deb file:/ms/k/download/debian potato main
  #deb http://http.us.debian.org/debian woody main contrib non-free
  deb http://http.us.debian.org/debian potato main contrib non-free
  deb http://non-us.debian.org/ potato/non-US main non-free contrib
  #deb http://security.debian.org potato updates
  
  # Uncomment if you want the apt-get source function to work
  deb-src http://http.us.debian.org/debian potato main contrib non-free
  deb-src http://non-us.debian.org/  potato/non-US main non-free contrib
  
  #Helix
  deb file:/usr/local/download/Helix woody main
  deb-src file:/usr/local/download/Helix woody main
  deb http://spidermonkey.helixcode.com/distributions/debian unstable main
  deb-src http://spidermonkey.helixcode.com/distributions/debian unstable main
  
 

Re: Zope newbie can't log in

[Adam Shand]

 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 anywhere (or that the
post-install script for the debian package sets it that way), however a
user you create, you must specify the hosts or domains that they can come
from when you create the user in zope.  i haven't tried to see if a * will
allow access from anywhere yet.

 I have removed apache still can not log in as user - even user 'a'
 with password 'a' which I created as superuser.  I have tried it on
 Mozilla, Netscape and Lynx.  Links would not work with Zope because it
 ignores the :9673 part in references.

apache has nothing to do with this if you are reaching zope on port
9673.  and lynx should work just fine.  just make sure you specify the url
correctly.

http://host.domain.com:9673/

adam.

Zope newbie can't log in

[Johann Spies]

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 still can not log in as user - even user 'a'
with password 'a' which I created as superuser.  I have tried it on
Mozilla, Netscape and Lynx.  Links would not work with Zope because it
ignores the :9673 part in references.

I have removed zope and /var/lib/zope and reinstalled it and the same
happens. I can not log in as normal user.

I found this in the FAQ:

2. I have installed Zope, and when I go to the URL in my web
   browser, I get a password prompt. Although I type in the correct
   username and password, I keep getting prompted. What is going on?

   Zope manages access control internally, but it relies on your
   web server software to relay any authentication information in
   web requests. Some web servers automatically filter this information
   out of requests passed to cgi programs. If you keep getting password
   prompts that never accept your password, this means that your web
   server is not properly configured to pass authentication info on to
   Zope. See the doc/WEBVSERVER.txt file for information on correctly
   configuring your web server to pass authentication information.

But I have removed the web server now and it still happens!

I hope somebody can help me on this one.

Johann

-- 
J.H. Spies - Tel. 082 782 0336 / 023 55 11 568
 Cast thy burden upon the LORD, and he shall sustain 
  thee; he shall never allow the righteous to fall.  
   Psalms 55:22 

- End forwarded message -

-- 
J.H. Spies - Tel. 082 782 0336 / 023 55 11 568
 Cast thy burden upon the LORD, and he shall sustain 
  thee; he shall never allow the righteous to fall.  
   Psalms 55:22 

I can't log in to tty1-6!

[Matheson]

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,
Cameron Matheson

RE: I can't log in to tty1-6!

[Rino Mardo]

What you can do 
is type "linux s" at the LILO prompt to get you to the shell without going to 
the login process.

hth.

P.S. This 
is my first time sending email from Outlook so if those console users get 
anything ugly please say so and I'll adjust my settings. Yeah my 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 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,
  Cameron 
Matheson


smime.p7s
Description: S/MIME cryptographic signature

Re: root filesystem corrupted, can't log in

[Ethan Benson]

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 IDE
 boxes, had a recurrent filesystem corruption problem. I was on kernel
 2.2.12 when I upgraded to RedHat 6.1 and it slaughtered me. Here's the
 routine that worked over and over again for me when boot up failed.

i can certainly attest to 2.2.13 trashing filesystems, it was always
`corrupted blocks' or some such thing too.

snip

 When they are all done, type 'exit' (without the quote marks). Your
 system will shutdown and you _should_ be able press restart and boot
 back up clean. Should.

unless it was 2.2.13 in which case all three times i had this
corruption all of /etc was gone, as was /bin and a few other things
that don't matter like /lib :(  they took a new nameless home in /lost+found...

 You mileage may vary, but I have had to do that so many times under Red
 Hat I've lost count. I'm surprised to encounter it in Debian. AND it may
 be different here, so if anyone thinks he shouldn't try this, please
 speak up NOW.

the kernel is the kernel, the distribution does not matter when your
kernel is puking all over the filesystem.  and 2.2.13 seemed to always
kill the root filesystem first.

 Good Luck,

you will need it.  and don't allow any 2.2 kernel earlier then 2.2.14
within a mile of any of your machines :|

fsck is a four letter word for a reason, its spelled f s c k but its
pronounced ...

-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpOVA3oGndQE.pgp
Description: PGP signature

Re: root filesystem corrupted, can't log in

[Philip Lehman]

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 to RedHat 6.1 and it slaughtered me. Here's the
 routine that worked over and over again for me when boot up failed.

i can certainly attest to 2.2.13 trashing filesystems, it was always
`corrupted blocks' or some such thing too.

snip

 When they are all done, type 'exit' (without the quote marks). Your
 system will shutdown and you _should_ be able press restart and boot
 back up clean. Should.

Did.

Nathan, montefin, aphro, Ethan: thanks to all of for the quick
replies. I managed to fix the filesystem some time after midnight
(CET) and the box it's up and running again.

[...]
you will need it.  and don't allow any 2.2 kernel earlier then 2.2.14
within a mile of any of your machines :|

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?

-- 
Philip Lehman [EMAIL PROTECTED]

Re: root filesystem corrupted, can't log in

[Ethan Benson]

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 the least time consuming thing to do is read Kernel
Traffic every week (http://www.kt.linuxcare.com find the link for
latest issue of the kernel version, they also have sumaries for many
other lists, including some debian lists) and possibly Linux Weekly
News (http://www.lwn.net) both of which have a summary of the
discussion topics of the week on linux kernel and other lists.  things
like massive filesystem corruption usually generate enough traffic on
linux kernel to make it into these sites.


-- 
Ethan Benson
http://www.alaska.net/~erbenson/


pgpl4VNffT9ge.pgp
Description: PGP signature

Re: root filesystem corrupted, can't log in

[Robert D. Hilliard]

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/filesystemname (my /var looks like /dev/hda7

 With e2fsprogs 1.18-3, the e2fsck manpage says:

   -r This  option  does  nothing  at all; it is provided
  only for backwards compatibility.

 What option did you intend to use?  (I'm not flaming - I'm
asking for information.)

Bob
-- 
   _
  |_)  _  |_   Robert D. Hilliard  [EMAIL PROTECTED]
  |_) (_) |_)  1294 S.W. Seagull Way   [EMAIL PROTECTED]
   Palm City, FL  USA   PGP Key ID: A8E40EB9

Re: root filesystem corrupted, can't log in

[montefin]

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 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/filesystemname (my /var looks like /dev/hda7
 
  With e2fsprogs 1.18-3, the e2fsck manpage says:
 
-r This  option  does  nothing  at all; it is provided
   only for backwards compatibility.
 
  What option did you intend to use?  (I'm not flaming - I'm
 asking for information.)
 
 Bob
 --

Yeah, I know, I read that too.

But I'd seen it mentioned in one of Barkakati's books, I think, so I
tried it and it worked for me when I was in the same jam as you. And it
didn't work without it. But maybe that's just Red Hat or my environemnt,
although it's worked for other people I passed it along to. -r is a hold
over from FSCK and it's supposed to be e2fsck's default behavior, but
there's a lot that isn't quite so about e2fsck.

Maybe it's just voodoo for me now, but, hey, if it doesn't do anything,
it can't hurt, right?

Read those other comments about the internal directives in the e2fsck
program. The -b 8193 alternate superblock routine is suggested after
_it_  produces the error. And wait until you see the 'bonehead' line in
the maybe it's a bug but it's probably YOU message. Anyway, I tend not
to believe everything I read in man pages.

Seriously though. Check to see if you're running e2fsprog along with or
as a part of e2fsck on your bootup. It's a little script that shows the
pretty hash marks or spinning pinwheel for e2fsck's progress. Well, it
was also known to trigger an unnessecary Signal 11 everytime the root
filesystem was checked. Not only for a power outage but even when you
reached maximum boots without a check. That's no fun. 

There's a bugfix on the Red Hat 6.1 Errata page

http://www.redhat.com/support/errata/rh61-errata-general.html

that supposedly corrects that, but I never saw it make a difference. I
think it's just e2fsck. I'm not sure if Red Hat fixes can be applied to
other Linuxes, but you might want to try it.

root filesystem corrupted, can't log in

[Philip Lehman]

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).

fsck tries to fix the problem but it fails, saying something
about an unexpected inconsistency (IIRC) and tries to dump me
to a sulogin prompt. At that point I get an error about
/sbin/sulogin not beeing found (I guess because the file system
is not mounted yet) and the machine simply reboots. If I don't
turn it off when the BIOS comes up, it keeps on looping.

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...

-- 
Philip Lehman [EMAIL PROTECTED]

Re: root filesystem corrupted, can't log in

[Nathan E Norman]

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
are going to do a new install.  In other words, do NOT specify a
root=/dev/hdn line at the syslinux prompt.

As soon as you see the initial setup screen, hit alt-f2 and then enter
to open the second VC.  You may now issue e2fsck commands as
necessary.

Good luck!

-- 
Nathan Norman Eschew Obfuscation  Network Engineer
GPG Key ID 1024D/51F98BB7http://home.midco.net/~nnorman/
Key fingerprint = C5F4 A147 416C E0BF AB73  8BEF F0C8 255C 51F9 8BB7


pgpOuzrML8PIl.pgp
Description: PGP signature

Re: root filesystem corrupted, can't log in

[montefin]

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 kernel
2.2.12 when I upgraded to RedHat 6.1 and it slaughtered me. Here's the
routine that worked over and over again for me when boot up failed.

IF, you can do what Nathan said and get to a root shell, all you may see
is

#

Here are the e2fsck commands that worked for me:

Type   e2fsck -b 8193 /dev/rootfilesystemname(my / looks like
/dev/hda9)

Hit ENTER and answer yes to all the questions by hitting ENTER until it
tells you

* FILE MODIFIED **

and gives you back the command prompt

#


Do the same for each of your filesystems /boot, /home, /usr, /var giving
your names for each in the form /dev/hdasomething, /dev/hdbsomething.
Don't worry about swap.

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/filesystemname (my /var looks like /dev/hda7

and it worked everytime giving me

** FILE MODIFIED **

#

You may also get a warning from the e2fsck programmer to the effect that
Either there is a bug in e2fsck or some bonehead, YOU, is attempting to
clean a mounted filesystem. That scared the daylights out of me the
first time I saw it, until I told myself Hey, I'm on a rescue disk.
None of these filesystems can possibly be mounted. Be sure that you
have not tried to mount any filesystems.

I continued to clean each of my filesystems getting

** FILE MODIFIED 

and the command prompt

#

after each one.


When they are all done, type 'exit' (without the quote marks). Your
system will shutdown and you _should_ be able press restart and boot
back up clean. Should.

You mileage may vary, but I have had to do that so many times under Red
Hat I've lost count. I'm surprised to encounter it in Debian. AND it may
be different here, so if anyone thinks he shouldn't try this, please
speak up NOW.

Good Luck,

montefin


Philip Lehman wrote:
 
 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).
 
 fsck tries to fix the problem but it fails, saying something
 about an unexpected inconsistency (IIRC) and tries to dump me
 to a sulogin prompt. At that point I get an error about
 /sbin/sulogin not beeing found (I guess because the file system
 is not mounted yet) and the machine simply reboots. If I don't
 turn it off when the BIOS comes up, it keeps on looping.
 
 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...
 
 --
 Philip Lehman [EMAIL PROTECTED]
 
 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null

Can't Log into FTPD

[Harlan Crystal]

I'm currently using the most updated unstable.

Whenever I attempt to FTP into my machine, it won't authorize me to log in.
Even when I ftp localhost, using my username/pw, it denies access.

I've removed and reinstalled the ftpd package 3 or 4 times.. and its the
same.  nothing in the man page said anything about this problem.

any suggestions?


 - harlan

Re: Can't Log into FTPD

[Seth R Arnold]

If it bugs you that much, you could install proftpd. :) 

On Tue, Sep 07, 1999 at 04:24:00AM -0400, Harlan Crystal wrote:
 I'm currently using the most updated unstable.
 
 Whenever I attempt to FTP into my machine, it won't authorize me to log in.
 Even when I ftp localhost, using my username/pw, it denies access.
 
 I've removed and reinstalled the ftpd package 3 or 4 times.. and its the
 same.  nothing in the man page said anything about this problem.
 
 any suggestions?
 
 
  - harlan
 
 
 -- 
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null

-- 
Seth Arnold | http://www.willamette.edu/~sarnold/
Hate spam? See http://maps.vix.com/rbl/ for help
Hi! I'm a .signature virus! Copy me into
your ~/.signature to help me spread!

Re: Can't Log into FTPD

[Ernest Johanson]

You might want to check your /etc/inetd.conf file. If the line for ftpd is
commented out, remove the comment character and restart inetd.

Ernest Johanson
Web Systems Administrator
Fuller Theological Seminary


On Tue, 7 Sep 1999, Harlan Crystal wrote:

 Date: Tue, 7 Sep 1999 04:24:00 -0400
 From: Harlan Crystal [EMAIL PROTECTED]
 To: debian-user@lists.debian.org
 Subject: Can't Log into FTPD
 
 I'm currently using the most updated unstable.
 
 Whenever I attempt to FTP into my machine, it won't authorize me to log in.
 Even when I ftp localhost, using my username/pw, it denies access.
 
 I've removed and reinstalled the ftpd package 3 or 4 times.. and its the
 same.  nothing in the man page said anything about this problem.
 
 any suggestions?
 
 
  - harlan
 

Re: Problem: can't log in/su with any non-root user

[Hamish Moffatt]

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 that very
well. X programs say they are unable to connecct with an error 111
or something like that (presumably because they can't create their
Unix domain socket in /tmp). Very ugly; I never found out what caused
it, but it went away in about 1.3.


Hamish
-- 
Hamish Moffatt VK3SB (ex-VK3TYD). 
CCs of replies from mailing lists are welcome.

Problem: can't log in/su with any non-root user

[Jeremy Morgan]

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 tried to login as another user:

Unable to cd to /home/porp

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:

-rwxr-xr-x   1 root root   364336 Jul 25 02:45 /bin/bash
-rwsr-xr-x   1 root root 9512 Jun  2 09:59 /bin/su

drwxr-sr-x   2 porp porp 1024 Jul 24 14:49 porp
drwxr-xr-x   2 root root 2048 Jul 25 02:39 bin
drwxrwsr-x   4 root staff1024 Jul 24 22:14 home

I've been on irc.debian.org and have asked many people to help me discover
the problem but no one has been of much help.  Nevertheless, I decided to
reinstall.  I figured doing that would fix all problems.  And it did.  I
could login as any one, exim would work, and I was happy.  But as soon as I
upgraded to potato (I like many of the packages in unstable), every thing
broke again.  Now I'm sure this can't be a widespread problem because I
would have found solutions.  But I cannot figure out what the problem is.
It can't be the permissions on bash because if I change the user's shell in
/etc/passwd, I get the same error, just a different shell is listed.  It has
to be with some potato packages, either one or a combination of some are
conflicting or broken.  But then again I do not know because many people use
potato.  I just know that I'm not smart enough to figure it out, and my
system is broken. I really do hope you guys can help.

RE: Problem: can't log in/su with any non-root user

[Pollywog]

 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 /bin/login?

--
Andrew

Re: Problem: can't log in/su with any non-root user

[Jeremy Morgan]

 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

Re: Problem: can't log in/su with any non-root user

[egm2]

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 over from a previous distribution are you? 
-- 

Eric G. Miller
Powered by the POTATO (http://www.debian.org)!

Re: Problem: can't log in/su with any non-root user

[Jeremy Morgan]

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 potato, it broke.  I did apt-get update and apt-get
dist-upgrade.  I had one problem with the samba package and apt died.  I
couldn't run apt again (something about can't handle the media swap) but I
ran dselect and went to install/configure packages (I'm not sure on exactly
what it's called, but its one of the options on the dselect main screen) and
dselect continued where apt broke.  After that, apt would work normally but
when I checked to see if the problem showed up again, I found that it was.
I can't figure out what in the world it could be.

 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 over from a previous distribution are you?
 --

 Eric G. Miller
 Powered by the POTATO (http://www.debian.org)!

Re: Problem: can't log in/su with any non-root user

[Brad]

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:
 
 su: cannot run /bin/bash: Permission denied
 
 When I tried to login as another user:
 
 Unable to cd to /home/porp
 
 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:
 
 -rwxr-xr-x   1 root root   364336 Jul 25 02:45 /bin/bash
 -rwsr-xr-x   1 root root 9512 Jun  2 09:59 /bin/su
 
 drwxr-sr-x   2 porp porp 1024 Jul 24 14:49 porp
 drwxr-xr-x   2 root root 2048 Jul 25 02:39 bin
 drwxrwsr-x   4 root staff1024 Jul 24 22:14 home

What're the permissions on /? (ls -ld /)

Re: Problem: can't log in/su with any non-root user

[Jeremy Morgan]

 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.  You're really helpful!

Re: Problem: can't log in/su with any non-root user

[Brad]

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 working.  Gosh, am I glad.
 Again, thanks guys.  You're really helpful!

Now, the only question is Which package did this?...

Re: Can't log in - Help!

[Brad]

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 that one either.

What happens when you do ls -ld /home and ls -l /home?

What happens if you login as root, su to dden, and try to cd /home/dden?

 Right before this happened I logged in as root and moved a subdirectory
 from my home directory to my root directory so that it would be
 inaccessable to my normal user account.  Could this have caused the
 problem?  I moved it back but that didn't help.

i don't think it would have caused the problem...

 I used Win98 to send this email, please forgive me.

i don't know... 95 maybe, but 98? ;)

Re: Can't log in - Help!

[Matthew Dalton]

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. cd /home
3. chown dden.dden dden
4. chmod 750 dden

Matthew

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 that one either.
 
 Right before this happened I logged in as root and moved a subdirectory
 from my home directory to my root directory so that it would be
 inaccessable to my normal user account.  Could this have caused the
 problem?  I moved it back but that didn't help.
 
 I used Win98 to send this email, please forgive me.
 
 David Densmore [EMAIL PROTECTED]
 
 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null

Can't log in - Help!

[David Densmore]

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 root and moved a subdirectory
from my home directory to my root directory so that it would be
inaccessable to my normal user account.  Could this have caused the
problem?  I moved it back but that didn't help.

I used Win98 to send this email, please forgive me.

David Densmore [EMAIL PROTECTED]