Are you by chance using a raspberry pi?


Sent from my Galaxy



-------- Original message --------
From: gene heskett <ghesk...@shentel.net>
Date: 2022-08-19 4:29 p.m. (GMT-08:00)
To: emc-developers@lists.sourceforge.net
Subject: Re: [Emc-developers] looks like I need a python3 patch

On 8/17/22 16:46, gene heskett wrote:
> On 8/17/22 15:12, Chris Morley wrote:
>> What ae you using to load qtvcp in the INI?
>> Something like this should work;
>>
>> # Embed tabs
>> EMBED_TAB_NAME= CamAlign
>> EMBED_TAB_COMMAND= halcmd loadusr -Wn qtvcp_embed qtvcp -d -c
>> qtvcp_embed  -x {XID} cam_align
>
After todays update, I seem to be getting a different, but the same end
result, error:

[QTvcp.QTVCP.QT_ISTAT][WARNING]  Embeded tab configuration -invalaid
number of TAB_NAMES vrs TAB_LOCATION - guessng default. (qt_istat.py:411)
halcmd loadusr -Wn qtvcp_embed qtvcp -d -c qtvcp_embed -x {XID} cam_align
[False]
Waiting for component 'qtvcp_embed' to become
ready................................................................................................^Ctask:
1534 cycles, min=0.000007, max=0.036086, avg=0.009952, 0 latency
excursions (> 10x expected cycle time of 0.010000s)
Traceback (most recent call last):
   File "/usr/bin/axis", line 4222, in <module>
     o.mainloop()
   File "/usr/lib/python3.7/tkinter/__init__.py", line 1283, in mainloop
.    self.tk.mainloop(n)
   File "/usr/lib/python3.7/tkinter/__init__.py", line 1700, in __call__
     def __call__(self, *args):
KeyboardInterrupt
.Shutting down and cleaning up LinuxCNC...
..Running HAL shutdown script
.hm2_5i25.0: dropping AnyIO board at 0000:01:02.0
hm2/hm2_5i25.0: unregistered
RTAPI_PCI: Unmapped 65536 bytes at 0x7f73afd72000
hm2_pci: driver unloaded
hm2: unloading
..................^C..Note: Using POSIX realtime
.gene@GO704:~$ ............^C
gene@GO704:~$ ......^C
gene@GO704:~$ ....^C
gene@GO704:~$ ...^C
gene@GO704:~$ ..^C
gene@GO704:~$ ...^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ...^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ...^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ...^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ..^C
gene@GO704:~$ ...^C
gene@GO704:~$ .....^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$ ^C
gene@GO704:~$ .^C
gene@GO704:~$
..................................................................................................................................................................................................................................[QTvcp][CRITICAL]
Aborted from Error Dialog
  Qtvcp encountered an error.  The following information may be useful
in troubleshooting:
LinuxCNC Version  : 2.9.0-pre0-7465-gc8dd11e89

Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in
activate_name_owner
     return self.get_name_owner(bus_name)
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in
get_name_owner
     's', (bus_name,), **keywords)
   File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651,
in call_blocking
     message, timeout)
dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name
'org.freedesktop.Notifications': no such name

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
   File "/usr/bin/qtvcp", line 511, in <module>
     APP = QTVCP()
   File "/usr/bin/qtvcp", line 133, in __init__
     from qtvcp import qt_makepins, qt_makegui
   File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 24,
in <module>
     from qtvcp.widgets.screen_options import ScreenOptions
   File
"/usr/lib/python3/dist-packages/qtvcp/widgets/screen_options.py", line
25, in <module>
     from qtvcp.lib.message import Message
   File "/usr/lib/python3/dist-packages/qtvcp/lib/message.py", line 5,
in <module>
     from qtvcp.widgets.dialog_widget import LcncDialog
   File "/usr/lib/python3/dist-packages/qtvcp/widgets/dialog_widget.py",
line 38, in <module>
     from qtvcp.lib.notify import Notify
   File "/usr/lib/python3/dist-packages/qtvcp/lib/notify.py", line 21,
in <module>
     sys_notify.init('notify')
   File "/usr/lib/python3/dist-packages/qtvcp/lib/sys_notify.py", line
63, in init
     proxy = bus.get_object(name, path)
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in
get_object
     follow_name_owner_changes=follow_name_owner_changes)
   File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 248, in
__init__
     self._named_service = conn.activate_name_owner(bus_name)
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 180, in
activate_name_owner
     self.start_service_by_name(bus_name)
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 278, in
start_service_by_name
     'su', (bus_name, flags)))
   File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651,
in call_blocking
     message, timeout)
   File "/usr/lib/python3/dist-packages/dbus/exceptions.py", line 45, in
__init__
     def __init__(self, *args, **kwargs):
KeyboardInterrupt

  (qtvcp:503)
'QTVCP' object has no attribute 'panel'
'QTVCP' object has no attribute 'panel'
Error in sys.excepthook:
Traceback (most recent call last):
   File "/usr/bin/qtvcp", line 504, in excepthook
     self.shutdown()
   File "/usr/bin/qtvcp", line 462, in shutdown
     self.panel.window.sync_qsettings()
AttributeError: 'QTVCP' object has no attribute 'panel'

Original exception was:
Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 175, in
activate_name_owner
     return self.get_name_owner(bus_name)
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 361, in
get_name_owner
     's', (bus_name,), **keywords)
   File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651,
in call_blocking
     message, timeout)
dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name
'org.freedesktop.Notifications': no such name

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
   File "/usr/bin/qtvcp", line 511, in <module>
     APP = QTVCP()
   File "/usr/bin/qtvcp", line 133, in __init__
     from qtvcp import qt_makepins, qt_makegui
   File "/usr/lib/python3/dist-packages/qtvcp/qt_makepins.py", line 24,
in <module>
     from qtvcp.widgets.screen_options import ScreenOptions
   File
"/usr/lib/python3/dist-packages/qtvcp/widgets/screen_options.py", line
25, in <module>
     from qtvcp.lib.message import Message
   File "/usr/lib/python3/dist-packages/qtvcp/lib/message.py", line 5,
in <module>
     from qtvcp.widgets.dialog_widget import LcncDialog
   File "/usr/lib/python3/dist-packages/qtvcp/widgets/dialog_widget.py",
line 38, in <module>
     from qtvcp.lib.notify import Notify
   File "/usr/lib/python3/dist-packages/qtvcp/lib/notify.py", line 21,
in <module>
     sys_notify.init('notify')
   File "/usr/lib/python3/dist-packages/qtvcp/lib/sys_notify.py", line
63, in init
     proxy = bus.get_object(name, path)
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 241, in
get_object
     follow_name_owner_changes=follow_name_owner_changes)
   File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 248, in
__init__
     self._named_service = conn.activate_name_owner(bus_name)
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 180, in
activate_name_owner
     self.start_service_by_name(bus_name)
   File "/usr/lib/python3/dist-packages/dbus/bus.py", line 278, in
start_service_by_name
     'su', (bus_name, flags)))
   File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651,
in call_blocking
     message, timeout)
   File "/usr/lib/python3/dist-packages/dbus/exceptions.py", line 45, in
__init__
     def __init__(self, *args, **kwargs):
KeyboardInterrupt
..<commandline>:0: waitpid failed qtvcp qtvcp_embed

<commandline>:0: qtvcp exited without becoming ready
shmctl(425992, IPC_STAT, ...): Invalid argument
shmctl(393223, IPC_STAT, ...): Invalid argument

I get a headache trying to trace thru that to see where the real error
is, so you get it all.

Thanks.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>



_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to