-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with xcb on a linux server #262
Comments
Mhh, I struggled with this error a lot in the past, I thought those days were finally over. I think CentOS 7 is too old to support Qt6, but I would have expected that your Rocky server would be ok. I assume you are able to get a graphical display from your server, right? I mean running |
Thanks so much for your super fast response, Marcel!
xclock comes up as "command not found" but xterm brings up a graphical
display.
Grateful again for the assistance.
Conor
…On Mon, 10 Mar 2025 at 16:08, Marcel Zwiers ***@***.***> wrote:
Mhh, I struggled with this error a lot in the past, I thought those days
were finally over. I think CentOS 7 is too old to support Qt6, but I would
have expected that your Rocky server would be ok. I assume you are able to
get a graphical display from your server, right? I mean running xclock
gives you the clock, right?
—
Reply to this email directly, view it on GitHub
<#262 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGCAJIHOM6AF7MK3AFXRQ7D2TYLPNAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGA2DOMBVGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: marcelzwiers]*marcelzwiers* left a comment
(Donders-Institute/bidscoin#262)
<#262 (comment)>
Mhh, I struggled with this error a lot in the past, I thought those days
were finally over. I think CentOS 7 is too old to support Qt6, but I would
have expected that your Rocky server would be ok. I assume you are able to
get a graphical display from your server, right? I mean running xclock
gives you the clock, right?
—
Reply to this email directly, view it on GitHub
<#262 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGCAJIHOM6AF7MK3AFXRQ7D2TYLPNAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGA2DOMBVGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I try rocky 9 in a VM tomorrow, to see if I can reproduce it
…_____________________
Sent from my phone
Op di 11 mrt 2025, 00:57 schreef Conor Owens-Walton <
***@***.***>:
Thanks so much for your super fast response, Marcel! <br> <br> xclock
comes up as "command not found" but xterm brings up a graphical
<br> display. <br> <br> Grateful again for the assistance. <br> Conor <br>
<br> On Mon, 10 Mar 2025 at 16:08, Marcel Zwiers ***@***.***> <br>
wrote: <br> <br> > Mhh, I struggled with this error a lot in the past, I
thought those days <br> > were finally over. I think CentOS 7 is too old
to support Qt6, but I would <br> > have expected that your Rocky server
would be ok. I assume you are able to <br> > get a graphical display
from your server, right? I mean running xclock <br> > gives you the
clock, right? <br> > <br> > — <br> > Reply to this email directly,
view it on GitHub <br> > <
#262 (comment)>,
<br> > or unsubscribe <br> > <
https://github.com/notifications/unsubscribe-auth/AGCAJIHOM6AF7MK3AFXRQ7D2TYLPNAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGA2DOMBVGQ>
<br> > . <br> > You are receiving this because you authored the
thread.Message ID: <br> > ***@***.***> <br> > [image:
marcelzwiers]*marcelzwiers* left a comment <br> >
(Donders-Institute/bidscoin#262) <br> > <
#262 (comment)>
<br> > <br> > Mhh, I struggled with this error a lot in the past, I
thought those days <br> > were finally over. I think CentOS 7 is too old
to support Qt6, but I would <br> > have expected that your Rocky server
would be ok. I assume you are able to <br> > get a graphical display
from your server, right? I mean running xclock <br> > gives you the
clock, right? <br> > <br> > — <br> > Reply to this email directly,
view it on GitHub <br> > <
#262 (comment)>,
<br> > or unsubscribe <br> > <
https://github.com/notifications/unsubscribe-auth/AGCAJIHOM6AF7MK3AFXRQ7D2TYLPNAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGA2DOMBVGQ>
<br> > . <br> > You are receiving this because you authored the
thread.Message ID: <br> > ***@***.***> <br> > <br>
—
Reply to this email directly, view it on GitHub
<#262 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADTUGL4YCKJZTH6KFJE73ZL2TYRGDAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGEYDQNZXHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
[image: ConorOW]*ConorOW* left a comment (Donders-Institute/bidscoin#262)
<#262 (comment)>
Thanks so much for your super fast response, Marcel! <br> <br> xclock
comes up as "command not found" but xterm brings up a graphical
<br> display. <br> <br> Grateful again for the assistance. <br> Conor <br>
<br> On Mon, 10 Mar 2025 at 16:08, Marcel Zwiers ***@***.***> <br>
wrote: <br> <br> > Mhh, I struggled with this error a lot in the past, I
thought those days <br> > were finally over. I think CentOS 7 is too old
to support Qt6, but I would <br> > have expected that your Rocky server
would be ok. I assume you are able to <br> > get a graphical display
from your server, right? I mean running xclock <br> > gives you the
clock, right? <br> > <br> > — <br> > Reply to this email directly,
view it on GitHub <br> > <
#262 (comment)>,
<br> > or unsubscribe <br> > <
https://github.com/notifications/unsubscribe-auth/AGCAJIHOM6AF7MK3AFXRQ7D2TYLPNAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGA2DOMBVGQ>
<br> > . <br> > You are receiving this because you authored the
thread.Message ID: <br> > ***@***.***> <br> > [image:
marcelzwiers]*marcelzwiers* left a comment <br> >
(Donders-Institute/bidscoin#262) <br> > <
#262 (comment)>
<br> > <br> > Mhh, I struggled with this error a lot in the past, I
thought those days <br> > were finally over. I think CentOS 7 is too old
to support Qt6, but I would <br> > have expected that your Rocky server
would be ok. I assume you are able to <br> > get a graphical display
from your server, right? I mean running xclock <br> > gives you the
clock, right? <br> > <br> > — <br> > Reply to this email directly,
view it on GitHub <br> > <
#262 (comment)>,
<br> > or unsubscribe <br> > <
https://github.com/notifications/unsubscribe-auth/AGCAJIHOM6AF7MK3AFXRQ7D2TYLPNAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGA2DOMBVGQ>
<br> > . <br> > You are receiving this because you authored the
thread.Message ID: <br> > ***@***.***> <br> > <br>
—
Reply to this email directly, view it on GitHub
<#262 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADTUGL4YCKJZTH6KFJE73ZL2TYRGDAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJSGEYDQNZXHA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I installed Rocky 9.5 (sorry, I accidentally installed the latest version from the 9 series, I think it doesn't make much difference), choosing the "workstation" pre-set. I pip installed bidscoin and was able to run the test successfully. So the problem seems to be with the way your sysadmin installed Rocky, i.e. the admin did not install the GUI libraries. If your admin needs help, any of these packages may be missing, so he/she can install: apt update && apt -y --no-install-recommends install pigz curl python3-pyqt6 build-essential libgl1 libxcb-cursor0 dbus qt6-wayland which for Rocky would be something like (I did not test this): dnf update -y && dnf install -y pigz curl python3-qt6 @development-tools mesa-libGL libxcb dbus qt6-qtwayland |
Otherwise you can always run bidscoin in an apptainer container? |
Thanks so much Marcel. We’re on a RHEL set up - but nonetheless I passed on
your helpful feedback to our sysadmin - hopefully they can find a solution.
Re an appraiser version, I’m testing bidscoin as I’m using the Nipoppy
pipeline but it’s failing at the step that uses Bbidscoin. The Nipoppy
folks recommended I tried the standalone bidscoin, which brings me here.
Will report back once my IT folks respond.
Cheers,
Conor
…On Tue, Mar 11, 2025 at 9:29 AM Marcel Zwiers ***@***.***> wrote:
Otherwise you can always run bidscoin in an apptainer container?
—
Reply to this email directly, view it on GitHub
<#262 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGCAJIDWQNNFFFI3ROV42JD2T4FPBAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJUHE4DQOBXHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: marcelzwiers]*marcelzwiers* left a comment
(Donders-Institute/bidscoin#262)
<#262 (comment)>
Otherwise you can always run bidscoin in an apptainer container?
—
Reply to this email directly, view it on GitHub
<#262 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGCAJIDWQNNFFFI3ROV42JD2T4FPBAVCNFSM6AAAAABYXMVDKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJUHE4DQOBXHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Perhaps I can solve the Nipoppy error, what was it? |
Thanks Marcel, that's really generous of you. The first Nipoppy error that pops up looks like the same as above [RUN STDOUT] qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. Here is the log file: |
I see, it's indeed a similar or the same issue. I had a look at the nipoppy page, but I couldn't find where or how they install bidscoin. I read that they use containers but there is no container definition file to be found anywhere? Without that info I can't resolve nipoppy errors, sorry |
Hi Marcel - just to update as I got it running. What I did was:
I don't understand things well enough to know why this approach worked but that was my workaround. Thanks again for your help - I really appreciate it. |
General summary:
Trying to use BIDScoin on a linux server but having issues. Installed bidscoin with pip inside a conda environment.
Error:
I am working on a
CentOS Linux release 7.8.2003
but it also happens on aRocky Linux release 9.4 (Blue Onyx)
Very grateful for any help.
Cheers,
Conor
The text was updated successfully, but these errors were encountered: