• 0 Posts
  • 104 Comments
Joined 3 years ago
cake
Cake day: July 9th, 2023

help-circle


  • Sure any idea on how?

    For my part i have been talking about linux to everybody for the last 10 years, it made me very pleasant at parties, highly recommend!

    The few people that actually listened tried it out, contacted me 5 times per day asking for tech support for half a week, then switched back because they did not like the shape of the icons in KDE.





  • I have had debian on my work laptops (3 of them, they where current gen when bought) for 10 years, the only issue I ever had with drivers was a printer driver and the supplier had a .deb on their website.

    Not everybody needs specific software and drivers, most people use the integrated microphone and camera of their laptop in their calls and that is about all that matters. Debian is pretty good at supporting the integrated stuff.

    Of course some OEMs work better than others, butthe widely available brands, which also correlate with the most users are usually well supported.



  • I ain’t your brah mate.

    Look, I am not that antagonistic man, no need to be this riled up. My main issue is that I lurk these threads to help people with their linux issues to help adoption, but we really have a lot of threads were flatpak is the issue, you can check the history.

    I am sorry you did check to see if the native one works and reproduced the issue, I somehow understood the exact contrary, I apologize.

    The next time I will ask the user to reproduce te issue with the native version before I start my rant.

    My usecase is to turn on my machine in the morning, edit some text files and run a browser and some command line tools. Then i turn it off in the evening, nothing special. I got no beef with wayland and especially nothing against systemd btw.

    Is there any chanche that your reboot aversion is due to wayland’s issues with session restoration?


    • the thread had no solution when I wrote, I assumed it was flatpak

    • You seem to have found a reason now, and it indeed seems to be flatpak again

    And the reason is always the same, flatpak runs as intended and breaks stuff by default, people find issues, write a thread here to ask for proper flags and settings for stuff that works natively out of the box 90% of the time when installed from the native repos in serious distros.

    Which brings us back to my point: it solves the wrong problem for the wrong people. Provides sandboxing and isolation for people that use it as a covenient software source unaware of its quirks.

    For those aware of them it is useless because they will know enough to do the isolation and sanboxing were it matters themselves.

    To be fair you did some good work understanding what was happening, so I ask you: why do you use flatpak?









  • I mean, that is not how it works? Sure there are a couple ms difference in latency but if you have that large of a speed difference it is more likely a routing or configuration issue. Pacman is 1 packet at a time by default on arch, but every procedure tells you to change that if possible.

    Also your government is not the most open one when it comes to internet traffic, maybe they filter pacman more than apt?