On 2013-08-18 14:44:33 Scott Kitterman <[email protected]> wrote: > > Ummm. When 13.10 is released is "when new releases appear". People running > the development series have to expect stuff to change.
Anyone who installed the KDE 4.11 from backports has also seen this change. For example, it is on my 13.04 laptop where I noticed the change and also implemented the udev rule to restore prior behavior. Some more data... * Arch: KDE is 4.10.5. Only udisks2 is packaged, not udisks. Mounted USB drives appear at /run/media/$USER * OpenSUSE Tumbleweed: KDE is 4.10.5. Only udisks2 is packaged, not udisks. Mounted USB drives appear at /run/media/$USER So, both Arch and Tumbleweed exhibit the newer upstream behavior, have done so for a while, and because they package only udisks2, not udisks. Furthermore, they retain the full change, mounting under /run/media/$USER. Ubuntu, OTOH, patched theirs so that that mounts occur under /media/$USER. (Why? Who the hell knows.) We exhibited the older behavior because we package udisks and our libsolid4 used that, until 4.11. Now, users of 12.04, 12.10, and 13.04 who upgrade KDE to 4.11 experience a confusing change that will break customized /etc/fstab among other surprises. I'm not suggesting we permanently revert to prior behavior; the trend is clear. I'm proposing that we add the udev rule to 12.04, 12.10, and 13.04 so that something as routine as a desktop version upgrade doesn't introduce fundamentally altered behavior. Should I really have to edit /etc/fstab because I upgraded my KDE? ...Steve -- kubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
