╭─gem@gem in ~
╰─λ sudo pacman -S hwinfo --needed
[sudo] password for gem:
warning: hwinfo-23.2-1 is up to date -- skipping
there is nothing to do
╭─gem@gem in ~ as 🧙 took 2s
╰─λ
╭─gem@gem in ~
╰─λ sudo hwinfo | grep -C3 "Resolution"
[sudo] password for gem:
╭─gem@gem in ~ as 🧙 took 12s
[[]|[🔴]] => 🔴ERROR ×
the native resolution of the monitor needs to be supported by the hardware by default in order to specify a resolution that will work in the grub configuration file.
the GRUB_GFXPAYLOAD_LINUX=keep parameter then sends that info to the kernel so any OS based resolution detection algorithms do not have to run since the system already has that info.
SGS is correct however in that it is wise to determine the precise info for GRUB_GFXMODE rather than just taking a resolution you want to use.
i should have considered this, my apologies.
You have a desktop PC , output from nothing is normal for lenovo laptops.
So check in grub, press c and type videoinfo, enter
(use e and you can test both before you edit the grub file)
a lot of what you said goes right over my head sadly, but what i think you mean?
is something like “i might have funky monitors with funky specs or funky support”
if that is the case, here is what i know:
my monitors are both 1920x1080p.
they have worked just dandy for the last 5 years, on arch distros.
they have worked just dandy for the last 2 years on garuda specifically.
this error with global scale only just started happening since the last 2 weekly update cycles.
i was told by someone who recommended garuda to me, that i should update it weekly.
i would otherwise normally update when ever the update pop up told me to.
when i update, i always use the garuda assistant tool to do updates. i never use octopi or pamac or discover for any updates.
i use pamac for finding/installing new software, like flameshot.
im sorry, i have no clue what you want me to do? 
would you like to hop on voice and guide me through screenshare?
i also have anydesk.
Start reading the wiki link, to restore the snapshot, its normal in the beginning to have stress if you got so many infos.
No sorry. I do not have this apps.
If you see grub look on the bottom and read, you will see e c “manual” maybe you can open smartphone with all the tips you need and what to type.
alright. i read through the link you posted earlier and did a rollback? in grub? to a previous snapshot? and my desktop scale is back to normal and the global scale slider in settings is working again 
what should i do going forward regarding updates?
if i update the system again, right now, i’ll likely run into the same problem again right?
while in GRUB and before selecting an OS to boot you press the ‘C’ key and type ‘videoinfo’ and then press ‘enter’.
this will create a list of natively supported hardware resolutions to specify in the GRUB configuration file i mentioned earlier.
IMO considering the make of your motherboard and the date of the BIOS and the GPU type, i find it exceedingly unlikely that the ‘1920x1080x32’ i specified won’t work as a resolution parameter to shunt over to the OS.
when your machine boots up the OS itself it has to detect the screen resolution to display, since you’ve tested a guest account and the scaling issue persists, then it is not a local setting in your home folder.
this is why i suggest bypassing the detection via specifying a display resolution in the GRUB bootloader to see if the problem is rectified.
if you’re just going to go with a ‘rollback’ make sure to restore the snapshot you want in Snapper and reboot the system.
The method and frequency of your update routine is fine, I would not change anything. It is okay to skip a week or few now and then, which may be useful in this case.
I would expect so, if the issue is coming from an updated package which has a bug or has introduced a regression.
It could be helpful to submit a bug report if you were able to track down the package which is causing the issue, but otherwise I would just wait another week and then try updating again. You can always roll back again if it is still broken.
This is right, you should have gotten a pop-up message encouraging you to do this. You may run into issues if you try just running while booted off a snapshot instead of properly restoring it. Post another garuda-inxi if you are not sure; the parameters line gives it away if you are booted into a snapshot.
╭─gem@gem in ~
╰─λ garuda-inxi
System:
Kernel: 6.5.9-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=362a2186-9834-456e-94cc-0e5df56caa01 rw rootflags=subvol=@
quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: ROG CROSSHAIR VIII IMPACT v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 3302
date: 03/05/2021
CPU:
Info: model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 4033 high: 4381 min/max: 2200/4409 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3519 2: 4346
3: 3768 4: 3599 5: 4254 6: 4366 7: 3518 8: 4350 9: 4381 10: 4350 11: 4351
12: 3599 bogomips: 91201
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GM204 [GeForce GTX 980] vendor: ZOTAC driver: nvidia
v: 535.113.01 alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-09) arch: Maxwell code: GMxxx
process: TSMC 28nm built: 2014-19 pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 09:00.0 chip-ID: 10de:13c0 class-ID: 0300
Device-2: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-1.1:4
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 3000x1920 s-dpi: 93 s-size: 819x519mm (32.24x20.43")
s-diag: 970mm (38.17")
Monitor-1: DP-2 pos: top-right res: 1080x1920 hz: 60 dpi: 94
size: 293x521mm (11.54x20.51") diag: 598mm (23.53") modes: N/A
Monitor-2: DP-4 pos: primary,bottom-l res: 1920x1080 hz: 60 dpi: 94
size: 521x293mm (20.51x11.54") diag: 598mm (23.53") modes: N/A
API: EGL Message: No EGL data available.
API: OpenGL v: 4.6.0 vendor: nvidia v: 535.113.01 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce GTX 980/PCIe/SSE2
memory: 3.91 GiB
API: Vulkan v: 1.3.269 layers: 5 device: 0 type: discrete-gpu
name: NVIDIA GeForce GTX 980 driver: nvidia v: 535.113.01
device-ID: 10de:13c0 surfaces: xcb,xlib
Audio:
Device-1: NVIDIA GM204 High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 09:00.1 chip-ID: 10de:0fbb class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-1.1:4
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
API: ALSA v: k6.5.9-zen2-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 0.3.83 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp4s0 state: down mac: <filter>
Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-5:4 chip-ID: 8087:0029
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 7c0104
Device-2: ASUSTek ASUS USB-BT500 driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-6:2 chip-ID: 0b05:190e
class-ID: e001 serial: <filter>
Report: ID: hci1 rfk-id: 1 state: up address: <filter> bt-v: 5.1 lmp-v: 10
status: discoverable: no pairing: no class-ID: 7c0104
Drives:
Local Storage: total: 1.38 TiB used: 1.03 TiB (75.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WDS512G1X0C-00ENX0 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: B35500WD temp: 42.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
Partition:
ID-1: / raw-size: 58.59 GiB size: 58.59 GiB (100.00%)
used: 49.01 GiB (83.6%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-2: /boot/efi raw-size: 385 MiB size: 384.2 MiB (99.80%)
used: 576 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p3 maj-min: 259:3
ID-3: /home raw-size: 417.97 GiB size: 417.97 GiB (100.00%)
used: 134.89 GiB (32.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 58.59 GiB size: 58.59 GiB (100.00%)
used: 49.01 GiB (83.6%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-5: /var/tmp raw-size: 58.59 GiB size: 58.59 GiB (100.00%)
used: 49.01 GiB (83.6%) fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.71 GiB used: 6.5 MiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 35.0 C mobo: 30.0 C gpu: nvidia temp: 33 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 35%
Info:
Processes: 361 Uptime: 9h 19m wakeups: 0 Memory: total: 64 GiB note: est.
available: 62.71 GiB used: 6.86 GiB (10.9%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 1831 libs: 505 tools: octopi,pamac,paru
pm: flatpak pkgs: 0 Shell: fish v: 3.6.1 default: Bash v: 5.2.15
running-in: yakuake inxi: 3.3.30
Garuda (2.6.17-1):
System install date: 2023-07-09
Last full system update: 2023-11-01
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut nvidia-dkms
Windows dual boot: No/Undetected
Failed units:
╭─gem@gem in ~ took 2s
╰─λ
did i do it right?
Looks good to me! 
now the question is, how do i go about updating individual packages such that i can still use discord?
discord needed to update in that last round of updates XD
should i open a new thread post for just that question?
Ah, sounds like you have a Catch 22 on your hands! 
The truth of the matter is, you really shouldn’t ever update one or a few packages without updating the rest; a partially upgraded system can quickly become very broken in ways that are not always easy to troubleshoot or fix. System maintenance - ArchWiki
Since you are holding off on the system upgrade for now, something you could try in the meanwhile would be installing Discord as an AppImage. AppImages are a form of “containerized” application, that have all the needed libraries and dependencies bundled inside of it (so it can be up to date even if your system is not).
I’m not sure if that will fix whatever issue you are having with Discord or not, but it is at least worth a try.
yep.
gotcha. I’ll try the appimage.
as for the “whatever issue you are having with discord” it’s pretty simple, it looks like this:
Oh wow, it won’t let you get around that or do it another time or something? I don’t use Discord but that seems kind of annoying. 
I get that a lot too. It’s VERY annoying. It won’t let you use it if there is a new version that is out that you don’t have. Even if you update your system on a daily basis, Discord loves to throw that message up at you. And when I try to update to fix it, a lot of the times I have to wait for the packages to become available for the official app.
I usually have to use it on my phone or on a browser until its ready.
I really hope alternatives like Revolt become more main stream eventually…
i installed armcord just now. seems legit so far, already on voice/cam calls. i’ll use that for now till official update happens
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
