Re: [gentoo-user] KDE and the new plasma 5 thing

[Alan McKinnon]

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 compatible display
manager?  The old kdm isn't supported and from what I read, doesn't
work.  That may explain the black screen.

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.

Slow interface?
It works quite well on my laptop. Did you add the "sddm" user to the "video"
group as mentioned in the upgrade guide?


--
Joost




I missed that part somehow.  I just went and added it to the video group
here.  It worked tho.

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

Re: [gentoo-user] KDE and the new plasma 5 thing

[Yuri K. Shatroff]

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





Since kdm is gone, it's now sddm.log in the same place where kdm was.
This is what my log looks like.  Yours should look something like it I
would think.


[23:29:06.330] (II) DAEMON: Initializing...
[23:29:06.334] (II) DAEMON: Starting...
[23:29:06.334] (II) DAEMON: Adding new display on vt 7 ...
[23:29:06.334] (II) DAEMON: Display server starting...
[23:29:06.334] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth
/var/run/sddm/{baadb08a-2764-4aec-b839-6c2b7283ef79} -background none
-noreset -displayfd 17 vt7
[23:29:06.838] (II) DAEMON: Running display setup script
"/usr/share/sddm/scripts/Xsetup"
[23:29:06.842] (II) DAEMON: Display server started.
[23:29:06.842] (II) DAEMON: Socket server starting...
[23:29:06.842] (II) DAEMON: Socket server started.
[23:29:06.842] (II) DAEMON: Greeter starting...
[23:29:06.842] (II) DAEMON: Adding cookie to
"/var/run/sddm/{baadb08a-2764-4aec-b839-6c2b7283ef79}"
[23:29:06.847] (II) HELPER: [PAM] Starting...
[23:29:06.847] (II) HELPER: [PAM] Authenticating...
[23:29:06.847] (II) HELPER: [PAM] returning.
[23:29:06.848] (II) DAEMON: Greeter session started successfully
[23:29:06.865] (II) DAEMON: Message received from greeter: Connect
[23:29:22.968] (II) DAEMON: Message received from greeter: Login
[23:29:22.969] (II) DAEMON: Reading from
"/usr/share/xsessions/plasma.desktop"
[23:29:22.969] (II) DAEMON: Session
"/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
[23:29:22.975] (II) HELPER: [PAM] Starting...
[23:29:22.975] (II) HELPER: [PAM] Authenticating...
[23:29:23.012] (II) HELPER: [PAM] Preparing to converse...
[23:29:23.012] (II) HELPER: [PAM] Conversation with 1 messages
[23:29:23.323] (II) HELPER: [PAM] returning.
[23:29:23.353] (II) DAEMON: Authenticated successfully
[23:29:23.360] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession"
"/usr/bin/startkde"
[23:29:23.362] (II) HELPER: Adding cookie to "/home/dale/.Xauthority"
[23:29:23.366] (II) DAEMON: Session started
[23:29:23.384] (II) HELPER: [PAM] Ended.
[23:29:23.384] (II) DAEMON: Auth: sddm-helper exited successfully
[23:29:23.385] (II) DAEMON: Greeter stopped.


I think I got a complete section of it.


Ah, I remember that one, but no, there wasn't anything related to black 
screens.
I believe it was some internal problem with nvidia drivers and plasma-5 
3D effects. This can explain the presence of mouse pointer and menus 
flickering-through the black screen.


I'll probably repeat that a while later when I have more time. That 
first post of mine was too emotional, I like to be on the bleeding edge, 
even despite such faux pas. Thanks everyone for your replies!



Dale

:-)  :-)



--
Regards,
Yuri K. Shatroff

[gentoo-user] Has my PC been compromised?

[Mick]

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: SCAN_MODE_DEV set to 'THOROUGH'
[20:23:33]   Checking /dev for suspicious file types [ Warning ]
[20:23:33] Warning: Suspicious file types found in /dev:
[20:23:33]  /dev/shm/pulse-shm-3629268439: data
[20:23:33]  /dev/shm/pulse-shm-2350047684: data
[20:23:33]  /dev/shm/pulse-shm-2469735543: data
[20:23:33]  /dev/shm/pulse-shm-2586322339: data
[20:23:33]  /dev/shm/PostgreSQL.1804289383: data
[20:23:34]   Checking for hidden files and directories   [ Warning ]
[20:23:34] Warning: Hidden file found: /usr/share/man/man5/.k5login.5: troff 
or preprocessor input, ASCII text
[20:23:34] Warning: Hidden file found: /usr/share/man/man5/.k5identity.5: 
troff or preprocessor input, ASCII text
[20:23:34]   Checking for missing log files  [ Skipped ]
[20:23:34]   Checking for empty log files[ Skipped ]


I search on the errors and I arrive at this FAQs:

https://www.cert-bund.de/ebury-faq


Now, I frequently login using ssh into remote servers and LAN boxen for admin 
purposes, but not the other way around.  Is my box compromised, or is this two 
false positives in a row?

Are you getting anything similar on your systems?
-- 
Regards,
Mick

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

Re: [gentoo-user] KDE and the new plasma 5 thing

[Daniel Frey]

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 and I went from a very slow
>> interface (i.e. 5-10 seconds to respond to alt-tab, and on resume from
>> standby plasma would hang for 1-2 minutes) to crashing plasma every 3
>> minutes with the binary nvidia driver.
> 
> I'm using nouveau and it takes a good second for the window list to
> appear when pressing Alt-Tab for the first time in a session, but it's
> pretty quick, but not instant, after that. It may depend on the type of
> switcher you are using. I use Breeze, but some of the others are faster.
> 
> 

