Arch Linux BBS - Applications & Desktop Environments

Hi. I'm trying to set up tigervnc so I can remotely access the physical screen not matter who is (or isn't) logged in. .. I have tried getting vnc installed on this machine many times but just can't quite get it right. Tried following the guide here TigerVNC. Step 3: Expose the local display directly. I created the file: /etc/X11/xorg.conf.d/10-vnc.conf and also moved passwd file to /home/.vnc/ as directed. Xorg logs show that it attempts to launch the vnc but I've not been able to confirm whether it is actually running.  I expected more in the logs than I get:[ 2755.569] (II) LoadModule: "vnc" [ 2755.569] (II) Loading /usr/lib/xorg/modules/extensions/libvnc.so [ 2755.617] (II) Module vnc: vendor="TigerVNC project" [ 2755.986] (II) Initializing extension VNCWhen I attempt to launch manually I get this.0vncserver -display :0 -rfbauth /home/user/.vnc/passwd -rfbport 5900 Authorization required, but no authorization protocol specified x0vncserver: Unable to open display ":0"My Xauth file has entries for other displays but not for :0.  Nor can I create an entry for :0 via xauth generate.  So I'm stuck. I don't know exactly when this entry should be getting generated on its own but it obviously is not happening.  ... I've been stuck on this service for a long time but am determined now to figure it out.  Any wisdom? Thank you!

It's fixed in chromium upstream and cherry-picked in Arch chromium package, so yes, should be fine now

I tried different xrandr combination with only the second monitor active but each time it freezesThat's the forementioned 1fps issue, did you try to disable DRI3?What's your ultimate goal here, ie. the desired output configuration/usecase scenario?

After a recent Arch update, I noticed that one of my Budgie panel applets was missing. Upon investigation, I found that applets created with Python are not working. It turns out that the python3loader module is missing in libpeas 1.36.0-7, which budgie-panel relies on.The module is available in libpeas-2, but budgie-panel does not use it.(budgie-panel:52670): libpeas-WARNING **: 22:39:57.229: Failed to load module 'python3loader': /usr/lib/libpeas-1.0/loaders/libpython3loader.so: не вдалося відкрити файл об’єктів спільного використання: Немає такого файла або каталогу(budgie-panel:52670): libpeas-WARNING **: 22:39:57.229: Could not load plugin loader 'python3'** (budgie-panel:52670): CRITICAL **: 22:39:57.229: plugin_manager.vala:69: Failed to find extension for: RotationLock

obconf-qt is also fine, personally I open configs in vim....\o/Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.Thanks.one thing to note [if off topic] arch wiki will need to be updated.Done, thanks for the heads up.

Mutter 48.1 was tagged for release, contains the fix(es) for this, and the package is now in [extra].Downgrading packages is always a workaround at best, and never a solution.This was marked [SOLVED] prematurely. It would be good to confirm the issue is indeed resolved.

Mutter 48.1 was tagged for release, contains the fix(es) for this, and the package is now in [extra].OP never replied, and only 1 post, but....@lcsavb: if you're still around please test and mark this thread [SOLVED] if you cannot reproduce the issue.

I guess you should delete /usr/share/fonts/mathjax2/HTML-CSS/Gyre-Pagella/woff/GyrePagellaMathJax_Symbols-Regular.woff file from your system. "Cannot proceed without the font" actually means "Unknown font file format" if you read the xdvipdfmx code O_oI've reported this bug https://tug.org/pipermail/tex-live/2025 … 51433.html Hope it will be fixed sooner or later

They're pretty active and responsive on g-c-c GitLab, so your report will likely get some action. Feel free to link it here. Good luck!

Hello, I've recently been experiencing issues with KDE plasma.Plasmashell (taskbar, desktop, etc.) has been crashing intermittently for me, resulting in my taskbar disappearing and then reappearing after a moment once plasmashell restarts. It seems to be random, where it may run file for a while without issues and then randomly crash a few times in a short time frame. The crashes don't affect any running apps at all, and even screen shares aren't interrupted. The only thing that's interrupting me is the crashing itself and the crash handler popping up afterwards.I've noticed that this issue is only appearing on my gaming rig and not my workstation or my laptop and I suspect it may be due to nvidia drivers as my gaming rig has a 4060 Ti while my workstation and laptop are on intel integrated graphics.Plasmashell crash dump with debugging info: https://0x0.st/824b.txtSystem info:KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 Kernel Version: 6.13.8-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 15.5 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4060 Ti Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B550M DS3H Graphics driver: nvidia-open-dkmsAny help appreciated. Thanks!

