DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Packages and Ports

OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 3rd February 2023
nevils1 nevils1 is offline
New User
 
Join Date: Feb 2023
Posts: 3
Default qtfm - xcb error

New install of OpenBSD 7.2 (added nano)

qtfm worked a couple of times after it was added (via pkg_add).

Now, when opened, in both root and user ...

"Warning: Could not find the Qt platform plugin "xcb" in "" ((null):0, (null))
Fatal: This application failed to start because no Qt platform plugin could be initialized."

The error output recommended re-installation. Tried that. No change.

qtfm version is 6.2.1

Code:
pkg_info | less
shows qt5-5.15.8p0, qt6-6.4.2, py3-qt5-5.15.7p1 installed.

Code:
find /usr/ Path/ -type l -ls |grep -i 'xcb' shows ... 
/usr/local/bin/python3-config.YgBcLLwTNy -> python3.10-config
/usr/local/bin/platforms -> /usr/local/lib/qt5/plugins/platforms/libqxcb.so
Code:
.Xresources file changes:
xrdb -merge $HOME/.Xresources

# set your background color
xsetroot -solid dimgray

# sadly, xclock has a bug where the font selection is ignored when UTF-8
# is enabled, so we unset LANG here.
LANG= xclock -strftime "%a %e %b %Y %H:%M" &

# disable system beep
xset b off

# start cwm!
exec cwm
Any ideas, please?
Reply With Quote
  #2   (View Single Post)  
Old 3rd February 2023
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,860
Default

Hello, and welcome!

You state you are running 7.2, but it appears to me that you are running a -current snapshot rather than -release, as you have noted some -current packages installed. As I'm running -current on an amd64 laptop (last updated via snapshot yesterday, Feb 2), I installed qtfm to try to replicate your problem. I could not. It ran without error.
Quote:
qtfm worked a couple of times after it was added (via pkg_add).

Now, when opened, in both root and user ...
Something changed between when the package was added, and when it began to fail. I cannot tell you what that is.

The maintainer for the qtfm port and the resulting package is Dr. Brian Callahan, who may be able to assist you with problem source identification if you cannot determine what has changed. His email address can be obtained from $ pkg_info qtfm.
Reply With Quote
  #3   (View Single Post)  
Old 3rd February 2023
Head_on_a_Stick's Avatar
Head_on_a_Stick Head_on_a_Stick is offline
Real Name: Matthew
Bitchy Nerd Elitist
 
Join Date: Dec 2015
Location: London
Posts: 400
Default

More information can be gathered by applying the debug parameter when launching the application:
Code:
QT_DEBUG_PLUGINS=1 qtfm
I don't use Qt myself so I won't be much help directly though, sorry.
Reply With Quote
  #4   (View Single Post)  
Old 3rd February 2023
nevils1 nevils1 is offline
New User
 
Join Date: Feb 2023
Posts: 3
Default

I forgot that I had run
Quote:
sysupdate - s and pkg_add -uU snap
to try to fix the problem.

I'll reinstall so I know exactly what is what.

OK re. the maintainer - I'll save that info in case I need it even after a reinstall.
Reply With Quote
  #5   (View Single Post)  
Old 3rd February 2023
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,036
Default

The problem is that you did a sysupdate to snap. So you don't have 7.2 anymore. You are now running a snapshot release of what in the future will become OpenBSD 7.3 release.

You also did a upgrade of your packages, but because package building takes some time, it is possible that your upgraded snapshot packages have been built on an slightly older snapshot version. Sometimes this works, sometimes it does not.

I would recommend to reinstall 7.2 so you can start with a clean slate
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
  #6   (View Single Post)  
Old 4th February 2023
nevils1 nevils1 is offline
New User
 
Join Date: Feb 2023
Posts: 3
Default

Clean install & same failure.

(Emailed the maintainer, no reply.)

Quote:
Edit:
New clean install.
Allowed xenodm to handle x-windows.
pkg_add -v nano
pkd_add -v qtfm

qtfm from root worked fine.


Created new user via adduser
Added new user to staff and wheel groups in /etc/group
wheel:*:0:root,user
staff:*:20:staff,user

Edited /etc/doas.conf
permit nopass keepenv :user
permit nopass keepenv :wheel
permit nopass keepenv root as root

su user
"Error: "ksh: Cannot determine current working directory" (???)
whoami = user

qtfm
"Warning: Could not connect to the display ((null):0, (null))
Info: Could not load the Qt platform plugin "xcb" in "" even though it was found. ((null):0, (null))
Fatal: This application failed to start because no Qt platform plugin could be initialized."

su back to root
qtfm still worked fine.

su - i user
qtfm
"Warning: Could not connect to the display ((null):0, (null))
Info: Could not load the Qt platform plugin "xcb" in "" even though it was found. ((null):0, (null))
Fatal: This application failed to start because no Qt platform plugin could be initialized."

su back to root
"Warning: Could not connect to the display ((null):0, (null))
Info: Could not load the Qt platform plugin "xcb" in "" even though it was found. ((null):0, (null))
Fatal: This application failed to start because no Qt platform plugin could be initialized."

su -i for user broke qtfm for root, why?
Edit 2 This looks similar ... https://github.com/ksh93/ksh/issues/141

Edit 3: Rebuilt /etc/doas.conf using vim rather than nano. Opened then saved /etc/group via vim as well. (Based on guidance that nano can cause a rare problem.)
Logged in as user, rather than root, and qtfm worked fine. su to root and the error occurred with root. Exit back to user and qtfm works OK. Very weird ...

Edit 4: Mucked around a bit more and have things as stable as I can get them. Moving on to server setup.

Last edited by nevils1; 8th February 2023 at 05:21 PM. Reason: added a lot of information
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Eggdrop tcl error - Error: error reading "sock7" koustab OpenBSD Packages and Ports 1 22nd August 2021 11:34 PM
6.8 drm error leave0 OpenBSD General 2 2nd April 2021 04:23 AM
An error? bsdun OpenBSD General 1 16th July 2020 08:50 PM
error: [drm:pid60567:intel_uncore_check_errors] *ERROR* Unclaimed register before int livestradamus OpenBSD Installation and Upgrading 11 4th November 2017 12:35 PM
shc unistd.h:239: error: syntax error before '&' token laraaj OpenBSD General 3 11th September 2010 07:21 AM


All times are GMT. The time now is 11:12 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2023, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick