On 14/04/2016 09:58, Dale wrote:
J. Roeleveld wrote:
On Thursday, April 14, 2016 10:33:10 AM Yuri K. Shatroff wrote:
14.04.2016 00:49, Dale wrote:
Yuri K. Shatroff wrote:
Hi Dale,
I'm not sure on where you got the black screen. If it is when X
started, did you switch to sddm or some other
14.04.2016 11:36, Dale wrote:
Yuri K. Shatroff wrote:
14.04.2016 10:43, J. Roeleveld wrote:
No idea here, logs?
I didn't see anything relevant in Xorg.?.log (neither in messages) and
since there was no kdm which usually tracks all KDE messages I didn't
know where to look. Neither any new log
I run chkrootkit and rkhunter on my laptop. Suddenly I noticed this in my
logs:
/dev/shm/pulse-shm-2469735543
Possible Linux/Ebury - Operation Windigo installetd
Then, rkhunter shows:
[20:23:27] Info: Starting test name 'filesystem'
[20:23:27] Performing filesystem checks
[20:23:27] Info:
On 04/14/2016 09:02 AM, Neil Bothwick wrote:
> On Thu, 14 Apr 2016 08:14:05 -0700, Daniel Frey wrote:
>
>> I didn't have any problems with sddm, but that slow interface drove me
>> nuts. I was using nouveau, and I read against running that with nvidia
>> cards, so I installed the binary driver
On 04/14/2016 01:06 PM, James wrote:
So,
I was going through the handbook to look at the logic therein
before bash scripting up some simple install recipies for my clustering
work, which is eclusively amd64+radeon, atm.
In the Kernel section of the amd64-handbook::
"root #nano -w /etc/fstab
On 04/14/2016 11:26 AM, Michael Palimaka wrote:
> Hi Dan,
>
>
> In System Settings -> Search there's options to turn off the file
> indexer as well as all the other search plugins (including recent
> documents). I've heard that sometimes it can take a little bit for the
> indexer to stop, but
On Tue, 12 Apr 2016 22:50:46 +0200
Alan McKinnon wrote:
> On 12/04/2016 22:46, Frank Steinmetzger wrote:
> >> Unfortunately I can't attach a screenshot as proof - both remove
> >> their own window to do the capture :-)
> >
> > import -window root screenshot.png
> >
On Wed, Apr 13, 2016 at 04:08:40PM +, James wrote
> »Q« gmx.net> writes:
>
>
> > tl;dr: Getting rid of USE="-*" was a lot easier than I'd expected. A
> > little rebuilding, a lot of (easy) USE flag pruning, and I'm done.
>
> > Until yesterday, I've had USE="-*" for years.
>
> I've
Hi Dan,
On 11/04/16 09:55, Daniel Frey wrote:
> OK
>
> We're in 2016 now. And KDE *still* doesn't make it easy to disable their
> damn indexer. I've never wanted to search through my menu, I've never
> wanted it to remember every damn file I've opened. It's a personal
> preference.
>
> WHY
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/14/2016 04:40 PM, Mick wrote:
> I run chkrootkit and rkhunter on my laptop. Suddenly I noticed
> this in my logs:
>
> /dev/shm/pulse-shm-2469735543 Possible Linux/Ebury - Operation
> Windigo installetd
>
>
> Then, rkhunter shows:
>
>
Corbin charter.net> writes:
> > In the Kernel section of the amd64-handbook::
> >
> > "root #nano -w /etc/fstab
> > FILE /etc/fstabConfiguring the /boot mountpoint
> > /dev/sda2 /boot ext2defaults0 2 "
> >
> >
Ah, thx, I did find this which matches up with the default
On Thursday 14 Apr 2016 13:38:15 walt wrote:
> On Tue, 12 Apr 2016 22:50:46 +0200
>
> Alan McKinnon wrote:
> > On 12/04/2016 22:46, Frank Steinmetzger wrote:
> > >> Unfortunately I can't attach a screenshot as proof - both remove
> > >> their own window to do the capture
On Fri, Apr 15, 2016 at 04:37:05AM +1000, Michael Palimaka wrote:
> Hi Peter,
>
> On 11/04/16 20:34, Peter Humphrey wrote:
> > On Saturday 09 April 2016 11:12:51 Mick wrote:
> >> I noticed today that Plasma 5 is now stable, which means I will soon have
> >> to deal with it.
> >
> > I saw that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/14/2016 03:39 PM, Mick wrote:
> On Thursday 14 Apr 2016 11:21:39 Yuri K. Shatroff wrote:
>> 14.04.2016 10:43, J. Roeleveld wrote:
>>> On Thursday, April 14, 2016 10:33:10 AM Yuri K. Shatroff
>>> wrote:
14.04.2016 00:49, Dale wrote:
>
On Thursday, April 14, 2016 02:58:09 AM Dale wrote:
> J. Roeleveld wrote:
> > On Thursday, April 14, 2016 10:33:10 AM Yuri K. Shatroff wrote:
> >> 14.04.2016 00:49, Dale wrote:
> >>> Yuri K. Shatroff wrote:
> >> Hi Dale,
> >>
> >>> I'm not sure on where you got the black screen. If it is when X
On Thursday, April 14, 2016 10:33:10 AM Yuri K. Shatroff wrote:
> 14.04.2016 00:49, Dale wrote:
> > Yuri K. Shatroff wrote:
> Hi Dale,
>
> > I'm not sure on where you got the black screen. If it is when X
> > started, did you switch to sddm or some other compatible display
> > manager? The old
Neil Bothwick wrote:
> On Thu, 14 Apr 2016 02:58:09 -0500, Dale wrote:
>
>> While at it, what is a command that lists all the users that are set up
>> on a system? I tried a couple things but only found one that lists who
>> is currently logged in. I would like them all listed.
> cat
Yuri K. Shatroff wrote:
> 14.04.2016 10:43, J. Roeleveld wrote:
>> No idea here, logs?
>
> I didn't see anything relevant in Xorg.?.log (neither in messages) and
> since there was no kdm which usually tracks all KDE messages I didn't
> know where to look. Neither any new log files appeared.
>
>
On Thu, 14 Apr 2016 02:58:09 -0500, Dale wrote:
> While at it, what is a command that lists all the users that are set up
> on a system? I tried a couple things but only found one that lists who
> is currently logged in. I would like them all listed.
cat /etc/passwd ;-)
Or if you want to get
On Thursday, April 14, 2016 09:03:08 AM Neil Bothwick wrote:
> On Thu, 14 Apr 2016 02:58:09 -0500, Dale wrote:
> > While at it, what is a command that lists all the users that are set up
> > on a system? I tried a couple things but only found one that lists who
> > is currently logged in. I
J. Roeleveld wrote:
> On Thursday, April 14, 2016 10:33:10 AM Yuri K. Shatroff wrote:
>> 14.04.2016 00:49, Dale wrote:
>>> Yuri K. Shatroff wrote:
>> Hi Dale,
>>
>>> I'm not sure on where you got the black screen. If it is when X
>>> started, did you switch to sddm or some other compatible
14.04.2016 00:49, Dale wrote:
Yuri K. Shatroff wrote:
Hi guys,
12.04.2016 08:38, Dale wrote:
Howdy,
Well, I went and did it.
So I went and did it, too.
Thank gods I made a backup. After emerging plasma-meta which wasn't
too easy because of dependency hell with eg networkmanager (Use-flag
14.04.2016 10:43, J. Roeleveld wrote:
On Thursday, April 14, 2016 10:33:10 AM Yuri K. Shatroff wrote:
14.04.2016 00:49, Dale wrote:
Yuri K. Shatroff wrote:
Hi Dale,
I'm not sure on where you got the black screen. If it is when X
started, did you switch to sddm or some other compatible
On Thu, 14 Apr 2016 10:14:14 +0200, J. Roeleveld wrote:
> > cat /etc/passwd ;-)
> >
> > Or if you want to get clever and give just a list of usernames
> >
> > awk -F: '{print $1}' /etc/passwd
>
> This doesn't work when using LDAP authentication or similar:
>
> nas ~ # cat /etc/passwd | grep
On Thursday 14 Apr 2016 19:43:52 Jonathan Callen wrote:
> On 04/14/2016 04:40 PM, Mick wrote:
> > I run chkrootkit and rkhunter on my laptop. Suddenly I noticed
> > this in my logs:
> >
> > /dev/shm/pulse-shm-2469735543 Possible Linux/Ebury - Operation
> > Windigo installetd
> >
> >
> > Then,
Hi Peter,
On 11/04/16 20:34, Peter Humphrey wrote:
> On Saturday 09 April 2016 11:12:51 Mick wrote:
>> I noticed today that Plasma 5 is now stable, which means I will soon have
>> to deal with it.
>
> I saw that too, and it cast a gloom over the rest of my day. I intend to
> stick
> with KDE-4
On Thursday 14 Apr 2016 11:21:39 Yuri K. Shatroff wrote:
> 14.04.2016 10:43, J. Roeleveld wrote:
> > On Thursday, April 14, 2016 10:33:10 AM Yuri K. Shatroff wrote:
> >> 14.04.2016 00:49, Dale wrote:
> >>> Yuri K. Shatroff wrote:
> >> Hi Dale,
> >>
> >>> I'm not sure on where you got the black
On Thu, Apr 14, 2016 at 4:21 AM, Yuri K. Shatroff wrote:
>
>> No idea here, logs?
>>
>
> I didn't see anything relevant in Xorg.?.log (neither in messages) and
> since there was no kdm which usually tracks all KDE messages I didn't know
> where to look. Neither any new log
On Thu, 14 Apr 2016 08:14:05 -0700, Daniel Frey wrote:
> I didn't have any problems with sddm, but that slow interface drove me
> nuts. I was using nouveau, and I read against running that with nvidia
> cards, so I installed the binary driver and I went from a very slow
> interface (i.e. 5-10
On 04/14/2016 12:33 AM, Yuri K. Shatroff wrote:
>
> Sddm worked as expected, not to mention its veeery slow interface (for
> that nvidia drivers can be blamed, but whatever). The black screen
> appeared after logging in.
>
I didn't have any problems with sddm, but that slow interface drove me
Michael Orlitzky gentoo.org> writes:
> > I should qualify that -- a lot of the descriptions suck, not all of
> > them. When in doubt, I let the profile decide.
Thanks for all the deprecated flag cleaning tools/ideas.
> Nah, most of them suck. USE=derp enables libderp? Awesome. WTF does
>
So,
I was going through the handbook to look at the logic therein
before bash scripting up some simple install recipies for my clustering
work, which is eclusively amd64+radeon, atm.
In the Kernel section of the amd64-handbook::
"root #nano -w /etc/fstab
FILE /etc/fstabConfiguring the /boot
32 matches
Mail list logo