Check ~/.local/share/xorg/Xorg.*.log - attempting to start an X11 session should™ log there.WRT the OT: did removing the GDK_BACKEND environment change anything about the behavior?Resp. you can try to "GDK_BACKEND=x11 audacity" from konsole and see whether that then triggers the bell (so whether the environment is relevant to your problem at all)

Hey everyone, I've just upgraded from my Intel Arc A380 to the new B580. Everything works fine, and it's using the new "Xe" driver. Looking at lspci, it seems the new B-Series doesn't even support the legacy i915 drivers.Anyway, in KDE Wayland session, I always get half the framerate. So when choosing 60Hz, it runs at 30Hz, and at 75Hz, it's 38Hz. I've been googling for hours now and couldn't find any solutions.It works just fine on X11.Intel Arc B580:03:00.0 VGA compatible controller: Intel Corporation Battlemage G21 [Arc B580] (prog-if 00 [VGA controller])        Subsystem: Intel Corporation Device 1100        Flags: bus master, fast devsel, latency 0, IRQ 161        Memory at 82000000 (64-bit, non-prefetchable) [size=16M]        Memory at 4000000000 (64-bit, prefetchable) [size=16G]        Expansion ROM at 83000000 [disabled] [size=2M]        Capabilities: [40] Vendor Specific Information: Len=0c <?>        Capabilities: [70] Express Endpoint, IntMsgNum 0        Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit+        Capabilities: [d0] Power Management version 3        Capabilities: [100] Alternative Routing-ID Interpretation (ARI)        Capabilities: [110] Null        Capabilities: [200] Address Translation Service (ATS)        Capabilities: [420] Physical Resizable BAR        Capabilities: [400] Latency Tolerance Reporting        Kernel driver in use: xe        Kernel modules: xeResolution options:Screen 0: minimum 16 x 16, current 2560 x 1440, maximum 32767 x 32767DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm   2560x1440     74.89*+   1920x1440     74.89     1600x1200     74.88     1440x1080     74.92     1400x1050     74.87     1280x1024     74.90     1280x960      74.86     1152x864      74.82     1024x768      74.67     800x600       74.91     640x480       74.77     320x240       73.82     1920x1200     74.93     1680x1050     74.89     1440x900      74.85     1280x800      74.76     1152x720      74.72     960x600       74.84     928x580       74.58     800x500       74.87     768x480       74.71     720x480       74.51     640x400       74.23     320x200       72.67     2048x1152     74.89     1920x1080     74.91     1600x900      74.89     1368x768      74.73     1280x720      74.78     1024x576      74.80     864x486       74.45     720x400       74.23     640x350       74.53

Sorry about the (very) late response, but I've encountered the same issue myself today, and I was able to solve it by linking org.kde.konsole.desktop to kitty.desktop in /usr/share/applications (Change kitty for whatever .desktop do you use). I've tried also to do it on ~/.local/share/applications in order to avoid sudo, but it didn't work. So:sudo ln -s /usr/share/applications/kitty.desktop /usr/share/applications/org.kde.konsole.desktop

The sway configuration is located in ~/.config/sway/configCopying this file from the manjaro installation to your arch installation should be everything needed to configure Sway. However there may be more items you may think are part of sway because they are included in the manjaro sway installaton. Like icons, fonts, applications. So if you are missing anything you would need to provide what you are missing and maybe more help can be given to complete the migration.

irql-notlessoreq wrote:Hi, I uploaded today an AUR package of my Intel legacy VA-API driver fork [1] and was wondering if anyone on older Intel hardware would be willing to try it out.It's main feature is that the issue with Chromium is fixed so you no longer see the following error:VaapiVideoDecoder: failed Initialize()ing the frame pool[1] https://aur.archlinux.org/packages/libv … river-irqlI've tested it on my laptop that has an Ivy Bridge CPU, and it actually shows that it's using Video Acceleration in intel_gpu_top now. Finally, video playback is not laggy af in Chromium on this laptop. Thank you for creating this fork.