Things not working after update

I have a dual screen setup where the screens have different maximum resolutions so I choose the lower of the two for both screens.
Since last update, everytime I start the computer it messes up the settings and the lower resolution monitor goes blank. I have to mess around with the settings and even though I acknowledge to save the new setting they are gone again next time I start.

Another thing I just noticed is that Shotcut now exits immediately and I can’t use it at all. It’s completely stopping me from doing my work.
Note I tried removing and reinstalling shotcut but it made no difference.
here is the last line of shotcut startup diagnostics, but sadly I have no idea what is causing it.

`

[Fatal ] <> Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile)

`

Is there any way I can reverse the recent update and preferably just disable them. I was perfectly happy with the way it was all working before and now I’m not.

Hi!
You can make a script with your configuration and add it to statup. This way every time you start your computer it’ll load your config.
Something like this:

#!/bin/bash
xrandr --output HDMI-0 --mode 1920x1080 --primary --output HDMI-1 --mode 1920x1080 --right-of HDMI-0

Just edit the optios the way you see fit and, save the file some like resolution.sh, make it executable with
chmod +x resolution.sh
And add it to the startup

Thanks, I did try that and certainly it is one way round it but searching for answers on my Shotcut I discovered that would be due to out of date graphics drivers.
The manjaro settings manager told me coudn’t update them due to “optional” dependency “cuda” so I boldly did

> sudo pacman -R cuda

then I let it do the automatic driver update and now it seems to be working again and doesn’t need the xrandr script.
I shall come back to confirm if this does solve my problem once I’ve checked a few more things because others may be experiencing similar issue with graphics intensive apps.

So you mean you were in a partial-upgrade state?
Thats otherwise known as broken.
Please make sure to take care of your dependencies and keep yourself up to date.

I don’t think I ever updated the graphics drivers before and not sure if they are part of the update process.

I don’t remember it ever telling me that an update had failed, I could have sworn the last one just said “done” at the time.

I think my real problem was that this didn’t show until I restarted the computer and then tried to run Shotcut.

I see … so your drivers were never configured and/or they were an older series.
(this is all guessing because no system info or similar. In future see this: How to provide good information)

1 Like

Although I made some progress Shotcut is still crashing. I tried to view filters and it did a Segmentation fault core dump…

… so let me try providing good information this time.
Here is inxi -Fazy, but can’t see anything suspicious here.

System:
Kernel: 5.8.18-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64
root=UUID=031cc1f5-d419-4666-b7f8-94a7613bac32 rw quiet
resume=UUID=fdb38678-537a-45ee-9a4e-15e6f9409cbb udev.log_priority=3
Desktop: Xfce 4.14.2 tk: Gtk 3.24.20 info: xfce4-panel wm: xfwm4
dm: LightDM 1.30.0 Distro: Manjaro Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME B450-PLUS v: Rev X.0x
serial: UEFI: American Megatrends v: 2008 date: 12/06/2019
CPU:
Info: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 2
family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701013
L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 115025
Speed: 3594 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz):
1: 3583 2: 2053 3: 2057 4: 4384 5: 2196 6: 2190 7: 2192 8: 2190 9: 2053
10: 3601 11: 2197 12: 2194 13: 2195 14: 2191 15: 3937 16: 2024
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP:
conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: ASUSTeK driver: nvidia
v: 455.38 alternate: nouveau,nvidia_drm bus ID: 09:00.0 chip ID: 10de:1d01
Display: x11 server: X.Org 1.20.9 driver: nvidia display ID: :0.0 screens: 1
Screen-1: 0 s-res: 3600x1080 s-dpi: 96 s-size: 953x286mm (37.5x11.3")
s-diag: 995mm (39.2")
Monitor-1: DVI-D-0 res: 1920x1080 hz: 60 dpi: 94
size: 521x293mm (20.5x11.5") diag: 598mm (23.5")
Monitor-2: HDMI-0 res: 1680x1050 hz: 60 dpi: 91 size: 470x300mm (18.5x11.8")
diag: 558mm (22")
OpenGL: renderer: GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 455.38
direct render: Yes
Audio:
Device-1: NVIDIA GP108 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 09:00.1 chip ID: 10de:0fb8
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 0b:00.4 chip ID: 1022:1487
Sound Server: ALSA v: k5.8.18-1-MANJARO
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0
chip ID: 10ec:8168
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac:
Drives:
Local Storage: total: 931.52 GiB used: 162.33 GiB (17.4%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB
size: 465.76 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 serial: rev: 2B2QEXM7 scheme: GPT
ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB
block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial:
rev: 3B6Q scheme: MBR
Partition:
ID-1: / raw size: 456.66 GiB size: 448.50 GiB (98.21%)
used: 21.56 GiB (4.8%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: /home raw size: 465.76 GiB size: 457.45 GiB (98.22%)
used: 140.77 GiB (30.8%) fs: ext4 dev: /dev/sda1
Swap:
Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 8.80 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p3
Sensors:
System Temperatures: cpu: 66.4 C mobo: N/A gpu: nvidia temp: 47 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 325 Uptime: 15m Memory: 62.81 GiB used: 1.41 GiB (2.2%)
Init: systemd v: 246 Compilers: gcc: 10.2.0 clang: 10.0.1 Packages:
pacman: 1122 lib: 335 Shell: Bash v: 5.0.18 running in: xfce4-terminal
inxi: 3.1.08

so I looked in /var/log to see what was produced today.

pacman.log confirms I removed and then reinstalled shotcut (which completed without giving any errors).

There is a file there called “lightdm” also Xorg.0.log and Xorg.1.log
Something has got corrupted but I have no idea what I’m looking for. :face_with_raised_eyebrow:

for a few days Shotcut was working fine, then I did another update and immediately back to the same problem:

<> Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile)
Aborted (core dumped)

I just want to get on with my work and don’t fancy learning all about how to post nicely formatted messages. I have enough problems with esoteric technology way beyond me. So the choices I now see, are:

  1. disconnect my “home” drive (that has all my work) then wipe the file system and start from scratch again hoping I will manage to remount my data drive once that’s working

  2. fork out hundreds of dollars for Windows license on my new computer

  3. switch to a different distro of Linux. I heard “mint” is popular but when I did try that some years ago their distro center got hacked and I end up in a very precarious situation… so Ubuntu then?? IDK. :unamused:

Why can’t what worked yesterday just be the same again today? I was happy with Windows XP and there is nothing in Windows 10 that would make me prefer it other than teh software I want is no longer XP compatible.