Debian Planet

Welcome to Debian Planet


All your woody are (not quite, but very very very soon) belong to us.
Main Menu

  • Home

  • Topics

  • Web Links

  • Your Account

  • Submit News

  • Stats

  • Top 10

  • Debian

    These are important Debian sites one should not be without!

  • Official Debian site

  • Package search

  • Mailing list archives

  • Bug reports

  • Debian on CD

  • Unofficial woody CD ISOs

  • Unofficial APT sources

  • Developers' Corner

    Other great Debian news sources:

  • Debian Weekly News

  • Kernel Cousin Debian

    (Debian mailing lists digested)
  • Community Groups

    Need help? You're not alone on this planet.

  • debianHELP

    (User support site)

  • Debian International



  • EsDebian


  • DebianWorld


  • MaximumDebian


  • DebianUsers


  • Debian-BR


  • IRC

    The place to get help on a Debian problem (after reading docs) or to just chat and chill is #debian on

    Many of the Debian Planet staff live there so pop by and say hello.

    Wanna write?

    Got that latest or greatest scoop? Perhaps you have some important news for the Debian community? Submit a news item!

    Or perhaps you've written a rather ground breaking insight into some aspect of Debian and you feel compelled to share it with others? Knock up a longer editorial article and send it to the editors.


    DP is sponsored by Xinit Systems and

    Domains paid for and hosted by

    Buy your Debian merchandise at

    Who's Online

    There are currently, 93 guest(s) and 4 member(s) that are online.

    You are Anonymous user. You can register for free by clicking here.

    Libpam was broken
    Contributed by jes5199 on Wednesday, June 27 @ 19:39:01 BST

    Package Management
    The submission:
    I can't log in... I don't even get a password prompt before it tells me it's incorrect

    As I understand it libpam 0.72-26 broke (thus the lack of logging in). Fixed deb is in unstable.

    If you are stuck without a root console - you can pass the init=/bin/sh option to the kernel at boot time (hitting Ctrl-Alt-Del should take the box down cleanly). If you can't do that then either boot via a rescue CDROM/floppy or put the disk in another box. You can chroot into your mounted rootfs and things should be normal enough to upgrade.

    And look on the bright side - your box is pretty damm secure.

    Related Links

  • Comparison by Joey Hess
  • More about Package Management
  • News by agl

    Most read story about Package Management:
    What are the *real* .deb and .rpm differences

    Last news about Package Management:

    Printer Friendly Page  Send this Story to a Friend
  • "Libpam was broken" | Login/Create Account | 11 comments

    The comments are owned by the poster. We aren't responsible for their content.

    Re: libpam was broken (Score: 3, Funny)
    by markybob on Wednesday, June 27 @ 21:16:44 BST
    (User Info)

    And look on the bright side - your box is pretty damm secure.

    HA! i like how you think 😀

    [ Reply ]

    Re: libpam was broken (Score: 4, Informative)
    by Anonymous on Wednesday, June 27 @ 21:20:13 BST

    You don't need to do the init=/bin/sh trick for this one. Just boot to single mode, Linux S from the LILO boot prompt, and it will let you in. Since Debian is brain-dead on what single mode should be, your networking will be up and you can apt-get update; apt-get upgrade your way into the fixed packages.

    [ Reply ]

    Re: libpam was broken (Score: 1, Informative)
    by Anonymous on Thursday, June 28 @ 11:18:50 BST

    All you gotta do is to obtain a root shell (if you have one, you're lucky. If not, reboot in single mode...)

    And then install the new fixed package using apt-get or downgrade to the previous one. (libpam_modules).


    Tuxisuau -

    [ Reply ]

    Re: Libpam was broken (Score: 1)
    by dac ( on Friday, June 29 @ 12:57:32 BST
    (User Info)


    I was shocked too when that happend to me. 'su' just told me about a wrong module or something -- so I went panic (what WHA the KGB hacked my box? help! help!).. but lucky me still had a remaining root session (after checking /var/log/syslog I telepathy there had to be something wrong with the libpam-modules package), and -- a apt-get dist-upgrade fixed the whole disaster again. I just think of those people which let their apt-get upgrade run automatically. What a shock if you want to log-in.... ;-). Ok, just to note down my impressions and what happend to me too after midnight, someday.

    Debian/unstable, sometimes it is a real adventure:)


    [ Reply ]

    Based on: PHP-Nuke

    All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © 2000 by Debian Planet

    You can syndicate our news using the file backend.php.