Other CDE Users Unite!

[kpedersen]

Yeah, I knew that. I guess I should have been more clear, I was really asking if dbus was really needed for CDE to interact with "modern" technologies. For example, librewolf complains about not being able to talk with dbus when run from the terminal.

Oh right. CDE doesn't need dbus but software like librewolf might need it. If its similar to firefox, it should work without. I think it uses dbus for some filesystem stuff.

Though note that CDE has no idea how to even use dbus (as you know, it didn't exist back then) so there won't be any comms through it. Building CDE doesn't pull in i.e libdbus for example.

 

[cy@]

<sigh> dbus and the like are a reimplementation of an old concept. The mainframe had (MVS) and has (zOS) the subsystem interface. Messages are passed to a function which in turn calls all its subsystems (apps that have registered with it) callbacks to notify it of the event/data. Unfortunately for UNIX/Linux, there was no one standard. It's the Wild West here.

 

[fmc000]

Another question: on my dual monitor setup dtlogin always starts on the laptop panel despite that in my sessionsetc I set up the external monitor as primary. Is it possible to change this behavior?

But the weirder thing is that after resuming from suspend only the laptop keyboard can be used to input the password, every other DE I tried could use the external keyboard just fine.

 

[Maturin]

Is it possible to change this behavior?

Since I don't use a displaymanager myself, and I'm not sure which comes first dm, or X, and what overrides what, so my answer may not solve your issue, but you can use xrandr(1) to define a primary monitor (see section "RandR version 1.3 options")

 

[fmc000]

Since I don't use a displaymanager myself, and I'm not sure which comes first dm, or X, and what overrides what, so my answer may not solve your issue, but you can use xrandr(1) to define a primary monitor (see section "RandR version 1.3 options")

Yeah, I have a xrandr command in my sessionsetc that works just fine but it's executed after dtlogin, therefore it is of no use in this case. I'll see if dtlogin can be customized but it's no big deal in any case.

 

[Maturin]

Yeah, I have a xrandr command in my sessionsetc that works just fine but it's executed after dtlogin, therefore it is of no use in this case. I'll see if dtlogin can be customized but it's no big deal in any case.

Well, it's completely up to you, of course, but maybe it's worth just a try (edit one line in two files each), and maybe leads to a satisfying solution for you:
As I said, I don't use no DM. My ~/.login simply ends with exec startx &
The rest (xrandr) is in ~/.xinitrc, of course:

[...]
default .xinitrc stuff
[...]
#my xrandr line
xrandr --output HDMI-0 --mode 1920x1080 --rotate......

# numlock be used as numlock by default
numlockx &

# start my WM:
fvwm # must be 'cde' here?

# gimme sound!
mixer vol 100:100
mixer speaker 100:100
mixer mix 100:100

This way I don't get a nice "welcome screen" when I start my machine up, but the default TTY login, and when I login (as user), then X and my WM is started.
I can abstain of (the to me) pure optical frills. As I said: If you see it otherwise, okay. It was simply a suggestion. You don't need to deal with DM setups, but "just" with X, and CDE.
Maybe it works, to change your primary monitor, maybe it won't. Maybe you say, 'that's more I like it', maybe you say, 'Nah, I prefer the other way.'

 

[fmc000]

Well, it's completely up to you, of course, but maybe it's worth just a try (edit one line in two files each), and maybe leads to a satisfying solution for you:
As I said, I don't use no DM. My ~/.login simply ends with exec startx &
The rest (xrandr) is in ~/.xinitrc, of course:

[...]
default .xinitrc stuff
[...]
#my xrandr line
xrandr --output HDMI-0 --mode 1920x1080 --rotate......

# numlock be used as numlock by default
numlockx &

# start my WM:
fvwm # must be 'cde' here?

# gimme sound!
mixer vol 100:100
mixer speaker 100:100
mixer mix 100:100

This way I don't get a nice "welcome screen" when I start my machine up, but the default TTY login, and when I login (as user), then X and my WM is started.
I can abstain of (the to me) pure optical frills. As I said: If you see it otherwise, okay. It was simply a suggestion. You don't need to deal with DM setups, but "just" with X, and CDE.
Maybe it works, to change your primary monitor, maybe it won't. Maybe you say, 'that's more I like it', maybe you say, 'Nah, I prefer the other way.'

Take a look at this post:

Other Post in thread 'CDE in 2025'

Mar 19, 2025

 ~ $ echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/home/naths/bin:/usr/local/dt/bin
naths@gnltfbsd:~ $

There was 'Action required message' box on top of beautifully loaded DE with a 'OK' button. Nothing was allowed.

What do you mean "action required message?"

~ $
ps alxww | grep ses
1001 49878 48339 4  20  0    24044 11124 select S     -  0:00.04 sshd-session: naths@pts/0 (sshd-session)
1001  5125  3869 1  20  0    15408  4344 wait   I    v0  0:00.01 /usr/local/bin/ksh93 /usr/local/dt
/bin/Xsession
1001  8721  5125 1  20  0    29992 16048...

• cy@

• 
• 

 

[Maturin]

OK. I never really dealt with any DM. Don't know in which file this thing is started, how it interferes, or if you have to deinstall it first... I'm no top-down, but a bottom-up kind of guy: starting on a white, empty sheet of paper, think of what I need, look for the quickest, and most easiest was to get there, and when it works I'm satsified with what I have.