yast --qt still opens in ncurses, so does yast --gtk

I find it odd that if I open a “konsole cli” and type “yast --qt” I get a ncurses interface. I get the same thing if I do “yast --gtk”.
So what’s up with that? Doesn’t opensuse understand command line interface commands?

My Specs:

System: Host: Larry Kernel: 4.4.46-11-default x86_64 (64 bit gcc: 4.8.5)
Desktop: KDE Plasma 5.8.3 (Qt 5.6.1) dm: sddm,sddm Distro: openSUSE Leap 42.2
Machine: Device: desktop Mobo: ASUSTeK model: M4N98TD EVO v: Rev 2.00 BIOS: American Megatrends v: 1301 date: 04/14/2011
CPU: Quad core AMD Phenom II X4 B50 (-MCP-) cache: 2048 KB
flags: (lm nx sse sse2 sse3 sse4a svm) bmips: 24801
clock speeds: min/max: 800/3100 MHz 1: 800 MHz 2: 3100 MHz 3: 800 MHz 4: 800 MHz
Graphics: Card: NVIDIA GT200 [GeForce GTX 260] bus-ID: 04:00.0 chip-ID: 10de:05e2
Display Server: X.org 1.18.3 drivers: nvidia (unloaded: modesetting,fbdev,nv,vesa,nouveau)
Resolution: 134x44
Audio: Card NVIDIA MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio
driver: snd_hda_intel bus-ID: 00:07.0 chip-ID: 10de:0774
Sound: Advanced Linux Sound Architecture v: k4.4.46-11-default
Network: Card: NVIDIA MCP77 Ethernet driver: forcedeth port: b480 bus-ID: 00:0a.0 chip-ID: 10de:0760
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: f4:6d:04:3b:8b:41
Drives: HDD Total Size: 6801.4GB (13.7% used)
ID-1: /dev/sda model: WDC_WD3000JB size: 300.1GB serial: WD-WMAMR1467144
ID-2: /dev/sdc model: WDC_WD40EZRX size: 4000.8GB serial: WD-WCC4E443RJKK
ID-3: /dev/sdb model: ST3500418AS size: 500.1GB serial: 9VM8WP1M
ID-4: /dev/sdd model: WDC_WD2003FZEX size: 2000.4GB serial: WD-WMC5C0EAD0MW
Partition: ID-1: / size: 917G used: 6.9G (1%) fs: ext4 dev: /dev/sdd2
ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
Sensors: System Temperatures: cpu: 33.0C mobo: 34.0C gpu: 0.0:55C
Fan Speeds (in rpm): cpu: 4272 sys-1: 0 sys-2: 0
Info: Processes: 200 Uptime: 15:08 Memory: 2193.5/7982.5MB
Init: systemd v: 228 runlevel: 5 default: graphical.target Gcc sys: 4.8.5
Client: Shell (bash 4.3.421 running in konsole) inxi: 2.3.8


zypper lr -d
zypper se -si yast

Please use Code-Tags for the Output.

It is not at all clear what you did.

I just checked, and “yast --qt” opens up a graphic yast. That was from an root “xterm” session.

If you opened a konsole, presumably that was not a root console.

Did you switch to a root konsole session? Or did you directly open a root konsole?

If you did “sudo yast --qt” from within “konsole”, then the problem is that “sudo” does not pass information about the graphic environment, so the curses version of yast is the only one that can run.

If you instead do “su -” within that CLI session, to get a root shell, then you should be able to do “yast --qt” from there.

I’ll be darned. A linux user since 1995, over twenty years, and I didn’t know that.
Ya’ learn something new every day, don’t ya’?
Thanks for the update. :shame: