- User Since
- Jan 4 2018, 10:00 AM (58 w, 1 d)
Fri, Feb 1
Thu, Jan 31
Tested on my Nvidia GTX 1050 Ti as by joebonrichie's instructions. Hardware acceleration seems to work fine with this update in VLC (~3% CPU utilization with hardware decoding, ~8-10% without in the video I tested).
Wed, Jan 30
Mon, Jan 28
Sun, Jan 20
Weird, works fine on my fresh Solus Unstable VM, my Solus Unstable PC, and my Solus Stable laptop. Also that check should be gone since version 2.1.6 (see this commit: https://github.com/dae/anki/commit/3cb073878a13079185be8fde9f70401da297bbdf) (the version that allowed initial inclusion into the Solus repo). Could you try a reinstall of anki perhaps? Not sure what is happening here.
I'll take a look, since it worked fine on my PC.
Jan 6 2019
Jan 3 2019
Dec 26 2018
Dec 25 2018
Probably should've kept the other stuff from the newer commit. I could do this later, have to go now.
Reverting the latest python-rope update makes Spyder3 launch again.
Oh yeah, I'm getting the same error. Investigating...
Dec 20 2018
Dec 18 2018
Update to 415.23
Nevermind, 415.25 has been released, will update soon
Dec 17 2018
Dec 16 2018
Dec 12 2018
@108saimon I just removed and re-installed Chrome from the Software Center without a problem. Could you try it again? Maybe you just got unlucky and ran into some sort of connection issue between you and the google download servers.
Installing Chrome works fine for me, and it's at the latest version for stable. A dev-channel update was released yesterday (after I already went to bed), which I will update to in a couple minutes.
Dec 11 2018
Dec 8 2018
Dec 7 2018
Fix builddeps order, fix PREFIX
Use single instead of doulbe quotes around version
Dec 4 2018
Dec 3 2018
Dec 2 2018
Rebase on current version
I can confirm this problem with the nvidia-developer-driver-current. Just tried it with the free game "b" and I get the exact same error message that is mentioned in the linked thread.
I've created a package for version 2.1.6-beta2. Works fine with current Qt now. I'm waiting for the stable release to create a diff.
Nov 20 2018
Rebase on current version
Actually update pspec.xml too
Nov 12 2018
Actually bump release number
Nov 11 2018
Nov 7 2018
Nov 5 2018
Fix package name and don't hardcode version in setup
@DataDrake Fine by me, I wasn't sure what to do here to be honest. I just thought calling it "OneDrive" would make it sound like an official Microsoft app, and took the name from the Task, which is also the header of the Readme.
Oct 28 2018
Oct 27 2018
The sed-stuff is because the original Makefile tries to get git version information, which obviously doesn't work with the tar.gz archive and is a bit silly for a release.
Sep 27 2018
Interesting, seems like either something is blocking your connection to the GitKraken servers, or their download servers were down. It shouldn't normally try to download from solus-project.com.
This is of course beside the point of the Software Center completely locking up.
Sep 22 2018
Thank you for the input, kyrios123. I've changed everything accordingly; totally forgot about using python3, even though I did so with another package I built for myself.
Use python3, order licenses alphabetically and only mention licenses once
Thank you again for the review. I don't mind the delay, since I know you've been busy (and m64py isn't, and shouldn't, be too high on the Solus priority list ^^).
Restructure licenses part again, according to Josh's suggestions
Sep 1 2018
Thank you for the review! I changed everything as requested, though I am still unsure about the licenses part. Is it okay like this now, or if it is not, could you maybe point me to another example of a package with multiple licenses like this?
Orderd deps alphabetically, removed unused setup part, added additional licenses
Aug 30 2018
Remove unnecessary builddep
Aug 29 2018
Aug 28 2018
Actually, forget what I was saying, it works perfectly fine on my end now. Not sure what the problem was before. I'll submit something soon.
Aug 26 2018
I will try to find that out and report back.
So, I've created a package locally, but I have one question: As it stands, it doesn't auto-detect the mupen64plus library and you have to manually locate it. Is this acceptable?
Jul 15 2018
Alright. Is the systemd update available on here already so I can maybe test it? (A quick search didn't show me anything, but then again I'm not used to working with phabricator)
Jul 13 2018
Mar 7 2018
No problem at all!
Okay, I just tested pcsx2. I found one minor issue and one small improvement over the old version. So overall a neutral result ^^ (actually in this case I would favour the new version)
Mar 6 2018
I just tried Dolphin-Emu and encountered several issues. I've created an album on imgur with screenshots and descriptions to show the problems:
Jan 4 2018
Whoops, sry, was in a hurry this morning and apparently didn't search thoroughly enough.