You are not logged in.
Pages: 1
When trying to launch from menu, System -> Zutty I get a brief flash of a black window.
Launching from Konsole I see this:
~$ zutty
E [charvdev.cc:277] Error: Compiling fragment shader:
0:1(10): error: GLSL ES 3.10 is not supported. Supported versions are: 1.00 ES, and 3.00 ES
terminate called after throwing an instance of 'std::system_error'
what(): Resource deadlock avoidedSegmentation fault
------------------------------------------------
System info as follows:
Fresh install of Aquarius Plasma
Panel on left edge
Cascading Application Menu
qreport.tar.gz attached
output of inxi -F:
System:
Host: vaio Kernel: 6.1.0-10-amd64 arch: x86_64 bits: 64 Desktop: KDE Plasma
v: 5.27.5 Distro: Q4OS 5.2.1-n1
Machine:
Type: Laptop System: Sony product: VPCZ2190X v: J004NQAB
serial: <superuser required>
Mobo: Sony model: VAIO serial: <superuser required> BIOS: INSYDE
v: R0173H5 date: 05/21/2012
Battery:
ID-1: BAT1 charge: 18.1 Wh (80.1%) condition: 22.6/47.5 Wh (47.6%)
CPU:
Info: dual core model: Intel Core i7-2620M bits: 64 type: MT MCP cache:
L2: 512 KiB
Speed (MHz): avg: 949 min/max: 800/3400 cores: 1: 798 2: 800 3: 1400
4: 798
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
driver: i915 v: kernel
Device-2: Cheng Uei Precision Industry (Foxlink) Webcam type: USB
driver: uvcvideo
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1920x1080~60Hz
API: OpenGL v: 3.3 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 3000 (SNB
GT2)
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel
API: ALSA v: k6.1.0-10-amd64 status: kernel-api
Server-1: PulseAudio v: 16.1 status: active
Network:
Device-1: Intel Centrino Advanced-N 6230 [Rainbow Peak] driver: iwlwifi
IF: wlp2s0 state: up mac: 88:53:2e:57:96:49
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp5s0 state: down mac: 54:42:49:98:d7:2d
Bluetooth:
Device-1: Intel Centrino Advanced-N 6230 Bluetooth adapter type: USB
driver: btusb
Report: hciconfig ID: hci0 state: up address: 88:53:2E:57:96:4D bt-v: 2.0
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
Drives:
Local Storage: total: 238.49 GiB used: 10.41 GiB (4.4%)
ID-1: /dev/sda vendor: Samsung model: MZRPC256HADR-000SO size: 119.24 GiB
ID-2: /dev/sdb vendor: Samsung model: MZRPC256HADR-000SO size: 119.24 GiB
Partition:
ID-1: / size: 38.64 GiB used: 7.56 GiB (19.6%) fs: ext4 dev: /dev/sda3
ID-2: /home size: 116.81 GiB used: 2.85 GiB (2.4%) fs: ext4 dev: /dev/sdb1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 57.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 188 Uptime: 11m Memory: 7.67 GiB used: 1.8 GiB (23.5%)
Shell: Bash inxi: 3.3.26
Last edited by nightflier (2023-07-21 20:29)
Offline
I can't say much because I'm using Q4OS 4 Gemini (Debian 11 Bullseye), not Q4OS 5 Aquarius (Debian 12 Bookworm).
Since Zutty is available neither in Debian 11 repositories nor in Gemini Software Centre, I downloaded source code for Zutty 0.14 (which is available for Debian 12), and compiled on my system. It doesn't crash.
If you haven't done so already, you could try to compile too. It's really easy thanks to the clear instructions given in the Zutty user guide. You can just copy-paste the commands in a terminal. You can even try to run the resulting binary before installing it. Everything is clearly explained.
Q4OS machine: Samsung R519 - Pentium T4200 2.0 GHz - 4 GB RAM - 500 GB SSD
Offline
We are not able to reproduce that in Virtualbox, zutty starts fine. This issue is hardware dependent and looks to be connected to opengl acceleration some way. We will try to reproduce on a real hardware, investigate and post here.
Offline
I can't say much because I'm using Q4OS 4 Gemini (Debian 11 Bullseye), not Q4OS 5 Aquarius (Debian 12 Bookworm).
Since Zutty is available neither in Debian 11 repositories nor in Gemini Software Centre, I downloaded source code for Zutty 0.14 (which is available for Debian 12), and compiled on my system. It doesn't crash.
If you haven't done so already, you could try to compile too. It's really easy thanks to the clear instructions given in the Zutty user guide. You can just copy-paste the commands in a terminal. You can even try to run the resulting binary before installing it. Everything is clearly explained.
I don't need zutty, but I'd be happy to help troubleshoot this issue. In addition to compiling my own, what other steps would be helpful for the developers?
Offline
It would be helpful to report it as a Debian bug, or directly to Zutty developers.
Offline
Looks like you need newer hardware than mine to run zutty:
https://github.com/tomscii/zutty/wiki/FAQ
Case closed :-)
Offline
Pages: 1