emwm-discuss Mailing List for EMWM
Enhanced Motif Window Manager and Utilities
Brought to you by:
alx210
Menu
▾
▴
emwm-discuss
You can subscribe to this list here.
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(1) |
Dec
|
|---|
|
From: Per B. <lis...@tu...> - 2025-11-16 17:16:28
|
Hello, Testing Emwm-alpha a little bit I find it hard to quit. Quit in the menu is greyed out and in .emwmrc it points to f.quit, not f.quit_wm. I tried some different things that did not work, setting a backdrop image with feh did not work and I tried two pagers, fbpager (intended primarily for Fluxbox) and ppager (I do not know where I got that one). Is there or will there be a way to start programs occupying all workspaces? Per B. -- http://www.tufftuff.net Railways, trams and suchlike |
|
From: izzy M. <izd...@di...> - 2025-10-31 01:09:39
|
On Thu, 23 Oct 2025 09:52:40 -0500 izzy Meyer <izd...@di...> wrote: > On Thu, 23 Oct 2025 08:17:24 -0500 > Carson Chittom <ca...@ch...> wrote: > > > izzy Meyer <izd...@di...> writes: > > > > > Hello, I am the maintainer of this port (In the future, mail > > > ports@ and CC me please). The port is patched to utilize bsd-auth > > > for the locking mechanism. This is not an upstreamed change. > > > > Apologies, it didn't occur to me that this would be the case. I'm > > replying here since the conversation started here, but will use > > ports@ in future should the need arise. > > > > > I cannot replicate this behavior. Could you check if the setgid > > > bit is set and is group owned to "auth" in the xmsm binary? Maybe > > > the pkg update between releases is buggy and didn't preserve this > > > across 1.2p0 to 1.3p1. > > > > monolith$ ls -l /usr/local/bin/xmsm > > -rwxr-sr-x 1 root auth 55688 Oct 10 06:07 /usr/local/bin/xmsm > > > > That looks right? > > > > I just was able to reproduce it again, this time by manually > > selecting "Lock" from the "Session" menu. Also, I don't see any of > > my unlock attempts in /var/log/authlog -- not sure if this is > > expected, but I do see unlocks from xlock. > > > > > > > > I just had rebooted my machine and was able to replicate this. I'll > have to ask ports@ as I'm still amateurish here. I'll CC you in the > thread. It shouldn't be logging to authlog, I never patched it to do > that and upstream doesn't do that either. > > Thanks, > I dropped maintainership for this port. I'd suggest using a different window manager on OpenBSD for the time being, as this will likely not get updates or fixes. -- iz (she/her) > i like to say mundane things, > there are too many uninteresting things > that go unnoticed. izder456 (dot) neocities (dot) org |
|
From: izzy M. <izd...@di...> - 2025-10-23 14:52:58
|
On Thu, 23 Oct 2025 08:17:24 -0500 Carson Chittom <ca...@ch...> wrote: > izzy Meyer <izd...@di...> writes: > > > Hello, I am the maintainer of this port (In the future, mail ports@ > > and CC me please). The port is patched to utilize bsd-auth for the > > locking mechanism. This is not an upstreamed change. > > Apologies, it didn't occur to me that this would be the case. I'm > replying here since the conversation started here, but will use ports@ > in future should the need arise. > > > I cannot replicate this behavior. Could you check if the setgid bit > > is set and is group owned to "auth" in the xmsm binary? Maybe the > > pkg update between releases is buggy and didn't preserve this > > across 1.2p0 to 1.3p1. > > monolith$ ls -l /usr/local/bin/xmsm > -rwxr-sr-x 1 root auth 55688 Oct 10 06:07 /usr/local/bin/xmsm > > That looks right? > > I just was able to reproduce it again, this time by manually selecting > "Lock" from the "Session" menu. Also, I don't see any of my unlock > attempts in /var/log/authlog -- not sure if this is expected, but I do > see unlocks from xlock. > > > I just had rebooted my machine and was able to replicate this. I'll have to ask ports@ as I'm still amateurish here. I'll CC you in the thread. It shouldn't be logging to authlog, I never patched it to do that and upstream doesn't do that either. Thanks, -- iz (she/her) > i like to say mundane things, > there are too many uninteresting things > that go unnoticed. izder456 (dot) neocities (dot) org |
|
From: Carson C. <ca...@ch...> - 2025-10-23 13:17:41
|
izzy Meyer <izd...@di...> writes: > Hello, I am the maintainer of this port (In the future, mail ports@ and > CC me please). The port is patched to utilize bsd-auth for the locking > mechanism. This is not an upstreamed change. Apologies, it didn't occur to me that this would be the case. I'm replying here since the conversation started here, but will use ports@ in future should the need arise. > I cannot replicate this behavior. Could you check if the setgid bit is > set and is group owned to "auth" in the xmsm binary? Maybe the pkg > update between releases is buggy and didn't preserve this across 1.2p0 > to 1.3p1. monolith$ ls -l /usr/local/bin/xmsm -rwxr-sr-x 1 root auth 55688 Oct 10 06:07 /usr/local/bin/xmsm That looks right? I just was able to reproduce it again, this time by manually selecting "Lock" from the "Session" menu. Also, I don't see any of my unlock attempts in /var/log/authlog -- not sure if this is expected, but I do see unlocks from xlock. -- https://web.chittom.family |
|
From: izzy M. <izd...@di...> - 2025-10-22 23:17:18
|
On Wed, 22 Oct 2025 08:01:52 -0500 Carson Chittom <ca...@ch...> wrote: > This morning I upgraded from OpenBSD 7.7 to 7.8, and in the process > upgraded from emwm/emwm-utils 1.2 to 1.3, using OpenBSD's prebuilt > packages. I wandered away from my desk to get coffee, and by the time > I got back, the display had locked with the built-in locking > mechanism. > > I entered my password, but it was not accepted (I tried several times, > of course). Just to make sure something had not gone seriously wrong > with my user account, I switched to a virtual console to try the same > password, and logged in successfully. > > In the meanwhile, I am simply disabling locking and just using > OpenBSD's xidle(1), but I have no real idea how to even troubleshoot > further. Any suggestions? > > > --- > https://web.chittom.family > > > > _______________________________________________ > EMWM-discuss mailing list > EMW...@li... > https://lists.sourceforge.net/lists/listinfo/emwm-discuss Hello, I am the maintainer of this port (In the future, mail ports@ and CC me please). The port is patched to utilize bsd-auth for the locking mechanism. This is not an upstreamed change. I cannot replicate this behavior. Could you check if the setgid bit is set and is group owned to "auth" in the xmsm binary? Maybe the pkg update between releases is buggy and didn't preserve this across 1.2p0 to 1.3p1. -- iz (she/her) > i like to say mundane things, > there are too many uninteresting things > that go unnoticed. izder456 (dot) neocities (dot) org |
|
From: Carson C. <ca...@ch...> - 2025-10-22 13:17:30
|
This morning I upgraded from OpenBSD 7.7 to 7.8, and in the process upgraded from emwm/emwm-utils 1.2 to 1.3, using OpenBSD's prebuilt packages. I wandered away from my desk to get coffee, and by the time I got back, the display had locked with the built-in locking mechanism. I entered my password, but it was not accepted (I tried several times, of course). Just to make sure something had not gone seriously wrong with my user account, I switched to a virtual console to try the same password, and logged in successfully. In the meanwhile, I am simply disabling locking and just using OpenBSD's xidle(1), but I have no real idea how to even troubleshoot further. Any suggestions? --- https://web.chittom.family |
