Hi, this is my first post.
I just started using openSUSE today. I used Arch Linux before with dwm as my window manager. Previously with Arch Linux, I just need to put my autostarted applications in ~/.xprofile script. But in openSUSE, it’s not working. I use lightdm as display manager. I tried to move the script to ~/.xsession but nothing changed. Any solution?
What you tell about Arch Linux is new to me. IMHO starting applications on GUI login is something to be done by the desktop software. What DE are you running?
First,
If you’re used to running only a window manager, have you considered doing that on openSUSE and not with lightdm?
By default, openSUSE installs with IceWM as a “window manager only” option no matter whether a full Desktop is installed or not but you can install and use any wm you want (I’ve experimented with fluxbox, openbox and a couple other wm only setups).
As for starting up an application automatically, to a certain extent that will require some knowledge about your wm and/or dm, and the specific apps you’re starting up… You may already know that any apps that are configured to start up by way of a sub-directory in /home will launch only when that particular User logs in so wouldn’t be suitable for system apps or apps used by multiple Users on the machine.
Now,
Based on a quick research of dwm…
It looks like the recommended way to autostart applications is to install the dwm autostart patch…
The bare patch is
https://dwm.suckless.org/patches/autostart/
The following is some code a dwm User posted that installs his 4 favorite dwm patches which includes autostart…
https://github.com/lotabout/dwm
Apparently the Statusbar can be configured to autostart an app according to the dwm ArchWiki(Generally, I’ve found that info in the ArchWiki articles are over 99% compatible with how to make things work in openSUSE)
https://wiki.archlinux.org/index.php/Dwm
HTH,
TSU
if you have time, recommend experimenting using virtualization to make things easy…
If you’ve already run IceWM, you’ve already run a machine using only a WM and with no DM… In fact, until very recently it was my personal speculation why only VESA display capabilities were possible using IceWM (no DM possibly meant no access to an advanced graphics driver like nouveau,nvidia, ATI, etc) but that just changed with 15.1… Now, it looks like in IceWM we have all the capabilities expected of an advanced video driver including very high display resolution, high color depth and supporting virtual graphics drivers like VBox, VMware, etc.
TSU
Okay. I’ll try this. I’ll post the result later cause I rather busy right now. Thanks for the suggestions.
What?!?!?
until very recently it was my personal speculation why only VESA display capabilities were possible using IceWM (no DM possibly meant no access to an advanced graphics driver like nouveau,nvidia, ATI, etc) but that just changed with 15.1…
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
Screen 0: minimum 320 x 200, current **4480 x 1440**, maximum 16384 x 16384
DVI-I-1 connected 1920x1200+2560+0 (normal left inverted right x axis y axis) 519mm x 324mm
DP-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
**2560x1440** 59.95*+ 74.92
1920x1200 59.95*+
# inxi -GxxS
System: Host: big31 Kernel: 4.4.180-102-default x86_64 bits: 64 compiler: gcc v: 4.8.5 Desktop: KDE 3.5.10 tk: Qt 3.3.8c
wm: kwin dm: startx Distro: **openSUSE Leap 42.3**
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] vendor: Dell driver: radeon
v: kernel bus ID: 01:00.0 chip ID: 1002:6611
Display: server: X.Org 1.18.3 **driver: modesetting** unloaded: fbdev,vesa alternate: ati,fglrx
resolution: 2560x1440~60Hz, 1920x1200~60Hz
OpenGL: renderer: Gallium 0.4 on AMD OLAND (DRM 2.43.0 / 4.4.180-102-default LLVM 3.8.0) v: 4.1 Mesa 17.0.5
compat-v: 3.0 direct render: Yes
VESA cannot provide 2560x1440, nor 4480x1440. Whether VESA employs KMS I don’t know, but I doubt it.
It worked with 4k too while I had one (too much mousetype trouble for the price paid), as well as worked in older Leap versions.
?
I’m not clear what your post may be about,
Your post is not about running a wm only or about dwm, your output clearly describes you running KDE/Plasma with kwin and which ordinarily requires a DM.
So, you’ll need to verify you’re running IceWM or some other “wm only” to be on-topic in this thread unless I’m missing something…
BTW -
For anyone who wants to review VESA capabilities and limitations, and explore the possibilities of loading KMS graphics,
There is a concurrent thread going on discussing this in depth at
https://forums.opensuse.org/showthread.php/536434-Change-plymouth-resolution
TSU
Sorry, too many threads happening at once, forgot to use IceWM instead of KDE:
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
Screen 0: minimum 320 x 200, current **4480 x 1440**, maximum 16384 x 16384
DVI-I-1 connected 1920x1200+2560+0 (normal left inverted right x axis y axis) 519mm x 324mm
DP-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
**2560x1440** 59.95*+ 74.92
1920x1200 59.95*+
# inxi -GxxS
System: Host: big31 Kernel: 4.4.180-102-default x86_64 bits: 64 compiler: gcc v: 4.8.5 **Desktop: IceWM** 1.3.12
**dm: startx** Distro: **openSUSE Leap 42.3**
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] vendor: Dell
driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:6611
Display: server: X.Org 1.18.3 **driver: modesetting** unloaded: fbdev,vesa alternate: ati,fglrx
resolution: 2560x1440~60Hz, 1920x1200~60Hz
OpenGL: renderer: Gallium 0.4 on AMD OLAND (DRM 2.43.0 / 4.4.180-102-default LLVM 3.8.0)
v: 4.1 Mesa 17.0.5 compat-v: 3.0 direct render: Yes
Your post does describe unloading the VESA driver and loading the ati fglrx driver.
I tend to run most of my throwaway machines in virtual machines, it may be that this capability was either extended to, or configured automatically for VMware and Virtualbox recently (and as I noted, at least in 15.1 is a change which suggested that my earlier assumption that the issue was related to a DM requirement was incorrect).
TSU
[quote="“mrmazda,post:8,topic:137149”]
**Display**: server: X.Org 1.18.3 **driver: modesetting** unloaded: fbdev,vesa alternate: ati,fglrx
[/QUOTE]My interpretation of inxi’s Display line is that alternate drivers means drivers that would be candidates for the existing hardware if they were installed/available. Clearly fglrx is/was not installed and thus never loaded:
# egrep -i "vesa|unload|not exist|matched|modesetting|v /dev/dri/card0" Xorg.0.log | egrep -v 'evdev|font'
57.977] (==) Matched fglrx as autoconfigured driver 0
57.977] (==) Matched ati as autoconfigured driver 1
57.977] (==) Matched fglrx as autoconfigured driver 2
57.977] (==) Matched ati as autoconfigured driver 3
57.977] (==) Matched modesetting as autoconfigured driver 4
57.977] (==) Matched fbdev as autoconfigured driver 5
57.977] (==) Matched vesa as autoconfigured driver 6
57.993] (II) UnloadModule: "fglrx"
57.993] (II) Unloading fglrx
57.993] (EE) Failed to load module "fglrx" (module does not exist, 0)
57.993] (II) UnloadModule: "ati"
57.993] (II) Unloading ati
57.993] (EE) Failed to load module "ati" (module does not exist, 0)
57.993] (II) LoadModule: "modesetting"
57.993] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
57.996] (II) Module modesetting: vendor="X.Org Foundation"
58.001] (II) LoadModule: "vesa"
58.001] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
58.002] (II) Module vesa: vendor="X.Org Foundation"
58.002] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
58.002] (II) VESA: driver for VESA chipsets: vesa
58.002] (II) modeset(0): using drv /dev/dri/card0
58.008] (WW) Falling back to old probe method for vesa
59.471] (II) UnloadModule: "fbdev"
59.471] (II) Unloading fbdev
59.472] (II) UnloadSubModule: "fbdevhw"
59.472] (II) Unloading fbdevhw
59.472] (II) UnloadModule: "vesa"
59.472] (II) Unloading vesa
Not apparent is inxi omitted another would-be driver, amdgpu. On same PC, where in 15.1 amdgpu is in use, the post-42.3 unsupported fglrx driver is omitted:
# inxi -GxxS
System: Host: big31 Kernel: 4.12.14-lp151.28.7-default x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Trinity R14.0.6
tk: Qt 3.5.0 wm: Twin dm: startx Distro: openSUSE Leap 15.1
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] vendor: Dell driver: amdgpu
v: kernel bus ID: 01:00.0 chip ID: 1002:6611
Display: server: X.Org 1.20.3 driver: amdgpu unloaded: fbdev,modesetting,vesa alternate: ati
resolution: 2560x1440~60Hz, 1920x1200~60Hz
OpenGL: renderer: AMD Radeon HD 8500 Series (OLAND DRM 3.27.0 4.12.14-lp151.28.7-default LLVM 7.0.1)
v: 4.5 Mesa 18.3.2 direct render: Yes
# egrep -i "amdgpu|vesa|unload|not exist|matched|modesetting|v /dev/dri/card0" Xorg.0.log | egrep -v 'evdev|font|AMDGPU\(0'
84.453] Kernel command line: root=/dev/sda24 mitigations=auto radeon.si_support=0 amdgpu.si_support=1
84.658] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0
84.658] loading driver: amdgpu
84.663] (==) Matched amdgpu as autoconfigured driver 0
84.663] (==) Matched ati as autoconfigured driver 1
84.663] (==) Matched modesetting as autoconfigured driver 2
84.663] (==) Matched fbdev as autoconfigured driver 3
84.663] (==) Matched vesa as autoconfigured driver 4
84.663] (II) LoadModule: "amdgpu"
84.664] (II) Loading /usr/lib64/xorg/modules/drivers/amdgpu_drv.so
84.689] (II) Module amdgpu: vendor="X.Org Foundation"
84.690] (EE) Failed to load module "ati" (module does not exist, 0)
84.690] (II) LoadModule: "modesetting"
84.690] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
84.698] (II) Module modesetting: vendor="X.Org Foundation"
84.701] (II) LoadModule: "vesa"
84.701] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
84.703] (II) Module vesa: vendor="X.Org Foundation"
84.703] (II) AMDGPU: Driver for AMD Radeon:
All GPUs supported by the amdgpu kernel driver
84.703] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
84.703] (II) VESA: driver for VESA chipsets: vesa
84.710] (WW) Falling back to old probe method for modesetting
86.187] (II) UnloadModule: "modesetting"
86.187] (II) Unloading modesetting
86.187] (II) UnloadModule: "fbdev"
86.187] (II) Unloading fbdev
86.187] (II) UnloadSubModule: "fbdevhw"
86.187] (II) Unloading fbdevhw
86.187] (II) UnloadModule: "vesa"
86.187] (II) Unloading vesa
<me>hopes this diversion isn’t confusing OP</me> On a mailing list such a diversion can be noted with a subject modification.
That’s a correct interpretation. Also, it’s Xorg that didn’t suggest amdgpu as alternate, inxi is just reporting what it’s found.