Conversation:
Notices
-
Today's all about #convenience, apparently: now I'm brute-forcing my way through discovery of the hundreds of packages I need to install before I can get the `convenient' Qt installer to run without segfaulting.
-
Oh, there we go--apparently the Qt installer needs DBus....
-
Everything needs dbus and pulseaudio and systemd these days. It's a trap I say!
-
@rozzin Today I went through a forum's thread on plasma 5.6 and opensuse. Spanning over three pages the participants were trying to de-puzzle version numbers of KDE Frameworks, Plasma, Qt and KDE Apps. Horribly convenient.
-
Now... why to people think it makes any sense whatsoever to present the #GPL as a #EULA? What part of "You are not required to accept this License in order to receive or run a copy of the Program" do these people not understand? That's the text *in the `agreement'* following the "You must accept the terms contained in this agreement before continuing with the installation" header.
-
@rozzin IME, they're mostly people who don't actually modify the generic install packages they use to be sensible in this regard. It's still a requirement usually to present the GPL which they are trying to do.
-
Progress: finished install, QT Creator fails after “Warning: QXcbWindow: Unhandled client message: "_GTK_LOAD_ICONTHEMES"”. Wait..., *what*?
-
Oh, no..., the error is actually “This application failed to start because it could not find or load the Qt platform plugin "xcb" [...] Reinstalling the application may fix this problem”. Somehow I suspect reinstalling is not the answer....
-
@vinzv @rozzin and i just found out that KDE nor GNOME isnt for me. ;-)
-
@brantarik Heh! I was a long-term Gnome and Xfce user. And Openbox of course.
Since Plasma5 I'm quite happy with KDE.
-
@brantarik, I'm really being (slightly) deliberately stupid here, esp re: the `how come Qt needs GTK+!?' thing. I remember the #badolddays when GTK+ and Qt didn't co-exist well at all--and then it was quite nice when they started being able to use each other's back-end engines. It was surprising to see what *looked* like a refusal of one to run without the other, though.
-
And TBH a big part of my problem is my being way more #paranoid than I needed to be—trying to bootstrap my Qt dev env in a minimal #chroot…
-
The #Qt installer appears to be much better-behaved than I expected; I'm too used to installers like this shitting all over the host system.