So, i'm having trouble with creating/editing bundles...Krita seems to ignore what i chose to save, and picks only a random portion of it to do so. The end result is a bundle with very little brushes, presets, workspaces...sometimes a few of them, sometimes not at all. This happens for both creating a new one or editing an existing one (this in particular tends to crash krita)

this is not new to 4.0, had the same issue with 3.x.

Linux mint 18.2
amd phenon2 6cores
geforce 1060 6Gb -with nvidia drivers
16Gb ram
krita 4 appimage

Just to confirm same issues on Mint Mate 18.3 (and with various Krita 3/4 releases), using appimages. Follow instructions to the letter, making sure all 3 parts needed are included (brush tips, patterns, and paintoppresets), but Krita says it can't load the bundle.

@kitsune09 - I think that is a confusion within Krita because I've tried that and the bundle is created as an active resource before it is Saved in the filesystem. If I then try to load it, Krita says the bundle doesn't exist, even though it's at the location I saved it to and Krita sees it on its internal file explorer. (There's actually no point in loading a bundle that is already active in Krita.) The internal logic of this may need looking at.

If I close Krita then delete the bundle from the bundles folder, then restart Krita, I can load the bundle with no problem. Have you tried that?

jeebsas seems to have a different and much worse problem.

I thought I had caught most of the bugs in the bundle creation process when deevad was bundling the 4.0 presets bundle... Please make a bug report with a detailed set of steps so I can try to reproduce.

I've made a bug report: https://bugs.kde.org/show_bug.cgi?id=392195

This is only for the 'logical/presentation' problem which I've seen myself and described above, which I've classed as minor.

Would you like me to make a bug report for the problem as reported by jeebsas in the original post?

I'd prefer it if jeebsas did that, so there isn't an intermediary

thank you kindly.
there is a minor feedback/behavior with the interface too...it toggles the highlight when selecting a bundle...not highlighting the selected one as i imagine is the intended visual feedback...so it is possible to have everything highlighted but the selected one is not.
Should i make a second bug report for this?

No, we don't control what highlights mean in list widgets.

ok, done!
https://bugs.kde.org/show_bug.cgi?id=392204