On Sun, 26 Apr 2020 22:26:11 -0700 Marc MERLIN <marc_...@merlins.org> said:
> On Sun, Apr 26, 2020 at 07:38:06PM -0700, Ross Vandegrift wrote:
> > The enlightenment package Recommends acpid, so by default, this should've
> > worked automatically. In Debian/Ubuntu, Recommends means "it's technically
> > possible to use without, but should be installed in all normal cases."
>
> Fair point Ross. So, you got me here, I have apt::recommend turned off
> due to the amount of random crap some packages pull along, especially
> transitively.
i noticed many people seem to ignore recommended things... so that's why e got
it's own nag dialog at runtime... it's smarter than the packages as it actually
looks to see if your hardware does acpi. e.g. your raspberry pi will not, thus
it won't nag you. if /proc/acpi exists... there's a very good chance your
hardware does .... acpi :)
> network-manager for instance installs modem-manager, with breaks all
> your serial ports, plus ppp (hello, 1999?), plus a bunch of other crap.
> That's just one package.
> I'm glad enlightenment is doing the right thing here, my apologies for
> getting this wrong.
it is. :) there is code explicitly to try and push you to do the right thing.
ignoring it's push will lead to things breaking and not working as
expected... :)
> -------
>
> Hi Raster,
>
> Thanks again for your quick and helpful answers. They are always
> appreciated.
>
> On Sun, Apr 26, 2020 at 07:38:10PM +0100, Carsten Haitzler wrote:
> > > 3) I get a complaint that I have 2 systrays when I'm not running
> > > stalonetray anymore and I never got the E systray working as nothing
> > > goes in it (hence stalonetray).
> >
> > is it e's dialog complaining? you may have 2 shelves with a systray in
> > both? it only allows one to exist.
>
> Apparently I had both a systray gadget and a shelf systray, fixed it.
> I'm not sure if I've fully gotten the gadget thing, especially as they
> might be buggy in my E version (or I'm holding it wrong)
try e from git that will be 0.24 in t he coming few weeks.
> > what is a gadget systray? systray presents a gadget for gadcon (gadget
> > controller) to request/position etc. ... ? gadcons can be in shelves - they
> > can also be placed on the desktop... you could also have a systray on the
> > desktop gadcon... ?
>
> That was the problem, yes. It's a bit surprising that it let me launch
> two when clearly that's not supported.
well gadcon itself doesn't understand the idea of "there can be only one" as
systray is the only gadget to do this. so the gadget itself when it gets
instanced a second time tells you and complains.
> > alt+scroll wheel == switch desktops in default bindings. it sounds like you
> > are not pressing middle mouse but scrolling the wheel instead. if the
> > button is
>
> I don't, but I believe you something is broken on my thinkpad setup in
> that it causes this. That would explain what I'm seeing. I'll spend some
> time to see why.
it smells like it - try xev to see what your events are. i have a bt logitech
mouse where there is a scroll wheel... but you can't press it to middle-button
press. there is another button next to it that is middle button. as this is a
trackpad, all bets are off as things like click/button and wheel events are
emulated by firmware on the trackpad... thus config of it matters.
> > both a wheel and a button it could be you are producing both or maybe it
> > isn't producing a middle button press at all? you can use xev to try and
> > see what happens when you press middle button on its window. also just
> > trying to add a binding for it too and see what input e sees.
>
> middle button works, both for cut & paste and shows up as 'button2' in
> xev. Alt + middle does a 'motion modify event 41'. Will need to
> debug. Not E's fault
and do you get something like:
MotionNotify event, serial 39, synthetic NO, window 0x1c00001,
root 0x6c1, subw 0x0, time 193796609, (576,360), root:(612,402),
state 0x0, is_hint 0, same_screen YES
KeyPress event, serial 39, synthetic NO, window 0x1c00001,
root 0x6c1, subw 0x0, time 193796803, (576,360), root:(612,402),
state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
LeaveNotify event, serial 39, synthetic NO, window 0x1c00001,
root 0x6c1, subw 0x0, time 193800161, (576,360), root:(612,402),
mode NotifyGrab, detail NotifyAncestor, same_screen YES,
focus YES, state 520
FocusOut event, serial 39, synthetic NO, window 0x1c00001,
mode NotifyGrab, detail NotifyNonlinear
if you see leave notifies and focus out's - that means that was an actual
binding being triggered 9you see similar events on alt+left mouse and alt+right
mouse too). whenever you see that leave focus out there ... that means a key or
mouse binding was triggered and E got the event, not the app and E would have
processed it. if you don't see this - e's binding didn't exist or was not
triggered by x (wrong conditions for it to trigger - like alt not pressed while
pressing middle mouse etc.).
> > > 5.5) worse: if I carefully move the mouse to the bottom right corner of
> > > a window, I cannot resize it. I can resize using window, resize with
> > > keyboard in the menu bar though
> >
> > what have you done? do you have weird modifier behavior on this box where
> > some modifier is always pressed?
>
> It works in xfe and cinnamon and the source laptop I copied ~/.e from.
> I checked that if I move the button to the top/bottom of the window, I can
> resize from the top/bottom. From the left/right or corners, it doesn't
> work.
what app is this? is this some gnome/gtk3 app with client-side decoration?
> > > This is really what I miss the most with E, and doesn't work in my older
> > > E either (0.21.11-1), I'm missing all those nice systray-like icons and
> > > status.
> >
> > again as per a previous mail - e from git has this fixed. as 0.24 is around
> > the corner after this elf 1.24 release ... don't expect any fixes for 0.23,
> > so try efl + e from git and report issues BEFORE a release so it's working
> > in the release. :) compiling from git is the exact same method as from a
> > tarball. zero difference.
>
> ok, I missed that.
> So systray in E 23 is broke and won't get fixed, but it'll work in 0.24.
well i hope it will work better for you - it does not do xmbed. so don't expect
those to work. you won't know unless you try. last i knew nm-applet needs to be
patched or specially compiled with specific options to support indicator/status
notifier dbus protocol.
e has full bluez5 support built in - in 0.23. you dont need to run extra
processes to have that work. it even supports fun things like enabling paired
bt devices to auto lock/unlock your system if around or not.
and wtf? chrome now is trying to become a "always running in background
process".... ouch. there goes the neighbourhood (or RAM) :)
> xfe/cinnamon: nm-applet, wicd, bluez, google-chrome-beta show up in the
> status bar E 23: nm-applet, wicd, bluez do not show up in E's systray, but
> they show up in stalonetray. Interestingly google-chrome does go in E's
> systray.
> The part I'm confused about is: you told me years ago that x-embbed is
> dead due to its design and that's why you stopped supporting it. But now
> it's years later, and all 3 of nm-applet + wicd + bluez still only go in
> stalonetray. How can I know if it's because they are still relying on
> x-embbed, or if it's because of the systray E bug that's apparently been
> in 0.21, 0.22, and 0.23, that you just alluded to?
they still do xmbed. kde moved from xmbed years ago. gnome kept supporting it.
it was horribly broken in most apps anyway. in fact even indicator protocol
support is broken in apps. if the status notifer dbus service goes away then
comes back - apps don't re-appear in it without re-running them,. this is an app
problem 100%. they never test loss of service + recovery. so restarting e
loses this service, then it comes back. the same would happen if you killed the
same service/panel applet thing in kde for example then started it again. the
thing is they almost never do this there where e restarts everything often
enough. this would be a "fix your app" issue as e can't do anything about
broken apps not handling this case. but back to xmbed - apps were the same. in
fact i found maybe 70% or so of apps didn't handle this and their icons
vanished. it was a pointless exercise in the end. broken apps all over the
place.
> Thanks,
> Marc
> --
> "A mouse is a device used to point at the xterm you want to type in" - A.S.R.
>
> Home page: http://marc.merlins.org/
>
>
> _______________________________________________
> 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
