Error Messages

More
6 years 7 months ago #159184 by cmorley
Replied by cmorley on topic Error Messages
Yes that's a really old file. There was a problem with making the preference file and so some variables don't get initialized. It's fixed now.

Chris

Please Log in to join the conversation.

More
6 years 7 months ago #159185 by phillc54
Replied by phillc54 on topic Error Messages
OK, thanks. I might try to do a build on RTAI tomorrow.

Please Log in to join the conversation.

More
6 years 7 months ago #159276 by andypugh
Replied by andypugh on topic Error Messages
I think that there is a stated issue with pcspkr during boot with that kernel.

Please Log in to join the conversation.

More
6 years 7 months ago #160578 by ajsinfotech
Replied by ajsinfotech on topic Error Messages
Hi people!

I installed linuxcnc master from source on a RPi3 running Raspbian Buster. Almost all of the installation steps were taken from gnipsel.com/linuxcnc/uspace/rpi4-rt.html .

I tested almost all sim examples and ran fine. I mean whatever example inside axis, gmoccapy, gscreen, etc. But, when I try to run any example from the qtvcp_screen (eg: qtaxis) I get the following errors:

Code:
task: main loop took 0.013536 seconds task: main loop took 0.011252 seconds task: main loop took 0.013171 seconds libEGL warning: DRI2: failed to authenticate task: main loop took 0.015964 seconds task: main loop took 0.012418 seconds task: main loop took 0.010137 seconds task: main loop took 0.013779 seconds task: main loop took 0.013827 seconds task: main loop took 0.011125 seconds task: main loop took 0.010002 seconds qt5ct: using qt5ct plugin [QTvcp][CRITICAL] Canceled from Error Dialog Qtvcp encountered an error. The following information may be useful in troubleshooting: LinuxCNC Version : 2.9.0~pre0 Traceback (most recent call last): File "/home/pi/linuxcnc/bin/qtvcp", line 358, in <module> APP = QTVCP() File "/home/pi/linuxcnc/bin/qtvcp", line 80, in __init__ from qtvcp import qt_makepins, qt_makegui File "/home/pi/linuxcnc/lib/python/qtvcp/qt_makepins.py", line 23, in <module> from qtvcp.widgets.screen_options import ScreenOptions File "/home/pi/linuxcnc/lib/python/qtvcp/widgets/screen_options.py", line 26, in <module> from qtvcp.lib.notify import Notify File "/home/pi/linuxcnc/lib/python/qtvcp/lib/notify.py", line 19, in <module> sys_notify.init('notify') File "/home/pi/linuxcnc/lib/python/qtvcp/lib/sys_notify.py", line 58, in init proxy = bus.get_object(name, path) File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__ self._named_service = conn.activate_name_owner(bus_name) File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in activate_name_owner self.start_service_by_name(bus_name) File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in start_service_by_name 'su', (bus_name, flags))) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files Shutting down and cleaning up LinuxCNC...

I also installed all Qt5 tools (Qt5 Assistant, Designer, Linguist & Creator) and all run fine. So I think there is no Qt missing package, though it could be possible there will be a conflicting one.

I was googling around but no luck.
Any idea?

Thanks!

Please Log in to join the conversation.

More
6 years 7 months ago #160593 by cmorley
Replied by cmorley on topic Error Messages
Open the file /home/pi/linuxcnc/lib/python/qtvcp/lib/sys_notify.py

look for this code and add the return marked:
Code:
def init(app_name): """Initializes the DBus connection""" global APP_NAME, DBUS_IFACE APP_NAME = app_name name = "org.freedesktop.Notifications" path = "/org/freedesktop/Notifications" interface = "org.freedesktop.Notifications" mainloop = None return # <- ADD THIS HERE if DBusQtMainLoop is not None: mainloop = DBusQtMainLoop(set_as_default=True) bus = dbus.SessionBus(mainloop) proxy = bus.get_object(name, path) DBUS_IFACE = dbus.Interface(proxy, interface) if mainloop is not None: # We have a mainloop, so connect callbacks DBUS_IFACE.connect_to_signal('ActionInvoked', _onActionInvoked) DBUS_IFACE.connect_to_signal('NotificationClosed', _onNotificationClosed)
If all goes well the screen should run but you won't have desktop notifications.
If you confirm this I will add a error trap to do this automatically
I'm not sure what the actual fix would be.

Chris
Chris

Please Log in to join the conversation.

More
6 years 7 months ago #160595 by ajsinfotech
Replied by ajsinfotech on topic Error Messages
Thanks Chris!

Sorry but no luck...

Now it throws this:

Code:
No option 'overlay_sound_type' in section: 'SCREEN_OPTIONS' [QTvcp.QTVCP.WIDGETS.OVERLAY_WIDGET][DEBUG] last removed: <qtvcp.qt_makegui.VCPWindow object at 0x767c4260> (overlay_widget.py:64) No option 'CalculatorDialog_play_sound' in section: 'DIALOG_OPTIONS' No option 'CalculatorDialog_sound_type' in section: 'DIALOG_OPTIONS' No option 'MachineLogDialog_play_sound' in section: 'DIALOG_OPTIONS' No option 'MachineLogDialog_sound_type' in section: 'DIALOG_OPTIONS' No option 'catch_errors' in section: 'SCREEN_OPTIONS' No option 'desktop_notify' in section: 'SCREEN_OPTIONS' No option 'shutdown_check' in section: 'SCREEN_OPTIONS' No option 'sound_player_on' in section: 'SCREEN_OPTIONS' No section: 'MCH_MSG_OPTIONS' Adding section MCH_MSG_OPTIONS No option 'mchnMsg_speak_errors' in section: 'MCH_MSG_OPTIONS' No option 'mchnMsg_sound_type' in section: 'MCH_MSG_OPTIONS' No section: 'USR_MSG_OPTIONS' Adding section USR_MSG_OPTIONS No option 'userMsg_sound_type' in section: 'USR_MSG_OPTIONS' No option 'userMsg_use_focusOverlay' in section: 'USR_MSG_OPTIONS' No section: 'SHUTDOWN_OPTIONS' Adding section SHUTDOWN_OPTIONS No option 'shutdown_alert_sound_type' in section: 'SHUTDOWN_OPTIONS' No option 'shutdown_exit_sound_type' in section: 'SHUTDOWN_OPTIONS' No option 'shutdown_msg_title' in section: 'SHUTDOWN_OPTIONS' No option 'shutdown_msg_detail' in section: 'SHUTDOWN_OPTIONS' No section: 'NOTIFY_OPTIONS' Adding section NOTIFY_OPTIONS No option 'notify_start_title' in section: 'NOTIFY_OPTIONS' No option 'notify_start_detail' in section: 'NOTIFY_OPTIONS' No option 'notify_start_timeout' in section: 'NOTIFY_OPTIONS' [QTvcp.QTVCP.LIB.NOTIFY][WARNING] show_noficication error: (notify.py:41) Traceback (most recent call last): File "/home/pi/linuxcnc/lib/python/qtvcp/lib/notify.py", line 39, in notify n = self.show_notification(title, message, icon, timeout) File "/home/pi/linuxcnc/lib/python/qtvcp/lib/notify.py", line 82, in show_notification n.show() File "/home/pi/linuxcnc/lib/python/qtvcp/lib/sys_notify.py", line 118, in show raise UninitializedError("You must call 'notify.init()' before 'notify.show()'") UninitializedError: You must call 'notify.init()' before 'notify.show()' Shutting down and cleaning up LinuxCNC...

Please Log in to join the conversation.

More
6 years 7 months ago #160596 by cmorley
Replied by cmorley on topic Error Messages
Did the errror message dialog display or did it crash?
did you press cancel or ok? (try ok)

Chris

Please Log in to join the conversation.

More
6 years 7 months ago #160597 by cmorley
Replied by cmorley on topic Error Messages
same file:
Code:
def show(self): if DBUS_IFACE is None: return # <- ADD THIS raise UninitializedError("You must call 'notify.init()' before 'notify.show()'") """Asks the notification server to show the notification""" nid = DBUS_IFACE.Notify(APP_NAME, self.id, self.icon, self.title, self.body, self._makeActionsList(), self.hints, self.timeout, ) self.id = int(nid) NOTIFICATIONS[self.id] = self return True

Please Log in to join the conversation.

More
6 years 7 months ago #160645 by cmorley
Replied by cmorley on topic Error Messages
I pushed code to work around this problem. Hopefully that works till we figure out what the real problem is (but I don;t have a raspberrry pi so...)

Chris

Please Log in to join the conversation.

More
6 years 7 months ago #160655 by ajsinfotech
Replied by ajsinfotech on topic Error Messages

Did the errror message dialog display or did it crash?

Dialog display and then crash

did you press cancel or ok? (try ok)

Either way, ok nor cancel work

Please Log in to join the conversation.

Time to create page: 0.088 seconds
Powered by Kunena Forum