Switching to Manjaro | Part 3 | 10 Day Challenge

23 thoughts on “Switching to Manjaro | Part 3 | 10 Day Challenge”

1. Don't get Too-Trusty with Updates!!!! This only happens once-in-a-blue-moon…. But… Updates will one day brick your install! This is why I depend on TimeShift these days. They only reason I switched to Manjaro as my daily-driver in 2019 is because of TimeShift. Why did I switch to Manjaro? It's fast. All the software you want or need is available/install-able without hassle. I thought 2019 was a good time to distance myself from Corporate-Ubuntu-Canonical and their derivatives.

2. How can I get Pacman on KDE? I'm using Octopi and can't find any thread in the forum. I'm afraid to ask, those dudes don't know how to properly deal with noobs

3. I've been watching your videos for a couple of months since I decided to switch to Linux to replace W7 on three PC's. I've learned quite a bit from your experiences. Aren't you the one that has a couple of monitors stacked vertically?

   I've been distro hopping for a couple of months on two pc's that have been running W7 for six years. One SSD on a Asus Z77 has been running Manjaro Gnome with dual monitors. A couple of days ago upgraded an Nvidia GTX 650 Ti to GTX 1050 Ti. Manjaro just booted up to the desktop like nothing changed running the same Nvidia driver. A pleasant experience. But one thing did change. The monitor number assignments. Left monitor is primary right is secondary. The original GPU had two DVI connectors. This one has DVI, HDMI, and display port. Since on the GPU side DVI is the first scanned for a monitor it is the one that displays the Asus splash screen after post. On the Manjaro side it labeled my primary #2 and secondary #1. Which is fine when running both monitors. Not so well when running single on the wrong monitor. Not sure why Manjaro reversed the number assignments. I need to reassign the numbers like they were with the old GPU. I can't find anywhere on linux forums how to do it or how these numbers get assigned. I can't be the only one that has observed this behavior.

4. Had neglected updating Manjaro for some time so I ended up having 535 packages that needed updating. I was expecting the worst but it went by smoothly, everything works perfectly there was just one aur package whose signature couldn't be verified but I'm gonna look into that later^^

5. I've been playing with the Archman JWM Edition distro today. Though I've used Manjaro a few times before I've never tried anything with Arch in the name.
   This version is rather nippy, to say the least. Very nicely done. Well worth a perusal.

6. I have the same problem with Windows updates if there's a lot of them (like with a fresh install). I have to tell it to a limited number at a time or the whole thing hangs and fails.

7. I must say, I had days where I upgraded ofer 1000 Packages on my Tumbleweed machine .. and it ran MOST (not always as you know from you challenge obviously xD) of the time fine.
   But yes, we all know that feeling … reboot after a kernel update o.o.
   BUT I must say (Some leap advertisement, again :D) with openSUSE Leap I had never issues with kernel upgrades and reboots (except of if I installed the NVIDIA driver with the original NVIDIA Installer from their website and not though the package manger, all I needed to do is to reinstall the driver because of the Kernel modules) it's so sad that the Leap Kernel is too old for a modern AMD GPU like you have x_x
   I saw, at opensuse software, that there are community Repos which offers a 4.20.3 Kernel but I'm note brave enough to test installing it xD

8. I have finally come to a stand still after Distro hopping for the last year or 2. Thanks to you, when you started your Manjaro 10 day Challenge I thought i'd give it one more go. Just to let you know I tried it a month or so ago and broke it within 30 minutes. I have never really liked Manjaro i'm the one in the background throwing rotten fruit at it. But I just tried Manjaro i3 and i'm blown away how amazing it has become. I am and always will be an Arch user so this is so familiar being it is based on Arch. It has the up to date software I need and when you install thing they work with no fiddling. It also has part of my backup plan Manjaro's version of Archiso so I can create my own backup iso with all my configs installed and manjaros version has AUR software included in the iso. I had to compile my own AUR software with Archiso(Again Fiddly. Thanks Great video.

9. do you have any experience with OSTree

10. I recently upgraded too.And my touchpad stopped working i did reinstall libinput.Reconfigured it,also tried synaptics but didnt worked.stuck with a mouse right now. Anyone else having this problem?

11. I am using Manjaro only inside VirtualBox but there, it's running smooth.

12. Actually partially upgrades are not recommended. It's better to upgrade them all at once.

13. Last week I was back on windows 10. Yesterday I checked the RAM usage after a cold boot. It was a f*&cking 3279MB. Today I switched back to linux. I reinstalled my OpenSUSE Tumbleweed backup, because I like it more than Manjaro. 768 packages needed to be updated, but the system booted up well after it. No problems whatsoever. I mostly like the fact that Tumbleweed does some serious testing on their Tumbleweed updates before releasing them. I also like the fact that Tumbleweed is backupped by a big company (and Manjaro is not). I run the latest KDE and use only 632MB after a cold boot. Compare this to the crazyness of Windows10. I'm glad I'm back. PS: I really like your 10-days challences.

14. I installed it on a VM myself just to see what the Arch world is like nowadays. On my second or third reboot of it, it changed the display language on its own (I'm not in the US, so I set regional settings but English as language.) I googled, apparently it does this routinely, so I erased the thing and installed a Kubuntu VM for now to play around on for disposable stuff (tested Traccar for instance the other day, great stuff.)

15. Goodbye part 3/5.

16. The biggest issue is i need windows for DRM games I play with friends that don't work on Linux, yet. So sometimes I'm not on it for awhile and then when I come back I'm so out of date that they've moved on to a new major version and it won't do it on it's own without -Syyu and sometime they make a major change that won't work because of a major pre change prior it can't do all at once lol. But it's always 5 minute fixes.

17. glad your part 3 was better than your part 2. I run manjaro and have had a pretty solid experience for the most part. I love the OS

18. Rule of thumb is to do backups before updates. And as late situation showed up, better not keep newer packages then in repos, so whenever manjaro downgrades some packages in repo, downgrade them too with sudo pacman -Syyuu, yes with double u. Those who didn't do it and had newer systemd, this update screw them over if they didn't do the downgrade before reboot. So things can get "interesting" (read: messy) on Manjaro too ;p.

    However, I'm glad your update went fine. Actually, for a 2,5 year Manjaro updates went fine on my current laptop (they were also fine on older one). The only update with problems was this one but I was cautious enough to withhold the reboot before I found a solution to many errors that I saw during update and which raised a red flag. This was the first time I saw any problems. Luckily solution was super easy and after making this one, tiny command, all was fine so I could reboot finally.

    By the way, a hundred something packages update is nothing. On stable, you can even get 500 packages updates (over 1,2 GB of download)

19. Manjaro sux.

20. I follow a modding guide when modding Bethesda games to make it more stable than vanilla, not less.

21. I was wondering how your experience was. I installed the update with no issues also. I use Cinnamon instead of KDE, do not like KDE.

22. Stability is prime for me, CentOS 6.10 is rock solid . I don’t need bleeding edge software. I’m trying out MX 18 on one of my other Thinkpads with the MATE desktop. It seems to be solid as well.

23. Tip for keeping rolling distros in one piece:

    * Freeze kernel and proprietary video card driver packages once you have it all working.
    * Keep backups of working versions. There is always the command line to install working versions in case anything goes wrong.
    * Upgrade those packages only when it explicitly tells to upgrade or there is some interesting new feature.
    * It is unlikely upgrading anything else will break the system.
    * And it helps using xfce (doesn't change much) or Cinnamon (upgrades every 6 months). They both never break anything.

    This keeps you alive in Debian's testing branch and Arch for forever.

    Great videos btw. I hope it works great for you too.
    I'm sure you are saving people from switching back and forth to Windows millions of times.
    It can be an endless loop that takes years without help 🙂

    Windows sucks => Try Linux => Can't figure out stuff in Linux => Go back to Windows => Windows now feels even worse => Give another shot to Linux => …………………………….
    .
    .

Comments are closed.