From: Viktar Patotski <xp.vit.blr@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: WARNING: Do not update your system on ~amd64
Date: Sat, 20 Jun 2020 23:41:57 +0200 [thread overview]
Message-ID: <CAA+wmxxXg9iXAA5q4dD_MShF9042YG_XFmjW+p6gHKbDa3FCWQ@mail.gmail.com> (raw)
In-Reply-To: <rcimeg$3emd$1@ciao.gmane.io>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
Hi All,
First of all thanks for this thread! It helped me a lot. In short:
I was not able to login to my notebook after battery discharge reboot...
Thanks, I always have Gentoo live USB drive. So:
1. I booted to livecd
2. chrooted to my system (thanks I still not encrypted my hdd)
3. emerge --ask --update --newuse --deep @world
4. reboot
5. Happy Login!
:-)
Viktar Patotski
On Fri, Jun 19, 2020 at 5:44 PM Nikos Chantziaras <realnc@gmail.com> wrote:
> On 19/06/2020 15:31, Arve Barsnes wrote:
> > On Fri, 19 Jun 2020 at 12:49, Neil Bothwick <neil@digimed.co.uk> wrote:
> >>
> >> On Fri, 19 Jun 2020 10:55:46 +0100, Peter Humphrey wrote:
> >>
> >>> And today, pam and pambase are restored to their earlier versions
> >>> because sddm requires them. But sddm has not changed versions, so why
> >>> did portage want to upgrade pam and pambase on Wednesday?
> >>
> >> The sddm ebuild has changed without changing the version
> >>
> >> - pam? ( sys-libs/pam )
> >> + pam? ( <=sys-libs/pam-1.3.1_p20200128-r1 )
> >
> > I only got a message about skipping sddm on my world update, so
> > apparently I'm now running an unsupported pam version. Rebooting
> > worked just fine though, so what I gain/lose by staying like this is
> > unknown.
>
> I lost my Plasma auto login. SDDM would just display a black screen at
> boot rather than log me in automatically.
>
> Fixing it was easy though:
>
> emerge -a1 =sys-auth/pambase-20200304 =sys-libs/pam-1.3.1_p20200128-r1
>
>
>
[-- Attachment #2: Type: text/html, Size: 2202 bytes --]
next prev parent reply other threads:[~2020-06-20 21:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 5:34 [gentoo-user] WARNING: Do not update your system on ~amd64 Andreas Fink
2020-06-17 8:29 ` Neil Bothwick
2020-06-17 8:51 ` Peter Humphrey
2020-06-17 9:03 ` Andreas Fink
2020-06-17 9:38 ` Neil Bothwick
2020-06-19 9:55 ` Peter Humphrey
2020-06-19 10:49 ` Neil Bothwick
2020-06-19 12:31 ` Arve Barsnes
2020-06-19 15:43 ` [gentoo-user] " Nikos Chantziaras
2020-06-20 21:41 ` Viktar Patotski [this message]
2020-06-21 13:08 ` Nikos Chantziaras
2020-06-19 12:52 ` [gentoo-user] " Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA+wmxxXg9iXAA5q4dD_MShF9042YG_XFmjW+p6gHKbDa3FCWQ@mail.gmail.com \
--to=xp.vit.blr@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox