And all marketing budget at that, we don't even know what it cost to develop.
Libra
joined 1 month ago
No, what you did is come into a productive post with a fair amount of serious engagement--and no apparent confusion about what I meant from anyone else--with an attitude and a snarky comment. I tried in my response to ignore that and sincerely engage with your question and you decided to double-down. So I'm gonna take that as a solid 'yes' re:dead-set on being an ass and go do something more productive with my time. Have a lovely day.
...weird. I don't understand why drop-down terminals are a thing? I can bring up Konsole with a hotkey too, only it just opens a window instead fo doing a fancy animation. That's such a tiny part of its functionality that I can't imagine how 'drop-down' became a descriptor for a terminal instead of just a bullet point on a feature list somewhere, much less a whole-ass category of terminals, lol.
But, fair enough.
Yeah I'm kinda getting that impression. Most of the responses to this post have generally been 'use what your DE ships with' or 'I use something obscure and tailored to this weird specific use case I have'. I've looked at a lot of the suggestions people have given and none of them seem like they would be a noticeable upgrade for me, so I'm content to continue using konsole until I come across a situation that requires me to do something fancy that it can't do.
The full error for anyone having issues with the screenshot is: Installation Failed Bootloader installation error The bootloader could not be installed. The installationc ommand grub2-install -target=i386-pc -recheck -force /dev/nvme0n1 returned error code 1.
Context: I've had a hell of a rough time trying to install linux on my system, I've tried Pop, 2 versions of Ubuntu, Mint, and now I'm trying Nobara, and it's the first one that failed to install (I've mostly had video driver issues with the others.) My current disk situation is kind of a mess, I have 4 in the system:
- ~15 year old OCZ SATA 128GB SSD (windows/boot)
- ~10 year old WD SATA 512GB SSD (windows libraries like pictures, documents, downloads, etc)
- ~6 month old Samsung 990 EVO 2TB M.2 NVMe SSD (games installed from windows)
- ~5 year old BPXPro 1TB M.2 NVMe SSD (previous Ubuntu install that I had other issues with)
#1 is my boot drive and has the bootloader on it (when I want to boot ubuntu I hit F11 and select the second entry for that drive in the menu.) Previous distro installs have had no problem installing right over top of that and disk #4, but for whatever reason Nobara has failed to install the boot loader and I have no idea how to even begin to resolve this. I've done some searching and only found results with similar situations that aren't quite the same, it seems this is commonly an issue with linux installs into partitions of a drive that is shared with windows, but that's not what I'm doing (at least not for the main install, I guess that is kind of what it's doing with the bootloader?)
I can manually erase disk #4 if that would help, but is there some way I can manually go in and clear out the old bootloader (without messing up the windows install/boot)?
Other specs in case it's relevant:
- Ryzen 7 3800X 3.9GHz 8-core CPU
- 32GB DDR4-3200 RAM
- Gigabite Vision OC 12 RTX3060 GPU
view more: next ›
But there would still be a genocide going on with your tacit support, so if you can enjoy brunch while your tax dollars are murdering children then I guess we just have different standards.