> On 11 Sep 2017, at 00:08, Alexey Eschenko wrote:
>
> I'm using Scaleway with Gentoo VM for two months. You can try to ask here but
> I don't know if I can answer to you properly.
Thanks.
I signed up for an account there a day or two ago, and set up a VM running
Gentoo.
Scaleway provide a
On Sun, Sep 10, 2017 at 06:19:55PM -0700, Daniel Campbell wrote
>
> Based on what I've read so far, Moonchild is up front about any
> breakage, and warns about unsupported compilers or settings. One of our
> regulars (Walter Dnes) helps maintain PM for us, too, so that's even
> better. :)
A bit
I started a plasma session and after some period of input inactivity I noticed
the screen blanked out. Later on I moved the mouse and to my surprise I
obtained this message:
*
"The screen locker is broken and unlocking is not possible anymore.
In order to unlock switch to a v
> On 11 Sep 2017, at 18:49, Mick wrote:
>
> …
> "The screen locker is broken and unlocking is not possible anymore.
> In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),
> log in and execute the command:
>
> loginctl unlock-sessions
>
> ...
>
> If this is a default Gentoo ins
I had a similar (if not identical problem). This solution is a
"difficult" solution, the reason I experienced this (if I understand)
was that I was running KDE at the same time I was updating KDE. I can't
remember if I simply rebooted, or if all it took was logging out, and
logging back in. Even
On Monday, 11 September 2017 19:18:30 BST Stroller wrote:
> > On 11 Sep 2017, at 18:49, Mick wrote:
> >
> > …
> > "The screen locker is broken and unlocking is not possible anymore.
> > In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),
> > log in and execute the command:
> >
>
On 09/11/2017 10:49 AM, Mick wrote:
I started a plasma session and after some period of input inactivity I noticed
the screen blanked out. Later on I moved the mouse and to my surprise I
obtained this message:
*
"The screen locker is broken and unlocking is not possible anymo
On Monday, 11 September 2017 19:27:02 BST Jigme Datse Yli-RAsku wrote:
> I had a similar (if not identical problem). This solution is a
> "difficult" solution, the reason I experienced this (if I understand)
> was that I was running KDE at the same time I was updating KDE.
No the user started a
On 11.09.2017 21:04, Mick wrote:
> On Monday, 11 September 2017 19:27:02 BST Jigme Datse Yli-RAsku wrote:
>> I had a similar (if not identical problem). This solution is a
>> "difficult" solution, the reason I experienced this (if I understand)
>> was that I was running KDE at the same time I was
On Monday, 11 September 2017 20:27:02 BST Dan Johansson wrote:
> On 11.09.2017 21:04, Mick wrote:
> > On Monday, 11 September 2017 19:27:02 BST Jigme Datse Yli-RAsku wrote:
> >> I had a similar (if not identical problem). This solution is a
> >> "difficult" solution, the reason I experienced this
Hi,
got a problem this morning:
>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-libs/glibc-2.24-r4
* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction
* ERROR: sys-libs/glibc-2.24-r4::gentoo failed (prete
tu...@posteo.de wrote:
> Hi,
>
> got a problem this morning:
>
Verifying ebuild manifests
Running pre-merge checks for sys-libs/glibc-2.24-r4
> * Sanity check to keep you from breaking your system:
> * Downgrading glibc is not supported and a sure way to destruction
> * ERROR: sys-lib
12 matches
Mail list logo
