- User Since
- Mar 20 2019, 12:44 PM (22 w, 4 d)
Fri, Aug 23
Just to put this out there, the Debian packaging is super behind (Standards-Version 3.9.7, debhelper 9) so the maintainer hasn't really been maintaining it. There's a FTCBFS with a patch from 2017 that hasn't been touched. There's also been some discussion about using the new fork with some options mentioned.
Thu, Aug 22
@tsimonq2 looks like waiting on upstream might take a long while. Maybe we should just implement this (as individual patches) and drop patches as needed as upstream makes developments?
So here's what we should probably have as required information for testing results:
- from lspci -nnk
- PCI ID of graphics card
- name of graphics card
- kernel module being used
- with ps -o rss -C compton | numfmt --header --field=1 --to=iec --padding=5, run under the same conditions and after the same amount of time elapsed since starting compton
- with old compton
- with new (PPA) compton
- The tests should be run under the following conditions
- with several windows open
- the same configuration, preferably with lots of opacity and transparency and shadows
- additional checks
- try youtube videos in full screen
- anything else graphic intensive: games, etc.
Wed, Aug 21
Thanks for working so hard on this.
@tsimonq2 you ok with this?
The good news: we've got the lxqt-globalkeys patch in proposed.
Tue, Aug 20
ps aux might be more helpful.
Closed per @hmollercl.
You can always close it then @hmollercl but I'll do it for you :)
A few problems:
- In that last change, you killed most of the changelog.
- Don't you want to use your lubuntu.me email?
- You need to update the changelog date. dch -r "" should do the trick.
I am so glad you discovered this mechanism. You sure you don't want to use your lubuntu.me address though?!
Also can't make any sense out of your notes.
@bjlockie thanks, though one thing that would be nice is a comparison to the old compton. Does one use more or less resources?
In case it wasn't obvious, I believe I have a solution that will make the lxqt-globalkeys patches work. If people could use the above PPA to test (see here for a testcase), that would be great. This is very important because if we don't have some sort of solution here, we won't be able to include our own Lubuntu-specific changes to the lxqt-globalkeys config, which means we won't really be able to do anything with the shortcuts. Raman's put a lot of hard work here that I would not like to see go to waste, nor would I like to make some rash decisions before release to deal with the fact that the Super key conflicts. So please go test!!!
Mon, Aug 19
Please drop the shebang on the desktop and then you won't need to override unusual-interpreter or script-not-executable though I still advise removing chmod +x lubuntu/*.desktop from the root Makefile. Also it looks like it's executable. You can undo that.
+1 on those automirror changes. I recognize we're still waiting on Lintian fixes.
Sun, Aug 18
LGTM. I didn't pine over every single key, but I assume you have. Land, upload, and tag away. We'll shake it out when we've got a new ISO.
I've looked for bugs as far as upstream related to NotShowIn and I can't find anything. I've pinged #ubuntu-flavors to see if they have problems as well.
Strangely xdg-desktop-menu forceupdate isn't really behaving nice, but a log out and back in does the trick. I can change various attributes but that indeed seems to have no effect.
No, that's not it. $XDG_CURRENT_DESKTOP is LXQt as it should be.
Bounced. Keep an eye on it.
@kc2bez what's the word here?
No movement on this, so I'm kicking it.
This is a good idea, but it's not something we can adequately control yet. All settings are specific to a particular device. There's no way to refer to pointing devices in general. There is some discussion about ways to implement this but it's uncertain.
OK doing that overwrite with the changelog was a bad idea. You need to restore the changes you dropped.
Sat, Aug 17
So I took the packaging for the current compton and tweaked it for the new one. I was freaked they use meson to build but it seems dh is all good with that. They do have a test.h submodule that's part of the build process that is going to included in the next release, due no later than next week. It was serendipity that while trying to figure that out, I noticed that in that same issue, someone had mentioned all the Ubuntu depends. So I trashed the old ones and used the new ones. I also dropped all the old patches. The only patch is the one for test.h.
Yeah you should be on ubuntu/eoan. This is why we use --nobranch with arc patch because otherwise it makes an arcpatch-Dn branch. I tried to pull down a new copy of the repo and the arc patch failed. So somehow your changes are based upon a local copy that is inconsistent with the remote copy. You might want to copy your xml file and debian/changelog, get a fresh repo, overwrite those files, and then arc diff --update D17.