Linux Questions

Title. Tried to search, found instructions on how to do it in debian-adjacent distros, but I'm in openSUSE, which doesn't use dpkg.

I also checked the manpage for zypper and found nothing that seemed the part, though I don't exclude the possibility that I just failed to read it properly.

I dual boot Windows 10 and Linux. Whnever Windows freezes or boot gets interrupted etc. I lose access to Linux because UEFI offers only Windows as boot options. On checking EFI partition still has rEFInd and PCLinuxOS entries needed.

I wonder why it cannot see them?

Went away from my computer for a bathroom break. When I came back I noticed it took a very long time to wake up. But that was the least of my worries, as Plasma seems to now be really bugged out:

Two things: Window decorations (like the ones at the top with the buttons to close and such) do not render properly. That's the simple part

The other, weirder one, is harder to explain in text so I made a video -- The short version is that whenever I mouse over any icon in a panel, be it a tray icon or something on the taskbar thingie -- it seems to jump to the top-right corner of that panel. Though only visually (as in, to interact with it, I still have to click the blank space the icon once occupied)

I have also noticed that icons within qt6 windows do not show in the proper place

!

These persisted after reboots.

Other info:

• Linux/KDE Plasma: OpenSUSE Tumbleweed 20240531
• KDE Plasma Version: 6.0.5
• KDE Frameworks Version: 6.2.0
• Qt Version: 6.7.1
• Kernel: 6.9.3-1-default (64-bit)
• Graphics platform: X11

Extra details about system (idk maybe it helps?):

1. I have an AMD Processor and GPU
2. All the things I have installed are either from the official SUSE Repos or from Flatpak. There's also some appimages and local executables in my user folder. There is 1(one) application I compiled from source and installed system-wide, and that was Orbiton, a text editor for terminal.
3. When I update the system I get a notification about how updating glibc-32bit would break Steam. So I marked it as untouchable on YaST. Maybe this broke something else? Idk.

Things I have already tried:

1. Updating the system
2. Rebooting
3. Changing theming configurations back to system defaults (hey, you never know)
4. Moving widgets around in panels
5. Disabling fancy effects
6. Disabling and re-enabling my second monitor/changing which monitor is the primary
7. Asking nicely

Things I have not tried:

1. Switching to Wayland (I would do so permanently but it breaks Inkscape for me and that's part of my workflow -- Plus I'm new to SUSE, and the last time I switched from X to Wayland was on EndeavourOS, dunno if the process is any different)
2. Crying

I have also posted this to the kde bug tracker. Posting it here to in hopes of getting an answer sooner :P

EDIT: I gave it some time to see if it would stick and it did. So. "Going into the Plasma Renderer settings and switching it to OpenGL" was the solution to my issue, even if I have no idea what caused it, I at least seem to have fixed it

Hello there. Was wondering if anyone had any suggestions for a Linux distro for grandparents? They are over 70 years old, with an old HP desktop and laptop running Windows 10. All they need is a Web browser, so no need for special software or wine to run Windows programs. Would preferably like something that is low maintenance so I don't have to be constant tech support for them (apart from the initial install and setup). Thanks for any suggestions.

I tried the following

``` sudo cryptsetup luksChangekey /dev/nvme0n1p3 < new passphrase >

```

It then asks for the Sudo password, then asks for the old passphrase, but then it prints this error message

Failed to open key file.

what went wrong ?

Edit: turns out using GNOME Disks is way more straightforward.. 😅, thank you all

I am looking for a way to play HDR content on Linux. From what I understand KDE 6 has experimental support for HDR, but isn't available on Pop OS 22.04. Apparently Cosmic desktop will support HDR when it's released, but I don't know if the experimental version will.

Can anybody help me here? Will I need to change distro?

My use case is splitting audio into separate channels in OBS for Twitch Streams so I can play music live without getting my VoDs struck. If my approach is entirely wrong for the use case, I'm happy to scrap the whole thing and sign it off as learning experience.

My solution is to use virtual sinks that I record through Audio Sources in OBS. I've got two loopback-devices (config at the end) with media.class = Audio/Sink, assign my playback streams to the relevant output capture. The loopback of each is then passed on to the common default (physical) output device, namely my headphones. So far, this has been working great for me, aside from minor inconveniences:

The first is that I want certain apps or playback streams to automatically be assigned to the capture sinks upon starting the app. I had a working pulseaudio¹ setup on Ubuntu where I used pavucontrol to set the output once per app and it remembered that setting. Every time I opened that app, it would direct its playback streams to that sink. I migrated to Nobara and opted to try configuring pipewire (directly)² instead. The devices are created correctly but every time I (re-)start a relevant app I have to go set its capture device again.

The second is that occasionaly upon logging in, one loopback stream will initially be passed to the other sink instead of the default output, which resolves upon restarting pipewire³. Is something wrong with my config? Both have the same target.object and restarting it fixes it, so I'm guessing it may be some race condition thing where the alsa_output isn't initialised at startup yet, but I don't know how to diagnose or fix that

----

1: I have since learned that apparently it's actually still pipewire parsing that config, but the point is I configured it through ~/.config/pulse/default.pa

2: ~/config/pipewire/pipewire.conf.d/default-devices.conf

3: Trying to set it in pavucontrol doesn't work and keeps resetting that playback's output to the given sink if I try to select the correct capture device. Repatching them in Helvum does the job, but then pavucontrol just shows blank for the device (doesn't interfere with controlling the volume, but maybe it's relevant for diagnosing)

----

My current ~/.config/pipewire/pipewire.conf.d/default-devices.conf:

context.modules = [ { name = libpipewire-module-loopback args = { audio.position = [ FL FR ] capture.props = { media.class = Audio/Sink node.name = vod_sink node.description = "Sink for VoD Audio" } playback.props = { node.name = "vod_sink.output" node.description = "VoD Audio" node.passive = true target.object = "alsa_output.pci-0000_00_1b.0.analog-stereo" } } } { name = libpipewire-module-loopback args = { audio.position = [ FL FR ] capture.props = { media.class = Audio/Sink node.name = live_sink node.description = "Sink for Live-Only Audio" } playback.props = { node.name = "live_sink.output" node.description = "Live-Only Audio" node.passive = true target.object = "alsa_output.pci-0000_00_1b.0.analog-stereo" } } } ]

I'm looking for a lowish priced laptop that I can put at least 2 extra monitors on. I want a second landscape 4k and a portrait 1080. Don't need anything special. One monitor has DP and HDMI, but the other just HDMI. Do I just get a DP hub and use a converter dongle for the second?

What would be a recommended laptop for this scenario? I only want AMD CPU and GPU as I can't be arsed to fight with noVideo and Intel doesn't deserve my business.

Yesterday I bought a new laptop that should be arriving to my home sometime next week. In the mean time, I've been digging around and researching some details in order to get Linux running on it as comfortably as possible. My main concern with the laptop is the fact that it has an RTX2050 Mobile on it (I couldn't find any dedicated AMD laptops within my budget), and my concerns include the fact that I prefer using Wayland on my systems and possible impacts on battery life as I know hybrid graphics in Linux are quite a nightmare.

I'd like to use this system for some casual gaming, however other than that my use cases for the laptop mostly consist of coding and web browsing, so I thought of the following idea: Leaving the dedicated graphics card as a pass-through device for a Windows VM where I could play all my games (though I'm not really sure on how VMs impact anti-cheat for multiplayer games and such), and leaving the Radeon 660M graphics on the Ryzen processor for the Linux system itself, which should be plenty capable of handling any DE and accomplishing my daily tasks, while also preserving battery life as the laptop is not running on the 2050 100% of the time

Does this make sense? Does anyone have a similar setup on their laptop and has it worked for them? Are there any possible consequences I should be wary of when attempting this?

If the laptop model is relevant in any way to answering this question, it's an HP Victus 15 with a Ryzen 5 7535HS, an RTX2050 Mobile (4GB) and 16GB of RAM.

Is there a way to move distro without loosing data in /home? I am currently running Pop OS and want to move to Nix OS while keeping the data. Normally I could use an external hard drive or my server, but most of my equipment is in storage at the moment. Current partition setup is using LUKS and LVM with ext4. I am guessing there is a way to manipulate the LVM to make it work by adding another partition and installing into it.

I know this is probably a convoluted idea. I am trying to avoid spending money an another external drive.

I am finding it difficult to fill in forms made with MS Word in LibreOffice. The formatting seems to end up all wrong among other things, and LibreOffice feels slow and clunky to use.

I've tried OnlyOffice, but it tends to crash and be slow as well.

At this moment in time I am trying to get MS Office 2010. Is there a better solution?

