this post was submitted on 29 Jun 2023
332 points (94.6% liked)

linuxmemes

21378 readers
1309 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
     
    (page 2) 47 comments
    sorted by: hot top controversial new old
    [–] [email protected] 1 points 1 year ago

    That's funny, I did the opposite - I got used to developing on osx, then Linux, but that was always on my work computer - my desktop has always been Windows (I'm still using the same license and chassis from the computer I bought in high school a decade and a half ago).

    Then I burnt out hard, and started picking up contracts here and there, but didn't have the money to pick up a second computer powerful enough for gaming or work. So I ran virtualbox and avoided cmd like the plague for a while... It was driving me nuts, so I made plans to run Linux with Windows in a hypervisor - I was looking at pci passthrough so I could give it direct access to the graphics card.

    But then wsl came out and it just didn't seem as important. Even as Linux gaming has grown, I just haven't felt the need to switch... It's sometimes finicky and setting everything up on a new computer is a pain, but the only time I considered switching one of my machines over is setting up LLMs - that was a real pain to coax into working, and it'd run better on Linux

    [–] [email protected] 0 points 1 year ago (1 children)

    Meanwhile, the huge improvements that Proton has gone through since 2018 have made Windows damn near obsolete for myself and many other Linux users. I really only keep it around on my gaming machine for VR titles and if I want to use Discord screen sharing (since they still haven't fixed the lack of audio on Linux) at this point, and my main laptop has been Windows-free for years now.

    [–] [email protected] 0 points 1 year ago (1 children)

    since they still haven’t fixed the lack of audio on Linux

    Huh, never heard of this. Do you mean that it's impossible to stream desktop audio through discord? As a workaround, you can try switching to Pipewire and patching your audio output's monitor into Discord through helvum. Or write a script that does that automatically.

    [–] [email protected] 0 points 1 year ago (1 children)

    Yeah, when you stream your desktop from Linux over Discord, your desktop's audio doesn't come through. It's been a known issue for years but it's a very low priority fix for Discord's developers.

    Does the method you're describing play well with speaking at the same time, or do you have to decide whether you want speech or audio?

    [–] [email protected] 0 points 1 year ago (1 children)

    Does the method you’re describing play well with speaking at the same time

    Yes.
    With pipewire, it is possible to patch two sources (i.e. your microphone and an application's audio) into a single input, and it will mix them together into one stream. I just tested this with Audacity (didn't feel like booting up Discord, but it should work the same). I could hear my voice and the application's audio at the same time. This is what it looked like for me in Helvum:

    The gray PortAudio block is Audacity (would be Discord in your case). "ALC3232 Analog" is my microphone (on the left) and my headphones (on the right). Music Player Daemon is the application whose audio I wanted to stream. The connection between the microphone and Audacity was made automatically as soon as I started the recording. I had to manually make the connections from Music Player Daemon to Audacity for both left and right channels. After that I could see both the mic sound and the music player daemon sound in the recording, mixed into one stream. It should work the same way with Discord. If you wanted to, for example, make your voice louder or quiter compared to the application audio, you could just adjust your mic's gain (or the application's volume) with Pavucontrol (it's an app made for Pulseaudio, but it works flawlessly under pipewire as well).

    In my original comment, I said that you could patch your output's monitor back into Discord. This is a bad idea, since if anyone speaks to you in the call, that audio will also be echoed back to them. So it's better to connect the individual applications' audio into Discord as opposed to the output monitor.

    Now, this could get a little tedious, making those connections by hand every time you want to screen share. So you could try to make a script that does something like that automatically. Pipewire also has the concept of a "session manager", which is basically a daemon that decides which connections are made by default, when new sources or sinks register with Pipewire. For example, wireplumber, the default session manager, was responsible for connection audacity to my microphone automatically. Maybe you could try to configure your session manager to also automatically make connection between Discord and any app that outputs audio (idk tho, never done it before).

    [–] [email protected] 0 points 1 year ago (1 children)

    Huh, this is all very informative. Thanks for the breakdown. I'll have to see if I can get Pipewire going on my gaming setup.

    [–] [email protected] 1 points 1 year ago (1 children)

    There's also discord-screenaudio on Flathub if you don't feel like doing the work yourself. It works out of the box for me.

    load more comments (1 replies)
    [–] [email protected] 0 points 1 year ago (1 children)

    Linux is Linux.

    WSL is Bill Gates' wet fart of an OS running Linux.

    Definitely not the same thing.

    [–] [email protected] 0 points 1 year ago (1 children)

    Is it not? It's basically a Linux container running on Windows, isn't it?

    [–] [email protected] -4 points 1 year ago* (last edited 1 year ago) (1 children)

    But it is Ubuntu, it essentially negates any benefit from being Linux.

    But seriously, you still have to sift through all the worst of Windows to make it to Linux. When you could be, you know, just using Linux and avoid the dead weight.

    [–] [email protected] 1 points 1 year ago

    You can install distros other than Ubuntu though. But what's wrong with Ubuntu anyway?

    I'm using it on a daily basis, and I haven't really encountered any real issues, so for me it's fine.

    [–] [email protected] -1 points 1 year ago (6 children)

    Combines the power of a really half-arsed Linux distro with the pure speed of the Windows file system.

    I mean, it's slightly better than nothing, but installing a real Linux distro on Windows through eg. VirtualBox absolutely fucks it into the bin. I don't see who WSL is for. People in really locked-down corporate environments?

    [–] [email protected] 0 points 1 year ago (1 children)

    I don’t see who WSL is for.

    My guess is that this time they really wanted to pull the developer demographic over into the M$ sphere of influence. MSYS, MingW, and Git Shell already fill the same niche as WSL, so it wasn't destined to succeed. Thing is, they probably didn't expect it to succeed either. Microsoft's strategy has always been to throw a hundred dicks at the wall and hope that one of them sticks (think Zune, Windows Phone, etc). This time, Azure kind of stuck. WSL didn't. When you're as big as Microsoft, the occasional win more than covers the cost of a hundred losses.

    load more comments (1 replies)
    load more comments (5 replies)
    [–] [email protected] -1 points 1 year ago (2 children)

    Ah, yes, the feature to update the operating system that is by default enabled but is able to be disabled completely.

    If a *nix user can't figure out how to disable automatic updates, it's on them.

    [–] [email protected] 1 points 1 year ago

    I mean, it's never an issue for a power user, which arguably most Linux advocates are. But the disable option available for the average user is known to be overridden by MS. And the way that is not susceptible to MS remote meddling requires a Pro license, technical knowledge, installation of advanced system administration tools. All things that most people either don't have, or are not allowed (restricted permissions in corporate equipment, etc.), or rightfully don't care to invest time into doing. So this is still a common occurrence.

    [–] [email protected] -2 points 1 year ago

    Yeah this always baffled me; I love Linux and use it as a core for all my projects (containerized and VM), but disabling updates on windows takes about two minutes to open run > gpedit.msc > set auto updates to false

    Are people really able to configure full Linux boxes to their liking but struggle to tick one box?

    load more comments
    view more: ‹ prev next ›