Hmm. On mine it wouldn't work, I had to keep holding alt for it to
register, eventually it would switch. Simply pressing alt+tab didn't do
anything on my desktop. This happened every time I wanted to switch to a
different window, and it got annoying very quickly.

I did try using different themes, it made no difference, plasma was
hanging (and crashing hard when I switched to the nvidia drivers.)

Dan

Re: [gentoo-user] Handbook(amd64)

[Corbin]

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
FILE /etc/fstabConfiguring the /boot mountpoint
/dev/sda2   /boot   ext2defaults0 2 "


Note
Further in the Gentoo installation, /etc/fstab will be configured again. The
/boot setting is needed right now as the genkernel application reads in this
configuration.

I build kernel by hand, similar to the handbook. I keep all of /usr/ on the
same partition, so I should not need at interramfs, right? But I am follow
the '4' partition example in the handbook, for this manual installation.


So it has been a long time since I looked that the handbook logic, so I may
just have missed the followup section on what the fstab should look like,
mostly following the amd64-handbook. In fact all I did was to add a
partition names 'local' for later mounting as /usr/local. But there is no
section on completing the fstab.

Now finishing up the manual installation I have this default /etc/fstab::

/dev/BOOT   /boot   ext2noauto,noatime  1 2
/dev/ROOT   /   ext3noatime 0 1
/dev/SWAP   noneswapsw  0 0
/dev/cdrom  /mnt/cdrom  autonoauto,ro   0 0
/dev/fd0/mnt/floppy autonoauto  0 0

which seems vintage. So a bug probable needs to be file on the handbook, but
a bit of discussion might be wise, first.


So where is the handbookd portion that describes these default steps that
leads to a simple (per the handbook exmaple) /etc/fstab? Or is this a bug?


<>

Also, I exclusively use amd video cards and we use to have a gentoo doc on
it's setup. Now in the gentoo wiki, I find::
https://wiki.gentoo.org/wiki/ATI_FAQ
https://wiki.gentoo.org/wiki/Radeon
https://wiki.gentoo.org/wiki/Amdgpu


I do not currently have any of the newest AMD (fury*) cards so scripting
up that part of radeon card installation seems most straightforward by
a generic make.conf entry for radeon and lesser defaults that work::
VIDEO_CARDS="radeon radeonsi vesa "

and then the appropriate ebuilds and kernel config options. Any suggestions
related to ebuild, flags, kernel option and installation steps would be
appreciated. I could have easily missed an existing doc, or interpertation
that lends a blanket system for radeon video card installations.

James






Info for you ...

Gentoo Handbook x86_64 ( A.K.A. amd64 )
Date : April 14,2016

Section Headings :

Configuring the Linux kernel
( Partial fstab file created for genkernel )

Configuring the system
( full fstab file creation / template provided )

The handbook expects you to use the template, any install notes you 
made, and info from the appropriate man pages to finalize the fstab 
file. Experience/Knowledge is key.

Re: [gentoo-user] Re: KDE5 & Disabling search and recent documents & thoughts

[Daniel Frey]

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 otherwise it seems to work OK fo rme.

I actually forgot I sent this to the list, I've calmed down now. I got
so mad at one point the whole K desktop looked red :-)

I did try disabling through system settings->search (and I found
balooctl shortly afterward and used that too) but even after multiple
reboots baloo insisted on running and indexing files.

> 
> Duncan has some patches floating around if you want to strip baloo out
> completely.

I actually don't care if it's installed, but it wasn't staying disabled
for me, even after multiple times telling it to.

> 
>> One other gripe on KDE5: it's 2016, why can't we use the meta key to pop
>> up the menu? Really...
> 
> Not sure the reason why it's not native functionality, but you might try
> x11-misc/ksuperkey.

Thanks for that tip! I'll check it out (although I'm back on kde4 now.
More on that below.)

> 
>> Other than that, things are a bit different. I'm not sure I like the
>> flat look yet. After the upgrade for some reason the K menu was
>> invisible, but when I set the theme to Oxygen it was visible again? I
>> thought that was odd, did anyone else experience that?
> 
> Maybe a botched settings migration?

I forgot to emerge the wedge-compatibility layer dev-libs/sni-qt,
figured that out a couple days later.

Last night I reverted back to kde4. Plasma was hanging quite freqently
(on resume, plasma would hang for 1-2 minutes before I could use the
taskbar/K menu. I also couldn't switch using alt+tab - if I pressed it
quickly like I would in kde4 nothing would happen. If I pressed alt+tab,
released tab, and held alt for 3-5 seconds it would work, which was
downright annoying.) I tried disabling the compositor, no luck. Then I
thought this might be because of the way I disabled baloo so I undid it
and remerged it but it made no difference.

I then discovered that functionality was broken in kde5, most notably
Dolphin stayed at the kde4 version (newest versions were keyworded
unstable) which means its integration was all broken.

