Re: [e-users] I might have found the solution to the black screen issue.

[Masaru Nomiya]

Hello,

In the Message; 

  Subject: Re: [e-users] I might have found the solution to the black 
screen issue.
  Message-ID : 
  Date & Time: Fri, 5 Aug 2022 22:43:22 +0930

[SL] == Simon Lees  has written:

[...]
MN> > As you know, system.conf included in the
MN> > enlightenment-0.25.3-269.5.src.rpm, it is set as fllows;

MN> > [...]
MN> > # deny everyone else by default
MN> > user: * deny:  *
MN> > 
MN> > In response to this setting, the enlightenment complains that it
MN> > should be changed to 'allow'.

SL>  This should be ok because atleast from
SL>  
https://build.opensuse.org/package/view_file/X11:Enlightenment:Factory/enlightenment/system.conf?expand=1
SL>  the following is before it

SL>  user:*  allow: backlight
SL>  user:*  allow: ddc
SL>  user:*  allow: rfkill
SL>  user:*  allow: l2ping
SL>  user:*  allow: cpufreq

SL>  which means that all users have access to all the modules we actually need.

I know it.

Enlightenment complains about the bottom part;

[...]
   # deny everyone else by default
   user: * deny:  *

I installed it yesterday from the Enlightenment:Nightly repo, and it
is fixed as follows;

[...]
   # deny everyone else by default
   user: * allow:  *

[...]
SL>>>  enlightenment-wayland.desktop file that is also installed which is
SL>>>  labeled in gdm as experimental again [...]

MN>> It is as you say with sddm, too.
 
MN>> In gdm, I can log in by entering my password, but in sddm, two
MN>> enlightenment items appear in the menu, and I have to select the lower
MN>> one and enter my password before I can log in.
MN>> 
MN>> I don't understand why two enlightenment items appear when there is
MN> > only one enlightenment.desktop in /usr/share/xsessions.

SL>  Can you please paste the output of "ls -la /usr/share/xsessions/" and ls
SL>  -la /usr/share/wayland-sessions/"

For a long time, they were

in /usr/share/xsessions/

   enlightenment.desktop -> ../wayland-xsessions/enlightenment.desktop

and, in /usr/share/wayland-xsessions/

   enlightenment-wayland.desktop
   enlightenment.desktop

Some time ago, they were changed to;

in /usr/share/xsessions/

   enlightenment.desktop

and, in /usr/share/wayland-xsessions/

   enlightenment-wayland.desktop
   enlightenment.desktop -> ../xsessions/enlightenment.desktop

In the above case, I had to do the following;

  1. # rm /usr/share/xsessions/enlightenment.desktop
  2. # cp /usr/share/waylans-xsessions/enlightenment.desktop 
/usr/share/xsessions/

Regardless of this change, in both cases, I had to select the
Enlightenment item at the bottom of the sddm menu to log in.

I am wondering if it would otherwise try to start in Wayland.

But now, with the efl & enlightenment installed from the
Enlightenment:Nightly repo, I can log in smoothly.

I changed the repo after I saw the enlightenment.spec said;

  # Wayland is broken with current efl waiting for a new e release
  %if 0%{?suse_version} > 1500 || 0%{?fedora_version} > 27
  # Disable wayland for now due to NVIDIA issues
  %define enable_wayland 0
  %else
  %define enable_wayland 0
  %endif

MN>> I have no intention to change to nouveau and I will not move to
MN>> Wayland because of it. I think Wayland itself　is just experimetal.
 
MN>> Or does Tumbleweed have the requirements for enable_wayland?

SL>  Yeah basically if you use gdm, and choose "Enlightenment" which comes
SL>  from /usr/share/xsessions you will get enlightenment and everything will
SL>  run fine, if you choose Enlightenment - Wayland (Experemental) or
SL>  whatever I called it you can test out wayland that one should live in
SL>  /usr/share/wayland-sessions/. Last time I tried sddm it ignored wayland
SL>  so I've never tested it there but I can confirm with an intel gpu and
SL>  gdm it works.

I had to go to nouveau

SL>  Raster said there has been some issues with Nvidia and efl in gles mode
SL>  if your seeing these issues at some point i'll i'll probably have to
SL>  build a separate efl package using traditional opengl for nvidia, this
SL>  is basically just work I haven't found time for yet.

What is the problem?

In any case, I'll wait until you have spare time.

Regards.

---
┏━━┓彡   Masaru Nomiya mail-to: m.nomiya @ galaxy.dti.ne.jp
┃＼／彡
┗━━┛   " Today’s China is not the old China humiliated and bullied over
   100 years ago. It is time for these people to wake up from their
   imperial dream."

  -- Hua Chunying’s Regular Press Conference on August 4, 2022 -- 


___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] I might have found the solution to the black screen issue.

[Simon Lees]

On 8/5/22 10:48, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject    : Re: [e-users] I might have found the solution to the black 
> screen issue.
>   Message-ID : <31a55bfd-93a7-9124-8d5b-de2119c7f...@suse.de>
>   Date & Time: Thu, 4 Aug 2022 23:40:33 +0930
> 
> [SL] == Simon Lees  has written:
> 
> [...]
> SL>  Feel free to ask those questions here, I look after those and still keep
> SL>  an eye on this list.
> 
> Many thanks.
> 
> SL>  In terms of system.conf we were disabling some modules that aren't used
> SL>  on systemd systems to reduce the security footprint, but then we stopped
> SL>  having a "users" group on new systems so it had to be changed, openqa
> SL>  seems to be telling me this is working again  but if its not right let
> SL>  me know which repo so I can fix it.
> 
> Sorry, I didn't check enough.
> 
> As you know, system.conf included in the
> enlightenment-0.25.3-269.5.src.rpm, it is set as fllows;
> 
> [...]
> # deny everyone else by default
> user: * deny:  *
> 
> In response to this setting, the enlightenment complains that it
> should be changed to 'allow'.

This should be ok because atleast from
https://build.opensuse.org/package/view_file/X11:Enlightenment:Factory/enlightenment/system.conf?expand=1
the following is before it

user:*  allow: backlight
user:*  allow: ddc
user:*  allow: rfkill
user:*  allow: l2ping
user:*  allow: cpufreq

which means that all users have access to all the modules we actually need.

> SL>  Similarly at one point in some repos there was a bug where a wayland
> SL>  enlightenment.desktop file was being installed which gdm will pick over
> SL>  the X11 one, as far as I know this should be fixed, so that the default
> SL>  option with enlightenment.desktop is X11 but there is now an
> SL>  enlightenment-wayland.desktop file that is also installed which is
> SL>  labeled in gdm as experimental again if this was missed in a  repo
> SL>  please let me know where (its a 2 line fix).
> 
> Those I am referring to as the openSUSE build is located at;
> 
> https://download.opensuse.org/repositories/X11:/Enlightenment:/Factory/openSUSE_Tumbleweed/
> 
> SL>  enlightenment-wayland.desktop file that is also installed which is
> SL>  labeled in gdm as experimental again [...]
> 
> It is as you say with sddm, too.
> 
> In gdm, I can log in by entering my password, but in sddm, two
> enlightenment items appear in the menu, and I have to select the lower
> one and enter my password before I can log in.
> 
> I don't understand why two enlightenment items appear when there is
> only one enlightenment.desktop in /usr/share/xsessions.

Can you please paste the output of "ls -la /usr/share/xsessions/" and ls
-la /usr/share/wayland-sessions/"
> 
> I have a basic question.
> 
> I can't figure out why Tumbleweed gives me
> 
>   %define enable_wayland 1
> 
> when it is written
> 
> # Wayland is broken with current efl waiting for a new e release
> 
> as the comments.
> 
> I have no intention to change to nouveau and I will not move to
> Wayland because of it. I think Wayland itself　is just experimetal.
> 
> Or does Tumbleweed have the requirements for enable_wayland?

Yeah basically if you use gdm, and choose "Enlightenment" which comes
from /usr/share/xsessions you will get enlightenment and everything will
run fine, if you choose Enlightenment - Wayland (Experemental) or
whatever I called it you can test out wayland that one should live in
/usr/share/wayland-sessions/. Last time I tried sddm it ignored wayland
so I've never tested it there but I can confirm with an intel gpu and
gdm it works.

Raster said there has been some issues with Nvidia and efl in gles mode
if your seeing these issues at some point i'll i'll probably have to
build a separate efl package using traditional opengl for nvidia, this
is basically just work I haven't found time for yet.

Cheers

-- 
Simon Lees (Simotek)http://simotek.net

Emergency Update Team   keybase.io/simotek
SUSE Linux   Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] I might have found the solution to the black screen issue.

[Masaru Nomiya]

Hello,

In the Message; 

  Subject: Re: [e-users] I might have found the solution to the black 
screen issue.
  Message-ID : <31a55bfd-93a7-9124-8d5b-de2119c7f...@suse.de>
  Date & Time: Thu, 4 Aug 2022 23:40:33 +0930

[SL] == Simon Lees  has written:

[...]
SL>  Feel free to ask those questions here, I look after those and still keep
SL>  an eye on this list.

Many thanks.

SL>  In terms of system.conf we were disabling some modules that aren't used
SL>  on systemd systems to reduce the security footprint, but then we stopped
SL>  having a "users" group on new systems so it had to be changed, openqa
SL>  seems to be telling me this is working again  but if its not right let
SL>  me know which repo so I can fix it.

Sorry, I didn't check enough.

As you know, system.conf included in the
enlightenment-0.25.3-269.5.src.rpm, it is set as fllows;

[...]
# deny everyone else by default
user: * deny:  *

In response to this setting, the enlightenment complains that it
should be changed to 'allow'.

SL>  Similarly at one point in some repos there was a bug where a wayland
SL>  enlightenment.desktop file was being installed which gdm will pick over
SL>  the X11 one, as far as I know this should be fixed, so that the default
SL>  option with enlightenment.desktop is X11 but there is now an
SL>  enlightenment-wayland.desktop file that is also installed which is
SL>  labeled in gdm as experimental again if this was missed in a  repo
SL>  please let me know where (its a 2 line fix).

Those I am referring to as the openSUSE build is located at;

https://download.opensuse.org/repositories/X11:/Enlightenment:/Factory/openSUSE_Tumbleweed/

SL>  enlightenment-wayland.desktop file that is also installed which is
SL>  labeled in gdm as experimental again [...]

It is as you say with sddm, too.

In gdm, I can log in by entering my password, but in sddm, two
enlightenment items appear in the menu, and I have to select the lower
one and enter my password before I can log in.

I don't understand why two enlightenment items appear when there is
only one enlightenment.desktop in /usr/share/xsessions.

I have a basic question.

I can't figure out why Tumbleweed gives me

  %define enable_wayland 1

when it is written

# Wayland is broken with current efl waiting for a new e release

as the comments.

I have no intention to change to nouveau and I will not move to
Wayland because of it. I think Wayland itself　is just experimetal.

Or does Tumbleweed have the requirements for enable_wayland?

Regards.

---
┏━━┓彡  Masaru Nomiya   mail-to: nomiya @ galaxy.dti.ne.jp
┃＼／彡
┗━━┛  "Tim Cook, the C.E.O. of Apple, said earlier this year that he would
   not let his nephew join social networks.
   Bill Gates banned cellphone until his children were teenagers, and
   Melinda Gates wrote that she wished they had waited even longer.
   Steve Jobs would not let his young children near iPads."
  -- The New York Times --


___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] I might have found the solution to the black screen issue.

[Simon Lees]

On 8/4/22 14:04, Masaru Nomiya wrote:
> Hello,
> 
> In the Message; 
> 
>   Subject    : Re: [e-users] I might have found the solution to the black 
> screen issue.
>   Message-ID : <20220803153042.0afbd724fe67ca3caa6cf...@rasterman.com>
>   Date & Time: Wed, 3 Aug 2022 15:30:42 +0100
> 
> [CH] == Carsten Haitzler  has written:
> 
> CH>  On Wed, 03 Aug 2022 22:49:20 +0900 Masaru Nomiya 
>  said:
> 
> [...]
> MN> > Xorg server crashed?
> 
> CH>  that's what it looks like. X I/O fatal error is e's x connection being 
> killed
> CH>  off. that is most likely because the Xserver crashed. check your X logs. 
> it
> CH>  might bein the Xorg.0.log.old - also double check Xorg.1.log - maybe your
> CH>  display manager runs 2 xservers. i have seen this with gdm these days i 
> think,
> CH>  so display is :1 not :0.
> 
> 
> MN> > --- enlightenment.desktop.orig 2022-08-03 10:28:09.525158438 +0900
> MN> > +++ enlightenment.desktop 2022-08-03 10:28:35.249074546 +0900
> MN> > @@ -1,5 +1,5 @@
> MN> >  [Desktop Entry] -Type=Application
> MN> > -Type=Application
> MN> > +Type=XSession
> MN> >  Name=Enlightenment
> MN> >  Name[ca]=Enlightenment
> MN> >  Name[de]=Enlightenment
> MN> >  Name[de]=Enlightenment
>  
> MN>  > So far, this seems to have solved the black screen problem.
> 
> CH>  WTF? That has never been a requirement. Type=Application has
> CH>  always worked and no one has every defined that it MUST be of
> CH>  Type=XSession ...
> 
> Thanks.
> 
> You gave me a big hint.
> 
> Come to think of it, my problem started when I moved to opensuse
> Tumbleweed and started using efl & enlightenment in the openSUSE build.
> 
> So I downloaded the enlightenment-0.25.3-269.5.src.rpm from the
> openSUSE site, built & installed, then shutdown & rebooted many times,
> no problem. Of course, I did not rewrite the "enlightenment.desktop"
> file.
> 
> To my surprise, the file contents are different.
> 
> For example, when I install an openSUSE build, enlightenment asks me
> to change the system.conf, but the one I built at hand has a
> system.conf that matches enlightenment's requirements. (_ _?
> 
> Anyway, there are some questions about the wayland handling in the
> openSUSE built, so I built and installed efl and enlightenment without
> wayland, and they works fine for me now.

Feel free to ask those questions here, I look after those and still keep
an eye on this list.

In terms of system.conf we were disabling some modules that aren't used
on systemd systems to reduce the security footprint, but then we stopped
having a "users" group on new systems so it had to be changed, openqa
seems to be telling me this is working again  but if its not right let
me know which repo so I can fix it.

Similarly at one point in some repos there was a bug where a wayland
enlightenment.desktop file was being installed which gdm will pick over
the X11 one, as far as I know this should be fixed, so that the default
option with enlightenment.desktop is X11 but there is now an
enlightenment-wayland.desktop file that is also installed which is
labeled in gdm as experimental again if this was missed in a  repo
please let me know where (its a 2 line fix).

-- 
Simon Lees (Simotek)http://simotek.net

Emergency Update Team   keybase.io/simotek
SUSE Linux   Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] I might have found the solution to the black screen issue.

[Masaru Nomiya]

Hello,

In the Message; 

  Subject: Re: [e-users] I might have found the solution to the black 
screen issue.
  Message-ID : <20220803153042.0afbd724fe67ca3caa6cf...@rasterman.com>
  Date & Time: Wed, 3 Aug 2022 15:30:42 +0100

[CH] == Carsten Haitzler  has written:

CH>  On Wed, 03 Aug 2022 22:49:20 +0900 Masaru Nomiya  
said:

[...]
MN> > Xorg server crashed?

CH>  that's what it looks like. X I/O fatal error is e's x connection being 
killed
CH>  off. that is most likely because the Xserver crashed. check your X logs. it
CH>  might bein the Xorg.0.log.old - also double check Xorg.1.log - maybe your
CH>  display manager runs 2 xservers. i have seen this with gdm these days i 
think,
CH>  so display is :1 not :0.


MN> > --- enlightenment.desktop.orig 2022-08-03 10:28:09.525158438 +0900
MN> > +++ enlightenment.desktop 2022-08-03 10:28:35.249074546 +0900
MN> > @@ -1,5 +1,5 @@
MN> >  [Desktop Entry] -Type=Application
MN> > -Type=Application
MN> > +Type=XSession
MN> >  Name=Enlightenment
MN> >  Name[ca]=Enlightenment
MN> >  Name[de]=Enlightenment
MN> >  Name[de]=Enlightenment
 
MN>  > So far, this seems to have solved the black screen problem.

CH>  WTF? That has never been a requirement. Type=Application has
CH>  always worked and no one has every defined that it MUST be of
CH>  Type=XSession ...

Thanks.

You gave me a big hint.

Come to think of it, my problem started when I moved to opensuse
Tumbleweed and started using efl & enlightenment in the openSUSE build.

So I downloaded the enlightenment-0.25.3-269.5.src.rpm from the
openSUSE site, built & installed, then shutdown & rebooted many times,
no problem. Of course, I did not rewrite the "enlightenment.desktop"
file.

To my surprise, the file contents are different.

For example, when I install an openSUSE build, enlightenment asks me
to change the system.conf, but the one I built at hand has a
system.conf that matches enlightenment's requirements. (_ _?

Anyway, there are some questions about the wayland handling in the
openSUSE built, so I built and installed efl and enlightenment without
wayland, and they works fine for me now.

Regards.

---
┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp
┃＼／彡
┗━━┛ Think.
-- The IBM slogan --


___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Re: [e-users] I might have found the solution to the black screen issue.

[Carsten Haitzler]

On Wed, 03 Aug 2022 22:49:20 +0900 Masaru Nomiya  said:

> Hello,
> 
> In the Message; 
> 
>   Subject: Re: [e-users] Black screen issue - Why been excluded fcitx?
>   Message-ID : <8735ehsjbu.wl-nom...@galaxy.dti.ne.jp>
>   Date & Time: Sun, 31 Jul 2022 18:49:25 +0900
> 
> [MN] == Masaru Nomiya  has written:
> 
> [...]
> MN> I changed sddm to gdm 
> MN> It was a good opportunity, so I rearranged the kde-related
> MN> files, it was unexpectedly clear.
> 
> Unfortunately, I was caught in the persistent black screen problem,
> again.
> So, I changed gdm to lightdm, but was aloso caught in the persistent
> black screen problem.
> 
> Here, the .e-log.log said;
> 
> [...]
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: iCCP: known incorrect sRGB profile
> ESTART: 1.39836 [0.29579] - SLEEP
> CPUFREQ: pstate [min=0 max=100 turbo=1]
> libpng warning: iCCP: known incorrect sRGB profile
> SSS: e_sys_ction_do ret=1 a=0
> X I/O Error - fatal. Exiting
> 
> Xorg server crashed?

that's what it looks like. X I/O fatal error is e's x connection being killed
off. that is most likely because the Xserver crashed. check your X logs. it
might bein the Xorg.0.log.old - also double check Xorg.1.log - maybe your
display manager runs 2 xservers. i have seen this with gdm these days i think,
so display is :1 not :0.

> I can't think so, then I looked it up and watched it.
> 
> The Xorg.0.log in /var/lib/gdm/.local/share/xorg says;
> 
> [...]
> 110.223] (II) systemd-logind: releasing fd for 13:66
> [   110.246] (II) NVIDIA(GPU-0): Deleting GPU-0
> [   110.252] (II) Server terminated successfully (0). Closing log file.
> 
> That is, the Xorg server worked just fine.
> 
> As I thought that DM could not find the enlightenment_start command,
> then checked the enlightenment.desktop file, and found a strange
> description
> 
> [Desktop Entry]
> Type=Application
> Name=Enlightenment
> 「．..]
> 
> I thought that Type=Application is a mistake, so changed the file
> enlightenment.desktop to
> 
> --- enlightenment.desktop.orig 2022-08-03 10:28:09.525158438 +0900
> +++ enlightenment.desktop 2022-08-03 10:28:35.249074546 +0900
> @@ -1,5 +1,5 @@
>  [Desktop Entry] -Type=Application
> -Type=Application
> +Type=XSession
>  Name=Enlightenment
>  Name[ca]=Enlightenment
>  Name[de]=Enlightenment
>  Name[de]=Enlightenment
> 
> So far, this seems to have solved the black screen problem.