Hey all! I've been having an issue I can't figure out. Suddenly, I realized I'm in the heart of Linux users! I can ask here! I'm a total noob, so please be gentle.

I installed Xubuntu and got everything but the touchscreen working properly. The touchscreen works but the cursor is consistently off a bit, with the least error in the center of the screen and increasing as it moves to the sides. I've tried running xinput_calibrator but it doesn't help. I attempted to run libinput.calibrate-touchscreen but keep getting a "is a Wayland compositor running?" error message.

Any suggestions?

cross-posted from: https://lemy.lol/post/24413858

> Help Needed: Configuring ASUS Fingerprint Sensor on Fedora > > I recently got my hands on an ASUS device equipped with an fingerprint sensor . As a Fedora user, I've been trying to set up the fingerprint sensor on my system, but it's proven to be quite a challenge. > > So, I'm reaching out to the community here for some guidance. Has anyone successfully configured an ASUS fingerprint sensor on Fedora before? If so, could you please share your experience and any tips or resources that might be helpful? > > Any assistance would be greatly appreciated! Thanks in advance.

cross-posted from: https://lemmy.ca/post/20291268

I recently acquired a Raspberry Pi 5, but I've been having a lot of difficulty in getting LUKS encryption to work. Has anyone had any luck?

Also, I am using an NVMe drive, so Raspbian is really the only OS that works well. NetBSD can see the disk, too, but I found it annoying to use; and FreeBSD ended up breaking itself. I have not yet tried Armbian.

How do I fix my home dir with nix? It seems I have messed something up and now I can't install home manager. Anytime I try to install a package with nix-env it gives this error too:

error: this derivation has bad 'meta.outputsToInstall'

Would someone #help me configure my #WireGuard server to access my home local network?

I've literally been stuck for 6 hours.

https://forum.yunohost.org/t/cant-access-yunohost-local-network-through-wireguard-server/29127/1

@linuxquestions

I have just set up a Raspberry Pi 3B+ with Raspbian "Bookworm", and I have decided that the classic desktop environment, FVWM-Crystal, is the one that feels right. However, I don't seem to be able to change the font.

Ordinarily, you would use the font selector dialog, but for some unknown reason it refuses to launch and I am unable to find it under /usr/bin, so I can't find out what's wrong.

Does anyone know either how to fix the dialog, how to find the binary, or how to change the font without using the dialog?

I understand that this is a very old DE, so if you can tell me about a newer alternative that looks the same and is equally lightweight, I'm all ears. Otherwise, please leave me to my madness.

Ok, so I had 1 ssd with Kubuntu and windows on it. I got a second ssd and I want to put opensuse on it, dual booting (well, triple). The problem is, when I went to install it, it showed the id of my two ssds as opposite of what the partition manager in Kubuntu says. I.e., Kubuntu calls the first one nvme0n1 and my new ssd nvme1n1, while the opensuse installer is calling the old ssd nvme1n1 and the new one nvme0n1. I know because it shows the existing partition sizes on them that way, and recognizes that windows and kubuntu are on the old ssd.

So is this normal? Is this ok? Is it ok to just install it with the ssd names this way? Would that confuse kubuntu at all, or are the two OSes ok with calling them different things? I just don't want the installer to overwrite anything on my existing partitions.

If I have my browser maximized in my center monitor, whenever I go to search on Lemmy or go to my inbox and it is empty, the screen goes completely blank/black. It looks as if it lost power. If the browser is not maximized, it wont happen. This happens whether I use Chrome or Firefox. Any ideas on how to start troubleshooting?

• OS: KDE Neon 6.0
• KDE PLasma: 6.0.2 (happened with KDE 5.x too)
• GPU: Nvidia GeForce GTX 1060 6GB
• Monitor messing up in connnected to the HDMI port.
• Other two monitors are connected (a) to the DisplayPort and (b) DVI-D

This will be for a physically small i5 laptop for various programming fun. The candidate linux should be easy to install, and provide a large selection of CLI programs.

I want to sync retroarch save files across devices on my local network using a bash script. Plan is to run the script as a cronjob to keep all machines synced.

This does the trick as a one-off in the terminal: rsync -a /home/localuser/.config/retroarch/states/ [email protected]:/home/remoteuser/.config/retroarch/states/

• Copies new save files to remote location
• Updates any save files which were modified

But when I put the same line in a bash script rsync's behavior changes. My bash script looks like this: #!/usr/bin/env bash rsync -a /home/localuser/.config/retroarch/states/ [email protected]:/home/remoteuser/.config/retroarch/states/ I call it with bash sync_saves.sh

