[SOLVED] KIT Scenarist GUI Only Opens With Sudo in Terminal

Questions about applications and software
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Charlie_M
Level 1
Level 1
Posts: 3
Joined: Fri Oct 15, 2021 7:48 pm

[SOLVED] KIT Scenarist GUI Only Opens With Sudo in Terminal

Post by Charlie_M »

Hi everyone!

The problem: KIT Scenarist (screenplay-writing application) GUI will only open if I launch it through the terminal as:

Code: Select all

sudo scenarist
It was functioning normally until I was viewing a screenplay through print preview, then hit escape, causing the application to crash. Since then, the GUI hasn't opened without running it with sudo through the terminal. I'd like to return the application to its original functioning (launching without sudo and through the menu)

As I understand it, opening an application with sudo is a security risk. As such, I've tried, and failed, to restore the application to its previous functioning. I've tried logging out and in; restarting my computer; reinstalling KIT Scenarist; reinstalling qt5ct; reinstalling OpenType fonts; and reverting to a previous Timeshift snapshot. Hours of searching Google and tinkering have yielded very little. I apologize if I've missed something obvious.

Launching KIT Scenarist through the Linux Mint menu results in the application launching (it shows up in the System Monitor), but no GUI. Running "scenarist" in the terminal results in no GUI but (including extra spaces):

Code: Select all

   OpenType support missing for "Ubuntu", script 17
Previously, it also resulted in complaints regarding the qt5ct palette being disabled. I'm not sure which of the reinstallations (if any) caused that error/warning message to stop showing up.
Running "sudo scenarist" results in:

Code: Select all

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
as well as lauching KIT Scenarist's GUI. It's usable, but has root access.
Once launched with "sudo scenarist", closing the application results in:

Code: Select all

QPainter::begin: Paint device returned engine == 0, type: 2
QWidget::render: Cannot render with an inactive painter
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
QBasicTimer::start: QBasicTimer can only be used with threads started with QThread
I'm not sure how to proceed and humbly request assistance. I've been using Linux Mint for a few years now, but I'm still quite the noob (especially with the terminal). Here's my system information:

Code: Select all

System:
  Kernel: 5.4.0-88-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.0.6 wm: muffin 5.0.2 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Laptop System: Dell product: Inspiron 3505 v: 1.4.5 
  serial: <filter> Chassis: type: 10 v: 1.4.5 serial: <filter> 
  Mobo: Dell model: 05HPX6 v: X01 serial: <filter> UEFI: Dell 
  v: 1.4.5 date: 03/04/2021 
Battery:
  ID-1: BAT1 charge: 42.0 Wh condition: 42.0/42.0 Wh (100%) 
  volts: 13.1/11.4 
  model: Simplo 0x32,0x39,0x37,0x55,0x0B,0x0A,0x0032 type: Li-ion 
  serial: <filter> status: Full 
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510 
  serial: <filter> charge: 55% (should be ignored) 
  rechargeable: yes status: Discharging 
CPU:
  Topology: Quad Core 
  model: AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx bits: 64 
  type: MT MCP arch: Zen+ rev: 1 L2 cache: 2048 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a 
  ssse3 svm 
  bogomips: 33534 
  Speed: 1264 MHz min/max: 1400/2100 MHz boost: enabled 
  Core speeds (MHz): 1: 1135 2: 1138 3: 1154 4: 1594 5: 1280 
  6: 1407 7: 1168 8: 1154 
Graphics:
  Device-1: AMD Picasso vendor: Dell driver: amdgpu v: kernel 
  bus ID: 04:00.0 chip ID: 1002:15d8 
  Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati 
  unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: AMD Radeon Vega 8 Graphics (RAVEN DRM 3.35.0 
  5.4.0-88-generic LLVM 12.0.0) 
  v: 4.6 Mesa 21.0.3 direct render: Yes 
