Some 15.04 annoyances...

[mr_raider]

It seems to me btrfs creates added complexity you don't want.

That's exactly the complexity I want. It allows me to install multiple OSes to the same partition.

[xennex81]

What is that good for? A LVM even allows you to install multiple OSes in the same partition without requiring a dedicated filesystem to do it.

There is nothing easier than LVM LV creation and it does not really add to complexity (except that there are no visualization tools).

It's the Git kinda complexity that gives headaches.

[vtpoet]

My annoyance for today: Apps not remembering my Activities preferences.

[SteveRiley]

It seems to me btrfs creates added complexity you don't want.

Recycling electrons: https://www.kubuntuforums.net/showthread.php?68088

Btrfs has oodles of advantages over other file systems. Note particularly Oshun's examples in his post #24 in that thread.

[mr_raider]

Ok. Figured it out. The /var/lib/machines subvolume seems critical. Don't touch it! Just rename @, @home and edit fstab to the new names. Then modify all isntances of @ in /boot/grub/grub.cfg

[timgood]

Another annoyance with Kate: does not show recently used files once Kate has been closed and re-opened. File/Open Recent is greyed out. Always.

[SteveRiley]

Another annoyance with Kate: does not show recently used files once Kate has been closed and re-opened. File/Open Recent is greyed out. Always.

That information is stored in ~/.local/share/kate/metainfos. Does that file exist, and does your user account have read/write access to the file?

[claydoh]

That information is stored in ~/.local/share/kate/metainfos. Does that file exist, and does your user account have read/write access to the file?

I think they are actually in ~/.local/share/RecentDocuments/, and the metainfos contain file-specific settings. I cleared my recents in Kate, and the .desktop files relating to the recent files in my list were removed from there, but not from metainfos.

I was thinking of file or directory permissions problems involving RecentDocuments

[SteveRiley]

I think they are actually in ~/.local/share/RecentDocuments/, and the metainfos contain file-specific settings. I cleared my recents in Kate, and the .desktop files relating to the recent files in my list were removed from there, but not from metainfos.

Hm. My ~/.local/share/RecentDocuments is empty (*). Each time I open a file in Kate, information about that document is added to metainfos (and also to anonymous.katesession). I wonder if this one of the many under-the-covers changes in Plasma / Frameworks 5?

I was thinking of file or directory permissions problems involving RecentDocuments

I was thinking the same, but for ~/.local/share/kate/.

(*) This is a new install, not an upgrade from 14.10

[claydoh]

Actually, RecentDocuments is for things like krunnner and the kmenu's recents. (and they are not removed when clearing kate's recent docs list), so I am in error there.
Clearing the recents in Kate does not seem to remove anything from metainfos or anonymous.katesession.

Seems to be the same on my fresh install, and my upgraded-since-raring install.


Oops, I forget that these things are not saved back to config files until program exit, silly me!


anonymous.katesession has the [Recent Files] section way at the bottom, so this is the one to look at.

[SteveRiley]

anonymous.katesession has the [Recent Files] section way at the bottom, so this is the one to look at.

Good find. I actually didn't look closely enough at that file. The word "anonymous" in the name made me think it wasn't all that relevant, heh.

[timgood]

1. Kate: sudo chown -R $user .local/share/kate does the trick. Again, I think editing fstab using sudo rather than kdesudo changed the permissions in that directory.
2. Muon Update Manager - notification icon does not update after updates have been installed. Sits in tray, looking pretty, and saying that updates are available even though they are not. Can only be fixed by logout/login.

[ronw]

2. Muon Update Manager - notification icon does not update after updates have been installed. Sits in tray, looking pretty, and saying that updates are available even though they are not. Can only be fixed by logout/login.

Same here, starting a couple of days ago. In addition to not hiding, if it goes red, it stays red even after you update. Sufficiently annoying that I just purged all the notification stuff.

[SteveRiley]

1. Kate: sudo chown -R $user .local/share/kate does the trick. Again, I think editing fstab using sudo rather than kdesudo changed the permissions in that directory.

Yes. Running graphical applications under sudo will often cause such problems.

[xennex81]

Recycling electrons: https://www.kubuntuforums.net/showthread.php?68088

Btrfs has oodles of advantages over other file systems. Note particularly Oshun's examples in his post #24 in that thread.

The problem is that it puts certain features in the wrong place. Most of these things are not meant for the filesystem to do.

You can see it because now to do these things, you are suddenly dependent on learning that specific filesystem's way of doing it. It is no longer a component that stands loose, that is separate from the filesystem layer. So it's like Microsoft selling windows with Explorer (Internet Explorer). You can't (couldn't get) explorer without Windows, and you can get Windows without Explorer. Not sure how to frame it.

You lose differentation into layers and the independence that results from it. Now suddenly in order to do backups you must do BTRFS. And how compatible is it going to be if some deviate form of that surfaces? You are putting all kinds of features into that FS and tying it to that FS. And you lack or lose the freedom to go elsewhere.

Rollback:
Auto-snapshot prior to package install/update.
Delete auto-snapshots at a configurable number or age.
Restore the rollback snapshot when requested.

Backup:
Incremental auto-backup at a configurable interval.
Restore backup on request.

The fun thing I'm playing with lately is the send/receive feature. You can send a subvolume to a different device or to a file for backup purposes.

Only the latter seems to be somewhat a part of what a filesystem could do. But now the filesystem is also taking the role of the volume manager.

I don't fancy this ****. You are going the wrong way. Added complexity, added dependence, trying to solve a problem in a place where it shouldn't be solved. Etc. Perhaps this is meant as one of those "let's agree to disagree" instances ;-).