- User Since
- Mar 13 2020, 9:44 PM (27 w, 2 d)
Sat, Sep 19
I volunteer as maintainer.
Thu, Sep 17
Jul 26 2020
@DataDrake I checked ~/.xsession-errors after the failure, and it was empty. I did reinstall slick-greeter though and the system booted to the greeter session as normal. I probably uninstalled slick-greeter by accident when I replaced LightDM with gdm during my Gnome experimentation on Solus. Thanks for your help
Jul 25 2020
@DataDrake here is the log from /var/log/lightdm
Jul 24 2020
Jul 23 2020
Jun 25 2020
May 22 2020
add a MAINTAINERS.md file
May 18 2020
fix license and packager name
May 15 2020
Latest release is now 0.6.1.
May 8 2020
move description to correct place. thanks @algent.
update to latest upstream release
May 2 2020
thanks @algent, will update the diff soon :)
Apr 23 2020
Apr 17 2020
update test plan
Apr 13 2020
Apr 11 2020
Apr 8 2020
Maybe this could be used to help? I've experienced this same bug and using these config files usually help.
Apr 3 2020
I know this is a little unconventional, but I just built an eopkg that installs that .deb package onto the system. You can download both the package.yml (if you want to build/install the package yourself) and/or the .eopkg (for a simple install on your system) here. Let me know if you have any installation issues, or if it even works, as I don't have an Epson printer myself lol. Hope I can help!
I love Joplin as well, but just download the appimage for now (or file a request on github for snap/flatpak support). This has also already been said by one of the lead devs:
I'll be honest, I don't really know how to use pushd commands, and even after reading manpages and articles I couldn't really understand it. I cut the install commands by half though by using the -t operand. Hope it works
Apr 2 2020
forgot to add manpages :/
added shell completions
Apr 1 2020
@dr03m I keep running into an error about missing libraries, and no matter how much I try to change pkgconfigs, pkgs, etc, I continue to get cmake errors. Sorry man, I tried lol
@dr03m instead of editing the comment, I deleted it :/
update to new upstream relese
Mar 27 2020
@kyrios123 alright I understand now. Thanks for your response!
Mar 26 2020
@DataDrake I'm not sure if I understand you correctly. Mesa has to incorporate changes from upstream vulkan? If so, I see what you mean about rebasing on a standard release being pointless. However, couldn't a more up-to-date vulkan-loader lib still increase performance along with mesa, or allow for more to date features (such as ray tracing, since it was introduced in 1.2.135)? Or could mesa use the newly introduced features from updated spec with an outdated vulkan-loader SDK?
@JoshStrobl I understand leaving this to the core team, but why base the release off of the SDK? According to the upstream github releases, SDK releases are very scattered and do not release for every version, and in turn, do not give users performance improvements such as those mentioned in T8849 for a while. Wouldn't it be better to release the SDK as a vulkan-devel package and rebase the vulkan package on the standard release in order to give end users performance improvements faster? Just kinda wondering 🤔
rebuilt against master branch.
GNOME Control Center's "Color" and "Removable Devices" options worked perfectly.
Mar 25 2020
@DataDrake I updated the summary per your request.
Revised .yml according to DataDrake's comments
Mar 24 2020
@DataDrake updated the .yml to have the tarball as the source
change source from binary to tarball
Okay, I completely understand. I'm working on a new .yml build with rust now :)
@EbonJaeger @Jacalz The repository is actually mine on github. The binary comes from official site here. All I did was create a makefile for the binary and create a repo for both on github in order to make it easier to package for multiple distros. If that is against any rules though, I was unaware, and I will work on a .yml based off the upstream tarball until we get word from the devs.
@algent updated :)
add resolution to summary
@DataDrake It should have been built with the correct python version this time. Let me know if I am mistaken. I also updated the summary with the upstream change log.
Update to 4.2.0, fixes T8841
@DataDrake I volunteer as a maintainer. I have a successfully built package with the accompanying package.yml and pspec files. I'm not sure how to use arcanist though. Do I make a git repository and upload it via arc diff, or do you guys make a repository on here and I clone it and use arc diff then?
Just made a revision here