https://bugs.kde.org/show_bug.cgi?id=383219
GizmoChicken <gizmochic...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|UPSTREAM |WAITINGFORINFO
--- Comment #4 from GizmoChicken <gizmochic...@gmail.com> ---
“The version [of the installer] used by neon and Kubuntu [has] a different
frontend on the same backend...”
Yes, I came that realization after my initial posting here. Indeed, as I
posted in Comment 17 for Bug #1510731 on Launchpad, “this bug may be in the
ubiquity-frontend-kde package,” and NOT in the “ubiquity” package itself. See
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1510731/comments/17
I updated the bug summary for this report so that it no longer refers to
ubiquity.
As I mentioned elsewhere, this bug does NOT affect Ubuntu 17.10, Ubuntu MATE
17.10, Ubuntu Budgie 17.10, or in any of the flavors that use the
“ubiquity-frontend-gtk” package. Rather, it seems to affect only KDE neon,
Kubuntu, and Lubuntu Next (Qt-based), all of which use the
ubiquity-frontend-kde package.
So it would seem that the bug resides, at least in part, in the
“ubiquity-frontend-kde” package, which I presume is maintained by KDE.
As I also mentioned in Comment 17 for Bug #1510731 on Launchpad,
“[u]nfortunately, the ubiquity-frontend-kde package doesn't seem to have its
own bug submission page, but instead relies on bug reports submitted [on
Launchpad], for ubiquity. See
https://packages.ubuntu.com/artful/ubiquity-frontend-kde ”
QUESTIONS:
If, as I presume, the “ubiquity-frontend-kde” package is indeed maintained by
KDE, where is the appropriate place to submit a bug report for that package?
Here? Somewhere else on the KDE bug reporting system? Somewhere else on
Launchpad?
ADDITIONAL COMMENTS:
I acknowledge that KDE’s frontend is more visually appealing than the frontend
used by the gtk-based Ubuntu flavors, including Ubuntu 17.10, Ubuntu MATE
17.10, and Ubuntu Budgie 17.10. But unfortunately, the changed frontend seems
to result in at least one major regression in the overall installation process,
namely an inability to create LUKS encrypted volumes during manual disk setup.
Looking at Bug #1510731 on Launchpad, this bug seems to have existed in Kubuntu
since Kubuntu 15.10, and probably longer. When I first noticed the bug, I was
happily using Unity, and so the bug, while interesting, didn’t really affect
me.
Now, I’m considering switching from vanilla Ubuntu to another Ubuntu flavor, or
perhaps to another distribution. If the neon/Kubuntu installer would allow me
to easily create LUKS encrypted volumes during manual disk setup, KDE neon and
Kubuntu would be my top contenders. In fact, I even created (but haven’t yet
published) a short video that demonstrates a little-known feature in KDE Plasma
that would be very attractive to my fellow Unity refugees.
But without an ability to easily create LUKS encrypted volumes during manual
disk setup, I’ll have to look elsewhere.
If, as I presume, the “ubiquity-frontend-kde” package is indeed maintained by
KDE, then I’m not sure whether its development should be considered “upstream”
of, or “parallel” to, the development of KDE neon and Kubuntu. But even if the
KDE neon and Kubuntu devs consider the “ubiquity-frontend-kde” package to be
“upstream” of their respective projects, the mere use of the
“ubiquity-frontend-kde” package (which has regressions compared to the
“ubiquity-frontend-gtk” package) in place of the “ubiquity-frontend-gtk”
package could, in-and-of-itself, be considered a bug. So with that in mind, I
hope that the neon/Kubuntu devs will either: (a) insure that the
“ubiquity-frontend-kde” package is fixed upstream (or wherever); or (b) revert
to the “ubiquity-frontend-gtk” package, which, although less visually
appealing, at least works without regressions.
--
You are receiving this mail because:
You are watching all bug changes.
