Clean it up ready for review
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 24 2022
Apr 23 2022
Should it be packaged in /opt/rocm as the official and Arch packages do, or in system directories like Fedora does? I tried going for the second approach but this mean getting rid of bundled ICD and moving headers to not conflict with other packages. And I am wondering if any of that will cause headaches in the future.
In my opinion all the packages are mostly done and ready to be reviewed, with the exception of rocm-opencl which I need help with testing.
I don't quite understand how to configure
-DROCM_PATH=%prefix% -DCMAKE_PREFIX_PATH="%workdir%/ROCclr-rocm-%version%;%prefix%" -DAMD_OPENCL_PATH="%workdir%/ROCm-OpenCL-Runtime-rocm-%version%"
If I should configure them to the build directories or the install directories. Could someone more experienced take a look and suggest something?
Apr 13 2022
Next [[ https://github.com/HansKristian-Work/vkd3d-proton/blob/master/README.md#amd-radv | vkd3d release will need at least Mesa 22.0 ]] but I think we have some time until that.
Apr 10 2022
There are 2 great projects that could help in a big way with building it on Solus: packages for Fedora and rocm-arch.
For now I spent a few hours basing my work on the Fedora package, and managed to build a small bit of necessary packages. I have encountered problems rocm-compilersupport that seem to be related to our LLVM, will try to work on it when I have time.
Just wanted to point out it might be a good chance to try with rocm once again.
Here are is my humble work: rocm-Solus.
Edit: I am getting an error:
[ 69%] Building CXX object CMakeFiles/amd_comgr.dir/src/comgr-symbolizer.cpp.o
/home/build/YPKG/root/rocm-compilersupport/build/ROCm-CompilerSupport-rocm-5.1.0/lib/comgr/src/comgr-compiler.cpp:484:16: error: no member named 'initSections' in 'llvm::MCStreamer'
Str.get()->initSections(Opts.NoExecStack, *STI);
~~~~~~~~~ ^
/home/build/YPKG/root/rocm-compilersupport/build/ROCm-CompilerSupport-rocm-5.1.0/lib/comgr/src/comgr-compiler.cpp:608:60: error: too many arguments to function call, expected 4, have 5
bool LLDRet = lld::elf::link(ArgRefs, LogS, LogE, false, false);
~~~~~~~~~~~~~~ ^~~~~
/usr/include/lld/Common/Driver.h:41:6: note: 'link' declared here
bool link(llvm::ArrayRef<const char *> args, bool canExitEarly,
^
/home/build/YPKG/root/rocm-compilersupport/build/ROCm-CompilerSupport-rocm-5.1.0/lib/comgr/src/comgr-compiler.cpp:609:8: error: no member named 'CommonLinkerContext' in namespace 'lld'
lld::CommonLinkerContext::destroy();
~~~~~^Arch needs to build rocm-llvm, Fedora does not, so I really hope I could get by without normal llvm
Apr 6 2022
Kind of similar to T10135, which is already uses default Firefox, but is harder to use.
Mar 22 2022
Could this issue be in any way related to this, which only affects 64-bit games? https://github.com/ValveSoftware/steam-for-linux/issues/5822
Mar 13 2022
This has been fixed with D13001
Mar 10 2022
Really sorry about time. I have packaged and have been testing it since the release date, but forgot to post a diff.
Replace mkdir with install
Mar 9 2022
Mar 2 2022
My suggestion is to update libcap2 package so /usr/sbin/getcap gets moved to /usr/bin/getcap or a simlink gets created in /usr/bin/.
Mar 1 2022
Feb 25 2022
Feb 17 2022
Feb 13 2022
Feb 6 2022
Rebase it on git head
Feb 5 2022
I would love to maintain it, as I am just getting into VR and need it for my setup. The progress has certainly slowed down, but it is still maintained, a lot of people are using it and it does support a lot of different hardware.
So I will be using it myself on Solus, it is your decision if you would accept it in the repos.
Feb 4 2022
Jan 31 2022
Jan 30 2022
Jan 27 2022
Fix license, NOCONFIGURE and static library
I am really sorry it took me so long to fix it, I am struggling with at my university and didn't have time.
Fix license, NOCONFIGURE and static library
Jan 23 2022
Dec 15 2021
Dec 5 2021
Nov 11 2021
Nov 7 2021
I uploaded D12236, it fixed all the issues for me. Hope I did it right
Oct 31 2021
I just noticed it is the same for /usr/share/defaults/etc/profile.d/70-flatpak.sh.
So solution for me is to have the following in /home/jacek/.config/fish/config.fish:
if status is-interactive
# Commands to run in interactive sessions can go here
end
for file in /etc/profile.d/*.sh
echo $file
replay source $file
end
replay source /usr/share/defaults/etc/profile.d/70-flatpak.shI have no idea how to solve it neatly for all users.
Oct 29 2021
Funny. I have been testing it on Plasma (unstable), it starts and video streaming works just fine.
So do you think the input might not work because I am on Plasma?
Also, I tried building it, but I get an error it can't unpack the xorg-server source. Do you get the same error as well?
Oct 28 2021
Oct 24 2021
There are 2 things I am not sure enough:
Oct 18 2021
Oct 9 2021
As for Prusa Slicer it should work just fine with GTK3 after adding -DSLIC3R_GTK=3. I could test it if needed.
Sep 15 2021
Replaced mkdir with install, as for IDOS' request
Sep 6 2021
Sep 5 2021
Remove one dependency, that is no longer needed
Aug 6 2021
Aug 1 2021
I think really soon this might no longer be needed, as latest version of Lutris will have integration for Epic, GOG and Humble Store: https://www.phoronix.com/scan.php?page=news_item&px=Lutris-0.5.9-Beta
Jul 31 2021
I don't know if I should resurrect this issue, or create a new one, but I this issue hasn't been fixed. My Synaptics touchpad work fine on Budgie for years. I just did a fresh install of Solus 4.3 Plasma, and some Touchpad options have been greyed out, including tap to click, which I think is mandatory for good experience.
And what was needed to fix it was to install xorg-driver-input-synaptics.
So the same problem and the same solution as in this original issue. Do you think that driver should be included by default, or would that cause a problem?
Jul 23 2021
Jul 20 2021
Jul 8 2021
I'm really sorry I missed that previously, even though I used sunshine for quite a while I haven't used all its features. So recently I have been going through and checking all of them and it turns out I never checked if Systemd service works. Turns out it didn't, and it expected binary in /home/build/YPKG/root/sunshine/build/sunshine.git/build/sunshine.
So if you wanted to make Sunshine run on each boot, it would fail. No other functionality was affected. Sorry I discovered it so late, after the original diff was already accepted.
Fix permissions for sunshine.conf and apps_linux.json, so the new web GUI can edit them
Jul 6 2021
Use %libdir% according to Josh's advice
I tested it on a fresh machine, and contrary to what program's readme says, you don't need to add user to input group! I even tested it a few months ago and back then it was needed but for some reason it no longer is.
So I think this package is now ready to be included, and all functions work without the need of qol-assist.
Should I create a new diff without [RFC] in the name, or can I just edit this one?
Make changes according to joebonrichie's comments
Jul 4 2021
Jul 3 2021
Clean up dependencies
Jul 2 2021
May 31 2021
May 25 2021
May 23 2021
Version 4.0.2 has just been released, a few versions ago the author removed the note it is an early development version.
I have used it for more than a year without a single problem, and author quickly makes sure it is compatible with all Gnome updates.
Apr 30 2021
Apr 24 2021
Apr 23 2021
In T9599#183848, @DataDrake wrote:I'm more than a bit skeptical that EGL would be required for this.
Mar 18 2021
Mar 8 2021
Another thing is that it and wxwidgets are still build against GTK-2, I don't know if at one point they can be build against GTK-3 or will they also need separate package.
Mar 2 2021
I don't think it has anything to do with compiling against Wayland, also you shouldn't need that env variable.
Also are you sure you are already running webrenderer and you don't also need gfx.webrender.enabled=true?
Feb 23 2021
Feb 20 2021
Feb 15 2021
I was trying to figure it out for so long, I troubleshooted every single part, and it turns out the culprit is extremely simple. Solus ships a really old Snap version of 2.39 and support of audio-playback was introduced in 2.40. So only apps that support deprecated pulseaudio interface will have sound, while newer like Teams-Insiders will not.
Check, maybe your app will still have sound, but to fix the core problem we will have to wait for T8609 to be resolved by the Core Team.
Feb 5 2021
Change .desktop name and remove Flatpak files
Feb 4 2021
Sorry for bringing it up again, but I don't feel confident enough to package and pattern it correctly, and it is needed for newest version of GOverlay for example. Could somebody more experienced look into it? It was even even already done in D4154 and probably it would work with almost no changes.
Jan 29 2021
Nov 28 2020
Just a wild guess, what GPU and drivers are you using. That could explain why newest Proton doesn't work, maybe try beta or stable instead if you are on Nvidia?
Nov 25 2020
There might be some problems with Snap after updating Pulseaudio, but I'm really not sure.
I just installed snap teams-insiders and no sound devices are visible in it. I also got an error during installation INFO snap "teams-insiders" has bad plugs or slots: audio-playback (unknown interface "audio-playback"); audio-record (unknown interface "audio-record"). Snap on my system completely lacks "audio-playback" and "audio-record" interfaces.
But I have not used it before, so it is quite likely my snap config is wrong, and it was that way before the update. Could somebody else check if audio still works in your snaps?
Nov 23 2020
Also both of my issues are now resolved, task list now works as expected and icon now will the entire screen in both orientations, and look really nice. You did a stellar job, thank you so much!