WTF? That has never been a requirement. Type=Application has always worked and
no one has every defined that it MUST be of Type=XSession ... 

> Now, I am using ENLIGHTENMENT via sddm, which has many reports of
> problems.
> 
> Am I misunderstanding something?
> 
> ---
> ┏━━┓彡 野宮  賢 mail-to: m.nomiya @ gmail.com
> ┃＼／彡
> ┗━━┛   "A bachelor’s degree still holds prestige as a ticket to the
>  middle class, but its value has received increasing scrutiny.
>  In the last several years, rising tuition and student loan debt
>  have led more Americans to reconsider an investment in
>  postsecondary education."
> 
>   -- Washington Post --
> 
> 
> ___
> enlightenment-users mailing list
> enlightenment-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> 


-- 
- Codito, ergo sum - "I code, therefore I am" --
Carsten Haitzler - ras...@rasterman.com



___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

[e-users] I might have found the solution to the black screen issue.

[Masaru Nomiya]

Hello,

In the Message; 

  Subject: Re: [e-users] Black screen issue - Why been excluded fcitx?
  Message-ID : <8735ehsjbu.wl-nom...@galaxy.dti.ne.jp>
  Date & Time: Sun, 31 Jul 2022 18:49:25 +0900

[MN] == Masaru Nomiya  has written:

[...]
MN> I changed sddm to gdm 
MN> It was a good opportunity, so I rearranged the kde-related
MN> files, it was unexpectedly clear.

Unfortunately, I was caught in the persistent black screen problem,
again.
So, I changed gdm to lightdm, but was aloso caught in the persistent
black screen problem.

Here, the .e-log.log said;

[...]
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
ESTART: 1.39836 [0.29579] - SLEEP
CPUFREQ: pstate [min=0 max=100 turbo=1]
libpng warning: iCCP: known incorrect sRGB profile
SSS: e_sys_ction_do ret=1 a=0
X I/O Error - fatal. Exiting

Xorg server crashed?

I can't think so, then I looked it up and watched it.

The Xorg.0.log in /var/lib/gdm/.local/share/xorg says;

[...]
110.223] (II) systemd-logind: releasing fd for 13:66
[   110.246] (II) NVIDIA(GPU-0): Deleting GPU-0
[   110.252] (II) Server terminated successfully (0). Closing log file.

That is, the Xorg server worked just fine.

As I thought that DM could not find the enlightenment_start command,
then checked the enlightenment.desktop file, and found a strange
description

[Desktop Entry]
Type=Application
Name=Enlightenment
「．..]

I thought that Type=Application is a mistake, so changed the file
enlightenment.desktop to

--- enlightenment.desktop.orig 2022-08-03 10:28:09.525158438 +0900
+++ enlightenment.desktop 2022-08-03 10:28:35.249074546 +0900
@@ -1,5 +1,5 @@
 [Desktop Entry] -Type=Application
-Type=Application
+Type=XSession
 Name=Enlightenment
 Name[ca]=Enlightenment
 Name[de]=Enlightenment
 Name[de]=Enlightenment

So far, this seems to have solved the black screen problem.

Now, I am using ENLIGHTENMENT via sddm, which has many reports of
problems.

Am I misunderstanding something?

---
┏━━┓彡 野宮  賢 mail-to: m.nomiya @ gmail.com
┃＼／彡
┗━━┛   "A bachelor’s degree still holds prestige as a ticket to the
   middle class, but its value has received increasing scrutiny.
   In the last several years, rising tuition and student loan debt
   have led more Americans to reconsider an investment in
   postsecondary education."

-- Washington Post --


___
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users