Totally forgot about this!!! Can you send me an SVG @Guephren and I'll get this implemented? I do agree with @JyotiGomes (as much as I appreciate his sketch!) that yours is a little better. For one, the white/winter coat is historically more associated with the ermine. There's a heraldry pattern called ermine that is white not brown. Also, the tail is totally essential.
- default hacks
Fri, Sep 13
Mon, Sep 9
@kc2bez what do you think about using one of the stock ones versus making something ourselves?
Regarding the path, using apt-file search, it seems that the XScreenSaver* files are provided by xscreensaver packages, so those are out. These are overwritten in Ubuntu Studio and Xubuntu's default settings packages via providing .xscreensaver in /etc/skel. The problem with this is anyone upgrading will not have the changes. Maybe we could postinst the installation for old users? Any other ideas?
Sun, Sep 8
Nice catch. To be fair, there's a lot of url and error variables thrown around that aren't the same and this makes the code really unreadable and unmaintainable. If you wanted to go ahead and fix that, using, e.g. httperror instead of error for the HTTPError exception, that would be an added plus.
Another idea (I'm full of them): we make our own hack for xscreensaver.
Maybe we should just pick one as the default rather than using random?
Sat, Sep 7
So I should have said this before but I really don't like popsquares or slidescreen and fuzzy flakes is not a big favorite, either. Someone please overrule me, but I'd really like us to not include those. Since @tsimonq2 is the op here, maybe he can chime in?
- Please add the Last-Update field with today's date.
- You added the T117 reference in the commit message, but not in the differential revision. When you're ready to submit changes, just do arc diff --edit and change the summary section so that it includes "resolves T117."
- Picky (but potentially something that would render it non-compliant, depending on how smart validation tools are): add a space after the colon before the URI in Applied-Upstream.
- Your choice: If it were me, I'd probably get rid of lines 5-7 as they're not required parts of the diff at all.
You need to edit the patch to be DEP3 compliant, as seen in the packaging example. Also might want to edit the description to say it "resolves T117," which can be done, I think, via the --edit switch to arc diff.
Fri, Sep 6
Thu, Sep 5
Wed, Sep 4
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.