Shortly after that I found out nouveau was not recommended for nvidia
cards, so I installed the binary driver and went from regular freezing
to downright crashing. Plasma would crash every 2-3 minutes instead of
freezing. :-(

I'm back on nouveau with kde4 and everything is working fine. I will
wait out the upgrade to kde5/plasma & mask it if needed for as long as
possible, it's nowhere near usable for me. I messed with it for 4-5 days
trying to get it to work without crashing and gave up.

Dan

[gentoo-user] Re: KDE and the new plasma 5 thing

[walt]

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
> >   
> 
> Hey that's neat! Attached...

Along the left edge of the screen you have a bunch of widgets for CPU,
disk, and network activity.  What kde/plasma stuff are you using to do
that, and does it all depend on ~arch packages?  Will it still work
tomorrow?  :p

Re: [gentoo-user] Re: confessions of a former USE=

[waltdnes]

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 only used (USE="-*") for small systems like firewalls, devices,
> or other minimized servers. If you think about it, most of us,
> on a workstation, what everything that will work. The exception being
> somebody with meager resources or other minimizations that warrant constraint.

  I used to use USE='-* blah blah blah", where "blah blah blah" was a
lot of flags.  My rule of thumb was to compare...

* how many "foobar" entries I'd have to make in package.use if I didn't
  include "foobar" in make.conf, versus...
* how many "-foobar" entries I'd have to make in package.use if I did
  include "foobar" in make.conf

  Which ever way resulted in fewer entries in package.use was the way
I'd go.  I effectively built my own custom profile.  I've now switched
to the conventional style, without "-*", but I now have a lot of
"-foobar" flags in USE, like so...

USE="10bit 12bit X apng bindist ffmpeg gles2 jpeg netifrc png snappy szip 
truetype x264 x265 xorg -acl -berkdb -caps -chatzilla -cracklib -crypt 
-filecaps -gallium -gdbm -gmp-autoupdate -graphite -gstreamer -iconv 
-introspection -ipc -iptables -ipv6 -libav -llvm -manpager -nls -openmp -pam 
-pch -roaming -sendmail -spell -tcpd -udev -udisks -unicode -upower -uuid 
-xinerama"

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

[gentoo-user] Re: KDE5 & Disabling search and recent documents & thoughts

[Michael Palimaka]

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 can't we have a single checkbox to disable all this crap? I found
> one and it didn't work (search in system settings.) Then when I was
> searching around online I found out it will reenable itself magically
> randomly anyway!
> 
> I also tried balooctl and it didn't work either.
> 
> So I got very pissed off at this point and did the following:
> 
> $ chmod 444 ~/.kde4/share/apps/RecentDocuments/
> $ rm /usr/bin/*baloo*
> 
> Rebooted
> 
> $ rm -rf ~/.config/baloo*
> $ rm -rf ~/.local/share/baloo
> 
> Rebooted again
> 
> ...and FINALLY it stopped indexing and remembering stuff that I told it
> not to. It still remembers the last application used, but I don't really
> care about that. I've put those commands in a script in /etc/local.d too.
> 
> Just figured others might want the info. A note, searching for files
> through Dolphin can be affected by this. I never do that myself, I
> always use a shell (konsole, etc.)
> 
> I've been using and tweaking for a couple hours now and haven't seen any
> ill side-effects from my "nuclear" option.

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 otherwise it seems to work OK fo rme.

Duncan has some patches floating around if you want to strip baloo out
completely.

> One other gripe on KDE5: it's 2016, why can't we use the meta key to pop
> up the menu? Really...

Not sure the reason why it's not native functionality, but you might try
x11-misc/ksuperkey.

> Other than that, things are a bit different. I'm not sure I like the
> flat look yet. After the upgrade for some reason the K menu was
> invisible, but when I set the theme to Oxygen it was visible again? I
> thought that was odd, did anyone else experience that?

Maybe a botched settings migration?

> 
> Dan
> 
> 

Kind regards,

Michael

[gentoo-user] Re: Has my PC been compromised?

[Jonathan Callen]

-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:
> 
> [20:23:27] Info: Starting test name 'filesystem' [20:23:27]
> Performing filesystem checks [20:23:27] Info: SCAN_MODE_DEV set to
> 'THOROUGH' [20:23:33]   Checking /dev for suspicious file types
> [ Warning ] [20:23:33] Warning: Suspicious file types found in
> /dev: [20:23:33]  /dev/shm/pulse-shm-3629268439: data 
> [20:23:33]  /dev/shm/pulse-shm-2350047684: data [20:23:33]
> /dev/shm/pulse-shm-2469735543: data [20:23:33]
> /dev/shm/pulse-shm-2586322339: data [20:23:33]
> /dev/shm/PostgreSQL.1804289383: data [20:23:34]   Checking for
> hidden files and directories   [ Warning ] [20:23:34] Warning:
> Hidden file found: /usr/share/man/man5/.k5login.5: troff or
> preprocessor input, ASCII text [20:23:34] Warning: Hidden file
> found: /usr/share/man/man5/.k5identity.5: troff or preprocessor
> input, ASCII text [20:23:34]   Checking for missing log files
> [ Skipped ] [20:23:34]   Checking for empty log files
> [ Skipped ]
> 
> 
> I search on the errors and I arrive at this FAQs:
> 
> https://www.cert-bund.de/ebury-faq
> 
> 
> Now, I frequently login using ssh into remote servers and LAN boxen
> for admin purposes, but not the other way around.  Is my box
> compromised, or is this two false positives in a row?
> 
> Are you getting anything similar on your systems?
> 

The hidden files in /usr/share/man/man5 are definitely false
positives.  These two files are installed by the app-crypt/mit-krb5
package, and just allow you to type "man .k5login" instead of "man
k5login" to get information about the ".k5login" file that you might
want to create in your home directory (if using kerberos).

The files in /dev/shm/ named "pulse-shm-*" are created by pulseaudio
for its own internal use; applications that may play sounds through
pulseaudio will create those files automatically.

The PostgreSQL.* file is likely also a false positive, but I do not
have postgres installed here to confirm.

- -- 
Jonathan Callen
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXECs4AAoJEEIQbvYRB3mgr94QAIztwA+j469ZZOFTFu7IHmCt
bWg2kHGA87nsNN4eQBrd2pqpHKTyMW3RrGYfstBGUX6/Qlt5QtP7D4FzIeFylNZI
gsJjpPowI4b//9b/W7IHrAfeOH9SyofryoZW/gDNmt3P/MRr1txPKQ/WWSj1i8kU
BgBrgJ3QbrP6Iu5HqyqwWc8oiMmMMLtDCzq2O203HpWqxiqqjUnviin1YY1s5+lP
WiCrK/AMhRXkZhvG2dVhQEoi1uBq535PwLghodl85WehZJHm/oWvda74XhiZvGXf
iF53CPb2qRY+Qu9dW6X/9cYXIOGiZH8N+vIoSQ0/WWucNaBPqaKqcfbDmuIroj+e
kDTWX1QsT8rj3rS57yEk7aLOLtF9tLgO1Eu46J2HE7ULbjpcRqUj2uylz4NH2knR
I1Hmpoy9WLJlqKaisFiCW9rywlRPjgUFp9oM1Tuv4UrjaefV7fSG7QHAgzXEr/8z
A5A06tSIDDRi9oTfzFYCfsur9XAIxih0yKBiujJbpbAFlRo39bJcoDfNYP4oFiX9
meO1oODp3JYq2o3XiNpUuPx5d5+60nWalJ7nHHlLyl0oMUUQOmjUKmDronQWjMvp
siK+bFH+Vl8eNcP8aOSOZO8CuPQtLsBbJJKnt3ZGbNLsquhuFBeDC+UJbmAV8Op0
4TEs+1Iw5qe6AQMD0UAz
=TVu5
-END PGP SIGNATURE-

[gentoo-user] Re: Handbook(amd64)

[James]

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 guidanced in the
setting up the disk secition::

/etc/fstabA full /etc/fstab example

/dev/sda2   /bootext2defaults,noatime 0 2
/dev/sda3   none swapsw   0 0
/dev/sda4   /ext4noatime  0 1
/dev/cdrom  /mnt/cdrom   autonoauto,user  0 0


But, I guess I was not clear in proposing this as a bug. There should be a
clickable link to jump ahead to that section (just above that you
mentioned). But even more problematic the minimal_CD leaves the fresh
install with what I listed below::



> > Now finishing up the manual installation I have this default /etc/fstab::
> >
> > /dev/BOOT   /boot   ext2noauto,noatime  1 2
> > /dev/ROOT   /   ext3noatime 0 1
> > /dev/SWAP   noneswapsw  0 0
> > /dev/cdrom /mnt/cdrom  autonoauto,ro   0 0
> > /dev/fd0   /mnt/floppy autonoauto  0 0
> >
> > which seems vintage. So a bug probable needs to be file on the 
> > handbook, but a bit of discussion might be wise, first.

I guess I was just expecting the minimal CD to match the handbook. So is
that a bug?  Is the missing link between the boot portion of the fstab
and the full fstab example a bug too? An enhancement

(yes, I did not see the full fstab in the subsequent section so thanks for
point that out.

Comments on if either if these are a bug?


James

Re: [gentoo-user] Re: KDE and the new plasma 5 thing

[Mick]

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 :-)
> > > 
> > > import -window root screenshot.png
> > 
> > Hey that's neat! Attached...
> 
> Along the left edge of the screen you have a bunch of widgets for CPU,
> disk, and network activity.  What kde/plasma stuff are you using to do
> that, and does it all depend on ~arch packages?  Will it still work
> tomorrow?  :p

Do you mean app-admin/gkrellm ?

-- 
Regards,
Mick

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

Re: [gentoo-user] Re: KDE Plasma 5 moved to stable

[Frank Steinmetzger]

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 too, and it cast a gloom over the rest of my day. I intend to 
> > stick 
> > with KDE-4 until some more sensible themes become available in Plasma 5, so 
> > I 
> > hope someone will be keeping an archive of KDE-4 somewhere, as in the 
> > earlier 
> > case of KDE 3 -> 4.
> 
> While both Plasma 4 and even Qt 4 are end-of-life upstream, I don't
> think they're going anywhere quite yet. There's no pressing need to
> remove it yet, and there's still a long way to go in terms of porting in
> the Qt ecosystem in general.
> 
> When it is eventually removed, I also don't see any reason why Qt 4 and
> KDE 4 can't go to the kde-sunset overlay along with 3.

What I loved about Gentoo in the olden days was that it was one of the very
few distros that still kept KDE3 in its normal repos for a long time, while
many other popular binary distros jumped on the band wagon as early as 4.1,
when it was barely usable and full of trivial bugs.

We even had the choice of installing both KDE3 and 4 at the same time. That
made transition far easier and it allowed me to get settled in due time. So
I'm not particularly worried about the next few months, especially with the
modularity and interchangeability of today's KDE components.

Thank you for that, devs and maintainers. Good night.
-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any social network.

All pleasant things are either immoral, illegal or make you fat.


signature.asc
Description: Digital signature

[gentoo-user] Re: KDE and the new plasma 5 thing

[Jonathan Callen]

-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:
> 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 kdm isn't supported
> and from what I read, doesn't work.  That may explain the
> black screen.
 
 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.
>>> 
>>> Slow interface? It works quite well on my laptop. Did you add
>>> the "sddm" user to the "video" group as mentioned in the
>>> upgrade guide?
>> 
>> No I didn't because I had a much more blatant issue with the
>> whole desktop than the 'SDDM display issues', I just didn't get
>> to that. Thanks for pointing it out, next time I'll give it a
>> try.
> 
> I don't have NVidia or use the full plasma desktop environment on
> my laptop (I use enlightenment instead with a Radeon card).
> However, I have not added sddm to the video group and have not
> noticed anything undue in my logs.  I have however noticed that
> sddm is slightly slower than kdm.
> 
> Why is the video group needed?  What does it do?
> 

The sddm user only needs to be in the video group if using the
proprietary NVIDIA driver, as it controls access to some low-level
device nodes created by that driver for the use of the NVIDIA driver's
userspace component.  It may be possible to use those device nodes to
perform certain privileged actions (the code behind them is in a
binary blob in the kernel with no source), so they are protected such
that only members of the video group can use them.

- -- 
Jonathan Callen
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJXECjYAAoJEEIQbvYRB3mgJK8P/1Komec/lz7TYLKM4SW7LfzW
54QCZJdJMh+Vc+fBCt39jtpdABpnJXaqkbB1kVFeMcxA+0qwr7jZ+Ba49sUq/zDH
LDCb+qBG+7Qn/5cVxHfiFj/mAQ7OEAPT1vTco5zfkFH8HhvqNEtte1P+5H5V2Yzq
//kHXwQ7Hwrk9pb/yRn0Ta4LAQBwSO/NgGCslFXyKUwzhENcnVnMz2LlxKadQrqS
pw6odg3yKBkFgruftsuj1m/4eayYCIDRGY+dFjLchMN48hq5uZ5HzXoEWoW9yqTB
1+uYo+kPr7lO+QhUyrLGv7UxNvpNOskZAcTr8Lk+8vndalV17IPRvrrKT6giVeGl
rU3wnD3AU57wfdqNJcm/LcEgk30OzsHl9ElEInbyADCh6x1yi3Ekw2Wbu2Kirat2
hSFK4efQn+yxu/taOFAFmvrYuDpGTOxs9WtA6tvMex8QOPKnovMWHz/WLAO0095U
M90slovPhSI1+gcxpHZgdMaBnwFm7ZNP31/EUKg3xQeiP2pATH11GC2a2kzIa5O7
9qUc8wX6nhJAO2to1snI5hhnwToRo0EvEO7Ia3MsUDwiN9GsGl/c5AD4jgk3iU6g
/e93JWuGvcYs+fJPDNEcx1GTrG822d7mb1n3N7A0HE3xfwVIhsKeqS03i6FcKd1s
fvJKT4IFNPvkZyrt45cg
=H+8Z
-END PGP SIGNATURE-

Re: [gentoo-user] KDE and the new plasma 5 thing

[J. Roeleveld]

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
> >>> started, did you switch to sddm or some other compatible display
> >>> manager?  The old kdm isn't supported and from what I read, doesn't
> >>> work.  That may explain the black screen.
> >> 
> >> 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.
> > 
> > Slow interface?
> > It works quite well on my laptop. Did you add the "sddm" user to the
> > "video" group as mentioned in the upgrade guide?
> > 
> > 
> > --
> > Joost
> 
> I missed that part somehow.  I just went and added it to the video group
> here.  It worked tho.
> 
> 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.

You mean things like:

# getent passwd
# getent group

--
Joost

Re: [gentoo-user] KDE and the new plasma 5 thing

[J. Roeleveld]

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 kdm isn't supported and from what I read, doesn't
> > work.  That may explain the black screen.
> 
> 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.

Slow interface?
It works quite well on my laptop. Did you add the "sddm" user to the "video" 
group as mentioned in the upgrade guide?

> > If it after you login, did you select the write session?  At first, I
> > wasn't sure which one to pick.  There is a couple at least KDE related.
> > I think I had one that said plasma and one that said KDE wayland.  I
> > have seen wayland talked about and tried it but I got a black screen.  I
> > had to restart xdm to reset it.  Then I chose plasma from the list and
> > it worked.  So, make sure you pick the right one.
> 
> There were three choices for the session. By default plasma was
> selected, this was the one that gave me the black screen. Others didn't
> plain work (returned to sddm).

No idea here, logs?


--
Joost

Re: [gentoo-user] KDE and the new plasma 5 thing

[Dale]

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 /etc/passwd ;-)
>
> Or if you want to get clever and give just a list of usernames
>
> awk -F: '{print $1}' /etc/passwd
>
>


It appears both yours and Joost's spit out the passwd file.  It works
tho.  I knew there was a way but couldn't remember what it was.  There
sure are a lot of them. 

Thanks to both.

Dale

:-)  :-) 

Re: [gentoo-user] KDE and the new plasma 5 thing

[Dale]

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


Since kdm is gone, it's now sddm.log in the same place where kdm was. 
This is what my log looks like.  Yours should look something like it I
would think.


[23:29:06.330] (II) DAEMON: Initializing...
[23:29:06.334] (II) DAEMON: Starting...
[23:29:06.334] (II) DAEMON: Adding new display on vt 7 ...
[23:29:06.334] (II) DAEMON: Display server starting...
[23:29:06.334] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth
/var/run/sddm/{baadb08a-2764-4aec-b839-6c2b7283ef79} -background none
-noreset -displayfd 17 vt7
[23:29:06.838] (II) DAEMON: Running display setup script 
"/usr/share/sddm/scripts/Xsetup"
[23:29:06.842] (II) DAEMON: Display server started.
[23:29:06.842] (II) DAEMON: Socket server starting...
[23:29:06.842] (II) DAEMON: Socket server started.
[23:29:06.842] (II) DAEMON: Greeter starting...
[23:29:06.842] (II) DAEMON: Adding cookie to
"/var/run/sddm/{baadb08a-2764-4aec-b839-6c2b7283ef79}"
[23:29:06.847] (II) HELPER: [PAM] Starting...
[23:29:06.847] (II) HELPER: [PAM] Authenticating...
[23:29:06.847] (II) HELPER: [PAM] returning.
[23:29:06.848] (II) DAEMON: Greeter session started successfully
[23:29:06.865] (II) DAEMON: Message received from greeter: Connect
[23:29:22.968] (II) DAEMON: Message received from greeter: Login
[23:29:22.969] (II) DAEMON: Reading from
"/usr/share/xsessions/plasma.desktop"
[23:29:22.969] (II) DAEMON: Session
"/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
[23:29:22.975] (II) HELPER: [PAM] Starting...
[23:29:22.975] (II) HELPER: [PAM] Authenticating...
[23:29:23.012] (II) HELPER: [PAM] Preparing to converse...
[23:29:23.012] (II) HELPER: [PAM] Conversation with 1 messages
[23:29:23.323] (II) HELPER: [PAM] returning.
[23:29:23.353] (II) DAEMON: Authenticated successfully
[23:29:23.360] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession"
"/usr/bin/startkde"
[23:29:23.362] (II) HELPER: Adding cookie to "/home/dale/.Xauthority"
[23:29:23.366] (II) DAEMON: Session started
[23:29:23.384] (II) HELPER: [PAM] Ended.
[23:29:23.384] (II) DAEMON: Auth: sddm-helper exited successfully
[23:29:23.385] (II) DAEMON: Greeter stopped.


I think I got a complete section of it. 

Dale

:-)  :-) 

Re: [gentoo-user] KDE and the new plasma 5 thing

[Neil Bothwick]

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 clever and give just a list of usernames

awk -F: '{print $1}' /etc/passwd


-- 
Neil Bothwick

Set phasers to extreme itching!


pgpSulPpb6l8D.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] KDE and the new plasma 5 thing

[J. Roeleveld]

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 would like them all listed.
> 
> 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 joost
nas ~ # getent passwd | grep joost
joost:x:1000:1000:System User:/home/joost:/bin/bash
nas ~ # 

--
Joost

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

Re: [gentoo-user] KDE and the new plasma 5 thing

[Dale]

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 display
>>> manager?  The old kdm isn't supported and from what I read, doesn't
>>> work.  That may explain the black screen.
>> 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.
> Slow interface?
> It works quite well on my laptop. Did you add the "sddm" user to the "video" 
> group as mentioned in the upgrade guide?
>
>
> --
> Joost
>
>

I missed that part somehow.  I just went and added it to the video group
here.  It worked tho. 

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. 

Dale

:-)  :-)

Re: [gentoo-user] KDE and the new plasma 5 thing

[Yuri K. Shatroff]

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
on plasma-meta was off but it turned out that another dependency
(`plasma-workspace`) has a quite irrelevant use-flag (`geolocation`)
which pulls in networkmanager) and ruby and all, I just got a black
screen with a sole mouse pointer. When I click mouse buttons, it
flickers and shows a glimpse of what the desktop should be, but then
again switches to black screen. I tried to remove ~/.kde4 but nothing
effectively changed.
Thanks but No thanks, I prefer to restore my backup. Not gonna repeat
this at home.




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 kdm isn't supported and from what I read, doesn't
work.  That may explain the black screen.


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.



If it after you login, did you select the write session?  At first, I
wasn't sure which one to pick.  There is a couple at least KDE related.
I think I had one that said plasma and one that said KDE wayland.  I
have seen wayland talked about and tried it but I got a black screen.  I
had to restart xdm to reset it.  Then I chose plasma from the list and
it worked.  So, make sure you pick the right one.


There were three choices for the session. By default plasma was 
selected, this was the one that gave me the black screen. Others didn't 
plain work (returned to sddm).



I might add, I don't solely depend on KDE for my desktop.  I have
Fluxbox and some other one as a backup.  If for some reason KDE doesn't
work, I use one of the backup desktops to get help.  Sometimes, it can
be something simple to fix which is better than losing everything that
was already done.  For me, it doesn't matter what that backup is as long
as my web browser and email program will run and is usable.  If I have
that, I can google and if needed post on this list for help.


Thanks for the hint, it's a good idea, I also had a couple of times when 
a working X would be helpful but failed to start due to kde related issues.


As for the new plasma stuff, I have almost all possible kde packages 
updated to 5.x (unstable), with the exception of kdm, kwin, settings and 
several others. My emerge of plasma-meta replaced these and additionally 
installed 78 packages, the larger half of which wasn't kde related 
(ruby, . What could have caused a black screen, I have no slightest idea 
and since it prevented me from work I gave it up.



Dale

:-)  :-)




--
Regards,
Yuri K. Shatroff

Re: [gentoo-user] KDE and the new plasma 5 thing

[Yuri K. Shatroff]

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 display
manager?  The old kdm isn't supported and from what I read, doesn't
work.  That may explain the black screen.


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.


Slow interface?
It works quite well on my laptop. Did you add the "sddm" user to the "video"
group as mentioned in the upgrade guide?


No I didn't because I had a much more blatant issue with the whole 
desktop than the 'SDDM display issues', I just didn't get to that. 
Thanks for pointing it out, next time I'll give it a try.



If it after you login, did you select the write session?  At first, I
wasn't sure which one to pick.  There is a couple at least KDE related.
I think I had one that said plasma and one that said KDE wayland.  I
have seen wayland talked about and tried it but I got a black screen.  I
had to restart xdm to reset it.  Then I chose plasma from the list and
it worked.  So, make sure you pick the right one.


There were three choices for the session. By default plasma was
selected, this was the one that gave me the black screen. Others didn't
plain work (returned to sddm).


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.



--
Regards,
Yuri K. Shatroff

Re: [gentoo-user] KDE and the new plasma 5 thing

[Neil Bothwick]

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 joost
> nas ~ # getent passwd | grep joost
> joost:x:1000:1000:System User:/home/joost:/bin/bash
> nas ~ # 

I know, but for Dale's purposes I knew it would be fine... and I didn't
need to double-check the use of cat :)


-- 
Neil Bothwick

Master of all I survey (at the moment, empty pizza boxes)


pgp9v4IbWa9mf.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] Re: Has my PC been compromised?

[Mick]

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, rkhunter shows:
> > 
> > [20:23:27] Info: Starting test name 'filesystem' [20:23:27]
> > Performing filesystem checks [20:23:27] Info: SCAN_MODE_DEV set to
> > 'THOROUGH' [20:23:33]   Checking /dev for suspicious file types
> > [ Warning ] [20:23:33] Warning: Suspicious file types found in
> > /dev: [20:23:33]  /dev/shm/pulse-shm-3629268439: data
> > [20:23:33]  /dev/shm/pulse-shm-2350047684: data [20:23:33]
> > /dev/shm/pulse-shm-2469735543: data [20:23:33]
> > /dev/shm/pulse-shm-2586322339: data [20:23:33]
> > /dev/shm/PostgreSQL.1804289383: data [20:23:34]   Checking for
> > hidden files and directories   [ Warning ] [20:23:34] Warning:
> > Hidden file found: /usr/share/man/man5/.k5login.5: troff or
> > preprocessor input, ASCII text [20:23:34] Warning: Hidden file
> > found: /usr/share/man/man5/.k5identity.5: troff or preprocessor
> > input, ASCII text [20:23:34]   Checking for missing log files
> > [ Skipped ] [20:23:34]   Checking for empty log files
> > [ Skipped ]
> > 
> > 
> > I search on the errors and I arrive at this FAQs:
> > 
> > https://www.cert-bund.de/ebury-faq
> > 
> > 
> > Now, I frequently login using ssh into remote servers and LAN boxen
> > for admin purposes, but not the other way around.  Is my box
> > compromised, or is this two false positives in a row?
> > 
> > Are you getting anything similar on your systems?
> 
> The hidden files in /usr/share/man/man5 are definitely false
> positives.  These two files are installed by the app-crypt/mit-krb5
> package, and just allow you to type "man .k5login" instead of "man
> k5login" to get information about the ".k5login" file that you might
> want to create in your home directory (if using kerberos).

OK, this is good to know.  I am not using kerberos, but I think it was 
installed as a dependency somewhere along the line.


> The files in /dev/shm/ named "pulse-shm-*" are created by pulseaudio
> for its own internal use; applications that may play sounds through
> pulseaudio will create those files automatically.
> 
> The PostgreSQL.* file is likely also a false positive, but I do not
> have postgres installed here to confirm.

I can't think why postgres would be flagged up as a warning.  I use it for 
akonadi instead of mysql, so unless some email ran a sql injection on it via 
kmail and got access to the database, it should be OK.

All these chrootkit and rkhunter warnings are about /dev/shm/ files/devices.  
Is there something that makes anything in /dev/shm inherently suspicious?

-- 
Regards,
Mick

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

[gentoo-user] Re: KDE Plasma 5 moved to stable

[Michael Palimaka]

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 until some more sensible themes become available in Plasma 5, so I 
> hope someone will be keeping an archive of KDE-4 somewhere, as in the earlier 
> case of KDE 3 -> 4.

While both Plasma 4 and even Qt 4 are end-of-life upstream, I don't
think they're going anywhere quite yet. There's no pressing need to
remove it yet, and there's still a long way to go in terms of porting in
the Qt ecosystem in general.

When it is eventually removed, I also don't see any reason why Qt 4 and
KDE 4 can't go to the kde-sunset overlay along with 3.

Kind regards,

Michael

Re: [gentoo-user] KDE and the new plasma 5 thing

[Mick]

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 screen.  If it is when X
> >>> started, did you switch to sddm or some other compatible display
> >>> manager?  The old kdm isn't supported and from what I read, doesn't
> >>> work.  That may explain the black screen.
> >> 
> >> 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.
> > 
> > Slow interface?
> > It works quite well on my laptop. Did you add the "sddm" user to the
> > "video" group as mentioned in the upgrade guide?
> 
> No I didn't because I had a much more blatant issue with the whole 
> desktop than the 'SDDM display issues', I just didn't get to that. 
> Thanks for pointing it out, next time I'll give it a try.

I don't have NVidia or use the full plasma desktop environment on my laptop (I 
use enlightenment instead with a Radeon card). However, I have not added sddm 
to the video group and have not noticed anything undue in my logs.  I have 
however noticed that sddm is slightly slower than kdm.

Why is the video group needed?  What does it do?

-- 
Regards,
Mick

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

Re: [gentoo-user] KDE and the new plasma 5 thing

[Gregory Woodbury]

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 files appeared.
>
> --
> Regards,
> Yuri K. Shatroff
>

​There might be some clues in ~/.xsession-errors, especially if there are
security or bad handle errors.​

-- 
-- 
G.Wolfe Woodbury
redwo...@gmail.com

Re: [gentoo-user] KDE and the new plasma 5 thing

[Neil Bothwick]

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 seconds to respond to alt-tab, and on resume from
> standby plasma would hang for 1-2 minutes) to crashing plasma every 3
> minutes with the binary nvidia driver.

I'm using nouveau and it takes a good second for the window list to
appear when pressing Alt-Tab for the first time in a session, but it's
pretty quick, but not instant, after that. It may depend on the type of
switcher you are using. I use Breeze, but some of the others are faster.


-- 
Neil Bothwick

Anyone able to feel pain is trainable.


pgpyflPhsZjzv.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] KDE and the new plasma 5 thing

[Daniel Frey]

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
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 seconds to respond to alt-tab, and on resume from
standby plasma would hang for 1-2 minutes) to crashing plasma every 3
minutes with the binary nvidia driver.

That coupled with an old version of Dolphin being installed creating
inconsistencies in the K menu made me revert and mask plasma for now.
It's far from ready for daily use.

It's not much use if it's that unstable. :-(

Dan

[gentoo-user] Re: confessions of a former USE=

[James]

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
> libderp actually DO for this package? We need a policy change to force
> developers to document all of their USE flags, but nobody wants to do
> the work I guess. (It would be hard.)

Yep. Digging a bit deeper into the ebuilds and codes does time limit
one's ability to discern what a particular flag is actually doing
in a given ebuild, particularly when used in multiple builds.

> First, you'd have to update euse (or a similar tool) to make the
> information available. There's no point in adding nice descriptions to
> metadata.xml if the users can't query it.

> Then, you'd have to figure out all the exceptions. Eclasses can add
> things to IUSE, so you would have to figure out the right language, like
> "you must document every flag in IUSE in the *ebuild*". You'd also want
> exceptions in cases like security bugs -- if there's a vulnerability in
> PHP tomorrow, you don't want to force me to add descriptions for 50 USE
> flags before I can fix it. Maybe just grandfather in existing versions.

Thanks for the insight and example. This is the sort of insight that belongs
in the devManual, imho. The devManual often does not explain the 'big'
picture and thus becomes a collections of facts, until one is bitten, goes
back and reads portions of the devManaul and then has an 'ah-ha' moment. 

> Repoman needs to enforce it, or else people will ignore it.

Excellent idea. I know that Gokturk has been working on the dev manual, and
doing a fantastic job, imho. He is quite friendly and receptive to ideas. I
just think he has keen insight in organizing and documents, so that is why I
mention him here. He seems to be sufficiently 'diplomatic' to mix all the
ideas and come up with a brew that is pleasing to most. Maybe this repoman
enhancement is a good topic for discussion in gentoo-dev, as repoman is
under study by quite a few folks these days? Surely the devManual and
repoman should be fully consistent and compatible resources

> Finally, you'd have to push it through the council and fight about it on
> the mailing lists for a while.


We'll be pulling for you (MO) on additional vision and upgrades to
repoman gentoo-dev is quite wonderful when folks 'go at it'. It keeps us
calm on  gentoo-user, since the devs usually have sharps as insight once
ideas start flying around 


Thanks to all for the insights,
James

[gentoo-user] Handbook(amd64)

[James]

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 mountpoint
/dev/sda2   /boot   ext2defaults0 2 "


Note
Further in the Gentoo installation, /etc/fstab will be configured again. The
/boot setting is needed right now as the genkernel application reads in this
configuration.

I build kernel by hand, similar to the handbook. I keep all of /usr/ on the
same partition, so I should not need at interramfs, right? But I am follow
the '4' partition example in the handbook, for this manual installation.


So it has been a long time since I looked that the handbook logic, so I may
just have missed the followup section on what the fstab should look like,
mostly following the amd64-handbook. In fact all I did was to add a
partition names 'local' for later mounting as /usr/local. But there is no
section on completing the fstab. 

Now finishing up the manual installation I have this default /etc/fstab::

/dev/BOOT   /boot   ext2noauto,noatime  1 2
/dev/ROOT   /   ext3noatime 0 1
/dev/SWAP   noneswapsw  0 0
/dev/cdrom  /mnt/cdrom  autonoauto,ro   0 0
/dev/fd0/mnt/floppy autonoauto  0 0

which seems vintage. So a bug probable needs to be file on the handbook, but
a bit of discussion might be wise, first.


So where is the handbookd portion that describes these default steps that
leads to a simple (per the handbook exmaple) /etc/fstab? Or is this a bug?


<>

Also, I exclusively use amd video cards and we use to have a gentoo doc on
it's setup. Now in the gentoo wiki, I find:: 
https://wiki.gentoo.org/wiki/ATI_FAQ
https://wiki.gentoo.org/wiki/Radeon
https://wiki.gentoo.org/wiki/Amdgpu


I do not currently have any of the newest AMD (fury*) cards so scripting
up that part of radeon card installation seems most straightforward by
a generic make.conf entry for radeon and lesser defaults that work::
VIDEO_CARDS="radeon radeonsi vesa "

and then the appropriate ebuilds and kernel config options. Any suggestions
related to ebuild, flags, kernel option and installation steps would be
appreciated. I could have easily missed an existing doc, or interpertation
that lends a blanket system for radeon video card installations.

James