Audio:
  Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Dell 
  driver: snd_hda_intel v: kernel bus ID: 04:00.1 
  chip ID: 1002:15de 
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor 
  vendor: Dell driver: N/A bus ID: 04:00.5 chip ID: 1022:15e2 
  Device-3: AMD Family 17h HD Audio vendor: Dell 
  driver: snd_hda_intel v: kernel bus ID: 04:00.6 
  chip ID: 1022:15e3 
  Sound Server: ALSA v: k5.4.0-88-generic 
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet 
  vendor: Dell driver: r8169 v: kernel port: 2000 bus ID: 02:00.0 
  chip ID: 10ec:8136 
  IF: enp2s0 state: down mac: <filter> 
  Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
  Adapter 
  vendor: Dell driver: ath10k_pci v: kernel port: 2000 
  bus ID: 03:00.0 chip ID: 168c:0042 
  IF: wlp3s0 state: up mac: <filter> 
  Device-3: Qualcomm Atheros type: USB driver: btusb 
  bus ID: 3-2.4:4 chip ID: 0cf3:e009 
Drives:
  Local Storage: total: 476.94 GiB used: 43.92 GiB (9.2%) 
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: BC511 NVMe 512GB 
  size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> 
  rev: 11004101 scheme: GPT 
Partition:
  ID-1: / size: 467.96 GiB used: 43.92 GiB (9.4%) fs: ext4 
  dev: /dev/nvme0n1p2 
Sensors:
  System Temperatures: cpu: 76.6 C mobo: N/A gpu: amdgpu 
  temp: 76 C 
  Fan Speeds (RPM): fan-1: 0 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/home:AndnoVember:KITScenarist.list 
  1: deb http://download.opensuse.org/repositories/home:/AndnoVember:/KITScenarist/xUbuntu_20.04/ /
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com uma main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
  Processes: 298 Uptime: 1h 09m Memory: 5.76 GiB 
  used: 4.48 GiB (77.8%) Init: systemd v: 245 runlevel: 5 
  Compilers: gcc: 9.3.0 alt: 9 Shell: bash v: 5.0.17 
  running in: gnome-terminal inxi: 3.0.38 
P.S. Long time lurker, first time poster :)
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
User avatar
BenTrabetere
Level 7
Level 7
Posts: 1890
Joined: Sat Jul 19, 2014 12:04 am
Location: Hattiesburg, MS USA

Re: KIT Scenarist GUI Only Opens With Sudo in Terminal

Post by BenTrabetere »

I was able to get the 0.7.2 rc13 x86_64 AppImage (the x86_64 one) to launch without a problem. The Scenarist website for the AppImage download point to https://download.opensuse.org/repositor ... /AppImage/. Download the file, make it executable, and run.
Patreon sponsor since August 2022
Image
Charlie_M
Level 1
Level 1
Posts: 3
Joined: Fri Oct 15, 2021 7:48 pm

Re: KIT Scenarist GUI Only Opens With Sudo in Terminal

Post by Charlie_M »

Same result, unfortunately. I downloaded the AppImage, set it as an executable, and ran it. Shows up in System Monitor, no GUI. Thanks for the reply, though.
mikeflan
Level 17
Level 17
Posts: 7152
Joined: Sun Apr 26, 2020 9:28 am
Location: Houston, TX

Re: KIT Scenarist GUI Only Opens With Sudo in Terminal

Post by mikeflan »

Try this. Shutdown KIT Scenarist. Delete the /home/YOU/.scenarist directory if there is one (or rename it). Restart KIT Scenarist normally.
Charlie_M
Level 1
Level 1
Posts: 3
Joined: Fri Oct 15, 2021 7:48 pm

Re: KIT Scenarist GUI Only Opens With Sudo in Terminal

Post by Charlie_M »

That worked, thank you!

There wasn't a .scenarist folder anywhere in /home, but I searched /home for "scenarist" and deleted everything found. Opened the application from the menu like regular, was prompted to set first-use settings. GUI restored, no sudo :D
Locked

Return to “Software & Applications”