• Copies new save files to remote location
• Updates any save files which were modified

Strangely, rsync doesn't update modified files when run as a script. But it's not failing altogether, because it transfers new files OK. What am I missing?

> Update: if I do the rsync in the reverse order (remote machine -> local machine) then the bash script works as expected. So my issue exists only when rsync goes local machine -> remote machine. Why would this matter?

Update 2 (Solution): I changed the command to rsync -razu /home/localuser/.config/retroarch/states/ [email protected]:/home/remoteuser/.config/retroarch/states/, but I'm not sure that made any impact. The issue was how I was doing my testing. I was doing touch testfile.txt to change the modification date on a file & then I'd try to transfer it with the bash script & watch the modification date on the downstream machine as confirmation that it moved correctly. Problem is that rsync must be smart & doesn't transfer a file if only the modification date changes. It requires the contents to also change. Whenever I tested this way I would never see the file transfer, but when I changed my testing method to change the contents of the file instead (not just the modification timestamp) then all worked fine!

I feel like a dummy for initially mixing testing methods & coming to the wrong conclusion about what was happening, but happy it's working now & maybe I learned a lesson!

Briefly: I'm running Kubuntu right now, just installed a second ssd. If I install another distro (say opensuse) on it, can I tell it to use the same /home that kubuntu is using (which is on a separate partition and drive)? Actually looking to switch distros, but I want to keep all my data where it is on the bigger hdd, while moving games to the ssd.

If you want/need more details:

• ssd1: windows, kubuntu /
• hdd1: kubuntu (opensuse) /home
• ssd2: (goal) opensuse /, second partition for games

Title. Plasma 6 just dropped on my arch-based distro, and it came with an option for a colorblindness correction filter: !

Neat little tool that my Protanope ass was very excited about, and it works.

The thing is.

Some time ago Windows also introduced one of those, and in Windows, you can turn it on and off with a key-combination shortcut. I use that a lot on Windows, to keep the filter off and turn it on just when it is necessary (look, every person experiences colorblindness differently, and on my end, these filters while useful for certain kinds of work, are very ugly most other times)

Now, I already know I can set a key-combination shortcut to a terminal command on plasma. Easy peasy.

But for me to do that on plasma I'd need to have a way to switch the effect on and off from the terminal.

I know that I can do systemsettings kcm_kwin_effects to launch the configs app straight into the relevant tab. But now I'm wondering if I could make that even more automatic, maybe using the --args thing, which apparently is literally meant for sending commands directly to the configuration module. But then I wouldn't know what the command is.

I want to configure a Raspberry Pi 4 as a web (application) server.

Although I could of course simply do it via Raspbian, I would love to use an Immutable/auto updating OS like Fedora Core OS/Fedora IoT/OpenSUSE MicroOS.

To my surprise, every solution does not look very turnkey ready for Raspberry Pi 4.

Please correct me, if I am wrong but it seems:

• For Fedora Core OS/OpenSUSE MicroOS it seems like I have to download the firmware for the Raspberry Pi, partition the sd card by hand and afterwards login to configure WiFi and/or use an ignition file on a separate USB stick on boot

• For Fedora IoT it seems I need a running Fedora system first (yes, I know about LiveCDs) and I still need to edit by hand the Wifi configuration How to install Fedora IoT on Raspberry Pi 4. Further, it seems Fedora IoT has 'fixed' version numbers and no automatic updates.

So, my questions:

• It seems Fedora IoT is the nearest fit for my use case and comparatively the easiest version to setup?
  • Am I missing out on Fedora Core OS or OpenSUSE MicroOS?
  • Are there other viable immutable options from reputable sources?
• Does anyone know about an immutable distribution, where the initial setup is basically like Raspbians 'dd image to sdcard and copy user credentials and wifi config to the /boot partition.'?
• How does Fedora IoT handle updates between versions (like Fedora 38 to Fedora 39)
  • Is it a regular update or do I have to tell the OS to update explicitly
• Most important question: Anyone here has experience with running Rasbian and one of my options in practice and can give some advice/recommendations if immutable is worth it?

Solution: I bought a dolphin bar. Its not here yet but it should work better.

Rebooted my computer earlier today and walked away while it did its thing. When I got back to to it some minutes later, I saw a black screen with that "_" text cursor flashing on the topleft corner. Which was, of course, odd.

Hitting Ctrl+Alt+F2 sent me to the TTY. Which is to say: The system was still up, and indeed, calling for a process manager loaded showed that sddm was still running, as were a bunch of other processes.

Still, attempts to get sddm to do its thing failed. I tried to systemctl restart the sddm service, I tried to reboot the computer. I tried to delete customizations to its config files in case they were breaking something.

In all of those cases -- Title happened. The mouse cursor would show up for a second or two. And then it'd kick me back to the black screen with text cursor because something was fucked.

I eventually managed to get to my desktop by entirely disabling the sddm service, rebooting so I'd just get the TTY, and then doing dbus-run-session startplasma-wayland to run Plasma manually once logged in (thank FUCK for smartphones and access to internet search on them for helping me figure this out).

So that's a workaround, and it sorta works but I'd like to get my display manager back, please. :P

Further information:

• I am running EndeavourOS.
• As implied, I use KDE Plasma under Wayland as my DE.
• I have an AMD GPU
• I am at the latest version of every relevant package -- The reboot I mentioned at the start of the thread was just after running a sudo pacman -Syyu
• I did try to search for my specific issue but nothing relevant came up? A lot of older issues, under X11, and most involving NVidia stuff. None seemed relevant to my case.
• Having found the workaround I used the computer all night and had no other issues, which to me signals it's something about sddm and ONLY sddm that is broken, whether it's some config that got fucked up or some bs with my own incompetent package management.
• I am, of course, able to provide logs and stuff if you tell me which ones and where to get them, cuz yeah.

Well, my issue is simple to explain, but I tried everything to solve it without success.

I like recording gameplays, just for fun. The game I currently make recordings for is not resource heavy (it's Doom 2 through GZDoom). I'm using Lubuntu 22.04.

So, here is the command I've just used:

ffmpeg -f x11grab -draw_mouse 0 -framerate 30 -probesize 42M -video_size 1920x1080 -i :0 -f pulse -i default -c:v libvpx-vp9 -r 30 -g 90 -quality realtime -frame-parallel 1 -qmin 4 -qmax 48 -b:v 4500k -c:a libvorbis prueba.mkv

The issue is, if I record without including the audio, then the video plays smoothly after being recorded. But if I record including the audio, no matter what parameters, codecs, bitrate or anything I use, then the video is barely watchable, with lots of choppiness, and even with delay between audio and video, apparently.

SimpleScreenRecorder works fine, but sometimes there are few frames dropped and I don't like it much. OBS is very heavy for my hardware (Mac Mini 2016, Intel Core i5 1.4 GHz 4260U, Intel HD Graphics 4000, 4 GB RAM).

I also tried VAAPI, with same results as above.

And the thing is that I remember recording some years ago, with no issues at all.

I don't know what to do. Any tip or solution?

I feel stupid, but I want to install Kubuntu, as a dual boot for my windows 10 PC. I am a total rookie with linux. Maybe even less than rookie. I have 3 Flash usb sticks, but one of them seems broken, and the two others too small. I also have a USB card reader, where I can put an SD card in but I don't seem to be able to boot from that.

I also tried a trick with Unetbootin, but windows wouldn't let me boot from that either, even though it gave me the option to, on restart.

My question is, can I install a smaller version of Kubuntu from my 3,8Gb usb stick and upgrade to the newest version later, after it has been installed? I am not totally locked to Kubuntu, but I think that i have read that its the best version for beginners. I will easilly be convinved to another version though, if you guys think its better

I have lingering setup and I can still access the container but for what ever reason Podman seems to be unable to access the GPU for no apparent reason.

I think this may be an issue with systemd but I'm not entirely sure.

Solution: you need to be logged in for it to work. I accomplished this on a separate VM with autologin to icewm.

I'm looking to pass though host power information to allow for the guest os to adjust power usage.

Title. Been meaning to upgrade my GPU, and Intel Arcs are undercutting their AMD equivalent by quite a bit?

But like, I am not going to switch back to Windows. And I don't want to spend a lot of money on a new computer part just to learn it doesn't support my OS properly.

Now. I did search for this and found a phoronix benchmark thing -- But it's from almost a full year ago.

So.

Anyone have an Intel Arc GPU and can tell how they are doing as of now?

I installed ~300 updates via Discover a couple of nights ago. I sensed something had gone amiss when Firefox both crashed and wouldn't resume after I opened a brand new session (ie. no tab reloads). I got the crash report box, then a subsequent crash.

Full reboot. Up comes the login screen. The password field cursor is unresponsive to keyboard input, and isn't blinking. The virtual keyboard button isn't responsive either, despite my having mouse movement. I then reboot, this time via recovery mode, which loads the crappy fallback graphics driver with only 1024*768 resolution available. This persists after package repair attempts and sudo apt autoremove to clear disk space. My AMDGPU drivers don't seem to be functional at all.

var/log/apt/term.log (below) reveals the latest driver versions are 24.x. Presumably these were upgraded during the update, prior to which I was on an earlier working version? That's all I can think of.

What other logs should I consult for troubleshooting? Would driver reversions work? How do I get back to a normal display? Your input is appreciated!

Preparing to unpack .../libglapi-mesa_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking libglapi-mesa:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Setting up libglapi-mesa:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Preparing to unpack .../libgbm-dev_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking libgbm-dev:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Preparing to unpack .../libgbm1_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking libgbm1:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Setting up libgbm1:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Preparing to unpack .../libegl-mesa0_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking libegl-mesa0:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Setting up libegl-mesa0:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Preparing to unpack .../libgl1-mesa-dri_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Setting up libgl1-mesa-dri:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Preparing to unpack .../libglx-mesa0_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking libglx-mesa0:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Setting up libglx-mesa0:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Preparing to unpack .../025-libegl1-mesa-dev_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking libegl1-mesa-dev:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Preparing to unpack .../048-libosmesa6_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking libosmesa6:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Preparing to unpack .../060-libxatracker2_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking libxatracker2:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Preparing to unpack .../080-mesa-va-drivers_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking mesa-va-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Preparing to unpack .../081-mesa-vdpau-drivers_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking mesa-vdpau-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Preparing to unpack .../082-mesa-vulkan-drivers_24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4_amd64.deb ... Unpacking mesa-vulkan-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) over (23.3.3+git2401121944.151cd31e051~j~mesarc4) ... Preparing to unpack .../102-xserver-xorg-video-amdgpu_23.0.0+git2401241940.4d7a9a6~j~mesarc0_amd64.deb ... Unpacking xserver-xorg-video-amdgpu (23.0.0+git2401241940.4d7a9a6~j~mesarc0) over (23.0.0+git2309251950.31a092a~j~mesarc0) ... Setting up mesa-vulkan-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Setting up mesa-vdpau-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Setting up xserver-xorg-video-amdgpu (23.0.0+git2401241940.4d7a9a6~j~mesarc0) ... Setting up libgbm-dev:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Setting up libxatracker2:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Setting up mesa-va-drivers:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Setting up libosmesa6:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Setting up libegl1-mesa-dev:amd64 (24.0.0~rc3+git2401302259.6dadb9b032c~j~mesarc4) ... Further info

• KDE neon 5.27, dual boot
• Kernel 6.5.0
• X11
• GPU R9 390, single monitor setup

Hello guys, I have a question about GNOME Nautilus and the sizes of icons in list view. In the included screenshot, you can see the list view of my home folder with lowest icon size. However, the entries are still rather tall compared to other file managers. To reduce the need of scrolling, I would like to reduce the icon size further. Is there any way to do this? Thanks!

Edit: The issue is resolved now. I found out, that padding is too large in the theme I use. The issue was already fixed upstream, only had to apply one commit to fix.

EDIT: Solved! Check this comment!

I use a keyboard with an american layout. I find it much better for coding and actually love this keyboard to pieces. However, I still need to write in portuguese.

The dead keys in Microsoft Windows worked perfectly for me but the Linux ones do not. Some characters are not available and are replaced by characters that don't exist in the portuguese language.

In X11 I fixed this by using an .XCompose file with the keybinds just like in Windows. Source here, it works perfectly.

In Wayland, the .XCompose file works for pretty much all apps. Firefox is fine, kitty is fine, Vivaldi is fine. Unfortunately electron apps with the --ozone-platform-hint=wayland ignores the .XCompose file and I get the default keybinds. Since I own an nvidia card I really need these flags, otherwise the electron apps will aggressively flicker and/or eat letters while I'm typing.

I've searched far and wide, there are several open bugs in chromium, electron and wayland repositories. Everyone seems to be pointing fingers at each other for years and no workaround to make .XCompose work seems to be available.

I'm wondering if there is an alternative way to customize the dead keys under Wayland. Thanks in advance.

