LogoopenSUSE Build Service > Projects
Sign Up | Log In

plasma5-workspace

No description set

Source Files (show merged sources derived from linked package)

Filename Size Changed Actions
0001-Add-suffix-to-the-wayland-session-s-name.patch 1.7 KB 7 months ago Download File
0001-Ignore-default-sddm-face-icons.patch 1.04 KB about 2 years ago Download File
0001-Rename-qdbus-in-startkde.patch 5.26 KB 3 months ago Download File
0001-Revert-No-icons-on-the-desktop-by-default.patch 4.64 KB 8 months ago Download File
0001-Set-GTK_BACKEND-x11-in-a-wayland-session.patch 980 Bytes 7 months ago Download File
0001-Set-XDG_SESSION_TYPE-wayland-in-startplasmacomposito.patch 965 Bytes 7 months ago Download File
baselibs.conf 24 Bytes about 4 years ago Download File
lazy-sddm-theme.patch 1.27 KB 6 months ago Download File
plasma-workspace-5.14.0.tar.xz 4.35 MB 11 days ago
plasma-workspace-5.14.0.tar.xz.sig 488 Bytes 11 days ago Download File
plasma.keyring 35.7 KB about 1 month ago Download File
plasma5-workspace.changes 79 KB 11 days ago Download File
plasma5-workspace.spec 19.7 KB 10 days ago Download File

Comments for home:wolfi323:branches:KDE:Frameworks5 (10)

akilgus wrote over 1 year ago

Hi Wolfgang,

upstream removed the functionality to let konqueror show the favicon of the currrently displayed website in the taskbar instead of its application icon. This renders my taskbar almost useless in most of (not only) my usecases. There's a patch known to bring back this functionality - that upstream refuses to apply. AFAIK the package I comment is the package the patch is aimed for.

http://linux.overshoot.tv/wiki/konqueror_taskbar_icon https://bugs.kde.org/show_bug.cgi?id=369658

Since I assume that you don't like the idea of patching your package "against upstreams will" (and I can understand that), I'm thinking about a package of my own with this patch applied. Ideally located in build service in my own home directory (to create then) and based on your package, so I can technically stand on your shoulders (g) and get patched updates without manual intervention. Before I start digging in build service docs: Can something like that work using build service? You update your package, my build directory clones your update, applies the patch, builds my package, this package reaches me using zypper?

Best Andi

wolfi323 wrote over 1 year ago

> Since I assume that you don't like the idea of patching your package "against upstreams will" (and I can understand that) Well, I'm not strictly opposed to that, this is my personal home repo after all... ;-) I do have some patches that are clearly "against upstreams will", but are necessary to have KDE4 and Plasma5 coexist in the first place.

I'm not sure about this particular one though. It apparently changes the behavior, and one of the goals of this repo was (and is) to follow the upstream development (I also use it to test or investigate reported bugs). It also means I have to maintain the patch and adapt it to new Plasma versions. It may even change things for other applications as I understand it.

So I'm probably not going to add it, I think...

> I'm thinking about a package of my own with this patch applied. Ideally located in build service in my own home directory (to create then) and based on your package, so I can technically stand on your shoulders (g) and get patched updates without manual intervention. Before I start digging in build service docs: Can something like that work using build service? You update your package, my build directory clones your update, applies the patch, builds my package, this package reaches me using zypper?

Yes that's possible, and quite easy even. (actually that's how I "maintain" all the KF5/Plasma5 packages here... ;-) )

Just click on "Branch Package", this will create a linked copy in your home repo (actually in a sub repo named "home:xxx:branches:...". You can make your own changes there, and changes in the original will "dripple" through too.

Alternatively, you can click on "Branch a package" in your home repo and type in the repo and package you want to branch from.

Be aware that there may be conflicts though if the original changes that OBS cannot manage to resolve itself, your package will be in state "broken" then. I have no idea how much knowledge you have about OBS, but feel free to ask me if you encounter such problems.

akilgus wrote over 1 year ago

Thanks for your answer and the explanations. I must have missed the corresponding info e-mail normally sent - I just got to see your comment by chance right now.

Anyway, this all sounds quite better and probably easier to manage than expected. Which is very good news - as my knowledge about the build service other than using it for getting software not found in the official repos is an euphemistic zero at the time being. :-)

Some time this week I'm going to try to follow your instructions above. I'm curious how far I'm going to get. :-)

... all these circumstances for that "much" of a patch:


diff --git a/libtaskmanager/xwindowtasksmodel.cpp b/libtaskmanager/xwindowtasksmodel.cpp index ad0bdf6..e18d573 100644 --- a/libtaskmanager/xwindowtasksmodel.cpp +++ b/libtaskmanager/xwindowtasksmodel.cpp @@ -458,12 +458,6 @@ AppData XWindowTasksModel::Private::appData(WId window)

QIcon XWindowTasksModel::Private::icon(WId window) {

- const AppData &app = appData(window);

  • if (!app.icon.isNull()) {
  • return app.icon;

- }

QIcon icon;

icon.addPixmap(KWindowSystem::icon(window, KIconLoader::SizeSmall, KIconLoader::SizeSmall, false));

A simple configuration option ("display favicons in taskbar" - yes/no) would have made both sides smile ... sigh

akilgus wrote over 1 year ago

OK, posting code seems to get partly misinterpreted as markup. Here's the patch, if you're interested:: https://bugsfiles.kde.org/attachment.cgi?id=103788

wolfi323 wrote over 1 year ago

Yes, I am aware of the patch. My reply was based on looking at that too... (and the upstream reactions of course)

And yes, the webinterface seems to mess up things sometimes, my reply to you too... ;-(

akilgus wrote over 1 year ago

Successfully branched your package - favicons have returned. :-) Maybe I additionally branch LTS and the official 42.2 repo adding the patch so others not using your repo (or a possible future me using LTS) can have back favicons, too.

But in the not so long term I am that much annoyed by the ease my workflow once again gets significantly broken (and not for the first time just because of "by design", concerning KDE) that I am looking for an alternative. Either I am going to try to write a taskbar replacement of my own (though I am not that keen on tying me even stronger to KDE and I am new to the API) or I am going to try to implement some as far as possible DE-independent session-within-a-session concept I am using Plasma's activities for at the moment to be able to switch to e.g. XFCE.

Anyway - thanks for your help.

akilgus wrote over 1 year ago

Is there a way to build the packages so they are available for interested users, but let the packages not be listed/found via http://software.opensuse.org/package/plasma5-workspace - since the only difference for all repositories I branched is the favicon patch?

wolfi323 wrote over 1 year ago

Sorry for the late reply. But no, I don't think there is a way unfortunately.

akilgus wrote over 1 year ago

Never mind and thanks. FTR: I branched plasma5-workspace of 42.2-Update, Frameworks5 and Frameworks5-LTS. I deleted my branch of your repo at the moment the source of your branch switched to beta versions, I will delete my branch of Frameworks5, since this repo switched recently to supply beta packages, too. Without any info on https://de.opensuse.org/KDE_Repositorys and https://en.opensuse.org/SDB:KDE_repositories. At the moment there seem to be no repos available that supply the current stable releases of Plasma5, KF5 and Applications for Leap - correct?

wolfi323 wrote over 1 year ago

Correct, except that KF5 and Applications are the latest stable releases in KDE:Applications and KDE:Frameworks5. Plasma currently is the latest beta release in KDE:Frameworks5.

But 5.10.0 is going to be released in less than two weeks already.

Login required, please login or signup in order to comment