On Wed, 19 Jan 2022 12:00:56 +0900 Masaru Nomiya <nom...@galaxy.dti.ne.jp> said:

> Hello,
> 
> Sorry for late reply.
> 
> In the Message; 
> 
>   Subject    : Re: [e-users] Regading latest enlightenment & efl
>   Message-ID : <20220112164927.75f90f9a82129fa192a2c...@rasterman.com>
>   Date & Time: Wed, 12 Jan 2022 16:49:27 +0000
> 
> [CH] == Carsten Haitzler <ras...@rasterman.com> has written:
> 
> CH>  On Sat, 08 Jan 2022 17:02:20 +0900 Masaru Nomiya
> CH> <nom...@galaxy.dti.ne.jp> said:
> 
> CH>  1. top shouldn't be ignored... unless it conflicts with other options
> CH>  (remembers, keeping windows in the visible area of the screen
> CH>  etc.). You almost definitely should not be configuring this stuff
> CH>  in emacs anyway as this cannot account for screen resolution and
> CH>  size changes, scaling changes, dynamic hot plug of screens and so
> CH>  on. you should definitely use e's remembers for this. it will
> CH>  remember window parameters like size, position etc. relative to
> CH>  screen, virtual desktop and so on and properly handle changes to
> CH>  these like screen resolution changes and so on.
> 
> Thanks.
> I set it, but only the height doesn't work with the memory function.

you mean remembers don't work with size? it should... perhaps emacs is sending
configure requests for size after it maps the window - this will then be an
application requested resize later after initial size. you can use locks to
LOCK applications from changing their size (e ignores size requests then and
enforces its sizing).

> So, I wrote in .emacs;
> 
>  (if (boundp 'window-system)
>      (setq initial-frame-alist
>            (append (list
>                     ;;'(font . "fontset-16")
>                  '(foreground-color . "green3")
>                     '(background-color . "black")
>                     '(border-color     . "gray")
>                     '(mouse-color      . "white")
>                     '(cursor-color     . "Blue")
>                     '(cursor-type      . box)
>                     '(menu-bar-lines . 1)
>                     '(vertical-scroll-bars . right)
>                     '(height . 51)
>                     )
> 
> 
> CH>  2. i don't know what causes this - is it really black or
> CH>  backlight is just very low/off? there is also it seems at least
> CH>  some kind of bug in the vmware driver where if e also opens input
> CH>  devices the xorg side driver will have lots of double displaying
> CH>  anything to the screen (at the driver end - e renders,
> CH>  screenshotting the results works. xrandr shows everything
> CH>  configured right - just nothing gets shown on screen. perhaps you
> CH>  suffer from this? you can disable the gesture support in e sat
> CH>  compile time in meson options and see if it changes anything?
> 
> I get the just black screen, not a blacklight.
> Now, I encounter this phenomenon at least once every two times.
> 
> I thought there were no logs, but they were recorded;
> 
> 1. normal case.
> 
> [...]
> @ match screens 0x2bb8a70[0] = 0 0 3840x2160 -- 0
> @ matches existing zone 0x257b450
>    move resize 0 0 3840x2160 -> 0 0 3840x2160
> RRR: New unconfigured screen on DVI-D-0
> RRR: New unconfigured screen on HDMI-0
> RRR: New unconfigured screen on DP-0
> RRR: New unconfigured screen on DP-1
> DEV: CHANGES ... have 18 devices, changed=1
> DEV: change [MX Vertical Mouse] [libinput Middle Emulation Enabled] -> 1
> DEV: CHANGES ... have 18 devices, changed=0
> DEV: CHANGES ... have 18 devices, changed=0
> 
> 2. Problematic cases
> 
> [...]
> @ match screens 0x1b76150[0] = 0 0 3840x2160 -- 0
> @ matches existing zone 0x1c24a00
>    move resize 0 0 3840x2160 -> 0 0 3840x2160
> RRR: New unconfigured screen on DVI-D-0
> RRR: New unconfigured screen on HDMI-0
> RRR: New unconfigured screen on DP-0
> RRR: New unconfigured screen on DP-1
> PAUSE !

^^^^ this is the segfault handler... so there is a crash. sometimes things stop
for a while while a gdb backtrace is captured. thee days gdb has become very
very slow and may take many 10's of seconds to catch the backtrace

> DEV: CHANGES ... have 18 devices, changed=1
> DEV: change [MX Vertical Mouse] [libinput Middle Emulation Enabled] -> 1
> DEV: CHANGES ... have 18 devices, changed=0
> DEV: CHANGES ... have 18 devices, changed=0
> DEV: CHANGES ... have 18 devices, changed=0
> X I/O Error - fatal. Exiting  <-- this means Ctrl+Alt+Backsopace keys
>                                  operarion
> 
> That is, after login operation;
> 
> 1. get the log in sound? (<-- I used to think it was an easter egg,
>   but lately I think it's turned into a login sound!)

yes - you logged back in... xorg was killed. new x session :)

> 2. But, the enlightenment logo does not appear and the mouse does not
>   respond.

does it crash again? if so - what is the backtrace? ~/.e-crashdump.txt ... ?
have you tried building efl and e with asan and catching the bug early?

> then, I press Ctrl+Alt+Backspace keys, and do login operation.
> 
> I doubted the bluetooth mouse, so replaced it with another bluetooth
> mouse, or usb mouse, but there were no effect.
> 
> Any idea?
> 
> Thanks.
> 
> ---
> ┏━━┓彡 Masaru Nomiya             mail-to: nomiya @ galaxy.dti.ne.jp
> ┃\/彡
> ┗━━┛ "Three young men died for Rationalization.
>            Yet, Margaret Bloody Thatcher LIVES!"
>                                             'Brassed Off'
> 
> 
> _______________________________________________
> 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

Reply via email to