Here is my problem:

Our TV is connected to a SBC running a GNOME/Wayland desktop, where we watch Jellyfin and sometimes Netflix/Hulu through Firefox.

I'd like to be able to trigger pause/play (space button) from Home Assistant, which is running on my home server.

What I am thinking of would be a server/daemon running on the TV computer that my home server would be able to send keys to via a CLI tool (in this case the space key). I am surprised to find that I cannot locate any program like this.

Can anyone provide any suggestions here?

Other ideas:

• Jellyfin's HA integration doesn't let me pause/play from it, and that still doesn't handle Hulu/Netflix.
• I was able to get this working through SSH and there are tools like ydotool/wtype here that work, but I found waiting for SSH to be a bit slow to connect.

Update: I got frustrated and coded up a solution: https://gitlab.com/neilsimp1/kbsrv

Can I get a better Nvidia+Wayland experience by using prime and connecting the display to an AMD iGPU? I saw that in the last year Nvidia Prime had some improvements, do they make it feasible?

I can't just try it because I have yet to buy said AMD iGPU. And I'd like to know it before buying

For reference I use MX Linux with Systemd enabled.

I'm pretty new to Linux and have been running this for around a month. Everything was perfectly fine until yesterday (7th) when, on booting, I saw a glimpse of the logon screen for a second and was then taken to a black screen with some white text that read "[7.300130]". Searching for this number doesn't bring up anything.

Eventually I found that I could get into a terminal here by pressing ALT+F1. I also found a lot of people suggesting that if you get past grub and then have a very similar problem (blank screen, flashing cursor rather than a number) then it could be graphics drivers so I uninstalled and reinstalled them to no avail.

Somewhat embarrassingly, the eventual solution was very simple. After I opened the terminal with ALT+F1 I could get back to the GUI with ALT+SHIFT+F7 and.. everything was fine.

Still though, whenever I boot now, I get a glimpse of the logon page, then the black screen with the number, and then doing the shortcuts above gets me back to the logon screen and after that everything is normal.

My first instinct is to say some update on the 6th must have caused this. I have checked /var/log/apt/history.log and I did run apt upgrade on the 6th but the only update was to mx-welcome which I don't think is relevant.

Although it's only a minor nuisance I would like to not have to do this every time I boot. Any idea what this is?

I've noticed that some apps sometimes don't start from the GUI. I've seen it on several computers (all running Ubuntu 22.04). That includes double-clicking an appimage icon from an explorer window, or launching an app through a launcher shortcut. But if I open them manually from a terminal window they never fail to start.

The terminal workaround is fine... But any ideas what could be wrong with the GUI? Is there a service I can restart to try to get the functionality back?

EDIT: I'll add that the issue is sporadic. Steam will open fine from the GUI today, but tomorrow it won't, etc. (It's not as simple as a bad path in a shortcut)

I'm very new to Linux but have wanted to set up a media server since the early 2000's so I've finally set up a mini-pc with Mint and I was roughly following this guide that I'd found on Lemmy Complete Guide to Building.... I've had very little luck with the instructions provided in the link but like most of the suggested packages and have successfully gotten OpenSSH, Jellyfin, Docker and Docker Composer installed and working as far as I know. The newest problem that I'm having trouble finding an answer to is while following the instructions on hub.docker.com.

I have pulled the Docker image but when I go to create and run the container I get a message docker: invalid reference format.

I believe I have everything entered exactly as I'm supposed to:

$ sudo docker run --name adguardhome --restart unless-stopped\ > -v /home/justin/server/adguard/workdir:/opt/adguardhome/work\ > -v /home/justin/server/adguard/confdir:/opt/adguardhome/conf\ > -p 53:53/tcp -p 53:53/udp\ > -p 67:67/udp -p 68:68/udp\ > -p 80:80/tcp -p 443:443/tcp -p 443:443/udp -p 3000:3000/tcp\ > -p 853:853/tcp\ > -p 784:784/udp -p 853:853/udp -p 8853:8853/udp\ > -p 5443:5443/tcp -p 5443:5443/udp\ > -d adguard/adguardhome

Does anyone have any advice for me?

I'm considering buying second small touchscreen monitor, but I've been only ever running single monitor setup. How much hassle would it be? Is it possible to make mouse captive to primary monitor, and operate this secondary only as touch? Would running screens at different resolutions be a big problem? Running KDE on Wayland, AMD graphics.