On 8/18/22 20:59, Carsten Haitzler wrote:
On Thu, 18 Aug 2022 17:08:31 +0200 leoutat...@gmx.fr said:
On 8/13/22 23:05, Carsten Haitzler wrote:
On Sat, 13 Aug 2022 10:58:17 +0200 leoutat...@gmx.fr said:
On 8/12/22 20:27, Carsten Haitzler wrote:
On Fri, 12 Aug 2022 10:02:55 +0100 Carsten
On 8/13/22 23:05, Carsten Haitzler wrote:
On Sat, 13 Aug 2022 10:58:17 +0200 leoutat...@gmx.fr said:
On 8/12/22 20:27, Carsten Haitzler wrote:
On Fri, 12 Aug 2022 10:02:55 +0100 Carsten Haitzler
said:
On Fri, 12 Aug 2022 10:18:32 +0200 leoutat...@gmx.fr said:
On 6/20/22 16:23, Carsten
On 8/12/22 20:27, Carsten Haitzler wrote:
On Fri, 12 Aug 2022 10:02:55 +0100 Carsten Haitzler said:
On Fri, 12 Aug 2022 10:18:32 +0200 leoutat...@gmx.fr said:
On 6/20/22 16:23, Carsten Haitzler wrote:
On Mon, 20 Jun 2022 15:46:15 +0200 leoutat...@gmx.fr said:
On 6/10/22 10:22, Carsten
On 8/12/22 11:02, Carsten Haitzler wrote:
On Fri, 12 Aug 2022 10:18:32 +0200 leoutat...@gmx.fr said:
On 6/20/22 16:23, Carsten Haitzler wrote:
On Mon, 20 Jun 2022 15:46:15 +0200 leoutat...@gmx.fr said:
On 6/10/22 10:22, Carsten Haitzler wrote:
On Fri, 10 Jun 2022 08:45:44 +0200
On 6/20/22 16:23, Carsten Haitzler wrote:
On Mon, 20 Jun 2022 15:46:15 +0200 leoutat...@gmx.fr said:
On 6/10/22 10:22, Carsten Haitzler wrote:
On Fri, 10 Jun 2022 08:45:44 +0200 leoutat...@gmx.fr said:
On 6/9/22 23:53, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 22:41:08 +0200
On 6/20/22 16:21, Carsten Haitzler wrote:
On Mon, 20 Jun 2022 14:01:44 +0200 leoutat...@gmx.fr said:
On 6/13/22 11:42, Carsten Haitzler wrote:
On Sun, 12 Jun 2022 17:13:15 +0200 leoutat...@gmx.fr said:
On 6/10/22 10:22, Carsten Haitzler wrote:
On Fri, 10 Jun 2022 08:45:44 +0200
On 6/10/22 10:22, Carsten Haitzler wrote:
On Fri, 10 Jun 2022 08:45:44 +0200 leoutat...@gmx.fr said:
On 6/9/22 23:53, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 22:41:08 +0200 leoutat...@gmx.fr said:
On 6/9/22 12:16, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 10:41:25 +0200
On 6/13/22 11:42, Carsten Haitzler wrote:
On Sun, 12 Jun 2022 17:13:15 +0200 leoutat...@gmx.fr said:
On 6/10/22 10:22, Carsten Haitzler wrote:
On Fri, 10 Jun 2022 08:45:44 +0200 leoutat...@gmx.fr said:
On 6/9/22 23:53, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 22:41:08 +0200
On 6/10/22 10:22, Carsten Haitzler wrote:
On Fri, 10 Jun 2022 08:45:44 +0200 leoutat...@gmx.fr said:
On 6/9/22 23:53, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 22:41:08 +0200 leoutat...@gmx.fr said:
On 6/9/22 12:16, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 10:41:25 +0200
On 6/10/22 10:22, Carsten Haitzler wrote:
On Fri, 10 Jun 2022 08:45:44 +0200 leoutat...@gmx.fr said:
On 6/9/22 23:53, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 22:41:08 +0200 leoutat...@gmx.fr said:
On 6/9/22 12:16, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 10:41:25 +0200
On 6/9/22 23:53, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 22:41:08 +0200 leoutat...@gmx.fr said:
On 6/9/22 12:16, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 10:41:25 +0200 leoutat...@gmx.fr said:
On 6/9/22 09:55, Carsten Haitzler wrote:
On Wed, 8 Jun 2022 19:50:27 +0200 leoutat...@gmx.fr
On 6/9/22 12:16, Carsten Haitzler wrote:
On Thu, 9 Jun 2022 10:41:25 +0200 leoutat...@gmx.fr said:
On 6/9/22 09:55, Carsten Haitzler wrote:
On Wed, 8 Jun 2022 19:50:27 +0200 leoutat...@gmx.fr said:
On 6/8/22 19:17, Carsten Haitzler wrote:
On Wed, 8 Jun 2022 15:39:17 +0200 leoutat...@gmx.fr
On 6/9/22 09:55, Carsten Haitzler wrote:
On Wed, 8 Jun 2022 19:50:27 +0200 leoutat...@gmx.fr said:
On 6/8/22 19:17, Carsten Haitzler wrote:
On Wed, 8 Jun 2022 15:39:17 +0200 leoutat...@gmx.fr said:
actually wait - is this a laptop? or using ddc? dimming timeout set? then
the 30 sec may be
On 6/8/22 19:17, Carsten Haitzler wrote:
On Wed, 8 Jun 2022 15:39:17 +0200 leoutat...@gmx.fr said:
actually wait - is this a laptop? or using ddc? dimming timeout set? then the
30 sec may be the dimming timeout. e will run a timer after that that then
totally blanks the screen. this timer is
On 6/7/22 22:24, Carsten Haitzler wrote:
On Tue, 7 Jun 2022 17:56:57 +0200 leoutat...@gmx.fr said:
Hi
I don't understand why, sometimes, screen blanking doesn't work on
enlightenment.
Most of time, it works but sometimes not. Before I thought this issue
comes from intel driver (modesetting
Hi
I don't understand why, sometimes, screen blanking doesn't work on
enlightenment.
Most of time, it works but sometimes not. Before I thought this issue
comes from intel driver (modesetting i915) but now, i'm sure this not
the case because i get same issue when i launch enlightenment using
On 2/7/22 17:05, Carsten Haitzler wrote:
On Mon, 7 Feb 2022 14:42:08 +0100 leoutat...@gmx.fr said:
are the fonts the same size as in e? have you tried changning the base dpi
from 76 to 90 or 96 in advanced scale settings? do you have a custom font set
for gtk things that used a very small font
On 2/7/22 17:05, Carsten Haitzler wrote:
On Mon, 7 Feb 2022 14:42:08 +0100 leoutat...@gmx.fr said:
are the fonts the same size as in e? have you tried changning the base dpi
from 76 to 90 or 96 in advanced scale settings? do you have a custom font set
for gtk things that used a very small font
Hi
Since last efl, enlightenment, *git* versions, some gtk applications,
firefox and thunderbird fonts, are very small: from/too/subject, tool
bar, menu bar, bookmarks in sidebar, but not in pages or inside mail
messages. Strangely, Gimp and Tor browser (based on firefox esr) are not
affected,
On 4/11/21 7:28 PM, Jérémy Zurcher wrote:
I just did
git clone ... && ./autogen.sh && ./configure && make
Issue came from my (Arch) custom build script.
It builds successfully now :)
On Sunday 11 April 2021 16:38, leoutat...@gmx.fr wrote :
Hi
I try to build enventor git master version
Hi
I try to build enventor git master version with but it fails.
Is it really possible to build it this way? (efl git master)
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking
On 3/27/21 5:10 PM, Carsten Haitzler wrote:
For those who are not watching git commits...
Flat theme has landed in git master efl today.
Yay!
Great news! Congratulations for all your work!
--
Maderios
___
enlightenment-devel mailing list
On 10/4/20 1:19 PM, Carsten Haitzler wrote:
On Sun, 4 Oct 2020 12:32:59 +0200 leoutat...@gmx.fr said:
I'll paste my response to the bug here so people know:
yup. don't do that. in x .. there is no way for e to know if the xserver is
active on the tty. that's private to x. e will use xrandr to
I report the bug here
https://phab.enlightenment.org/T8835
On 10/3/20 7:22 PM, leoutat...@gmx.fr wrote:
Hi
I launch two X session in same time, two differents users.
In tty1, enlightenment git, screen blanking with DPMS 1 mn
In tty2, enlightenment16, screen blanking with in .xsession 'xset
Hi
I launch two X session in same time, two differents users.
In tty1, enlightenment git, screen blanking with DPMS 1 mn
In tty2, enlightenment16, screen blanking with in .xsession 'xset +dpms
s 240'
When I am in enlightenment16/tty2 user, screen is blanking after 1 mn,
just like in
On 5/1/20 8:04 PM, Boris Faure wrote:
On 20-05-01 13:04, leoutat...@gmx.fr wrote:
On 5/1/20 12:48 PM, Boris Faure wrote:
On 20-05-01 12:34, leoutat...@gmx.fr wrote:
On 5/1/20 11:23 AM, Boris Faure wrote:
On 20-05-01 11:11, leoutat...@gmx.fr wrote:
Since last efl enlightenment
On 5/1/20 12:48 PM, Boris Faure wrote:
On 20-05-01 12:34, leoutat...@gmx.fr wrote:
On 5/1/20 11:23 AM, Boris Faure wrote:
On 20-05-01 11:11, leoutat...@gmx.fr wrote:
Since last efl enlightenment terminology git versions (1.24),
terminology crashes after 4 seconds.
segmentation fault
On 5/1/20 11:23 AM, Boris Faure wrote:
On 20-05-01 11:11, leoutat...@gmx.fr wrote:
Since last efl enlightenment terminology git versions (1.24),
terminology crashes after 4 seconds.
segmentation fault (core dumped) terminology
Could you please provide us with a backtrace from the core
Since last efl enlightenment terminology git versions (1.24),
terminology crashes after 4 seconds.
segmentation fault (core dumped) terminology
--
Maderios
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
On 4/29/20 2:16 PM, Carsten Haitzler wrote:
On Wed, 29 Apr 2020 10:49:18 +0200 leoutat...@gmx.fr said:
On 4/28/20 6:31 PM, Carsten Haitzler wrote:
On Tue, 28 Apr 2020 14:46:30 +0200 leoutat...@gmx.fr said:
On 4/27/20 1:13 PM, Carsten Haitzler wrote:
On Mon, 27 Apr 2020 11:59:52 +0200
On 4/29/20 12:55 PM, Simon Lees wrote:
On 4/29/20 6:19 PM, leoutat...@gmx.fr wrote:
On 4/28/20 6:31 PM, Carsten Haitzler wrote:
On Tue, 28 Apr 2020 14:46:30 +0200 leoutat...@gmx.fr said:
On 4/27/20 1:13 PM, Carsten Haitzler wrote:
On Mon, 27 Apr 2020 11:59:52 +0200
On 4/28/20 6:31 PM, Carsten Haitzler wrote:
On Tue, 28 Apr 2020 14:46:30 +0200 leoutat...@gmx.fr said:
On 4/27/20 1:13 PM, Carsten Haitzler wrote:
On Mon, 27 Apr 2020 11:59:52 +0200 leoutat...@gmx.fr said:
it looks like your user is not permitted to do anything. fix the
rules.
On 4/27/20 1:13 PM, Carsten Haitzler wrote:
On Mon, 27 Apr 2020 11:59:52 +0200 leoutat...@gmx.fr said:
it looks like your user is not permitted to do anything. fix the
rules. /etc/enlightenment/system.conf
Yes, fixing issue is easy with adding user group in this file.
Problem: system.conf
When i start enlightenment in console
enlightenment_start
I get these messages:
LOAD WL_DRM MODULE
E_SYSTEM_INF: Deny rule: user: * deny: *
E_SYSTEM_INF: Deny rule: user: * deny: *
E_SYSTEM_INF: Deny rule: user: * deny: *
E_SYSTEM_INF: Deny rule: user:
Hi
Since last git efl and enlightenment versions, i get error:
"Enlightenment cannot successfully start the enlightenment_systems
service". It happens just after launching e.
X or wayland sessions
--
Maderios
___
enlightenment-devel mailing list
On 10/4/19 12:51 AM, Carsten Haitzler (The Rasterman) wrote:
On Thu, 3 Oct 2019 22:47:43 +0200 leoutat...@gmx.fr said:
On 10/2/19 3:35 PM, Christopher Michael wrote:
Hi,
I updated efl & e from git this morning and ran some tests for this
crash. I cannot reproduce it using either software OR
On 10/2/19 3:35 PM, Christopher Michael wrote:
Hi,
I updated efl & e from git this morning and ran some tests for this
crash. I cannot reproduce it using either software OR gl rendering :(
Can you provide a backtrace of the crash ??
https://www.enlightenment.org/contrib/efl-debug.md
On 10/3/19 12:13 PM, Carsten Haitzler (The Rasterman) wrote:
On Wed, 2 Oct 2019 16:19:43 +0200 leoutat...@gmx.fr said:
On 10/2/19 3:35 PM, Christopher Michael wrote:
Hi,
I updated efl & e from git this morning and ran some tests for this
crash. I cannot reproduce it using either software OR
This issue doesn't happen in other user X session.
=> it concerns only wayland sessions
--
Maderios
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
On 10/2/19 3:35 PM, Christopher Michael wrote:
Hi,
I updated efl & e from git this morning and ran some tests for this
crash. I cannot reproduce it using either software OR gl rendering :(
Can you provide a backtrace of the crash ??
https://www.enlightenment.org/contrib/efl-debug.md
Hi
I get crash (with wonderful red warning) each time I do:
ibar -> settings -> setup -> order (or add) move up/down
Conditions
Arch/Aur system
wayland session
opengl rendering
efl-git 1.23.99.63866 + enlightenment-git 0.23.99.23723 and all previous
versions
--
Maderios
On 7/11/19 12:29 PM, Carsten Haitzler (The Rasterman) wrote:
FYI I have migrated:
http://www.enlightenment.org
http://docs.enlightenment.org
I see black page here https://docs.enlightenment.org/
over to e5 yesterday. http://download.enlightenment.org already was moved a
while back. phab,
42 matches
Mail list logo
